Bug 1942094 - Network issue after hard shutdown of 2 controller nodes
Summary: Network issue after hard shutdown of 2 controller nodes
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 16.1 (Train)
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Terry Wilson
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-23 16:13 UTC by Luigi Tamagnone
Modified: 2022-08-30 14:39 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-01 20:23:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-1466 0 None None None 2022-08-30 14:39:43 UTC

Description Luigi Tamagnone 2021-03-23 16:13:48 UTC 
Description of problem:
During a disaster recovery test, the network environment seems to went in the wrong state. 

Version-Release number of selected component (if applicable):
[rhosp-release] Red Hat OpenStack Platform release 16.1.3 GA (Train)
[os-release] Red Hat Enterprise Linux 8.2 (Ootpa) 8.2 (Ootpa)

How reproducible:
Customer reproduced the DR test in their environment and after the hard shutdown and start of 2 controller nodes the network have always this issue, also if from overcloud perspective seems everything ok.

Steps to Reproduce:
1. hard shutdown a controller node 
2. hard shutdown a second controller nodes
3. start one controller node
4. start the other controller node
5. lunch an instance

Actual results:
Instance creation on some network failed

Expected results:
Instance creation success


Additional info:
SOSreport on case 02883588
Note You need to log in before you can comment on or make changes to this bug.