Back to bug 2108212
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2022-07-18 15:54:23 UTC | Link ID | Red Hat Issue Tracker OSP-17675 | |
| Eran Kuris | 2022-07-20 15:05:59 UTC | Keywords | AutomationBlocker, Regression | |
| James Smith | 2022-07-21 13:22:22 UTC | CC | jamsmith | |
| Miro Tomaska | 2022-07-21 13:22:31 UTC | Assignee | rhos-maint | mtomaska |
| CC | mtomaska | |||
| James Smith | 2022-07-21 13:23:28 UTC | Docs Contact | jamsmith | |
| Miro Tomaska | 2022-08-03 03:26:01 UTC | Keywords | Regression | Triaged |
| Priority | unspecified | high | ||
| Bernard Cafarelli | 2022-08-04 14:59:30 UTC | Status | NEW | ASSIGNED |
| Mike Burns | 2022-08-11 12:20:40 UTC | CC | mburns | |
| Eran Kuris | 2023-06-13 13:37:19 UTC | Target Release | --- | 17.1 |
| Target Milestone | --- | ga | ||
| RHEL Program Management | 2023-06-13 13:37:26 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| James Smith | 2023-06-15 00:57:09 UTC | Flags | needinfo?(rsafrono) needinfo?(mtomaska) | |
| RHEL Program Management | 2023-06-15 00:57:20 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| Roman Safronov | 2023-06-15 08:22:49 UTC | Flags | needinfo?(rsafrono) | |
| RHEL Program Management | 2023-06-15 08:22:58 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| Lukas Svaty | 2023-06-16 08:44:02 UTC | Flags | needinfo?(ekuris) | |
| CC | ekuris, lsvaty | |||
| RHEL Program Management | 2023-06-16 08:44:13 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| Miro Tomaska | 2023-06-16 20:06:08 UTC | Doc Text | Cause: The Router Advertisment daemon (radvd) for IPv6 is stopped during migration process Consequence: When radvd daemon is stopped, the IPv6 router advertisments are no longer broadcasted which results in connection loss to VMs over an IPv6. IPv6 communication is automatically restored once new ML2/OVN services are first started. Workaround (if any): If constant connection to VMs is required during migration, it is advised to use IPv4. One note, even with IPv4 some pocket can occur but it should no be continous outage. Result: No connection with VMs over IPv6 for the duration when ML2/OVS agents are stopped until ML2/OVN services are started. Depending on the size of enviroment that can last couple of minutes. | |
| Doc Type | If docs needed, set a value | Known Issue | ||
| Flags | needinfo?(mtomaska) | |||
| RHEL Program Management | 2023-06-16 20:06:19 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| Eran Kuris | 2023-06-18 11:41:54 UTC | Flags | needinfo?(ekuris) | |
| RHEL Program Management | 2023-06-18 11:42:03 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| James Smith | 2023-06-22 15:48:11 UTC | Doc Text | Cause: The Router Advertisment daemon (radvd) for IPv6 is stopped during migration process Consequence: When radvd daemon is stopped, the IPv6 router advertisments are no longer broadcasted which results in connection loss to VMs over an IPv6. IPv6 communication is automatically restored once new ML2/OVN services are first started. Workaround (if any): If constant connection to VMs is required during migration, it is advised to use IPv4. One note, even with IPv4 some pocket can occur but it should no be continous outage. Result: No connection with VMs over IPv6 for the duration when ML2/OVS agents are stopped until ML2/OVN services are started. Depending on the size of enviroment that can last couple of minutes. | If you use IPv6 to connect to VM instances during migration to the OVN mechanism driver, connection to the instances might be disrupted for up to several minutes when the ML2/OVN services are started. To avoid this, use IPv4 instead. The router advertisement daemon `radvd` for IPv6 is stopped during migration to the OVN mechanism driver. While `radvd` is stopped, router advertisements are no longer broadcast. This broadcast interruption results in VM instance connection loss over IPv6. IPv6 communication is automatically restored once the new ML2/OVN services start. To avoid the problem, use IPv4 instead. |
| RHEL Program Management | 2023-06-22 15:48:21 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| James Smith | 2023-06-22 15:55:35 UTC | Doc Text | If you use IPv6 to connect to VM instances during migration to the OVN mechanism driver, connection to the instances might be disrupted for up to several minutes when the ML2/OVN services are started. To avoid this, use IPv4 instead. The router advertisement daemon `radvd` for IPv6 is stopped during migration to the OVN mechanism driver. While `radvd` is stopped, router advertisements are no longer broadcast. This broadcast interruption results in VM instance connection loss over IPv6. IPv6 communication is automatically restored once the new ML2/OVN services start. To avoid the problem, use IPv4 instead. | If you use IPv6 to connect to VM instances during migration to the OVN mechanism driver, connection to the instances might be disrupted for up to several minutes when the ML2/OVN services are started. To avoid this, use IPv4 instead. The router advertisement daemon `radvd` for IPv6 is stopped during migration to the OVN mechanism driver. While `radvd` is stopped, router advertisements are no longer broadcast. This broadcast interruption results in VM instance connection loss over IPv6. IPv6 communication is automatically restored once the new ML2/OVN services start. To avoid the potential disruption, use IPv4 instead. |
| RHEL Program Management | 2023-06-22 15:55:46 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| James Smith | 2023-06-22 16:04:34 UTC | Doc Text | If you use IPv6 to connect to VM instances during migration to the OVN mechanism driver, connection to the instances might be disrupted for up to several minutes when the ML2/OVN services are started. To avoid this, use IPv4 instead. The router advertisement daemon `radvd` for IPv6 is stopped during migration to the OVN mechanism driver. While `radvd` is stopped, router advertisements are no longer broadcast. This broadcast interruption results in VM instance connection loss over IPv6. IPv6 communication is automatically restored once the new ML2/OVN services start. To avoid the potential disruption, use IPv4 instead. | If you use IPv6 to connect to VM instances during migration to the OVN mechanism driver, connection to the instances might be disrupted for up to several minutes when the ML2/OVN services are started. To avoid this, use IPv4 instead. + The router advertisement daemon `radvd` for IPv6 is stopped during migration to the OVN mechanism driver. While `radvd` is stopped, router advertisements are no longer broadcast. This broadcast interruption results in VM instance connection loss over IPv6. IPv6 communication is automatically restored once the new ML2/OVN services start. + To avoid the potential disruption, use IPv4 instead. |
| RHEL Program Management | 2023-06-22 16:04:44 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| James Smith | 2023-06-22 16:06:14 UTC | Doc Text | If you use IPv6 to connect to VM instances during migration to the OVN mechanism driver, connection to the instances might be disrupted for up to several minutes when the ML2/OVN services are started. To avoid this, use IPv4 instead. + The router advertisement daemon `radvd` for IPv6 is stopped during migration to the OVN mechanism driver. While `radvd` is stopped, router advertisements are no longer broadcast. This broadcast interruption results in VM instance connection loss over IPv6. IPv6 communication is automatically restored once the new ML2/OVN services start. + To avoid the potential disruption, use IPv4 instead. | If you use IPv6 to connect to VM instances during migration to the OVN mechanism driver, connection to the instances might be disrupted for up to several minutes when the ML2/OVN services start. To avoid this, use IPv4 instead. + The router advertisement daemon `radvd` for IPv6 is stopped during migration to the OVN mechanism driver. While `radvd` is stopped, router advertisements are no longer broadcast. This broadcast interruption results in VM instance connection loss over IPv6. IPv6 communication is automatically restored once the new ML2/OVN services start. + To avoid the potential disruption, use IPv4 instead. |
| RHEL Program Management | 2023-06-22 16:06:22 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| Eran Kuris | 2023-06-25 09:18:37 UTC | Keywords | AutomationBlocker | Automation |
| RHEL Program Management | 2023-06-25 09:18:48 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| Eran Kuris | 2023-06-25 09:19:20 UTC | Severity | high | medium |
| RHEL Program Management | 2023-06-25 09:19:31 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| Eran Kuris | 2023-06-25 09:20:35 UTC | Target Milestone | ga | z1 |
| RHEL Program Management | 2023-06-25 09:20:45 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| Paul Grist | 2023-06-27 13:03:50 UTC | CC | pgrist | |
| RHEL Program Management | 2023-06-27 13:03:59 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| Miro Tomaska | 2023-06-28 18:42:14 UTC | Flags | needinfo?(jamsmith) | |
| RHEL Program Management | 2023-06-28 18:42:23 UTC | Target Release | 17.1 17.0 | 17.0 17.1 |
| Bernard Cafarelli | 2023-06-29 14:45:17 UTC | CC | bcafarel | |
| James Smith | 2023-07-03 13:16:09 UTC | Doc Text | If you use IPv6 to connect to VM instances during migration to the OVN mechanism driver, connection to the instances might be disrupted for up to several minutes when the ML2/OVN services start. To avoid this, use IPv4 instead. + The router advertisement daemon `radvd` for IPv6 is stopped during migration to the OVN mechanism driver. While `radvd` is stopped, router advertisements are no longer broadcast. This broadcast interruption results in VM instance connection loss over IPv6. IPv6 communication is automatically restored once the new ML2/OVN services start. + To avoid the potential disruption, use IPv4 instead. | If you use IPv6 to connect to VM instances during migration to the OVN mechanism driver, connection to the instances might be disrupted for up to several minutes when the ML2/OVS services are stopped. To avoid this, use IPv4 instead. + The router advertisement daemon `radvd` for IPv6 is stopped during migration to the OVN mechanism driver. While `radvd` is stopped, router advertisements are no longer broadcast. This broadcast interruption results in VM instance connection loss over IPv6. IPv6 communication is automatically restored once the new ML2/OVN services start. + To avoid the potential disruption, use IPv4 instead. |
| Bernard Cafarelli | 2023-08-01 07:26:53 UTC | Target Milestone | z1 | z2 |
| Miro Tomaska | 2023-08-01 13:22:43 UTC | Link ID | Github RedHatCRE/znoyder/pull/147/commits/7deb69f37eac8094e267ecebb20b307d448342c0#diff-6238496c8bf4dec73b0edd0fd1404623e1515bcc8a2c4cb5f1acb3d824eec93c | |
| Miro Tomaska | 2023-08-01 13:23:02 UTC | Link ID | Github RedHatCRE/znoyder/pull/147/commits/7deb69f37eac8094e267ecebb20b307d448342c0#diff-6238496c8bf4dec73b0edd0fd1404623e1515bcc8a2c4cb5f1acb3d824eec93c | |
| Ian Frangs | 2023-08-03 15:46:23 UTC | Flags | needinfo?(mtomaska) | |
| Miro Tomaska | 2023-08-04 19:35:09 UTC | Flags | needinfo?(mtomaska) | |
| Miro Tomaska | 2023-08-04 19:43:39 UTC | Status | ASSIGNED | ON_DEV |
| Ian Frangs | 2023-08-11 11:34:17 UTC | Doc Text | If you use IPv6 to connect to VM instances during migration to the OVN mechanism driver, connection to the instances might be disrupted for up to several minutes when the ML2/OVS services are stopped. To avoid this, use IPv4 instead. + The router advertisement daemon `radvd` for IPv6 is stopped during migration to the OVN mechanism driver. While `radvd` is stopped, router advertisements are no longer broadcast. This broadcast interruption results in VM instance connection loss over IPv6. IPv6 communication is automatically restored once the new ML2/OVN services start. + To avoid the potential disruption, use IPv4 instead. | If you use IPv6 to connect to instances during migration to the OVN mechanism driver, connection to the instances might be disrupted for up to several minutes when the ML2/OVS services are stopped. To avoid this, use IPv4 instead. + The router advertisement daemon `radvd` for IPv6 is stopped during migration to the OVN mechanism driver. While `radvd` is stopped, router advertisements are no longer broadcast. This broadcast interruption results in instance connection loss over IPv6. IPv6 communication is automatically restored once the new ML2/OVN services start. + To avoid the potential disruption, use IPv4 instead. |
| CC | ifrangs | |||
| Ian Frangs | 2023-08-11 16:45:10 UTC | CC | ifrangs |
Back to bug 2108212