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 doe
Tested and made sure OpenStack is now coming up using the latest
released charms from the charmstore.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
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://
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
+
** Changed in: openstack (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576412
Title:
package does not use released charms
To manage notification
** Description changed:
- openstack package should use the released charms from the charmstore
- rather than openstack-charmers-next
+ [Impact]
+ All users wanting to deploy a production grade OpenStack via Juju bundles.
+
+ [Test Case]
+ This basically uses the vetted 16.04 charms from charmstor