I like that idea. If there is no data in the db we could pick the xen version (which i think is more useful)
Vish
On Jan 25, 2012, at 8:24 AM, Thierry Carrez wrote:
> Maybe when there is no data yet, we could avoid the difficult question,
> so that it only bites old users.
>
> --
> You received this bug notification because you are subscribed to
> OpenStack Compute (nova).
> https://bugs.launchpad.net/bugs/921294
>
> Title:
> Migration 074 assumes connection_type is defined locally during
> migrations
>
> Status in OpenStack Compute (Nova):
> Incomplete
>
> Bug description:
> The recently added migration 074_change_flavor_local_gb.py references
> the config flag connection_type in its upgrade. Since this flag only
> applies to nodes running nova-compute services, it may not be set on
> the node where database migrations are actually run, resulting in
> exception.Error("Need connection_type specified to run migration")
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nova/+bug/921294/+subscriptions
I like that idea. If there is no data in the db we could pick the xen version (which i think is more useful)
Vish
On Jan 25, 2012, at 8:24 AM, Thierry Carrez wrote:
> Maybe when there is no data yet, we could avoid the difficult question, /bugs.launchpad .net/bugs/ 921294 flavor_ local_gb. py references Error(" Need connection_type specified to run migration") /bugs.launchpad .net/nova/ +bug/921294/ +subscriptions
> so that it only bites old users.
>
> --
> You received this bug notification because you are subscribed to
> OpenStack Compute (nova).
> https:/
>
> Title:
> Migration 074 assumes connection_type is defined locally during
> migrations
>
> Status in OpenStack Compute (Nova):
> Incomplete
>
> Bug description:
> The recently added migration 074_change_
> the config flag connection_type in its upgrade. Since this flag only
> applies to nodes running nova-compute services, it may not be set on
> the node where database migrations are actually run, resulting in
> exception.
>
> To manage notifications about this bug go to:
> https:/