amulet/openstack service checks need init system awareness

Bug #1461535 reported by Ryan Beisner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Charm Helpers
Undecided
Unassigned

Bug Description

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.

Affected charm-helper pieces are:

[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

Once resolved and landed, other openstack charms can also have vivid/wily++ amulet tests.

Related branches

Ryan Beisner (1chb1n)
description: updated
Ryan Beisner (1chb1n)
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers