Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #6225

/assign jianlinliu

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 31, 2022

@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug 2118514 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details.

Full error message. code 106: Sorry, entering a bug into the product OpenShift Container Platform has been disabled.

Please contact an administrator to resolve this issue, then request a bug refresh with /bugzilla refresh.

Details

In response to this:

[release-4.10] Bug 2118514: [4.11] Download yq in upi installer containers

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.

@jianlinliu
Copy link
Contributor

/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 Aug 31, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 31, 2022

@openshift-cherrypick-robot: 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-openstack 9556ed6 link false /test e2e-openstack
ci/prow/e2e-ibmcloud 9556ed6 link false /test e2e-ibmcloud
ci/prow/okd-e2e-gcp 9556ed6 link false /test okd-e2e-gcp
ci/prow/e2e-azurestack-upi 9556ed6 link false /test e2e-azurestack-upi
ci/prow/e2e-metal-single-node-live-iso 9556ed6 link false /test e2e-metal-single-node-live-iso
ci/prow/e2e-aws-single-node 9556ed6 link false /test e2e-aws-single-node
ci/prow/e2e-azure-upi 9556ed6 link false /test e2e-azure-upi
ci/prow/okd-e2e-vsphere 9556ed6 link false /test okd-e2e-vsphere
ci/prow/e2e-alibaba 9556ed6 link false /test e2e-alibaba
ci/prow/e2e-crc 9556ed6 link false /test e2e-crc
ci/prow/e2e-azurestack 9556ed6 link false /test e2e-azurestack
ci/prow/okd-e2e-gcp-upgrade 9556ed6 link false /test okd-e2e-gcp-upgrade
ci/prow/e2e-libvirt 9556ed6 link false /test e2e-libvirt

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.

@jianlinliu
Copy link
Contributor

/retitle [release-4.10] OCPBUGS-784: Download yq in upi installer containers

@openshift-ci openshift-ci bot changed the title [release-4.10] Bug 2118514: [4.11] Download yq in upi installer containers [release-4.10] [OCPBUGS-784](https://issues.redhat.com//browse/OCPBUGS-784): Download yq in upi installer containers Sep 1, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 1, 2022

@openshift-cherrypick-robot: 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:

[release-4.10] OCPBUGS-784: Download yq in upi installer containers

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.

@jianlinliu
Copy link
Contributor

/retitle [release-4.10] OCPBUGS-784: Download yq in upi installer containers

@openshift-ci openshift-ci bot changed the title [release-4.10] [OCPBUGS-784](https://issues.redhat.com//browse/OCPBUGS-784): Download yq in upi installer containers [release-4.10] OCPBUGS-784: Download yq in upi installer containers Sep 1, 2022
@openshift-ci-robot openshift-ci-robot added the jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. label Sep 1, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 1, 2022

@openshift-cherrypick-robot: 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:

[release-4.10] OCPBUGS-784: Download yq in upi installer containers

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 added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 1, 2022
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-784, which is invalid:

  • expected the bug to target the "4.10.z" version, but no target version was set
  • expected Jira Issue OCPBUGS-784 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), 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.

Details

In response to this:

This is an automated cherry-pick of #6225

/assign jianlinliu

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.

@jianlinliu
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@jianlinliu: This pull request references Jira Issue OCPBUGS-784, which is invalid:

  • expected Jira Issue OCPBUGS-784 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), 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.

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.

@jianlinliu
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@jianlinliu: This pull request references Jira Issue OCPBUGS-784, which is invalid:

  • expected Jira Issue OCPBUGS-784 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), 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.

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.

@jianlinliu
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@jianlinliu: This pull request references Jira Issue OCPBUGS-784, which is invalid:

  • expected Jira Issue OCPBUGS-784 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), 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.

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.

@jianlinliu
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@jianlinliu: This pull request references Jira Issue OCPBUGS-784, which is invalid:

  • expected Jira Issue OCPBUGS-784 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), 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.

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.

@jianlinliu
Copy link
Contributor

/retitle [release-4.10] OCPBUGS-784: Download yq in upi installer containers

@openshift-ci openshift-ci bot changed the title [release-4.10] OCPBUGS-784: Download yq in upi installer containers [release-4.10] [OCPBUGS-784](https://issues.redhat.com//browse/OCPBUGS-784): Download yq in upi installer containers Sep 1, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 1, 2022

@openshift-cherrypick-robot: 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:

[release-4.10] OCPBUGS-784: Download yq in upi installer containers

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.

@jianlinliu
Copy link
Contributor

/retitle [release-4.10] OCPBUGS-784: Download yq in upi installer containers

@openshift-ci openshift-ci bot changed the title [release-4.10] [OCPBUGS-784](https://issues.redhat.com//browse/OCPBUGS-784): Download yq in upi installer containers [release-4.10] OCPBUGS-784: Download yq in upi installer containers Sep 1, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 1, 2022

@openshift-cherrypick-robot: 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:

[release-4.10] OCPBUGS-784: Download yq in upi installer containers

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

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-784, which is invalid:

  • expected Jira Issue OCPBUGS-784 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), 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.

Details

In response to this:

This is an automated cherry-pick of #6225

/assign jianlinliu

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.

@jianlinliu
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@jianlinliu: This pull request references Jira Issue OCPBUGS-784, which is invalid:

  • expected dependent Jira Issue OCPBUGS-786 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), but it is Closed (Done) 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.

@jianlinliu
Copy link
Contributor

/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. bugzilla/valid-bug Indicates that a referenced Bugzilla 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 Sep 1, 2022
@openshift-ci-robot
Copy link
Contributor

@jianlinliu: This pull request references Jira Issue OCPBUGS-784, 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 version (4.10.z) matches configured target version for branch (4.10.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-786 is in the state Closed (Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE))
  • dependent Jira Issue OCPBUGS-786 targets the "4.11.z" version, which is one of the valid target versions: 4.11.0, 4.11.z
  • bug has dependents

Requesting review from QA contact:
/cc @jianlinliu

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 openshift-ci bot requested a review from jianlinliu September 1, 2022 04:48
@jianlinliu
Copy link
Contributor

/lgtm

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

sadasu commented Sep 1, 2022

/approve
/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 Sep 1, 2022
@sdodson
Copy link
Member

sdodson commented Sep 2, 2022

/approve
The bots were taking a break I guess when Sandhya did this above.

@sdodson sdodson added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 2, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 2, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sadasu, sdodson

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

1 similar comment
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 2, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sadasu, sdodson

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-merge-robot openshift-merge-robot merged commit dc2dff1 into openshift:release-4.10 Sep 2, 2022
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-784 is in an unrecognized state (Verified) and will not be moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #6225

/assign jianlinliu

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.

@jianlinliu
Copy link
Contributor

/cherry-pick release-4.9

2 similar comments
@jianlinliu
Copy link
Contributor

/cherry-pick release-4.9

@sdodson
Copy link
Member

sdodson commented Sep 8, 2022

/cherry-pick release-4.9

@openshift-cherrypick-robot
Copy link
Author

@sdodson: new pull request created: #6316

Details

In response to this:

/cherry-pick release-4.9

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/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. jira/severity-moderate Referenced Jira bug's severity is moderate 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. 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