New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MGMT-12552: Day-2 agent stuck with status_info rebooting although the node is already part of the cluster #4610
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: eranco74 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
… node is already part of the cluster The following applies to kube-API only The host UpdateInstallProgress will not update day-2 hosts to HostStatusAddedToExistingCluster if the host stage is Rebooting. The host UpdateInstallProgress will update day-2 hosts to HostStatusAddedToExistingCluster if the host stage is Done The agent controller will keep updateing day-2 agents if the agent stage is Rebooting, Configuring or Joined.
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #4610 +/- ##
==========================================
+ Coverage 67.07% 67.10% +0.02%
==========================================
Files 199 200 +1
Lines 28062 28086 +24
==========================================
+ Hits 18823 18847 +24
- Misses 7556 7557 +1
+ Partials 1683 1682 -1
|
/lgtm |
/retest-required |
/override edge-e2e-metal-assisted-capi |
@eranco74: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@eranco74: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
operator-ztp seems flakey:
/retest-required |
… node is already part of the cluster (openshift#4610) The following applies to kube-API only The host UpdateInstallProgress will not update day-2 hosts to HostStatusAddedToExistingCluster if the host stage is Rebooting. The host UpdateInstallProgress will update day-2 hosts to HostStatusAddedToExistingCluster if the host stage is Done The agent controller will keep updateing day-2 agents if the agent stage is Rebooting, Configuring or Joined.
The following applies to kube-API only:
The host UpdateInstallProgress will not update day-2 hosts to HostStatusAddedToExistingCluster if the host stage is Rebooting. The host UpdateInstallProgress will update day-2 hosts to HostStatusAddedToExistingCluster if the host stage is Done The agent controller will keep updateing day-2 agents if the agent stage is Rebooting, Configuring or Joined.
-->
List all the issues related to this PR
https://issues.redhat.com/browse/MGMT-12552
What environments does this code impact?
How was this code tested?
Checklist
docs
, README, etc)Reviewers Checklist