Skip to content

AGENT-1303: Wait for cluster creation when creating InfraEnv#8007

Closed
zaneb wants to merge 2 commits intoopenshift:masterfrom
zaneb:wait-for-cluster
Closed

AGENT-1303: Wait for cluster creation when creating InfraEnv#8007
zaneb wants to merge 2 commits intoopenshift:masterfrom
zaneb:wait-for-cluster

Conversation

@zaneb
Copy link
Member

@zaneb zaneb commented Sep 12, 2025

When creating the InfraEnv in ABI, instead of exiting with an error if the Cluster has not been created, poll the API until it is. Previously we would exit with an error code and systemd would restart the whole process instead.

The 'register' command has long since been split into separate
'registerCluster' and 'registerInfraEnv' phases, so the duplicate code
can be removed.
In an interactive workflow the user interacting with the UI creates the
Cluster object in the database; however, we wish to use the same client
to register the InfraEnv as in the ABI flow. To enable this, when
registering the InfraEnv wait until the Cluster has been created, since
in the future this may happen asynchronously. Previously we returned an
error and systemd would have restarted the service.
@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 12, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 12, 2025

@zaneb: This pull request references AGENT-1303 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.

Details

In response to this:

When creating the InfraEnv in ABI, instead of exiting with an error if the Cluster has not been created, poll the API until it is. Previously we would exit with an error code and systemd would restart the whole process instead.

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 openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Sep 12, 2025
@openshift-ci openshift-ci bot requested review from celebdor and rwsu September 12, 2025 12:51
@openshift-ci
Copy link

openshift-ci bot commented Sep 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zaneb

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

The pull request process is described here

Details 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 12, 2025
@zaneb
Copy link
Member Author

zaneb commented Sep 22, 2025

/retest

@codecov
Copy link

codecov bot commented Sep 22, 2025

Codecov Report

❌ Patch coverage is 0% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 73.78%. Comparing base (cab6cc9) to head (b47f047).
⚠️ Report is 15 commits behind head on master.

Files with missing lines Patch % Lines
cmd/agentbasedinstaller/client/main.go 0.00% 8 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #8007      +/-   ##
==========================================
+ Coverage   73.68%   73.78%   +0.09%     
==========================================
  Files         400      403       +3     
  Lines       68657    69155     +498     
==========================================
+ Hits        50587    51023     +436     
- Misses      15356    15394      +38     
- Partials     2714     2738      +24     
Files with missing lines Coverage Δ
cmd/agentbasedinstaller/client/main.go 0.00% <0.00%> (ø)

... and 16 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@openshift-ci
Copy link

openshift-ci bot commented Sep 22, 2025

@zaneb: 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-subsystem-kubeapi-aws b47f047 link true /test edge-subsystem-kubeapi-aws

Full PR test history. Your PR dashboard.

Details

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.

@zaneb
Copy link
Member Author

zaneb commented Sep 24, 2025

/close
Closing in favour of #8059

@openshift-ci openshift-ci bot closed this Sep 24, 2025
@openshift-ci
Copy link

openshift-ci bot commented Sep 24, 2025

@zaneb: Closed this PR.

Details

In response to this:

/close
Closing in favour of #8059

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants