ha not working when deployed in phycal nodes

Bug #1441367 reported by Samantha Jian-Pielak
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
quantum-gateway (Juju Charms Collection)
Won't Fix
Undecided
Unassigned

Bug Description

When deploying quantum-gateway with ha-legacy-mode enabled, it only works when deployed to the lxc containers. The corosync and pacemaker won't start if deployed to physical nodes.

https://wiki.ubuntu.com/ServerTeam/OpenStackCharms/ReleaseNotes1501

Revision history for this message
James Page (james-page) wrote :

Please can we get the full juju logs from /var/log/juju from this deployment, the output of juju status and all of the configuration options being used for quantum-gateway and hacluster in this deployment.

Changed in quantum-gateway (Juju Charms Collection):
status: New → Incomplete
Revision history for this message
Shang Wu (shangwu) wrote :

Hi James,

Thanks for looking into this. Here is the steps to reproduce the issue:

1. Deploy service (ex, mysql) to 3 of physical nodes by using Juju. -> OK

2. Deploy trusty/hacluster-18 -> OK

3. Hook up relation between mysql – hacluster -> Hookup failed.

4. Use “juju resolved –retry” command to fix issue -> no help. Still shows red line.

5. Login to one of physical node to run a check.

a. Verify the corosync & pacemaker status -> both of services not start

b. Verify corosync.conf -> mysql HA setting hasn’t been written to this file.

c. Run “sudo crm_mon” -> connection refused. Node cluster failed.

*I can also reproduce the issue by following the steps:

Mine step was:

1. bootstrap
2. juju deploy -n 3 -constrains tags=physical keystone
3. juju deploy hacluster hacluster-keystone
4. juju add-relation hacluster-keystone keystone

juju stat keystone gives:
http://paste.ubuntu.com/10790371/

even if I deploy services to the container, the hooks will fail as well.

Attach logs for analysis

Revision history for this message
Shang Wu (shangwu) wrote :
Revision history for this message
Shang Wu (shangwu) wrote :
Revision history for this message
Samantha Jian-Pielak (samantha-jian) wrote :

Configuration options for quantum-gateway and hacluster-quantum-gateway.
 quantum-gateway:
    ha-bindiface: eth0
    instance-mtu: 1350
    ext-port: eth1
    ha-legacy-mode: true
    plugin: ovs
    openstack-origin: cloud:trusty-juno
  hacluster-quantum-gateway:
     corosync_transport: unicast

Configuration options for the other data point with keystone:
keystone:
   vip: 10.5.9.202
   enable-pki: "false"
   admin-password: openstack
   admin-token: openstacktesting
   debug: 'True'
   log-level: DEBUG
   ha-bindiface: eth0
   openstack-origin: cloud:trusty-juno
hacluster-keystone:
   corosync_transport: unicast

Changed in quantum-gateway (Juju Charms Collection):
status: Incomplete → Confirmed
Revision history for this message
James Page (james-page) wrote :

ha-legacy-mode was always a bit of a stop gap until Neutron grew support for HA router support, so I'm going to mark this as Won't Fix - we should also drop support from the charm at a suitable point in time.

Changed in quantum-gateway (Juju Charms Collection):
status: Confirmed → Won't Fix
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.