Misconfiguration of openstack-origin causes obfuscated charm behaviour
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron Gateway Charm |
Triaged
|
Low
|
Unassigned | ||
neutron-gateway (Juju Charms Collection) |
Invalid
|
Low
|
Unassigned |
Bug Description
neutron-
=======
I have the following topology (see attached opentack-juju.svg for graphical view):
- 1 MAAS server (also used as the Juju client), on trusty
- 1 Juju bootstrap node, on xenial
- 1 controller node, on xenial
- 2 compute nodes, on xenial
They're all connected to the same network, with a single NIC each.
I use MAAS Version 1.9.3+bzr4577-
I bootstrapped Juju using the environment attached in `environments.
After registering the machines onto juju (`juju machine add X.maas`), I manually deploy my charms, and relate them.
For conveniance, I provide in the attached `mybundle.yaml`, the final configuration as seen in the WebGUI.
Unfortunately, everything looks like it runs well, except neutron-gateway:
root@maas:~# juju status --format tabular neutron-gateway/0
[Services]
NAME STATUS EXPOSED CHARM
neutron-
[Units]
ID WORKLOAD-STATE AGENT-STATE VERSION MACHINE PORTS PUBLIC-ADDRESS MESSAGE
neutron-
[Machines]
ID STATE VERSION DNS INS-ID SERIES HARDWARE
3 started 1.25.6 controller.maas /MAAS/api/
I pasted the complete status output in `juju-status-
I used a similar setup on trusty (only other difference is that mysql was used instead of percona-cluster), and did not meet that issue, all Units were OK.
Furthermore, I don't know if it is related, but I can't spawn a VM on a compute node, the VM is displayed in ERROR status, but I don't see anything in either nova-compute logs or nova-cloud-
The commands attached in `start_vm.sh` are the ones I typed on nova-compute to try and get my VM started (same command worked with my earlier trusty setup).
Changed in neutron-gateway (Juju Charms Collection): | |
importance: | Undecided → Medium |
status: | New → Triaged |
milestone: | none → 16.10 |
Changed in neutron-gateway (Juju Charms Collection): | |
milestone: | 16.10 → 17.01 |
Changed in neutron-gateway (Juju Charms Collection): | |
importance: | Medium → Low |
Changed in charm-neutron-gateway: | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in neutron-gateway (Juju Charms Collection): | |
status: | Triaged → Invalid |
Hi Pascal. Sorry you've hit this issue. Could you confirm whether the neutron- plugin- openvswitch- agent service was running on neutron-gateway/0 ? It would be good to know if this is a bug with the service not being started or a bug with the code assessing the service status.
Could you run "nova show <server UUID>" for the guest that failed to boot and attach the logs from /var/log/nova on the compute nodes as well please?
Thanks
Liam