Back to bug 2182371
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2023-03-28 12:57:45 UTC | Link ID | Red Hat Issue Tracker OSP-23787 | |
| Miguel Angel Nieto | 2023-03-28 13:12:25 UTC | Keywords | Regression | |
| Priority | unspecified | high | ||
| Eran Kuris | 2023-03-28 13:29:23 UTC | Priority | high | unspecified |
| Severity | unspecified | high | ||
| Red Hat One Jira (issues.redhat.com) | 2023-03-28 13:30:51 UTC | Link ID | Red Hat Issue Tracker NFV-2793 | |
| Marcelo Ricardo Leitner | 2023-03-28 14:58:45 UTC | CC | mleitner | |
| Blocks | 2172622 | |||
| Haresh Khandelwal | 2023-03-28 15:30:10 UTC | CC | hakhande | |
| Eran Kuris | 2023-04-03 14:04:11 UTC | Flags | needinfo?(hakhande) | |
| Haresh Khandelwal | 2023-04-04 08:35:22 UTC | Flags | needinfo?(hakhande) | |
| Timothy Redaelli | 2023-04-19 13:41:10 UTC | CC | qding | |
| Assignee | ovs-bugzilla | ovs-triage | ||
| Vijay Chundury | 2023-04-27 09:19:34 UTC | CC | vchundur | |
| Haresh Khandelwal | 2023-05-11 11:29:57 UTC | Assignee | ovs-triage | hakhande |
| Christophe Fontaine | 2023-05-16 08:17:15 UTC | CC | cfontain | |
| Priority | unspecified | medium | ||
| Haresh Khandelwal | 2023-05-16 11:53:56 UTC | Flags | needinfo?(maord) | |
| CC | maord | |||
| Pradipta Kumar Sahoo | 2023-05-17 12:26:32 UTC | CC | psahoo | |
| Haresh Khandelwal | 2023-05-18 13:26:18 UTC | Keywords | Triaged | |
| Haresh Khandelwal | 2023-05-18 13:26:39 UTC | Status | NEW | ASSIGNED |
| Eran Kuris | 2023-05-21 07:31:50 UTC | Target Release | --- | 17.1 |
| Target Milestone | --- | ga | ||
| Denise Hughes | 2023-05-22 20:05:18 UTC | CC | dhughes | |
| Amir Tzin (Mellanox) | 2023-05-30 13:55:26 UTC | CC | atzin | |
| Haresh Khandelwal | 2023-06-06 14:37:11 UTC | Flags | needinfo?(atzin) | |
| Anthony Harivel | 2023-06-07 09:44:56 UTC | CC | aharivel | |
| Lukas Svaty | 2023-06-12 16:45:27 UTC | CC | lsvaty | |
| Keywords | Performance | |||
| Vadim Khitrin | 2023-06-13 06:49:33 UTC | Doc Type | If docs needed, set a value | Known Issue |
| CC | vkhitrin | |||
| James Smith | 2023-06-13 17:52:53 UTC | Flags | needinfo?(vkhitrin) needinfo?(mnietoji) needinfo?(ekuris) | |
| CC | ekuris, jamsmith | |||
| Vadim Khitrin | 2023-06-14 05:04:19 UTC | Doc Text | Cause: This applies to guest instances using Mellanox Connect-X5 NICs with offload (switchdev) ports. Nvidia is investigating the exact root cause. Consequence: It takes a long time to initialize the system when rebooting the operating system from the guest directly (example: sudo systemctl reboot --reboot-arg=now). Workaround (if any): Note: performing a reboot using the OpenStack API is not the same procedure as rebooting the guest instance directly. If required, operators can reboot the guest using OpenStack APIs. Result: Using OpenStack APIs, operators can reinitialize the guest instance in a timely manner. |
|
| Vadim Khitrin | 2023-06-14 05:12:55 UTC | Flags | needinfo?(vkhitrin) | |
| Eran Kuris | 2023-06-14 08:51:14 UTC | Flags | needinfo?(ekuris) | |
| Miguel Angel Nieto | 2023-06-14 10:30:00 UTC | Doc Text | Cause: This applies to guest instances using Mellanox Connect-X5 NICs with offload (switchdev) ports. Nvidia is investigating the exact root cause. Consequence: It takes a long time to initialize the system when rebooting the operating system from the guest directly (example: sudo systemctl reboot --reboot-arg=now). Workaround (if any): Note: performing a reboot using the OpenStack API is not the same procedure as rebooting the guest instance directly. If required, operators can reboot the guest using OpenStack APIs. Result: Using OpenStack APIs, operators can reinitialize the guest instance in a timely manner. | Cause: This applies to guest instances using Mellanox Connect-X5 NICs with offload (switchdev) ports. Nvidia is investigating the exact root cause. Consequence: It takes a long time to initialize the system when rebooting the operating system from the guest directly (example: sudo systemctl reboot --reboot-arg=now). In case the VM is configured with two VFs from the same PF, it may be possible that the initialization of one of the VFs fails and it cause a longer initialization time. Workaround (if any): Note: performing a reboot using the OpenStack API is not the same procedure as rebooting the guest instance directly. If required, operators can reboot the guest using OpenStack APIs. Result: Using OpenStack APIs, operators can reinitialize the guest instance in a timely manner. |
| Flags | needinfo?(maord) needinfo?(atzin) needinfo?(mnietoji) | |||
| Jenny-Anne Lynch | 2023-06-14 13:05:10 UTC | Doc Text | Cause: This applies to guest instances using Mellanox Connect-X5 NICs with offload (switchdev) ports. Nvidia is investigating the exact root cause. Consequence: It takes a long time to initialize the system when rebooting the operating system from the guest directly (example: sudo systemctl reboot --reboot-arg=now). In case the VM is configured with two VFs from the same PF, it may be possible that the initialization of one of the VFs fails and it cause a longer initialization time. Workaround (if any): Note: performing a reboot using the OpenStack API is not the same procedure as rebooting the guest instance directly. If required, operators can reboot the guest using OpenStack APIs. Result: Using OpenStack APIs, operators can reinitialize the guest instance in a timely manner. | There is currently a known issue with guest instances that user Mellanox Connect-X5 NICs with offload (switchdev) ports. It takes a long time to initialize the system when you reboot the operating system from the guest directly, for example, by using the command `sudo systemctl reboot --reboot-arg=now`. If the VM is configured with two Virtual Functions (VFs) from the same Physical Function (PF), the initialization of one of the VFs might fail and cause a longer initialization time. Workaround: Reboot the guest instance in a timely manner by using the OpenStack API instead of rebooting the guest instance directly. |
| CC | jelynch | |||
| Flags | needinfo?(mnietoji) | |||
| Miguel Angel Nieto | 2023-06-14 13:12:47 UTC | Flags | needinfo?(mnietoji) | |
| Doc Text | There is currently a known issue with guest instances that user Mellanox Connect-X5 NICs with offload (switchdev) ports. It takes a long time to initialize the system when you reboot the operating system from the guest directly, for example, by using the command `sudo systemctl reboot --reboot-arg=now`. If the VM is configured with two Virtual Functions (VFs) from the same Physical Function (PF), the initialization of one of the VFs might fail and cause a longer initialization time. Workaround: Reboot the guest instance in a timely manner by using the OpenStack API instead of rebooting the guest instance directly. | There is currently a known issue with guest instances that use Mellanox Connect-X5 NICs with offload (switchdev) ports. It takes a long time to initialize the system when you reboot the operating system from the guest directly, for example, by using the command `sudo systemctl reboot --reboot-arg=now`. If the VM is configured with two Virtual Functions (VFs) from the same Physical Function (PF), the initialization of one of the VFs might fail and cause a longer initialization time. Workaround: Reboot the guest instance in a timely manner by using the OpenStack API instead of rebooting the guest instance directly. | ||
| Miguel Angel Nieto | 2023-06-15 09:02:47 UTC | Summary | [17.1][OVN HWOFFLOAD][CX5] Vms with offload vfs takes a long time to boot up | [17.1][OVN HWOFFLOAD][CX5 & Bluefield-2 CX6] Vms with offload vfs takes a long time to boot up |
| Miguel Angel Nieto | 2023-06-15 09:05:15 UTC | Doc Text | There is currently a known issue with guest instances that use Mellanox Connect-X5 NICs with offload (switchdev) ports. It takes a long time to initialize the system when you reboot the operating system from the guest directly, for example, by using the command `sudo systemctl reboot --reboot-arg=now`. If the VM is configured with two Virtual Functions (VFs) from the same Physical Function (PF), the initialization of one of the VFs might fail and cause a longer initialization time. Workaround: Reboot the guest instance in a timely manner by using the OpenStack API instead of rebooting the guest instance directly. | There is currently a known issue with guest instances that use Mellanox Connect-X5 and Bluefield-2 Connect-X6 NICs with offload (switchdev) ports. It takes a long time to initialize the system when you reboot the operating system from the guest directly, for example, by using the command `sudo systemctl reboot --reboot-arg=now`. If the VM is configured with two Virtual Functions (VFs) from the same Physical Function (PF), the initialization of one of the VFs might fail and cause a longer initialization time. Workaround: Reboot the guest instance in a timely manner by using the OpenStack API instead of rebooting the guest instance directly. |
| James Smith | 2023-06-15 13:22:07 UTC | Summary | [17.1][OVN HWOFFLOAD][CX5 & Bluefield-2 CX6] Vms with offload vfs takes a long time to boot up | [17.1][OVN HWOFFLOAD][CX-5, CX-6 & Bluefield-2] Vms with offload vfs takes a long time to boot up |
| Doc Text | There is currently a known issue with guest instances that use Mellanox Connect-X5 and Bluefield-2 Connect-X6 NICs with offload (switchdev) ports. It takes a long time to initialize the system when you reboot the operating system from the guest directly, for example, by using the command `sudo systemctl reboot --reboot-arg=now`. If the VM is configured with two Virtual Functions (VFs) from the same Physical Function (PF), the initialization of one of the VFs might fail and cause a longer initialization time. Workaround: Reboot the guest instance in a timely manner by using the OpenStack API instead of rebooting the guest instance directly. | There is currently a known issue with guest instances that use Mellanox ConnectX-5, ConnectX-6, and Bluefield-2 NICs with offload (switchdev) ports. It takes a long time to initialize the system when you reboot the operating system from the guest directly, for example, by using the command `sudo systemctl reboot --reboot-arg=now`. If the VM is configured with two Virtual Functions (VFs) from the same Physical Function (PF), the initialization of one of the VFs might fail and cause a longer initialization time. Workaround: Reboot the guest instance in a timely manner by using the OpenStack API instead of rebooting the guest instance directly. | ||
| Gurpreet Singh | 2023-06-21 18:40:06 UTC | CC | gurpsing | |
| Flags | needinfo?(hakhande) | |||
| Haresh Khandelwal | 2023-06-22 09:40:11 UTC | Flags | needinfo?(hakhande) | |
| Eran Kuris | 2023-06-22 10:29:31 UTC | Flags | needinfo?(gurpsing) | |
| Gurpreet Singh | 2023-06-22 10:48:44 UTC | Target Milestone | ga | z1 |
| Eran Kuris | 2023-06-27 08:56:11 UTC | Summary | [17.1][OVN HWOFFLOAD][CX-5, CX-6 & Bluefield-2] Vms with offload vfs takes a long time to boot up | [17.1][OVN HWOFFLOAD][CX-5, CX-6 & Bluefield-2] Vms with offload vfs takes a long time to boot up [10 min+] |
| Eran Kuris | 2023-06-27 11:26:55 UTC | Blocks | 2172622 | |
| Depends On | 2172622 | |||
| Eran Kuris | 2023-06-28 12:27:53 UTC | Depends On | 2217881 | |
| Gurpreet Singh | 2023-06-28 14:54:44 UTC | Flags | needinfo?(gurpsing) | needinfo- |
| Paul Grist | 2023-06-29 17:16:35 UTC | CC | pgrist | |
| Eran Kuris | 2023-07-11 09:56:49 UTC | Status | ASSIGNED | MODIFIED |
| Eran Kuris | 2023-07-11 13:08:42 UTC | Target Milestone | z1 | ga |
| errata-xmlrpc | 2023-07-12 12:00:32 UTC | Status | MODIFIED | ON_QA |
| Jenny-Anne Lynch | 2023-07-12 13:57:10 UTC | CC | jelynch | |
| Eran Kuris | 2023-07-13 09:27:56 UTC | QA Contact | ekuris | mnietoji |
| Miguel Angel Nieto | 2023-07-14 08:25:05 UTC | Status | ON_QA | VERIFIED |
| Ian Frangs | 2023-08-03 15:46:23 UTC | Flags | needinfo?(hakhande) | |
| Haresh Khandelwal | 2023-08-04 12:14:16 UTC | Flags | needinfo?(hakhande) | |
| Ian Frangs | 2023-08-11 11:38:48 UTC | CC | ifrangs | |
| Doc Text | There is currently a known issue with guest instances that use Mellanox ConnectX-5, ConnectX-6, and Bluefield-2 NICs with offload (switchdev) ports. It takes a long time to initialize the system when you reboot the operating system from the guest directly, for example, by using the command `sudo systemctl reboot --reboot-arg=now`. If the VM is configured with two Virtual Functions (VFs) from the same Physical Function (PF), the initialization of one of the VFs might fail and cause a longer initialization time. Workaround: Reboot the guest instance in a timely manner by using the OpenStack API instead of rebooting the guest instance directly. | There is currently a known issue with guest instances that use Mellanox ConnectX-5, ConnectX-6, and Bluefield-2 NICs with offload (switchdev) ports. It takes a long time to initialize the system when you reboot the operating system from the guest directly, for example, by using the command `sudo systemctl reboot --reboot-arg=now`. If the instance is configured with two Virtual Functions (VFs) from the same Physical Function (PF), the initialization of one of the VFs might fail and cause a longer initialization time. Workaround: Reboot the guest instance in a timely manner by using the OpenStack API instead of rebooting the guest instance directly. | ||
| Ian Frangs | 2023-08-11 16:08:49 UTC | CC | ifrangs | |
| Doc Text | There is currently a known issue with guest instances that use Mellanox ConnectX-5, ConnectX-6, and Bluefield-2 NICs with offload (switchdev) ports. It takes a long time to initialize the system when you reboot the operating system from the guest directly, for example, by using the command `sudo systemctl reboot --reboot-arg=now`. If the instance is configured with two Virtual Functions (VFs) from the same Physical Function (PF), the initialization of one of the VFs might fail and cause a longer initialization time. Workaround: Reboot the guest instance in a timely manner by using the OpenStack API instead of rebooting the guest instance directly. | There is currently a known issue with guest instances that use Mellanox ConnectX-5, ConnectX-6, and Bluefield-2 NICs with offload (switchdev) ports. It takes a long time to initialize the system when you reboot the operating system from the guest directly, for example, by using the command `sudo systemctl reboot --reboot-arg=now`. If the instance is configured with two Virtual Functions (VFs) from the same Physical Function (PF), the initialization of one of the VFs might fail and cause a longer initialization time. + Workaround: Reboot the guest instance in a timely manner by using the OpenStack API instead of rebooting the guest instance directly. |
||
| James Smith | 2023-08-15 18:29:22 UTC | Flags | needinfo?(hakhande) | |
| errata-xmlrpc | 2023-08-16 00:02:16 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-08-16 01:14:34 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2023-08-16 01:14:34 UTC | |||
| errata-xmlrpc | 2023-08-16 01:15:11 UTC | Link ID | Red Hat Product Errata RHEA-2023:4577 |
Back to bug 2182371