← Back to team overview

registry team mailing list archive

[Bug 654025] [NEW] nova-manage project zip and nova-manage vpn list broken by change in DB semantics when networks are missing

 

Public bug reported:

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.

** Affects: nova
     Importance: Undecided
         Status: New

** Summary changed:

- nova-manage project zip broken by change in DB semantics when networks are missing
+ nova-manage project zip and nova-manage vpn list broken by change in DB semantics when networks are missing

** Description changed:

  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.

-- 
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.



Follow ups

References