← Back to team overview

openstack team mailing list archive

Re: server_name column missing in Instances table of Nova database in Grizzly release


Also, If I have upgraded the setup from Folsom to Grizzly, then why is the
updated Nova-Compute node using the old column-names. Shouldn't it be that
it should use the new column_names?

On Mon, May 20, 2013 at 8:49 PM, Rahul Sharma <rahulsharmaait@xxxxxxxxx>wrote:

> Hi All,
> I was running Openstack Multinode setup with Folsom release. I upgraded it
> to Grizzly. Due to some reasons I had to format the Controller Node. Now I
> have a newly deployed Grizzly controller node and upgraded Compute and
> Network nodes. I am facing an issue with this setup which is described
> below:-
> If I check the *INSTANCES* table in *NOVA* database of Folsom release, I
> could see that it contains a column "*server_name*" which is now *not
> present* in the Grizzly release. Is there a specific reason why this
> column is removed from the database? I am facing an issue that the upgraded
> Compute node's code is looking for server_name column which is not present
> in my Nova database since the node is fresh installed.
> Is there a way to completely remove the installed nova-packages for Folsom
> release from the node and install the latest Grizzly ones without format?
> Most of the times I try apt-get remove <package-name>, I end up messing up
> with the setup and libraries.
> Your feedback for this issue would be really helpful.
> Thanks and Regards
> Rahul Sharma