Skip to content

Conversation

@vrutkovs
Copy link
Contributor

@vrutkovs vrutkovs commented Apr 14, 2021

Instead of hardcoding 4.5 release image use from: upi-installer.
Ideally we'd have "aws-tools" and "gcp-tools" images w/ oc to avoid using UPI installer image.

Requires #17482 to fix "pip<21" install issue

@vrutkovs
Copy link
Contributor Author

/hold

for rehearsals

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 14, 2021
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vrutkovs

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 14, 2021
@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 20, 2021
@vrutkovs vrutkovs force-pushed the gather-aws-gcp-console-upi-tag branch from 22f5445 to 1cd2f0b Compare June 15, 2021 07:27
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 15, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vrutkovs

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

@vrutkovs
Copy link
Contributor Author

/hold cancel

rehearsals are passing now

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 15, 2021
Instead of hardcoding 4.5 release image use `from: upi-installer`.
Ideally we'd have "aws-tools" and "gcp-tools" images w/ oc to avoid using UPI installer image
@vrutkovs vrutkovs force-pushed the gather-aws-gcp-console-upi-tag branch from 1cd2f0b to 11f5a57 Compare June 28, 2021 08:02
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 28, 2021
@vrutkovs
Copy link
Contributor Author

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 9, 2021

@vrutkovs: 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/rehearse/openshift/origin/release-4.9/e2e-agnostic-cmd 22f54457809dd3b7df6a6d5b249d9cd7c7096eeb link /test pj-rehearse
ci/rehearse/openshift/ocs-operator/release-4.7/ocs-operator-bundle-e2e-aws 22f54457809dd3b7df6a6d5b249d9cd7c7096eeb link /test pj-rehearse
ci/rehearse/periodic-ci-redhat-operator-ecosystem-playground-cvp-ocp-4.7-cvp-common-aws 22f54457809dd3b7df6a6d5b249d9cd7c7096eeb link /test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/release-4.9/e2e-aws-disruptive-ovn 22f54457809dd3b7df6a6d5b249d9cd7c7096eeb link /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.8-upgrade-from-stable-4.7-e2e-gcp-ovn-upgrade 22f54457809dd3b7df6a6d5b249d9cd7c7096eeb link /test pj-rehearse
ci/rehearse/openshift/oauth-proxy/release-4.9/e2e-component 1cd2f0b19b3ad692b06bbb61e74102fb6552ad4f link /test pj-rehearse
ci/rehearse/periodic-ci-redhat-operator-ecosystem-cvp-ocp-4.8-cvp-common-aws 1cd2f0b19b3ad692b06bbb61e74102fb6552ad4f link /test pj-rehearse
ci/rehearse/openshift/ocs-operator/release-4.8/ocs-operator-bundle-e2e-aws 1cd2f0b19b3ad692b06bbb61e74102fb6552ad4f link /test pj-rehearse
ci/rehearse/openshift/origin/release-4.1/e2e-aws-image-ecosystem 11f5a57 link /test pj-rehearse
ci/rehearse/openshift/origin/release-4.1/e2e-aws-builds 11f5a57 link /test pj-rehearse
ci/rehearse/openshift/installer/release-4.9/e2e-aws-shared-vpc 11f5a57 link /test pj-rehearse
ci/rehearse/redhat-developer/jenkins-operator/main/e2e 11f5a57 link /test pj-rehearse
ci/rehearse/openshift/cluster-logging-operator/tech-preview/e2e-operator 11f5a57 link /test pj-rehearse
ci/rehearse/openshift/route-monitor-operator/master/test-integration 11f5a57 link /test pj-rehearse
ci/rehearse/openshift/installer/release-4.9/e2e-gcp-upgrade 11f5a57 link /test pj-rehearse
ci/rehearse/openshift/origin/release-4.2/e2e-cmd 11f5a57 link /test pj-rehearse
ci/rehearse/openshift/cluster-cloud-controller-manager-operator/release-4.9/e2e-aws-ccm-install 11f5a57 link /test pj-rehearse
ci/rehearse/openshift/cloud-credential-operator/release-4.9/e2e-aws-manual-oidc 11f5a57 link /test pj-rehearse
ci/rehearse/openshift/origin/release-4.9/e2e-gcp-disruptive 11f5a57 link /test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/release-4.9/e2e-gcp-disruptive-ovn 11f5a57 link /test pj-rehearse
ci/rehearse/operator-framework/operator-marketplace/release-4.9/e2e-aws-upgrade 11f5a57 link /test pj-rehearse
ci/rehearse/openshift/installer/release-4.9/e2e-aws-upgrade 11f5a57 link /test pj-rehearse
ci/rehearse/openshift/origin/release-4.9/e2e-aws-disruptive 11f5a57 link /test pj-rehearse
ci/rehearse/openshift/cluster-logging-operator/master/e2e-gcp 11f5a57 link /test pj-rehearse
ci/prow/pj-rehearse 11f5a57 link /test pj-rehearse
ci/prow/openshift-image-mirror-mappings 11f5a57 link /test openshift-image-mirror-mappings

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

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 26, 2021
@openshift-bot
Copy link
Contributor

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 10, 2022
@openshift-bot
Copy link
Contributor

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Jan 25, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 25, 2022

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants