Unfortunately this doesn't seem to be doing it for me.
Working from Ubuntu 12.04 originally installed with Essex and
incrementally upgraded using cloud archive. The Grizzly - Havana
transition choked, then I discovered your patch and like Blair copied
it in place. After a bit of thrashing found
Hi Joshua,
Thanks for the quick fix, I appreciate it.
I took your fixed 185_rename_unique_constraints.py, copied it into
/usr/share/pyshared/nova/db/sqlalchemy/migrate_repo/versions/185_rename_unique_constraints.py,
restored MySQL back to 1 week ago and reran all the migrations and
Hi Blair,
No trouble, glad I could help. I'll be working backporting this as is
appropriate.
Cheers,
Josh
Rackspace Australia
On 10/30/13 5:06 PM, Blair Zajac wrote:
Hi Joshua,
Thanks for the quick fix, I appreciate it.
I took your fixed 185_rename_unique_constraints.py, copied it into
Hi Blair,
So from your dump a few weeks ago you have both fkeys
'instance_info_caches_ibfk_1' and
'instance_info_caches_instance_uuid_fkey'? Yet your original bug report
only lists the former key. Was the original bug report after attempting
to run migration 185 and failing (ie, no
On 10/29/2013 04:04 PM, Joshua Hesketh wrote:
Hi Blair,
So from your dump a few weeks ago you have both fkeys
'instance_info_caches_ibfk_1' and
'instance_info_caches_instance_uuid_fkey'?
Hi Joshua,
Yes, that's correct.
Yet your original bug report
only lists the former key. Was the
Hi Blair,
Thanks for the clarifications, that helps.
At the moment I'm trying to determine how you ended up with both fkeys
so I can ensure the problem is properly fixed. What version did you
first start deploying openstack from? Essex? and have you been just
upgrading with releases or RC's
On 10/29/2013 05:16 PM, Joshua Hesketh wrote:
Hi Blair,
Thanks for the clarifications, that helps.
At the moment I'm trying to determine how you ended up with both fkeys
so I can ensure the problem is properly fixed. What version did you
first start deploying openstack from? Essex? and have
Hi Blair,
I have proposed a new fix which I believe should work for you. However
I've been unable to determine where exactly the duplicate keys were
introduced. Looking up what versions were available in Ubuntu from 12.10
you have been running since Folsom. This means you did not have the
On 10/27/13 4:39 PM, Michael Still wrote:
These sound like bugs worth filing...
I opened https://bugs.launchpad.net/nova/+bug/1245502
Blair
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to :
Hello,
I was running Ubuntu 13.04 and upgraded tonight to 13.10. I was running
the Ubuntu Precise 1:2013.1.3-0ubuntu1.1 on 13.04 and am now on 13.10's
provided 1:2013.2~rc2-0ubuntu1.
After getting the box up, migrating the nova database failed with the
below error. I am using MySQL.
Can you run this against your nova mysql database and let us know the result?
show create table instance_info_caches \G
Thanks,
Michael
On Sun, Oct 27, 2013 at 7:58 PM, Blair Zajac bl...@orcaware.com wrote:
Hello,
I was running Ubuntu 13.04 and upgraded tonight to 13.10. I was running the
...@gmail.com] On Behalf Of Michael
Still
Sent: October-27-13 7:39 PM
To: David Hill
Cc: Blair Zajac; openstack@lists.openstack.org
Subject: Re: [Openstack] Grizzly - Havana nova upgrade failure: Cannot drop
index 'instance_uuid'
These sound like bugs worth filing...
Is it too late to get a list of tables
12 matches
Mail list logo
