Skip to content

[release-4.16] OCPBUGS-43967: Revendor assisted service external platform oci#9150

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.16from
pawanpinjarkar:cherrypick-revendor-assisted-service-external-platform-oci-4.17
Nov 7, 2024
Merged

[release-4.16] OCPBUGS-43967: Revendor assisted service external platform oci#9150
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.16from
pawanpinjarkar:cherrypick-revendor-assisted-service-external-platform-oci-4.17

Conversation

@pawanpinjarkar
Copy link
Copy Markdown
Contributor

Manual cherry-pick of #9147

@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 Oct 29, 2024
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@pawanpinjarkar: This pull request references Jira Issue OCPBUGS-43967, which is invalid:

  • expected Jira Issue OCPBUGS-43967 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

Manual cherry-pick of #9147

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.

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@pawanpinjarkar: This pull request references Jira Issue OCPBUGS-43967, which is invalid:

  • expected dependent Jira Issue OCPBUGS-43897 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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 openshift-eng/jira-lifecycle-plugin repository.

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/retest-required

@bfournie
Copy link
Copy Markdown
Contributor

bfournie commented Nov 5, 2024

I'm wondering why verify-vendor is failing. It doesn't look like a sporadic issue.

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/retest-required

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Nov 5, 2024

@pawanpinjarkar: 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/okd-scos-e2e-vsphere-ovn 51a68e0 link false /test okd-scos-e2e-vsphere-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-sigs/prow repository. I understand the commands that are listed here.

@bfournie
Copy link
Copy Markdown
Contributor

bfournie commented Nov 5, 2024

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Nov 5, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bfournie

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 Nov 5, 2024
@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 6, 2024
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@pawanpinjarkar: This pull request references Jira Issue OCPBUGS-43967, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.z) matches configured target version for branch (4.16.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-43897 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-43897 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
  • bug has dependents

Requesting review from QA contact:
/cc @mhanss

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot requested a review from mhanss November 6, 2024 15:51
@zaneb
Copy link
Copy Markdown
Member

zaneb commented Nov 6, 2024

This is revendoring to the same commit as the 4.17 PR, which is presumably in the 4.17 (or worse, 4.18) branch. That seems risky to me as it will pick up far more commits than we are intending, with unknown consequences.
What is that patch that we actually need? It would be safer to backport that patch to the 4.16 branch of assisted-installer and then rebase to that.

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

This is revendoring to the same commit as the 4.17 PR, which is presumably in the 4.17 (or worse, 4.18) branch. That seems risky to me as it will pick up far more commits than we are intending, with unknown consequences. What is that patch that we actually need? It would be safer to backport that patch to the 4.16 branch of assisted-installer and then rebase to that.

in 4.17 PR, we only revendored this specific commit openshift/assisted-service@d41f536

If it is safer to not cherrypick from 4.17 but do a seperate revendoring of assisted-service in 4.16 (this specific commit openshift/assisted-service@d41f536 ), I can close this PR and open a new one.

@zaneb
Copy link
Copy Markdown
Member

zaneb commented Nov 7, 2024

The specific point we are revendoring to (openshift/assisted-service@6573b5d7021d) is already part of the release-4.16 branch, so we are not pulling in any changes to assisted-service that post-date this release. A manual review of the diff shows nothing too alarming.
/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Nov 7, 2024
@mhanss
Copy link
Copy Markdown
Contributor

mhanss commented Nov 7, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci Bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Nov 7, 2024
@rwsu
Copy link
Copy Markdown
Contributor

rwsu commented Nov 7, 2024

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Nov 7, 2024
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD edf5606 and 2 for PR HEAD 51a68e0 in total

@openshift-merge-bot openshift-merge-bot Bot merged commit f12bc39 into openshift:release-4.16 Nov 7, 2024
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@pawanpinjarkar: Jira Issue OCPBUGS-43967: All pull requests linked via external trackers have merged:

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

Details

In response to this:

Manual cherry-pick of #9147

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-bot
Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-baremetal-installer
This PR has been included in build ose-baremetal-installer-container-v4.16.0-202411080236.p0.gf12bc39.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-altinfra
This PR has been included in build ose-installer-altinfra-container-v4.16.0-202411080236.p0.gf12bc39.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-terraform-providers
This PR has been included in build ose-installer-terraform-providers-container-v4.16.0-202411080236.p0.gf12bc39.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-artifacts
This PR has been included in build ose-installer-artifacts-container-v4.16.0-202411080236.p0.gf12bc39.assembly.stream.el9.
All builds following this will include this PR.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.

7 participants