Juju Charms Collection
nova-compute-vmware package

failed neutron configuration - unit: nova-vmware/0: machine: 1 agent-state: error details: hook failed: cloud-compute-relation-changed

Bug #1574657 reported by Larry Michel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nova-compute-vmware (Juju Charms Collection)
Fix Released
Critical
Larry Michel

Bug Description

With removal of neutron config from nova-cloud-controller, this charm is broken:

2016-04-24 00:39:20,300 [INFO] deployer.import: Adding relation nova-vmware:amqp <-> rabbitmq-server:amqp
2016-04-24 00:39:21,068 [INFO] deployer.import: Adding relation nova-vmware <-> glance
2016-04-24 00:39:21,777 [INFO] deployer.import: Adding relation nsx-transport-node <-> neutron-gateway
2016-04-24 00:39:22,412 [INFO] deployer.import: Adding relation swift-proxy <-> glance
2016-04-24 00:39:23,115 [DEBUG] deployer.import: Waiting for relation convergence 600s
2016-04-24 00:49:23,428 [ERROR] deployer.env: The following units had errors:
   unit: nova-vmware/0: machine: 1 agent-state: error details: hook failed: "cloud-compute-relation-changed"
2016-04-24 00:49:23,431 [ERROR] oil_ci.deploy.oil_deployer: Deployment failed:

In the unit log:

dir "/var/lib/juju/agents/unit-nova-vmware-0/charm"
2016-04-23 22:46:23 INFO worker.uniter.jujuc server.go:172 running hook tool "relation-get" ["--format=json" "-r" "cloud-compute:44" "quantum_url" "nova-cloud-controller/0"]
2016-04-23 22:46:23 DEBUG worker.uniter.jujuc server.go:173 hook context id "nova-vmware/0-cloud-compute-relation-changed-5531436630117252393"; dir "/var/lib/juju/agents/unit-nova-vmware-0/charm"
2016-04-23 22:46:23 INFO cloud-compute-relation-changed Traceback (most recent call last):
2016-04-23 22:46:23 INFO cloud-compute-relation-changed File "/var/lib/juju/agents/unit-nova-vmware-0/charm/hooks/cloud-compute-relation-changed", line 136, in <module>
2016-04-23 22:46:23 INFO cloud-compute-relation-changed hooks.execute(sys.argv)
2016-04-23 22:46:23 INFO cloud-compute-relation-changed File "/var/lib/juju/agents/unit-nova-vmware-0/charm/hooks/charmhelpers/core/hookenv.py", line 672, in execute
2016-04-23 22:46:23 INFO cloud-compute-relation-changed self._hooks[hook_name]()
2016-04-23 22:46:23 INFO cloud-compute-relation-changed File "/var/lib/juju/agents/unit-nova-vmware-0/charm/hooks/charmhelpers/core/host.py", line 393, in wrapped_f
2016-04-23 22:46:23 INFO cloud-compute-relation-changed f(*args, **kwargs)
2016-04-23 22:46:23 INFO cloud-compute-relation-changed File "/var/lib/juju/agents/unit-nova-vmware-0/charm/hooks/cloud-compute-relation-changed", line 131, in cloud_compute_changed
2016-04-23 22:46:23 INFO cloud-compute-relation-changed CONFIGS.write(constants.NOVA_CONF)
2016-04-23 22:46:23 INFO cloud-compute-relation-changed File "/var/lib/juju/agents/unit-nova-vmware-0/charm/hooks/charmhelpers/contrib/openstack/templating.py", line 266, in write
2016-04-23 22:46:23 INFO cloud-compute-relation-changed _out = self.render(config_file)
2016-04-23 22:46:23 INFO cloud-compute-relation-changed File "/var/lib/juju/agents/unit-nova-vmware-0/charm/hooks/charmhelpers/contrib/openstack/templating.py", line 237, in render
2016-04-23 22:46:23 INFO cloud-compute-relation-changed ctxt = self.templates[config_file].context()
2016-04-23 22:46:23 INFO cloud-compute-relation-changed File "/var/lib/juju/agents/unit-nova-vmware-0/charm/hooks/charmhelpers/contrib/openstack/templating.py", line 104, in context
2016-04-23 22:46:23 INFO cloud-compute-relation-changed _ctxt = context()
2016-04-23 22:46:23 INFO cloud-compute-relation-changed File "/var/lib/juju/agents/unit-nova-vmware-0/charm/hooks/nova_vmware_context.py", line 123, in __call__
2016-04-23 22:46:23 INFO cloud-compute-relation-changed self.validate_network_manager()
2016-04-23 22:46:23 INFO cloud-compute-relation-changed File "/var/lib/juju/agents/unit-nova-vmware-0/charm/hooks/nova_vmware_context.py", line 77, in validate_network_manager
2016-04-23 22:46:23 INFO cloud-compute-relation-changed raise NovaVMwareIncompatable(m)
2016-04-23 22:46:23 INFO cloud-compute-relation-changed nova_vmware_context.NovaVMwareIncompatable: Neutron plugin not compatable with VMware: None
2016-04-23 22:46:24 INFO juju.worker.uniter.context context.go:579 handling reboot
2016-04-23 22:46:24 ERROR juju.worker.uniter.operation runhook.go:107 hook "cloud-compute-relation-changed" failed: exit status 1
2016-04-23 22:46:24 DEBUG juju.worker.uniter modes.go:31 [AGENT-STATUS] failed: run relation-changed (44; nova-cloud-controller/0) hook
2016-04-23 22:46:24 INFO juju.worker.uniter modes.go:569 ModeAbide exiting
2016-04-23 22:46:24 INFO juju.worker.uniter modes.go:567 ModeHookError starting

So charm should be getting the plugin information from neutron-api

Tags: oil

Related branches

lp://qastaging/~james-page/charms/trusty/nova-compute-vmware/bug-1574657
David Ames (community): Approve
Diff: 13 lines (+2/-1)
1 file modified
hooks/nova_vmware_context.py (+2/-1)
Revision history for this message
Larry Michel (lmic) wrote :

I tested replacing the nova-cloud-controller relation with neutron-api relation in the charm, and I was able to deploy without any error. So, I'll link the branch I tested with to this bug.

summary: - unit: nova-vmware/0: machine: 1 agent-state: error details: hook failed:
- "cloud-compute-relation-changed"
+ failed neutron configuration - unit: nova-vmware/0: machine: 1 agent-
+ state: error details: hook failed: cloud-compute-relation-changed
Larry Michel (lmic)
Changed in nova-compute-vmware (Juju Charms Collection):
status: New → In Progress
assignee: nobody → Larry Michel (lmic)
importance: Undecided → Critical
Revision history for this message
James Page (james-page) wrote :

The nova-cc charm should still be propagating the network-manager and neutron plugin directly to the nova-compute-vmware charm, in the same way that they do for the stock nova-compute charm; so I think that switching the relation to the neutron-api does not make a huge amount of sense.

David Ames (thedac)
Changed in nova-compute-vmware (Juju Charms Collection):
status: In Progress → Fix Released
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.