Amulet/openstack service check methods need series and init system awareness for testing Vivid and later.
I'm using the heat amulet test writing effort to also update charm-helpers to resolve this Vivid issue, and other general Wily prep.
[1] validate_services() http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/amulet/utils.py
[2] _get_openstack_release_string() http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/openstack/amulet/deployment.py
This affects all openstack charm amulet tests, keystone as an example: Previous approach presumes presence of upstart: http://paste.ubuntu.com/11542366/ http://bazaar.launchpad.net/~openstack-charmers/charms/trusty/keystone/next/view/head:/tests/basic_deployment.py
Amulet/openstack service check methods need series and init system awareness for testing Vivid and later.
I'm using the heat amulet test writing effort to also update charm-helpers to resolve this Vivid issue, and other general Wily prep.
[1] validate_services() bazaar. launchpad. net/~charm- helpers/ charm-helpers/ devel/view/ head:/charmhelp ers/contrib/ amulet/ utils.py
http://
[2] _get_openstack_ release_ string( ) bazaar. launchpad. net/~charm- helpers/ charm-helpers/ devel/view/ head:/charmhelp ers/contrib/ openstack/ amulet/ deployment. py
http://
This affects all openstack charm amulet tests, keystone as an example: paste.ubuntu. com/11542366/ bazaar. launchpad. net/~openstack- charmers/ charms/ trusty/ keystone/ next/view/ head:/tests/ basic_deploymen t.py
Previous approach presumes presence of upstart:
http://
http://