Back to bug 1301015
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Hugh Brock | 2016-01-22 10:46:18 UTC | CC | hbrock | |
| Assignee | calfonso | gfidente | ||
| Giulio Fidente | 2016-01-22 12:32:50 UTC | Status | NEW | ASSIGNED |
| Component | rhel-osp-director | openstack-tripleo-heat-templates | ||
| Link ID | OpenStack gerrit 267647 | |||
| Giulio Fidente | 2016-01-22 12:35:05 UTC | Blocks | 1301046 | |
| Giulio Fidente | 2016-01-22 12:36:15 UTC | Blocks | 1301046 | |
| Giulio Fidente | 2016-01-22 12:36:43 UTC | Depends On | 1301046 | |
| Jaromir Coufal | 2016-01-22 15:35:43 UTC | CC | jcoufal | |
| Steve Linabery | 2016-01-22 19:09:31 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | openstack-tripleo-heat-templates-0.8.6-112.el7ost | |||
| errata-xmlrpc | 2016-01-22 19:21:52 UTC | Status | MODIFIED | ON_QA |
| yeylon | 2016-01-24 08:21:06 UTC | QA Contact | yeylon | mcornea |
| Marius Cornea | 2016-01-25 11:40:13 UTC | Status | ON_QA | VERIFIED |
| Giulio Fidente | 2016-02-12 13:55:01 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. |
|
| Dan Macpherson | 2016-02-15 04:01:46 UTC | CC | dmacpher | |
| 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. | 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. | ||
| errata-xmlrpc | 2016-02-18 15:46:31 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-02-18 16:51:29 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-02-18 11:51:29 UTC |
Back to bug 1301015