Skip to content

Conversation

@JoelSpeed
Copy link
Contributor

What this PR does / why we need it:

MCO recently introduced a new flag --payload-version that expects to take the payload release version as a value. This is currently inert but will be required once openshift/machine-config-operator#3688 is merged.
This was added to the installer in openshift/installer#7160.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

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

@JoelSpeed: This pull request references Jira Issue OCPBUGS-13547, 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 @sunzhaohua2

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

Details

In response to this:

What this PR does / why we need it:

MCO recently introduced a new flag --payload-version that expects to take the payload release version as a value. This is currently inert but will be required once openshift/machine-config-operator#3688 is merged.
This was added to the installer in openshift/installer#7160.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

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 requested a review from sunzhaohua2 May 17, 2023 15:51
@openshift-ci openshift-ci bot requested review from enxebre and sjenning May 17, 2023 15:52
@openshift-ci openshift-ci bot added area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release and removed do-not-merge/needs-area labels May 17, 2023
fmt.Sprintf("--pull-secret=%s/pull-secret.yaml", configDir),
fmt.Sprintf("--dest-dir=%s", destDir),
fmt.Sprintf("--additional-trust-bundle-config-file=%s/user-ca-bundle-config.yaml", configDir),
fmt.Sprintf("--payload-version=%s", releaseVersion),
Copy link
Contributor

Choose a reason for hiding this comment

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

you can just use imageProvider.Version() here and the previous changes are not required

@csrwng
Copy link
Contributor

csrwng commented May 17, 2023

/approve

The mcoBootstrapScript is a codepath we no longer use, so we should eventually remove it.

@JoelSpeed JoelSpeed force-pushed the mco-payload-version branch from f07780e to 9e225af Compare May 17, 2023 15:58
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 17, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: csrwng, JoelSpeed

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 May 17, 2023
@JoelSpeed
Copy link
Contributor Author

/test verify

@enxebre
Copy link
Member

enxebre commented May 18, 2023

capturing slack discussion:
For the nodepool upgrade test we boot them from PreviousReleaseImage.. There's a precedent for the same problematic scenario where MCO flags are not backward compatible #1781.
We need to consolidate this new flag with that code some how, e.g. continue with the fallback approach or may be having specific versions checks. Also we need to raise this to MCO so they can consider new flags to not be that disruptive.
Let's include a version check for now and then sync with mco to explore making new flags less disruptive.

lgtm

@JoelSpeed JoelSpeed force-pushed the mco-payload-version branch from 603fb9a to 54b9bad Compare May 18, 2023 13:43
@JoelSpeed
Copy link
Contributor Author

Looks to me like the API server went down for a bit during this test, not sure if this is expected to pass or not, will retest
/test e2e-kubevirt-aws-ovn

@csrwng
Copy link
Contributor

csrwng commented May 18, 2023

/lgtm
thx!

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

/retest-required

Remaining retests: 0 against base HEAD 2bbe22d and 2 for PR HEAD 54b9bad in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 19, 2023

@JoelSpeed: 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/e2e-kubevirt-aws-ovn 54b9bad link false /test e2e-kubevirt-aws-ovn

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 b2daa64 into openshift:main May 19, 2023
@openshift-ci-robot
Copy link

@JoelSpeed: Jira Issue OCPBUGS-13547: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

Details

In response to this:

What this PR does / why we need it:

MCO recently introduced a new flag --payload-version that expects to take the payload release version as a value. This is currently inert but will be required once openshift/machine-config-operator#3688 is merged.
This was added to the installer in openshift/installer#7160.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

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. area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid 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