Bug 1301015
| Summary: | IPv4 VIP resources get created with 64 cidr_netmask in mixed IPv4/IPv6 environment | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> | |
| Component: | openstack-tripleo-heat-templates | Assignee: | Giulio Fidente <gfidente> | |
| Status: | CLOSED ERRATA | QA Contact: | Marius Cornea <mcornea> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 7.0 (Kilo) | CC: | dmacpher, hbrock, jcoufal, mburns, rhel-osp-director-maint | |
| Target Milestone: | y3 | |||
| Target Release: | 7.0 (Kilo) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-tripleo-heat-templates-0.8.6-112.el7ost | Doc Type: | Bug Fix | |
| Doc Text: |
In mixed environments where some networks use IPv4 addressing and others IPv6 addressing, the Overcloud used IPv6 CIDR for IPv4 VIPs too. The Overcloud deployment failed because Pacemaker refused to start the IPv4 VIPs. This fix adds functionality to identify the VIP type (IPv4 or IPv6) during deployment and adapt the appropriate CIDR. Each IPv4 and IPv6 VIP now uses the appropriate CIDR.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1301046 (view as bug list) | Environment: | ||
| Last Closed: | 2016-02-18 16:51:29 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: | ||||
| Bug Depends On: | 1301046 | |||
| Bug Blocks: | ||||
[root@overcloud-controller-0 ~]# pcs resource show ip-2001.db8.fd00.1000..10
Resource: ip-2001.db8.fd00.1000..10 (class=ocf provider=heartbeat type=IPaddr2)
Attributes: ip=2001:db8:fd00:1000::10 cidr_netmask=64
Operations: start interval=0s timeout=20s (ip-2001.db8.fd00.1000..10-start-interval-0s)
stop interval=0s timeout=20s (ip-2001.db8.fd00.1000..10-stop-interval-0s)
monitor interval=10s timeout=20s (ip-2001.db8.fd00.1000..10-monitor-interval-10s)
[root@overcloud-controller-0 ~]# pcs resource show ip-172.16.3.4
Resource: ip-172.16.3.4 (class=ocf provider=heartbeat type=IPaddr2)
Attributes: ip=172.16.3.4 cidr_netmask=32
Operations: start interval=0s timeout=20s (ip-172.16.3.4-start-interval-0s)
stop interval=0s timeout=20s (ip-172.16.3.4-stop-interval-0s)
monitor interval=10s timeout=20s (ip-172.16.3.4-monitor-interval-10s)
[root@overcloud-controller-0 ~]#
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 |
Description of problem: IPv4 public VIP resources get created with 64 cidr_netmask in mixed IPv4/IPv6 environment Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-0.8.6-110.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy mixed IPv4/IPv6 environment (storage and storage management network on ipv4) Actual results: The IPV4 VIP resource are unable to start: root@overcloud-controller-0 ~]# pcs status | grep Stopped ip-172.16.3.4 (ocf::heartbeat:IPaddr2): Stopped ip-172.16.1.4 (ocf::heartbeat:IPaddr2): Stopped Expected results: The resources get started. Additional info: overcloud-controller-0-ip-172.16.3.4_start_0:6 [ ocf-exit-reason:Invalid netmask specification [64].\n ] [root@overcloud-controller-0 ~]# pcs resource show ip-172.16.3.4 Resource: ip-172.16.3.4 (class=ocf provider=heartbeat type=IPaddr2) Attributes: ip=172.16.3.4 cidr_netmask=64 Operations: start interval=0s timeout=20s (ip-172.16.3.4-start-interval-0s) stop interval=0s timeout=20s (ip-172.16.3.4-stop-interval-0s) monitor interval=10s timeout=20s (ip-172.16.3.4-monitor-interval-10s)