Bug 2102011
| Summary: | [IPI on Alibabacloud] cluster operators "network" and "kube-apiserver" turned degraded after rebooting each node of the cluster | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jianli Wei <jiwei> | ||||
| Component: | kube-apiserver | Assignee: | Abu Kashem <akashem> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Ke Wang <kewang> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.11 | CC: | gpei, jialiu, kewang, mfojtik, wlewis, xxia | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Known Issue | |||||
| Doc Text: |
Cause: After rebooting each cluster node.
Consequence: The cluster operators "network" and "kube-apiserver" turned into degraded.
Workaround (if any): n/a
Result: The cluster turns unhealthy.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-01-16 11:33:33 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Jianli Wei
2022-06-29 06:14:08 UTC
- does this happen with (4.10, alibaba)? I want to know if this is a regression. - can you confirm that this is "Always" reproducible - have you found any workaround that resolves the issue? I am setting blocker- for now until we determine this is impacting a broader set of platforms and occurs more frequently. (In reply to Abu Kashem from comment #1) > - does this happen with (4.10, alibaba)? I want to know if this is a > regression. > - can you confirm that this is "Always" reproducible > - have you found any workaround that resolves the issue? No such issue with 4.10 on alibaba, see below (from the original description) >FYI We also tried the scenario with 4.10.20-x86_64, where no such issue. >FYI We also tried the scenario with 4.11.0-0.nightly-2022-06-28-160049 on GCP, where no such issue. Yes, we tried multiple times and met the issue every time. We did not find any workaround so far. Dear reporter, we greatly appreciate the bug you have reported here. Unfortunately, due to migration to a new issue-tracking system (https://issues.redhat.com/), we cannot continue triaging bugs reported in Bugzilla. Since this bug has been stale for multiple days, we, therefore, decided to close this bug. If you think this is a mistake or this bug has a higher priority or severity as set today, please feel free to reopen this bug and tell us why. We are going to move every re-opened bug to https://issues.redhat.com. Thank you for your patience and understanding. |