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)
[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