Skip to content

Conversation

@r4f4
Copy link
Contributor

@r4f4 r4f4 commented Mar 16, 2022

Co-authored-by: Joel Diaz [email protected]

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2022

@r4f4: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

stop considering Mint mode as supported on Azure (#5699)

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.

@r4f4
Copy link
Contributor Author

r4f4 commented Mar 16, 2022

/cherry-pick release-4.9
/cherry-pick release-4.8

@openshift-cherrypick-robot

@r4f4: once the present PR merges, I will cherry-pick it on top of release-4.9 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.9
/cherry-pick release-4.8

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 review from jhixson74 and rna-afk March 16, 2022 20:53
@patrickdillon
Copy link
Contributor

@r4f4 what you should do is create a bugzilla for #5699 and then cherry pick from that PR. The bot will create the needed bugzillas correctly. Let me know if I can help you with that.

@r4f4
Copy link
Contributor Author

r4f4 commented Mar 17, 2022

@r4f4 what you should do is create a bugzilla for #5699 and then cherry pick from that PR. The bot will create the needed bugzillas correctly. Let me know if I can help you with that.

@patrickdillon I tried cherry-picking from the PR but there are merge conflicts #5699 (comment). That's why I did the cherry-pick manually and submitted a new PR.

@patrickdillon
Copy link
Contributor

I tried cherry-picking from the PR but there are merge conflicts #5699 (comment). That's why I did the cherry-pick manually and submitted a new PR.

Got it, then this is correct. You will still need to create a BZ for the master branch for the cherry picks.

@r4f4 r4f4 changed the title stop considering Mint mode as supported on Azure (#5699) Bug 2065808: stop considering Mint mode as supported on Azure (#5699) Mar 18, 2022
@openshift-ci openshift-ci bot added bugzilla/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Mar 18, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 18, 2022

@r4f4: This pull request references Bugzilla bug 2065808, which is invalid:

  • expected dependent Bugzilla bug 2065806 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Bug 2065808: stop considering Mint mode as supported on Azure (#5699)

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.

@jianping-shu
Copy link

Verified with Flexy-install with the following LAUNCHER_VARS:
credentials_mode: "Mint"
installer_payload_image: registry.build01.ci.openshift.org/ci-ln-8wg6m9k/release:latest(build #5717)

The install failed with the following error info, Passed

03-21 11:00:13.294 [INFO] Generating manifests files.....
03-21 11:00:13.294 level=fatal msg=failed to fetch Master Machines: failed to load asset "Install Config": invalid "install-config.yaml" file: credentialsMode: Unsupported value: "Mint": supported values: "Manual", "Passthrough"

@jianping-shu
Copy link

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Mar 21, 2022
@jianping-shu
Copy link

/label cherry-pick-approved

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 21, 2022

@jianping-shu: Can not set label cherry-pick-approved: Must be member in one of these teams: []

Details

In response to this:

/label cherry-pick-approved

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.

@gpei
Copy link
Contributor

gpei commented Mar 21, 2022

/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 Mar 21, 2022
@r4f4
Copy link
Contributor Author

r4f4 commented Mar 21, 2022

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 21, 2022

@r4f4: This pull request references Bugzilla bug 2065808, which is invalid:

  • expected the bug to target the "4.10.z" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/bugzilla 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.

@r4f4
Copy link
Contributor Author

r4f4 commented Mar 21, 2022

/bugzilla refresh

@openshift-ci openshift-ci bot added bugzilla/severity-low Referenced Bugzilla bug's severity is low 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. and removed bugzilla/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Mar 21, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 21, 2022

@r4f4: This pull request references Bugzilla bug 2065808, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.10.z) matches configured target release for branch (4.10.z)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2065806 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2065806 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
  • bug has dependents

Requesting review from QA contact:
/cc @jianping-shu

Details

In response to this:

/bugzilla 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 openshift-ci bot requested a review from jianping-shu March 21, 2022 08:31
@jianping-shu
Copy link

Verification done, passed

@r4f4
Copy link
Contributor Author

r4f4 commented Mar 22, 2022

/assign @staebler

Copy link
Contributor

@staebler staebler left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve
/labal backport-risk-assessed

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 22, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 22, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: staebler

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 Mar 22, 2022
@staebler
Copy link
Contributor

/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 Mar 22, 2022
@r4f4
Copy link
Contributor Author

r4f4 commented Mar 22, 2022

/test e2e-aws

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

10 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 23, 2022

@r4f4: The following tests 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-crc db171bf link false /test e2e-crc
ci/prow/e2e-azurestack db171bf link false /test e2e-azurestack
ci/prow/okd-e2e-gcp db171bf link false /test okd-e2e-gcp
ci/prow/okd-e2e-gcp-upgrade db171bf link false /test okd-e2e-gcp-upgrade
ci/prow/e2e-openstack-kuryr db171bf link false /test e2e-openstack-kuryr
ci/prow/okd-e2e-aws-upgrade db171bf link false /test okd-e2e-aws-upgrade
ci/prow/e2e-alibaba db171bf link false /test e2e-alibaba
ci/prow/okd-e2e-vsphere db171bf link false /test okd-e2e-vsphere
ci/prow/e2e-ibmcloud db171bf link false /test e2e-ibmcloud
ci/prow/e2e-azurestack-upi db171bf link false /test e2e-azurestack-upi
ci/prow/e2e-azure-upi db171bf link false /test e2e-azure-upi

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

/retest-required

Please review the full test history for this PR and help us cut down flakes.

2 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 6e3ddd3 into openshift:release-4.10 Mar 23, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 23, 2022

@r4f4: All pull requests linked via external trackers have merged:

Bugzilla bug 2065808 has been moved to the MODIFIED state.

Details

In response to this:

Bug 2065808: stop considering Mint mode as supported on Azure (#5699)

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-cherrypick-robot

@r4f4: #5717 failed to apply on top of branch "release-4.9":

Applying: stop considering Mint mode as supported on Azure (#5699)
Using index info to reconstruct a base tree...
M	data/data/install.openshift.io_installconfigs.yaml
M	pkg/explain/printer_test.go
M	pkg/types/installconfig.go
M	pkg/types/validation/installconfig.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/types/validation/installconfig.go
Auto-merging pkg/types/installconfig.go
Auto-merging pkg/explain/printer_test.go
CONFLICT (content): Merge conflict in pkg/explain/printer_test.go
Auto-merging data/data/install.openshift.io_installconfigs.yaml
CONFLICT (content): Merge conflict in data/data/install.openshift.io_installconfigs.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 stop considering Mint mode as supported on Azure (#5699)
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherry-pick release-4.9
/cherry-pick release-4.8

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-cherrypick-robot

@r4f4: #5717 failed to apply on top of branch "release-4.8":

Applying: stop considering Mint mode as supported on Azure (#5699)
Using index info to reconstruct a base tree...
M	data/data/install.openshift.io_installconfigs.yaml
M	pkg/explain/printer_test.go
M	pkg/types/installconfig.go
M	pkg/types/validation/installconfig.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/types/validation/installconfig.go
CONFLICT (content): Merge conflict in pkg/types/validation/installconfig.go
Auto-merging pkg/types/installconfig.go
CONFLICT (content): Merge conflict in pkg/types/installconfig.go
Auto-merging pkg/explain/printer_test.go
CONFLICT (content): Merge conflict in pkg/explain/printer_test.go
Auto-merging data/data/install.openshift.io_installconfigs.yaml
CONFLICT (content): Merge conflict in data/data/install.openshift.io_installconfigs.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 stop considering Mint mode as supported on Azure (#5699)
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherry-pick release-4.9
/cherry-pick release-4.8

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/severity-low Referenced Bugzilla bug's severity is low 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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants