registry team mailing list archive

[Ewan Mellor <654025@xxxxxxxxxxxxxxxxxx>]

Whether or not we _should_ be in this situation, debugging it is a lot easier
if your tools don't blow up in your face.

Some form of schema upgrade tool is likely to be necessary, but my experience
is that the best you can hope for is if those are kept up-to-date from
release to release.  Within a given development period, however, the schema
will be in rapid flux, and no-one will be able to keep the tool perfectly
up-to-date with all possible "before" and "after" schemas.  We will need
developers to be able to dig themselves out of a hole, and that means tools
that cope when values are missing.

Ewan.

On Mon, Oct 04, 2010 at 07:45:39AM +0100, Soren Hansen wrote:

> On 03-10-2010 13:45, Ewan Mellor wrote:
> > The code in auth.manager used to cope with this situation, but it looks
> > like the DB layer semantics have changed so that it raises
> > exception.NotFound now rather than returning None.
> > 
> > A similar problem affects nova-manage vpn list.
> 
> I'm not completely convinced that this is a nova-manage problem. Auth
> manager unconditionally creates a network for a project, so I think the
> /real/ problem here is that we have gotten into a situation where
> projects added before this change was made still don't have a network
> assigned, so it's more a schema change that hasn't been handled gracefully.
> 
> Perhaps we should add a "nova-manage upgrade" command that can handle
> this sort of thing?
> 
>   status incomplete
> 
> -- 
> Soren Hansen
> Ubuntu Developer    http://www.ubuntu.com/
> OpenStack Developer http://www.openstack.org/
> 
> 
> ** Changed in: nova
>        Status: Fix Committed => Incomplete
> 
> -- 
> nova-manage project zip and nova-manage vpn list broken by change in DB semantics when networks are missing
> https://bugs.launchpad.net/bugs/654025
> You received this bug notification because you are a direct subscriber
> of the bug.
> 
> Status in OpenStack Compute (Nova): Incomplete
> 
> Bug description:
> If a project does not have a network assigned, nova-manage project zip fails like this:
> 
> Traceback (most recent call last):
>   File "/home/emellor/openstack/nova/xenapi/bin/nova-manage", line 463, in <module>
>     main()
>   File "/home/emellor/openstack/nova/xenapi/bin/nova-manage", line 454, in main
>     fn(*argv)
>   File "/home/emellor/openstack/nova/xenapi/bin/nova-manage", line 347, in zipfile
>     zip_file = self.manager.get_credentials(user_id, project_id)
>   File "/home/emellor/openstack/nova/xenapi/nova/auth/manager.py", line 662, in get_credentials
>     (vpn_ip, vpn_port) = self.get_project_vpn_data(project)
>   File "/home/emellor/openstack/nova/xenapi/nova/auth/manager.py", line 558, in get_project_vpn_data
>     Project.safe_id(project))
>   File "/home/emellor/openstack/nova/xenapi/nova/db/api.py", line 440, in project_get_network
>     return IMPL.project_get_network(context, project_id)
>   File "/home/emellor/openstack/nova/xenapi/nova/db/sqlalchemy/api.py", line 103, in wrapper
>     return f(*args, **kwargs)
>   File "/home/emellor/openstack/nova/xenapi/nova/db/sqlalchemy/api.py", line 980, in project_get_network
>     raise exception.NotFound('No network for project: %s' % project_id)
> nova.exception.NotFound: No network for project: ewan
> 
> The code in auth.manager used to cope with this situation, but it looks like the DB layer semantics have changed so that it raises exception.NotFound now rather than returning None.
> 
> A similar problem affects nova-manage vpn list.
> 
> 
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/nova/+bug/654025/+subscribe

-- 
nova-manage project zip and nova-manage vpn list broken by change in DB semantics when networks are missing
https://bugs.launchpad.net/bugs/654025
You received this bug notification because you are a member of Registry
Administrators, which is subscribed to OpenStack.