[SRU] Juno nova-* ImportError: No module named rootwrap.cmd (when used without neutron)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Invalid
|
Undecided
|
Unassigned | ||
Juno |
Fix Released
|
Critical
|
Corey Bryant | ||
nova-compute (Juju Charms Collection) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Following Juno 2014.2.4 and related SRUs:
https:/
https:/
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-
- nova-compute
- (This list may not be complete, still reviewing.)
nova-api.log:
http://
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/
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/
2015-12-08 22:25:05.002 17818 TRACE nova server = service.
2015-12-08 22:25:05.002 17818 TRACE nova File "/usr/lib/
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/
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/
2015-12-08 22:25:05.002 17818 TRACE nova self.network_
2015-12-08 22:25:05.002 17818 TRACE nova File "/usr/lib/
2015-12-08 22:25:05.002 17818 TRACE nova iptables_
2015-12-08 22:25:05.002 17818 TRACE nova File "/usr/lib/
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/
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/
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/
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/
2015-12-08 22:25:05.002 17818 TRACE nova return processutils.
2015-12-08 22:25:05.002 17818 TRACE nova File "/usr/lib/
2015-12-08 22:25:05.002 17818 TRACE nova cmd=sanitized_cmd)
2015-12-08 22:25:05.002 17818 TRACE nova ProcessExecutio
2015-12-08 22:25:05.002 17818 TRACE nova Command: sudo nova-rootwrap /etc/nova/
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.
2015-12-08 22:26:04.259 20741 WARNING nova.compute.
A full /var/log tarball is attached from nova-compute/0 in the amulet test topology.
summary: |
- nova-* fails with ImportError: No module named rootwrap.cmd, sans - neutron + Juno nova-* ImportError: No module named rootwrap.cmd (when used without + neutron) |
summary: |
- 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 |
status: | Incomplete → Invalid |
Changed in cloud-archive: | |
status: | New → In Progress |
status: | In Progress → Invalid |
This appears to be an issue with the recent change to run dh_python2 with --no-guessing-deps. d/control files in various packages are out-of-date with respect to dependencies specified in the Depends section and this is exposed when dependencies aren't guessed by dh_python2. Unfortunately we need to use --no-guessing-deps due to upstream changes in 2014.2.4 to requirements.txt files where logic changes were causing package install failures do to dh_python2 not being able to handle logic such as !=.
The following packages need to be updated to bring the Depends section inline with upstream: cinder, glance, horizon, and keystone.