package does not use released charms

[Adam Stokes]

[Impact]
All users wanting to deploy a production grade OpenStack via Juju bundles.

[Test Case]
This basically uses the vetted 16.04 charms from charmstore so just running 'conjure-up openstack' and seeing the services start and booting an instance is enough.

[Regression Potential]
This would would actually reduce regression risks as we were pulling from the charmers next branch where at any given time could break.

[Additional Info]
openstack package should use the released charms from the charmstore rather than openstack-charmers-next

[Martin Pitt (pitti)]

The debian/rules diff looks weird, and the changelog does not explicitly mention it:

 %:
- dh $@
+ dh $@ --with systemd
+
+override_dh_installinit:
+ dh_systemd_enable -popenstack --name=openstack openstack.service
+ dh_installinit -popenstack --no-start --noscripts
+ dh_systemd_start -popenstack --no-restart-on-upgrade
+
+override_dh_systemd_start:
+ echo "Not running dh_systemd_start"

This second-guesses debhelper's automatic ordering of which dh_* commands to call at what time (although this order here is correct). But it's still bad/brittle/confusing style to have an explicit override to disable dh_systemd_start and then call it in a *different* rule. Also, like that dh_systemd_enable will be called twice, once in dh_installinit and another one through the auto-generated one via "dh --with systemd". Finally, the dh_installinit call looks like a no-op, what does that do?

What does not work if you drop both overrides and simply do "dh $@ --with systemd"?

[Martin Pitt (pitti)]

Hello Adam, or anyone else affected,

Accepted openstack into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openstack/1.0.7.16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. 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-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-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!

[Adam Stokes (adam-stokes)]

Tested and made sure OpenStack is now coming up using the latest released charms from the charmstore.

[Launchpad Janitor (janitor)]

This bug was fixed in the package openstack - 1.0.7.16.04.1

---------------
openstack (1.0.7.16.04.1) xenial-proposed; urgency=medium

  * Fixes post processing neutron fails to configure network (LP: #1575800)
  * Fixes post processing fails to add ssh keypair (LP: #1575906)
  * Fixes package does not use released charms (LP: #1576412)

 -- Michael McCracken <email address hidden> Fri, 22 Apr 2016 14:50:00 -0700

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for openstack has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.