Bug 2222460 - [OSP13] ovs-vswitchd fails to start after compute reboot
Summary: [OSP13] ovs-vswitchd fails to start after compute reboot
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openvswitch
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: RHOSP:NFV_Eng
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-12 21:11 UTC by Flavio Piccioni
Modified: 2023-07-25 12:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-25 12:38:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-26559 0 None None None 2023-07-12 21:13:09 UTC

Description Flavio Piccioni 2023-07-12 21:11:40 UTC 
Description of problem:
customer rebooted a bunch of dpdk (3 bonds) computes for some maintenance (bios update).

One of them (compute 213) is failing to start network services due to ovs-vswitchd timing out during.
Tried to increase systemd unit from 5 mins to 10 for testing but no luck

Version-Release number of selected component (if applicable):
RHEL 7.6 - openvswitch 2.9.0-130.el7fdp.bz1845209.1 (same for other computes, too)

How reproducible:
reboot compute

Steps to Reproduce:
1. reboot compute
2. wait for ovs-vswitchd to timeout

Actual results:
network services are failing to start.

Additional info:
Problems seems matching [0] but other rebooted and healthy computes are not running any systemd unit tuning at all.


[0] https://access.redhat.com/solutions/3538621
Comment 3 Lukas Svaty 2023-07-18 10:36:27 UTC 
OSP13 is EOL, closing, if you believe this reproduces in newer versions feel free to reopen on 16.2 or 17.1
Comment 5 Lukas Svaty 2023-07-18 11:32:21 UTC 
Hi Flavio, thanks for the quick turnaround on this one, reopening.
Note You need to log in before you can comment on or make changes to this bug.