Bug 1297850
| Summary: | Corosync fails to start in an ipv6 deployment | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Jiri Stransky <jstransk> |
| Status: | CLOSED ERRATA | QA Contact: | yeylon <yeylon> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.0 (Kilo) | CC: | dmacpher, emacchi, gdubreui, jslagle, mburns, michele, rhel-osp-director-maint, sathlang, srevivo, yeylon |
| Target Milestone: | y3 | Keywords: | ZStream |
| Target Release: | 7.0 (Kilo) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-0.8.6-99.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Corosync failed to start in an IPv6-based Overcloud. This is due to a missing '--ipv6' option when the director tries to start Corosync. This fix adds this option to the Controller's Puppet manifest and also adds related parameters to the Heat template collection. Corosync now starts successfully in IPv6-based Overclouds.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-02-18 16:48:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Marius Cornea
2016-01-12 15:45:58 UTC
I think TripleO Heat Templates is missing some useful options to enable Corosync on the overcloud: https://github.com/redhat-openstack/puppet-pacemaker/blob/master/manifests/corosync.pp#L25-L27 Looking at THT now, it seems like cluster_setup_extras is empty now, which could be the reason why Corosync configure IPv4 by default. Effectively when using IPv6 the cluster_setup_extras must bear the --ipv6 option.
For instance:
-------------
class {"pacemaker::corosync":
cluster_name => "cluster_test",
cluster_members => "one.pcs.tst two.pcs.tst three.pcs.tst",
cluster_setup_extras => { '--ipv6' => '' },
}
--------------
With above, the cluster starts properly.
The option must be added to the deployment parameters.
openstack-tripleo-heat-templates-0.8.6-106.el7ost.noarch
[root@overcloud-controller-0 ~]# systemctl status corosync
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/usr/lib/systemd/system/corosync.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2016-01-19 05:30:34 EST; 22min ago
Main PID: 25781 (corosync)
CGroup: /system.slice/corosync.service
└─25781 corosync
Jan 19 05:30:34 overcloud-controller-0.localdomain corosync[25781]: [SERV ] Service engine loaded: corosync vote quorum service v1.0 [5]
Jan 19 05:30:34 overcloud-controller-0.localdomain corosync[25781]: [QB ] server name: votequorum
Jan 19 05:30:34 overcloud-controller-0.localdomain corosync[25781]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Jan 19 05:30:34 overcloud-controller-0.localdomain corosync[25781]: [QB ] server name: quorum
Jan 19 05:30:34 overcloud-controller-0.localdomain corosync[25781]: [TOTEM ] adding new UDPU member {fd00:fd00:fd00:2000:f816:3eff:feeb:3100}
Jan 19 05:30:34 overcloud-controller-0.localdomain corosync[25781]: [TOTEM ] A new membership (fd00:fd00:fd00:2000:f816:3eff:feeb:3100:4) was formed. Members joined: 1
Jan 19 05:30:34 overcloud-controller-0.localdomain corosync[25781]: [QUORUM] Members[1]: 1
Jan 19 05:30:34 overcloud-controller-0.localdomain corosync[25781]: [MAIN ] Completed service synchronization, ready to provide service.
Jan 19 05:30:34 overcloud-controller-0.localdomain corosync[25774]: Starting Corosync Cluster Engine (corosync): [ OK ]
Jan 19 05:30:34 overcloud-controller-0.localdomain systemd[1]: Started Corosync Cluster Engine.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0264.html |