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 jhixson74 and jstuever January 11, 2022 00:55
@lranjbar lranjbar marked this pull request as ready for review January 11, 2022 01:09
@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
@lranjbar lranjbar force-pushed the packet-account-split-03-installer branch from 7c024fa to 12403ce Compare January 12, 2022 00:16
Copy link
Contributor

@jstuever jstuever left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 13, 2022
@jstuever jstuever removed their assignment Jan 14, 2022
@lranjbar lranjbar force-pushed the packet-account-split-03-installer branch from 12403ce to 7ca1752 Compare January 17, 2022 21:43
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 17, 2022
This updates the installer 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-03-installer branch from 7ca1752 to 118f050 Compare January 18, 2022 22:03
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 18, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 19, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 19, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jstuever, lranjbar, osherdp

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

openshift-ci bot commented Jan 19, 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/installer/release-4.7/e2e-aws 7c024faa2d3fc6a33572632a2e7b89928ce11294 link unknown /test pj-rehearse
ci/rehearse/openshift/installer/release-4.7/e2e-aws-proxy 7c024faa2d3fc6a33572632a2e7b89928ce11294 link unknown /test pj-rehearse
ci/rehearse/openshift/installer/release-4.7/e2e-aws-disruptive 7c024faa2d3fc6a33572632a2e7b89928ce11294 link unknown /test pj-rehearse
ci/rehearse/openshift/installer/release-4.7/e2e-aws-fips 7c024faa2d3fc6a33572632a2e7b89928ce11294 link unknown /test pj-rehearse
ci/rehearse/openshift/installer/release-4.7/e2e-aws-shared-vpc 7c024faa2d3fc6a33572632a2e7b89928ce11294 link unknown /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-proxy 7ca1752aa4796dc9b868ac17d14226879db1fdd5 link unknown /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-disruptive 7ca1752aa4796dc9b868ac17d14226879db1fdd5 link unknown /test pj-rehearse
ci/rehearse/openshift/installer/release-4.10/e2e-aws-disruptive 118f050 link unknown /test pj-rehearse
ci/prow/pj-rehearse 118f050 link false /test pj-rehearse
ci/rehearse/openshift/installer/release-4.10/e2e-aws-proxy 118f050 link unknown /test pj-rehearse

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-merge-robot openshift-merge-robot merged commit 33bace4 into openshift:master Jan 19, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 19, 2022

@lranjbar: Updated the following 12 configmaps:

  • ci-operator-4.7-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-release-4.7.yaml using file ci-operator/config/openshift/installer/openshift-installer-release-4.7.yaml
  • ci-operator-4.8-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-release-4.8.yaml using file ci-operator/config/openshift/installer/openshift-installer-release-4.8.yaml
  • ci-operator-4.9-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-release-4.9.yaml using file ci-operator/config/openshift/installer/openshift-installer-release-4.9.yaml
  • job-config-4.7 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-release-4.7-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-release-4.7-presubmits.yaml
  • ci-operator-4.10-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-release-4.10.yaml using file ci-operator/config/openshift/installer/openshift-installer-release-4.10.yaml
  • ci-operator-4.11-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-release-4.11.yaml using file ci-operator/config/openshift/installer/openshift-installer-release-4.11.yaml
  • job-config-4.10 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-release-4.10-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-release-4.10-presubmits.yaml
  • job-config-4.11 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-release-4.11-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-release-4.11-presubmits.yaml
  • job-config-4.8 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-release-4.8-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-release-4.8-presubmits.yaml
  • job-config-4.9 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-release-4.9-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-release-4.9-presubmits.yaml
  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-master.yaml using file ci-operator/config/openshift/installer/openshift-installer-master.yaml
  • job-config-master-presubmits configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-master-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-master-presubmits.yaml
Details

In response to this:

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

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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants