Skip to content
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

OCPBUGS-41811: (agent-based installer) let the bootstrap wait for workers before the reboot #910

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

andfasano
Copy link

As described by the analysis in https://issues.redhat.com/browse/OCPBUGS-41811, in some cases the bootstrap node may reboot before the workers started the joining process, thus removing the assisted-service that it's still required by the workers. This prevents the worker to successfully join the cluster, causing the failure of the cluster deployment.

This patch introduces an explicit synchronization between the bootstrap node and the workers (only in case the installation was performed via the agent-based installer), delaying the bootstrap reboot until all the workers passed the waiting for control plane stage.

In some cases the bootstrap node may reboot before the workers started the joining process, thus removing the assisted-service that it's still required by the workers
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 25, 2024
@openshift-ci-robot
Copy link

@andfasano: This pull request references Jira Issue OCPBUGS-41811, which is invalid:

  • expected the bug to target the "4.18.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

As described by the analysis in https://issues.redhat.com/browse/OCPBUGS-41811, in some cases the bootstrap node may reboot before the workers started the joining process, thus removing the assisted-service that it's still required by the workers. This prevents the worker to successfully join the cluster, causing the failure of the cluster deployment.

This patch introduces an explicit synchronization between the bootstrap node and the workers (only in case the installation was performed via the agent-based installer), delaying the bootstrap reboot until all the workers passed the waiting for control plane stage.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 25, 2024
@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Sep 25, 2024
Copy link

openshift-ci bot commented Sep 25, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: andfasano
Once this PR has been reviewed and has the lgtm label, please assign jhernand for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@andfasano
Copy link
Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 25, 2024
@openshift-ci-robot
Copy link

@andfasano: This pull request references Jira Issue OCPBUGS-41811, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @anuragthehatter

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@andfasano
Copy link
Author

/test ?

Copy link

openshift-ci bot commented Sep 25, 2024

@andfasano: The following commands are available to trigger required jobs:

  • /test e2e-agent-compact-ipv4
  • /test edge-e2e-ai-operator-ztp
  • /test edge-e2e-metal-assisted
  • /test edge-format-check
  • /test edge-images
  • /test edge-lint
  • /test edge-unit-test
  • /test images
  • /test mce-images

The following commands are available to trigger optional jobs:

  • /test e2e-agent-ha-dualstack
  • /test e2e-agent-sno-ipv6
  • /test edge-e2e-metal-assisted-cnv-4-16
  • /test edge-e2e-metal-assisted-external
  • /test edge-e2e-metal-assisted-ipv6
  • /test edge-e2e-metal-assisted-lvm
  • /test edge-e2e-metal-assisted-odf-4-16
  • /test edge-e2e-metal-assisted-single-node
  • /test edge-e2e-oci-assisted
  • /test edge-e2e-oci-assisted-4-16
  • /test edge-e2e-vsphere-assisted
  • /test edge-e2e-vsphere-assisted-4-16
  • /test edge-publish-multi-arch-images-dry-run
  • /test okd-scos-images

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-assisted-installer-master-e2e-agent-compact-ipv4
  • pull-ci-openshift-assisted-installer-master-edge-e2e-ai-operator-ztp
  • pull-ci-openshift-assisted-installer-master-edge-e2e-metal-assisted
  • pull-ci-openshift-assisted-installer-master-edge-e2e-metal-assisted-cnv-4-16
  • pull-ci-openshift-assisted-installer-master-edge-e2e-metal-assisted-odf-4-16
  • pull-ci-openshift-assisted-installer-master-edge-format-check
  • pull-ci-openshift-assisted-installer-master-edge-images
  • pull-ci-openshift-assisted-installer-master-edge-lint
  • pull-ci-openshift-assisted-installer-master-edge-unit-test
  • pull-ci-openshift-assisted-installer-master-images
  • pull-ci-openshift-assisted-installer-master-mce-images

In response to this:

/test ?

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-sigs/prow repository.

@andfasano
Copy link
Author

/test e2e-agent-ha-dualstack
/test e2e-agent-sno-ipv6

Copy link

codecov bot commented Sep 25, 2024

Codecov Report

Attention: Patch coverage is 43.47826% with 13 lines in your changes missing coverage. Please review.

Project coverage is 55.61%. Comparing base (2bb58e1) to head (8c89da4).

Files with missing lines Patch % Lines
src/installer/installer.go 43.47% 8 Missing and 5 partials ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #910      +/-   ##
==========================================
- Coverage   55.70%   55.61%   -0.09%     
==========================================
  Files          15       15              
  Lines        3208     3231      +23     
==========================================
+ Hits         1787     1797      +10     
- Misses       1249     1257       +8     
- Partials      172      177       +5     
Flag Coverage Δ
55.61% <43.47%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
src/installer/installer.go 68.13% <43.47%> (-1.01%) ⬇️

@andfasano
Copy link
Author

/test e2e-agent-ha-dualstack
/test e2e-agent-sno-ipv6

1 similar comment
@andfasano
Copy link
Author

/test e2e-agent-ha-dualstack
/test e2e-agent-sno-ipv6

Copy link

openshift-ci bot commented Sep 26, 2024

@andfasano: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/edge-e2e-ai-operator-ztp 8c89da4 link true /test edge-e2e-ai-operator-ztp

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-sigs/prow repository. I understand the commands that are listed here.

@andfasano
Copy link
Author

/test e2e-agent-ha-dualstack
/test e2e-agent-sno-ipv6

return true
}

i.log.Infof("Found %d workers, verifying their current installation stage", len(workers))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From just reading the log output, it is unclear what the wait is for. Perhaps change this log message to indicate that we are waiting for the worker to reach reboot.

Suggested change
i.log.Infof("Found %d workers, verifying their current installation stage", len(workers))
i.log.Infof("Found %d workers, waiting for workers to reach reboot stage", len(workers))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants