Back to bug 1301046

Who When What Removed Added
Giulio Fidente 2016-01-22 12:36:15 UTC Status NEW ASSIGNED
Depends On 1301015
Giulio Fidente 2016-01-22 12:36:43 UTC Blocks 1301015
Giulio Fidente 2016-01-22 12:44:49 UTC Assignee emacchi gfidente
RHEL Program Management 2016-01-22 12:45:13 UTC Keywords ZStream
Mike Burns 2016-01-22 13:53:17 UTC Target Milestone y3 z4
Lukas Bezdicka 2016-01-22 14:05:25 UTC Status ASSIGNED MODIFIED
CC lbezdick
Fixed In Version openstack-puppet-modules-2015.1.8-44.el7ost
Lon Hohberger 2016-01-22 15:01:22 UTC Priority unspecified urgent
errata-xmlrpc 2016-01-22 18:58:50 UTC Status MODIFIED ON_QA
yeylon 2016-01-24 08:21:24 UTC QA Contact yeylon ohochman
Marius Cornea 2016-01-25 11:39:49 UTC Status ON_QA VERIFIED
Deepti Navale 2016-02-12 02:29:33 UTC CC dnavale, gfidente
Flags needinfo?(gfidente)
Giulio Fidente 2016-02-12 13:23:30 UTC Doc Text Cause: In mixed environments where some networks use IPv4 addressing and others IPv6 addressing we were incorrectly setting the IPv6 cidr for IPv4 addresses too.

Consequence: The deployment of the overcloud would fail with Pacemaker refusing to start the IPv4 virtual IPs.

Fix: We added a functionality to identify during the deployment of which type (if IPv4 or IPv6) each virtuap IP is, adapting the cidr accordingly.

Result: Each virtual IPs is configured with the appropriate cidr being it of the IPv4 or IPv6 class.
Flags needinfo?(gfidente)
Giulio Fidente 2016-02-12 13:32:35 UTC Doc Text Cause: In mixed environments where some networks use IPv4 addressing and others IPv6 addressing we were incorrectly setting the IPv6 cidr for IPv4 addresses too.

Consequence: The deployment of the overcloud would fail with Pacemaker refusing to start the IPv4 virtual IPs.

Fix: We added a functionality to identify during the deployment of which type (if IPv4 or IPv6) each virtuap IP is, adapting the cidr accordingly.

Result: Each virtual IPs is configured with the appropriate cidr being it of the IPv4 or IPv6 class. 		Cause: In mixed environments where some networks use IPv4 addressing and others IPv6 addressing, the IPv6 cidr was incorrectly used for IPv4 virtual IPs too.

Consequence: The deployment of the overcloud would fail with Pacemaker refusing to start the IPv4 virtual IPs.

Fix: We added a functionality to identify during the deployment of which type (if IPv4 or IPv6) each virtuap IP is, adapting the cidr accordingly.

Result: Each virtual IPs is configured with the appropriate cidr being it of the IPv4 or IPv6 class.
Deepti Navale 2016-02-15 03:16:41 UTC Doc Text Cause: In mixed environments where some networks use IPv4 addressing and others IPv6 addressing, the IPv6 cidr was incorrectly used for IPv4 virtual IPs too.

Consequence: The deployment of the overcloud would fail with Pacemaker refusing to start the IPv4 virtual IPs.

Fix: We added a functionality to identify during the deployment of which type (if IPv4 or IPv6) each virtuap IP is, adapting the cidr accordingly.

Result: Each virtual IPs is configured with the appropriate cidr being it of the IPv4 or IPv6 class. 		Previously, in mixed environments where some networks use IPv4 addresses and others use IPv6 addresses, the IPv6 CIDR was incorrectly used for the IPv4 virtual IP addresses too. As a result, the deployment of the overcloud failed with Pacemaker refusing to start the IPv4 virtual IP addresses.

With this update, a new functionality which identifies the type of virtual IP (whether IPv4 or IPv6) is added, adapting the CIDR accordingly. As a result, each virtual IP address is configured with the appropriate CIDR, of either the IPv4 or IPv6 class.
errata-xmlrpc 2016-02-18 15:50:51 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-02-18 16:44:37 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-02-18 11:44:37 UTC

Back to bug 1301046