Skip to content

Conversation

@lranjbar
Copy link
Contributor

Updates the jobs for Assisted Installer to the latest images and uses the correct cluster profile.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 11, 2022

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 11, 2022
@openshift-ci openshift-ci bot requested review from dusk125 and hongkailiu January 11, 2022 00:23
@lranjbar lranjbar force-pushed the packet-account-split-02-etcd branch 2 times, most recently from 380e015 to 56e1c03 Compare January 11, 2022 00:37
@lranjbar lranjbar marked this pull request as ready for review January 11, 2022 00:40
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 11, 2022
@hongkailiu
Copy link
Member

/uncc

@openshift-ci openshift-ci bot removed the request for review from hongkailiu January 13, 2022 15:51
@lranjbar lranjbar force-pushed the packet-account-split-02-etcd branch from 56e1c03 to 5272f04 Compare January 17, 2022 21:38
This updates the cluster-etcd-operator jobs for Assisted Installer:

1. Updates the cluster_profile to "packet-assisted" from "packet".
This will increase flexibility in using the Equinix cloud offering
by splitting the workflows into an account for Assisted Installer.

2. Updates the Assisted Installer images to the latest images coming
from our master branch. We needed to update the promotion scheme for
Assisted Installer and this will pick the lastest version for testing.
@lranjbar lranjbar force-pushed the packet-account-split-02-etcd branch from 5272f04 to 9010ba7 Compare January 19, 2022 21:18
@dusk125
Copy link
Contributor

dusk125 commented Jan 24, 2022

/lgtm

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

openshift-ci bot commented Jan 24, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dusk125, lranjbar
To complete the pull request process, please assign sttts after the PR has been reviewed.
You can assign the PR to them by writing /assign @sttts in a comment when ready.

The full list of commands accepted by this bot can be found 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
Copy link
Contributor

openshift-ci bot commented Feb 25, 2022

@lranjbar: PR needs rebase.

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.

1 similar comment
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 25, 2022

@lranjbar: PR needs rebase.

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.

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 25, 2022
@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 Mar 28, 2022
@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 Apr 12, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 25, 2022

@lranjbar: 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/cluster-etcd-operator/master/e2e-aws-disruptive 56e1c0394321becd3829b0a46c9ff2a02321cb64 link unknown /test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/master/configmap-scale 56e1c0394321becd3829b0a46c9ff2a02321cb64 link unknown /test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/release-4.10/e2e-aws-disruptive 5272f0453bad80adcbadfc5df505c0e55b1054c4 link unknown /test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/release-4.10/configmap-scale 5272f0453bad80adcbadfc5df505c0e55b1054c4 link unknown /test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/release-4.6/configmap-scale 9010ba7 link unknown /test pj-rehearse
ci/prow/pj-rehearse 9010ba7 link false /test pj-rehearse
ci/prow/generated-config 9010ba7 link true /test generated-config
ci/prow/services-valid 9010ba7 link true /test services-valid
ci/build-farm/build05-dry 9010ba7 link true /test build05-dry

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

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 May 11, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 11, 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

lgtm Indicates that a PR is ready to be merged. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants