Skip to content

Conversation

@rwsu
Copy link
Contributor

@rwsu rwsu commented Aug 10, 2023

Adds a validation check to ensure that MachineAPI capability is included for IPI deployments.

@openshift-ci-robot openshift-ci-robot added the jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. label Aug 10, 2023
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 10, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 10, 2023

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 10, 2023
@openshift-ci-robot
Copy link
Contributor

@rwsu: This pull request references Jira Issue OCPBUGS-15659, which is invalid:

  • expected the bug to target the "4.14.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.

Details

In response to this:

replicas is > 0.

Adds a validation check to ensure that MachineAPI capability is included for the cluster when the number of compute replicas is greater than 0.

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.

@rwsu
Copy link
Contributor Author

rwsu commented Aug 10, 2023

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@rwsu: This pull request references Jira Issue OCPBUGS-15659, which is invalid:

  • expected the bug to target the "4.14.0" version, but it targets "4.14" instead

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.

Details

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 kubernetes/test-infra repository.

@rwsu
Copy link
Contributor Author

rwsu commented Aug 10, 2023

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Aug 10, 2023
@openshift-ci-robot
Copy link
Contributor

@rwsu: This pull request references Jira Issue OCPBUGS-15659, 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.14.0) matches configured target version for branch (4.14.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jinyunma

Details

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 kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 10, 2023
@openshift-ci openshift-ci bot requested a review from jinyunma August 10, 2023 03:08
Copy link
Contributor

@patrickdillon patrickdillon left a comment

Choose a reason for hiding this comment

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

/approve

Copy link
Contributor

Choose a reason for hiding this comment

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

can you move this into its own import block preceding this one? I believe this will actually cause unit tests to fail (otherwise I would consider it a nit): https://github.com/openshift/installer/blob/master/CONTRIBUTING.md#import-order

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 14, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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 Aug 14, 2023
@rwsu rwsu marked this pull request as ready for review August 15, 2023 23:33
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 15, 2023
@openshift-ci openshift-ci bot requested review from andfasano and sadasu August 15, 2023 23:33
@jinyunma
Copy link
Contributor

@rwsu FYI. MachineAPI is required on IPI including IPI SON, IPI compact and common IPI (3 masters + N workers). It only can be disabled in UPI cluster.
Discussion is here.

Adds a validation check for IPI to ensure that MachineAPI capability is
included for the cluster.
@rwsu rwsu changed the title OCPBUGS-15659: IPI pre-check for MachineAPI capability when compute OCPBUGS-15659: IPI pre-check for MachineAPI capability Aug 22, 2023
@openshift-ci-robot
Copy link
Contributor

@rwsu: This pull request references Jira Issue OCPBUGS-15659, which is valid.

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

Requesting review from QA contact:
/cc @jinyunma

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

Details

In response to this:

Adds a validation check to ensure that MachineAPI capability is included for IPI deployments.

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.

@rwsu
Copy link
Contributor Author

rwsu commented Aug 22, 2023

/retest-required

2 similar comments
@rwsu
Copy link
Contributor Author

rwsu commented Aug 22, 2023

/retest-required

@rwsu
Copy link
Contributor Author

rwsu commented Aug 23, 2023

/retest-required

@bfournie
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 25, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 25, 2023

@rwsu: all tests passed!

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

@openshift-merge-robot openshift-merge-robot merged commit 41e3c2e into openshift:master Aug 25, 2023
@openshift-ci-robot
Copy link
Contributor

@rwsu: Jira Issue OCPBUGS-15659: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-15659 has been moved to the MODIFIED state.

Details

In response to this:

Adds a validation check to ensure that MachineAPI capability is included for IPI deployments.

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.

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/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. 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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants