-
Notifications
You must be signed in to change notification settings - Fork 255
AGENT-1303: Allow InfraEnv registration to use late binding #8059
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
Merged
openshift-merge-bot
merged 3 commits into
openshift:master
from
zaneb:infra-env-late-binding
Oct 18, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried a POC including this PR and openshift/installer#9960 This works fine such that now first the infra-env is created and cluster object is only attempted to be created when in case of OVE, user enters details such as name, basedomain, pull-secret etc from the first page and hits next button. At that time, assisted service does throw an error here because the infra-env was already created. -
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case, it should first check if infra-env is already created
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agent-register-infraenv.serviceThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is expected with the current UI implementation, because in ABI we define the InfraEnv UUID at ISO generation time (it's passed as an env var to assisted-service). That shouldn't block merging of this PR because this one has no effect in practice by itself.
However, before merging openshift/installer#9960 we will need to update the UI to cope with this flow. To start with, having the UI check for the existence of an InfraEnv before creating a new one would allow you to get a bit further with the PoC.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pawanpinjarkar the main goal of the PoC is to support designing a solution for https://issues.redhat.com/browse/AGENT-1294, and thus identify a gap list - to prepare a breakdown for the epic. I also didn't expect that the UI worked out-of-the-box, and the good thing is that the PoC confirmed that - so another point for the gap list.
A quick hack to proceed with the exploration in the PoC is to disable the UI and manually simulate its behavior by directly interacting with AS after the agent-register-infraenv service (with the basic idea of supporting just one workflow, where instead of running the
start-cluster-installationservice then theagent-start-uiis executed (when requested)