[Bug 1830770] Please test proposed package

[Corey Bryant]

Hello Paul, or anyone else affected,

Accepted nova into ocata-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:ocata-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-ocata-needed to verification-ocata-done. If it does
not fix the bug for you, please add a comment stating that, and change
the tag to verification-ocata-failed. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

** Changed in: cloud-archive/ocata
       Status: In Progress => Fix Committed

** Tags added: verification-ocata-needed

-- 
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/1830770

Title:
  UCA python-nova requires UCA python-oslo.middleware but doesn't
  specify in dependency

Status in Ubuntu Cloud Archive:
  In Progress
Status in Ubuntu Cloud Archive ocata series:
  Fix Committed

Bug description:
  This occurred specifically on python-nova 2:15.1.5-0ubuntu1~cloud3,
  pulled from http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-
  updates/ocata/main amd64 Packages.

  Upon attempting to deploy some nova compute nodes, we ended up with
  several nodes which would not start up properly.  /var/log/syslog had
  a traceback which seems to point at python-nova:

  May 27 16:49:50 <HOSTNAME> systemd[1]: Starting OpenStack Compute...
  May 27 16:49:50 <HOSTNAME> systemd[1]: Started OpenStack Compute.
  May 27 16:49:51 <HOSTNAME> nova-compute[20093]: Traceback (most recent call last):
  May 27 16:49:51 <HOSTNAME> nova-compute[20093]:   File "/usr/bin/nova-compute", line 10, in <module>
  May 27 16:49:51 <HOSTNAME> nova-compute[20093]:     sys.exit(main())
  May 27 16:49:51 <HOSTNAME> nova-compute[20093]:   File "/usr/lib/python2.7/dist-packages/nova/cmd/compute.py", line 42, in main
  May 27 16:49:51 <HOSTNAME> nova-compute[20093]:     config.parse_args(sys.argv)
  May 27 16:49:51 <HOSTNAME> nova-compute[20093]:   File "/usr/lib/python2.7/dist-packages/nova/config.py", line 47, in parse_args
  May 27 16:49:51 <HOSTNAME> nova-compute[20093]:     config.set_middleware_defaults()
  May 27 16:49:51 <HOSTNAME> nova-compute[20093]:   File "/usr/lib/python2.7/dist-packages/nova/common/config.py", line 20, in set_middleware_defaults
  May 27 16:49:51 <HOSTNAME> nova-compute[20093]:     cors.set_defaults(
  May 27 16:49:51 <HOSTNAME> nova-compute[20093]: AttributeError: 'module' object has no attribute 'set_defaults'
  May 27 16:49:51 <HOSTNAME> systemd[1]: nova-compute.service: Main process exited, code=exited, status=1/FAILURE
  May 27 16:49:51 <HOSTNAME> systemd[1]: nova-compute.service: Unit entered failed state.
  May 27 16:49:51 <HOSTNAME> systemd[1]: nova-compute.service: Failed with result 'exit-code'.

  Upon deeper investigation, it appears that the system is running
  python-oslo.middleware version 3.8.0-2ubuntu1, rather than the UCA
  version 3.23.1-0ubuntu1.1~cloud0.  As such, it's missing the
  set_defaults() function which is available in the UCA version.

  The reason we ended up in this state: ubuntu-cloud-keyring was
  installed after python-nova, thus originally python-nova and python-
  oslo.middleware were both pulled from the distro.  However, a package
  installed after the cloud keychain was available required an upgrade
  of python-nova.  However, since the UCA python-nova simply requires
  "python-oslo.middleware (>= 3.0.0)", no update to python-
  oslo.middleware was pulled.

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