[Bug 1524177] Re: [SRU] Juno nova-* ImportError: No module named rootwrap.cmd (when used without neutron)

Corey Bryant corey.bryant at canonical.com
Wed Dec 9 17:31:09 UTC 2015


** Summary changed:

- Juno nova-* ImportError: No module named rootwrap.cmd (when used without neutron)
+ [SRU] Juno nova-* ImportError: No module named rootwrap.cmd (when used without neutron)

** Changed in: nova-compute (Juju Charms Collection)
       Status: New => Incomplete

** Changed in: nova-compute (Juju Charms Collection)
       Status: Incomplete => Invalid

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

** Changed in: cloud-archive
       Status: New => In Progress

** Also affects: cloud-archive/juno
   Importance: Undecided
       Status: New

** Changed in: cloud-archive
       Status: In Progress => Invalid

** Changed in: cloud-archive/juno
       Status: New => In Progress

** Changed in: cloud-archive/juno
   Importance: Undecided => Critical

** Changed in: cloud-archive/juno
     Assignee: (unassigned) => Corey Bryant (corey.bryant)

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1524177

Title:
  [SRU] Juno nova-* ImportError: No module named rootwrap.cmd (when used
  without neutron)

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive juno series:
  In Progress
Status in nova-compute package in Juju Charms Collection:
  Invalid

Bug description:
  Following Juno 2014.2.4 and related SRUs:
  https://bugs.launchpad.net/cloud-archive/+bug/1518323
  https://bugs.launchpad.net/nova/+bug/1353939

  When neutron is not related, nova-* services fail on nova-compute
  units with ImportError: No module named rootwrap.cmd

  juno nova-*, from the perspective of our existing amulet tests, is
  definitely broken following recent Juno SRUs in the cloud archive.
  I've re-confirmed that the amulet tests were passing for nova-
  compute/next prior to these updates.

  juno nova-*, from the perspective of our full deployments, seems to be
  fine following the same.  These full deploys are the tests, along with
  tempest, which are exercised during the staging and proposed period.

  To differentiate:  the amulet test has a minimal topology which
  doesn't include the neutron-*, whereas the full deploy does.

  Granted, nova-network was to-be, then not-to-be deprecated in Juno.
  Ultimately, as I understand it, upstream decided to hold that
  deprecation until certain feature parity was met in neutron.  It may
  exist, but I've not located an indicator of anyone actually pulling
  the nova-network deprecation trigger on Juno.

  This issue causes amulet tests to fail for the following openstack-charms, where those tests include nova without neutron:
   - ceilometer
   - heat
   - nova-cloud-controller
   - nova-compute
   - (This list may not be complete, still reviewing.)

  nova-api.log:
  http://paste.ubuntu.com/13846932/

  2015-12-08 22:25:05.002 17818 TRACE nova Traceback (most recent call last):
  2015-12-08 22:25:05.002 17818 TRACE nova   File "/usr/bin/nova-api", line 10, in <module>
  2015-12-08 22:25:05.002 17818 TRACE nova     sys.exit(main())
  2015-12-08 22:25:05.002 17818 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/cmd/api.py", line 55, in main
  2015-12-08 22:25:05.002 17818 TRACE nova     server = service.WSGIService(api, use_ssl=should_use_ssl)
  2015-12-08 22:25:05.002 17818 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/service.py", line 331, in __init__
  2015-12-08 22:25:05.002 17818 TRACE nova     self.manager = self._get_manager()
  2015-12-08 22:25:05.002 17818 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/service.py", line 383, in _get_manager
  2015-12-08 22:25:05.002 17818 TRACE nova     return manager_class()
  2015-12-08 22:25:05.002 17818 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/api/manager.py", line 30, in __init__
  2015-12-08 22:25:05.002 17818 TRACE nova     self.network_driver.metadata_accept()
  2015-12-08 22:25:05.002 17818 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/network/linux_net.py", line 667, in metadata_accept
  2015-12-08 22:25:05.002 17818 TRACE nova     iptables_manager.apply()
  2015-12-08 22:25:05.002 17818 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/network/linux_net.py", line 435, in apply
  2015-12-08 22:25:05.002 17818 TRACE nova     self._apply()
  2015-12-08 22:25:05.002 17818 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/openstack/common/lockutils.py", line 272, in inner
  2015-12-08 22:25:05.002 17818 TRACE nova     return f(*args, **kwargs)
  2015-12-08 22:25:05.002 17818 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/network/linux_net.py", line 455, in _apply
  2015-12-08 22:25:05.002 17818 TRACE nova     attempts=5)
  2015-12-08 22:25:05.002 17818 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/network/linux_net.py", line 1229, in _execute
  2015-12-08 22:25:05.002 17818 TRACE nova     return utils.execute(*cmd, **kwargs)
  2015-12-08 22:25:05.002 17818 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/utils.py", line 187, in execute
  2015-12-08 22:25:05.002 17818 TRACE nova     return processutils.execute(*cmd, **kwargs)
  2015-12-08 22:25:05.002 17818 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/openstack/common/processutils.py", line 222, in execute
  2015-12-08 22:25:05.002 17818 TRACE nova     cmd=sanitized_cmd)
  2015-12-08 22:25:05.002 17818 TRACE nova ProcessExecutionError: Unexpected error while running command.
  2015-12-08 22:25:05.002 17818 TRACE nova Command: sudo nova-rootwrap /etc/nova/rootwrap.conf iptables-save -c
  2015-12-08 22:25:05.002 17818 TRACE nova Exit code: 1

  nova-compute log:
  2015-12-08 22:26:03.933 20741 WARNING nova.virt.libvirt.driver [req-a54c8cbd-c24e-4ccf-ad33-d865bf753a82 None] Cannot update service status on host: juju-osci-sv07-machine-5,since it is not registered.
  2015-12-08 22:26:04.259 20741 WARNING nova.compute.resource_tracker [-] No compute node record for juju-osci-sv07-machine-5:juju-osci-sv07-machine-5.openstacklocal

  A full /var/log tarball is attached from nova-compute/0 in the amulet
  test topology.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1524177/+subscriptions



More information about the Ubuntu-openstack-bugs mailing list