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

AGENT-557: Split register into registerCluster and registerInfraEnv #5376

Merged
merged 1 commit into from Jul 28, 2023

Conversation

rwsu
Copy link
Contributor

@rwsu rwsu commented Jul 21, 2023

The split is desired to enable the interactive flow. Users will register the cluster through the GUI instead of including the cluster information in the ignition/agent ISO.

registerCluster is able to detect if a cluster has already been registered with the REST-API and exits with status 0, skipping cluster registration from manifest files.

registerInfraEnv requires and checks that a cluster has been registered with the REST-API. It also skips infraenv registration if it detects one has already been created.

List all the issues related to this PR

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • [] None

How was this code tested?

  • assisted-test-infra environment
  • dev-scripts environment
  • Reviewer's test appreciated
  • Waiting for CI to do a full test run
  • Manual (Elaborate on how it was tested)
  • No tests needed

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)
  • Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 21, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 21, 2023

@rwsu: This pull request references AGENT-557 which is a valid jira issue.

In response to this:

The split is desired to enable the interactive flow. Users will register the cluster through the GUI instead of including the cluster information in the ignition/agent ISO.

registerCluster is able to detect if a cluster has already been registered with the REST-API and exits with status 0, skipping cluster registration from manifest files.

registerInfraEnv requires and checks that a cluster has been registered with the REST-API. It also skips infraenv registration if it detects one has already been created.

List all the issues related to this PR

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • [] None

How was this code tested?

  • assisted-test-infra environment
  • dev-scripts environment
  • Reviewer's test appreciated
  • Waiting for CI to do a full test run
  • Manual (Elaborate on how it was tested)
  • No tests needed

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)
  • Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

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.

@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 21, 2023
@openshift-ci openshift-ci bot requested review from celebdor and zaneb July 21, 2023 20:11
@openshift-ci
Copy link

openshift-ci bot commented Jul 21, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rwsu

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 /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 Jul 21, 2023
@rwsu
Copy link
Contributor Author

rwsu commented Jul 21, 2023

@codecov
Copy link

codecov bot commented Jul 21, 2023

Codecov Report

Merging #5376 (97c32d4) into master (3756e7f) will increase coverage by 0.31%.
Report is 14 commits behind head on master.
The diff coverage is 0.00%.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #5376      +/-   ##
==========================================
+ Coverage   67.59%   67.90%   +0.31%     
==========================================
  Files         226      226              
  Lines       33304    34044     +740     
==========================================
+ Hits        22513    23119     +606     
- Misses       8758     8876     +118     
- Partials     2033     2049      +16     
Files Changed Coverage Δ
cmd/agentbasedinstaller/register.go 12.57% <0.00%> (-2.12%) ⬇️

... and 13 files with indirect coverage changes

The split is desired to enable the interactive flow.
Users will register the cluster through the GUI instead of including
the cluster information in the ignition/agent ISO.

registerCluster is able to detect if a cluster has already been
registered with the REST-API and exits with status 0, skipping
cluster registration from manifest files.

registerInfraEnv requires and checks that a cluster has been
registered with the REST-API. It also skips infraenv registration
if it detects one has already been created.

Signed-off-by: Richard Su <rwsu@redhat.com>
rwsu added a commit to rwsu/installer that referenced this pull request Jul 25, 2023
The service has been removed and split into
agent-register-cluster.service
agent-register-infraenv.service

Both services continuously retries until their respective resource
has been registered with the assisted-service REST-API or if the
client sees that a resource as already been registered.

Requires: openshift/assisted-service#5376
Signed-off-by: Richard Su <rwsu@redhat.com>
@rwsu
Copy link
Contributor Author

rwsu commented Jul 25, 2023

/retest-required

Copy link
Contributor

@pawanpinjarkar pawanpinjarkar left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 27, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 33855b7 and 2 for PR HEAD 97c32d4 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 5ad5976 and 1 for PR HEAD 97c32d4 in total

@rwsu
Copy link
Contributor Author

rwsu commented Jul 28, 2023

/test edge-subsystem-kubeapi-aws

@openshift-ci
Copy link

openshift-ci bot commented Jul 28, 2023

@rwsu: all tests passed!

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.

@openshift-merge-robot openshift-merge-robot merged commit bcd58c9 into openshift:master Jul 28, 2023
14 checks passed
rwsu added a commit to rwsu/installer that referenced this pull request Jul 31, 2023
The service has been removed and split into
agent-register-cluster.service
agent-register-infraenv.service

Both services continuously retries until their respective resource
has been registered with the assisted-service REST-API or if the
client sees that a resource as already been registered.

Requires: openshift/assisted-service#5376
Signed-off-by: Richard Su <rwsu@redhat.com>
CrystalChun pushed a commit to CrystalChun/assisted-service that referenced this pull request Aug 25, 2023
…penshift#5376)

The split is desired to enable the interactive flow.
Users will register the cluster through the GUI instead of including
the cluster information in the ignition/agent ISO.

registerCluster is able to detect if a cluster has already been
registered with the REST-API and exits with status 0, skipping
cluster registration from manifest files.

registerInfraEnv requires and checks that a cluster has been
registered with the REST-API. It also skips infraenv registration
if it detects one has already been created.

Signed-off-by: Richard Su <rwsu@redhat.com>
rwsu added a commit to rwsu/installer that referenced this pull request Oct 9, 2023
The service has been removed and split into
agent-register-cluster.service
agent-register-infraenv.service

Both services continuously retries until their respective resource
has been registered with the assisted-service REST-API or if the
client sees that a resource as already been registered.

Requires: openshift/assisted-service#5376
Signed-off-by: Richard Su <rwsu@redhat.com>
danielerez pushed a commit to danielerez/assisted-service that referenced this pull request Oct 15, 2023
…penshift#5376)

The split is desired to enable the interactive flow.
Users will register the cluster through the GUI instead of including
the cluster information in the ignition/agent ISO.

registerCluster is able to detect if a cluster has already been
registered with the REST-API and exits with status 0, skipping
cluster registration from manifest files.

registerInfraEnv requires and checks that a cluster has been
registered with the REST-API. It also skips infraenv registration
if it detects one has already been created.

Signed-off-by: Richard Su <rwsu@redhat.com>
rwsu added a commit to rwsu/installer that referenced this pull request Oct 20, 2023
The service has been removed and split into
agent-register-cluster.service
agent-register-infraenv.service

Both services continuously retries until their respective resource
has been registered with the assisted-service REST-API or if the
client sees that a resource as already been registered.

Requires: openshift/assisted-service#5376
Signed-off-by: Richard Su <rwsu@redhat.com>
rwsu added a commit to rwsu/installer that referenced this pull request Nov 1, 2023
The service has been removed and split into
agent-register-cluster.service
agent-register-infraenv.service

Both services continuously retries until their respective resource
has been registered with the assisted-service REST-API or if the
client sees that a resource as already been registered.

Requires: openshift/assisted-service#5376
Signed-off-by: Richard Su <rwsu@redhat.com>
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. lgtm Indicates that a PR is ready to be merged. 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.

None yet

4 participants