vivid-kilo FATAL ERROR: Could not determine OpenStack codename for version 2.2.2

Bug #1423680 reported by Ryan Beisner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
swift-proxy (Juju Charms Collection)
Fix Released
Undecided
Unassigned

Bug Description

For vivid-kilo deployments, "FATAL ERROR: Could not determine OpenStack codename for version 2.2.2." A charmhelper sync should resolve.

# deployer
17:20:22 2015-02-19 17:20:22 [DEBUG] deployer.env: Delta unit: nova-compute/2 change:installed
17:20:27 2015-02-19 17:20:27 [DEBUG] deployer.env: Delta unit: swift-proxy/0 change:error
17:20:27 2015-02-19 17:20:27 [ERROR] deployer.env: The following units had errors:
17:20:27 unit: swift-proxy/0: machine: 19 agent-state: error details: hook failed: "config-changed"

# unit
2015-02-19 17:20:27 INFO worker.uniter.jujuc server.go:110 running hook tool "juju-log" ["-l" "ERROR" "FATAL ERROR: Could not determine OpenStack codename for version 2.2.2"]
2015-02-19 17:20:27 DEBUG worker.uniter.jujuc server.go:111 hook context id "swift-proxy/0-config-changed-436590104649555810"; dir "/var/lib/juju/agents/unit-swift-proxy-0/charm"
2015-02-19 17:20:27 ERROR unit.swift-proxy/0.juju-log cmd.go:247 FATAL ERROR: Could not determine OpenStack codename for version 2.2.2
2015-02-19 17:20:27 INFO juju.worker.uniter.context context.go:304 handling reboot
2015-02-19 17:20:27 ERROR juju.worker.uniter uniter.go:608 hook "config-changed" failed: exit status 1
2015-02-19 17:20:27 DEBUG juju.worker.uniter modes.go:430 ModeConfigChanged exiting
2015-02-19 17:20:27 INFO juju.worker.uniter modes.go:428 ModeHookError starting
2015-02-19 17:20:27 DEBUG juju.worker.uniter.filter filter.go:498 want resolved event
2015-02-19 17:20:27 DEBUG juju.worker.uniter.filter filter.go:492 want forced upgrade true
2015-02-19 17:20:27 DEBUG juju.worker.uniter.filter filter.go:614 no new charm event

Related branches

Changed in swift-proxy (Juju Charms Collection):
status: New → Fix Committed
Changed in swift-proxy (Juju Charms Collection):
milestone: none → 15.04
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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