OpenStack Charm Testing

essex bundle needed for testing as it is in-support for +3yrs

Bug #1423579 reported by Ryan Beisner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Charm Testing
Won't Fix
High
Ryan Beisner

Bug Description

A precise-essex bundle is needed for testing as it is in-support for ~+3yrs

Some basic charm work may be necessary (keystone for sure). We should also periodically deploy-test precise-essex to ensure stack functionality for the security team's essex patch testing.

# keystone essex log template issue
https://bugs.launchpad.net/charms/+source/keystone/+bug/1423513

# keystone essex keystoneclient.apiclient.exceptions issue
https://code.launchpad.net/~hopem/charms/trusty/keystone/fix-legacy-import-error/+merge/250315

# WIP essex bundle:
http://bazaar.launchpad.net/~1chb1n/openstack-charm-testing/essex-revival/view/head:/bundles-legacy/essex.yaml

See original description
Ryan Beisner (1chb1n)
Changed in openstack-charm-testing:
assignee: nobody → Ryan Beisner (1chb1n)
importance: Undecided → High
description: updated
Ryan Beisner (1chb1n)
description: updated
description: updated
Ryan Beisner (1chb1n)
description: updated
Revision history for this message
Ryan Beisner (1chb1n) wrote :

Current dev bundle (new location):
http://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/bundles/legacy/essex.yaml

The bundle deploys, but there are still some nova API issues. Currently assessing that.

Revision history for this message
Ryan Beisner (1chb1n) wrote :

I found that the nova-api-* services fail to start on the nova-cloud-controller unit, as haproxy is already bound to the attempted TCP port. Once manually worked around that, another issue surfaced on n-c-c:

BadRequest: Malformed request url (HTTP 400) (Request-ID: req-9d773c81-75f0-4dec-ba6e-b11f015ec54f)
ERROR: Malformed request url (HTTP 400) (Request-ID: req-9d773c81-75f0-4dec-ba6e-b11f015ec54f)

More detail @ http://paste.ubuntu.com/10510592/

It appears to be non-trivial to deploy a working Essex cloud from charms at this point, but I'll confer with the rest of the os charm dev team to determine how deep the essex-functionality rabbit hole could go.

Ryan Beisner (1chb1n)
Changed in openstack-charm-testing:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.