This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2239560 - MHC: services within the node did not restart.
Summary: MHC: services within the node did not restart.
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Infrastructure
Version: 4.14.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Dominik Holler
QA Contact: Shijie Xue
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-09-19 03:18 UTC by Shijie Xue
Modified: 2023-12-14 16:05 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-12-14 16:05:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
log details (4.24 MB, application/zip)
2023-09-19 03:18 UTC, Shijie Xue 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   CNV-33030 0 None None None 2023-12-14 16:05:34 UTC

Description Shijie Xue 2023-09-19 03:18:28 UTC 
Created attachment 1989502 [details]
log details

Description of problem:
After MHC did the remediation, sometimes two services（crio wipe. service, NetworkManager wait online. service） within the node did not restart correctly.
Version-Release number of selected component (if applicable):

How reproducible:
https://code.engineering.redhat.com/gerrit/c/cnv-tests/+/446329
About 1/6 of the probability
Steps to Reproduce:
1.pytest -s cnv-tests/tests/compute/fencing/ha_vm/test_ha_vm.py 
2.
3.

Actual results:
The services within the node failed to restart, resulting in POD running failure.

Expected results:
After test, all pods are healthy.

Additional info:
https://privatebin.corp.redhat.com/?3c93087f669bedf8#7TWq93kiGrqikAUyYc3T9tPmvh9VyfLkZiRJpBqA9rLt
Note You need to log in before you can comment on or make changes to this bug.