Back to bug 1302081
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| John Skeoch | 2016-02-01 02:52:05 UTC | Assignee | calfonso | hbrock |
| Mike Burns | 2016-04-07 21:07:13 UTC | Target Release | 8.0 | 10.0 |
| John Skeoch | 2016-04-18 08:04:16 UTC | CC | yeylon | srevivo |
| John Skeoch | 2016-04-18 09:05:59 UTC | QA Contact | yeylon | srevivo |
| Dan Sneddon | 2016-07-27 21:19:35 UTC | CC | bfournie | |
| Jaromir Coufal | 2016-10-10 04:14:47 UTC | CC | jcoufal | |
| Dan Sneddon | 2016-10-14 16:00:45 UTC | Priority | unspecified | low |
| Target Release | 10.0 (Newton) | 11.0 (Ocata) | ||
| Version | 7.0 (Kilo) | 10.0 (Newton) | ||
| Assignee | hbrock | dsneddon | ||
| Summary | When one of the leading zeros of the last IPv6 quartet is omitted the public VIP gets set on all 3 controllers | [DOC] When one of the leading zeros of the last IPv6 quartet is omitted the public VIP gets set on all 3 controllers | ||
| Doc Text | Cause: IPv6 networks and IP allocation pools must be input in a valid format according to RFC 5952. Leading zeros may be omitted, or may be included entirely, but incomplete entries do not work. Consequence: When entering address ranges for the AllocationPools, invalid entries will cause an error. Workaround (if any): IPv6 addresses should be entered in valid format. Leading zeroes can be omitted or entered in full, and repeating sequences of zeros may be replaced by "::". Result: An IP address of "fd00:0001:0000:0000:00a1:00b2:00c3:0010" may be represented as: "fd00:1::a1:b2:c3:10", but not as: "fd00:01::0b2:0c3:10", because there are an invalid number of leading zeros (01, 0b2, 0c3). The field must be truncated of leading zeros or fully padded. | |||
| Doc Type | Bug Fix | Known Issue | ||
| Severity | high | low | ||
| Dan Sneddon | 2016-10-14 16:01:47 UTC | Target Release | 11.0 (Ocata) | 10.0 (Newton) |
| Bob Fournier | 2016-10-17 15:04:58 UTC | Keywords | Documentation | |
| Component | rhel-osp-director | documentation | ||
| Assignee | dsneddon | rhos-docs | ||
| QA Contact | srevivo | rhos-docs | ||
| Martin Lopes | 2016-11-01 23:55:47 UTC | CC | mlopes | |
| Doc Text | Cause: IPv6 networks and IP allocation pools must be input in a valid format according to RFC 5952. Leading zeros may be omitted, or may be included entirely, but incomplete entries do not work. Consequence: When entering address ranges for the AllocationPools, invalid entries will cause an error. Workaround (if any): IPv6 addresses should be entered in valid format. Leading zeroes can be omitted or entered in full, and repeating sequences of zeros may be replaced by "::". Result: An IP address of "fd00:0001:0000:0000:00a1:00b2:00c3:0010" may be represented as: "fd00:1::a1:b2:c3:10", but not as: "fd00:01::0b2:0c3:10", because there are an invalid number of leading zeros (01, 0b2, 0c3). The field must be truncated of leading zeros or fully padded. | Address ranges entered for the `AllocationPools` IPv6 networks and IP allocation pools must be input in a valid format according to RFC 5952. Leading zeros may be omitted, or may be included entirely, but incomplete entries do not work. Consequently, invalid entries will result in an error. As a result, IPv6 addresses should be entered in a valid format: Leading zeroes can be omitted or entered in full, and repeating sequences of zeros may be replaced by "::". For example, an IP address of "fd00:0001:0000:0000:00a1:00b2:00c3:0010" may be represented as: "fd00:1::a1:b2:c3:10", but not as: "fd00:01::0b2:0c3:10", because there are an invalid number of leading zeros (01, 0b2, 0c3). The field must be truncated of leading zeros or fully padded. |
||
| Dan Macpherson | 2016-12-08 05:39:09 UTC | Status | NEW | ASSIGNED |
| CC | dmacpher | |||
| Assignee | rhos-docs | dmacpher | ||
| Martin Lopes | 2017-01-10 03:45:39 UTC | Doc Text | Address ranges entered for the `AllocationPools` IPv6 networks and IP allocation pools must be input in a valid format according to RFC 5952. Leading zeros may be omitted, or may be included entirely, but incomplete entries do not work. Consequently, invalid entries will result in an error. As a result, IPv6 addresses should be entered in a valid format: Leading zeroes can be omitted or entered in full, and repeating sequences of zeros may be replaced by "::". For example, an IP address of "fd00:0001:0000:0000:00a1:00b2:00c3:0010" may be represented as: "fd00:1::a1:b2:c3:10", but not as: "fd00:01::0b2:0c3:10", because there are an invalid number of leading zeros (01, 0b2, 0c3). The field must be truncated of leading zeros or fully padded. | Address ranges entered for the `AllocationPools` IPv6 networks and IP allocation pools must be input in a valid format according to RFC 5952. Consequently, invalid entries will result in an error. As a result, IPv6 addresses should be entered in a valid format: Leading zeros can be omitted or entered in full, and repeating sequences of zeros may be replaced by "::". For example, an IP address of "fd00:0001:0000:0000:00a1:00b2:00c3:0010" may be represented as: "fd00:1::a1:b2:c3:10", but not as: "fd00:01::0b2:0c3:10", because there are an invalid number of leading zeros (01, 0b2, 0c3). The field must be truncated of leading zeros or fully padded. |
| Dan Macpherson | 2017-09-12 05:04:27 UTC | Status | ASSIGNED | POST |
| Flags | needinfo?(dsneddon) | |||
| Dan Sneddon | 2017-09-12 19:16:02 UTC | Flags | needinfo?(dsneddon) | |
| Dan Macpherson | 2017-09-13 01:16:13 UTC | Status | POST | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2017-09-12 21:16:13 UTC |
Back to bug 1302081