Skip to content

Comments

Updating ose-csi-snapshot-controller images to be consistent with ART#70

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
openshift-bot:art-consistency-openshift-4.11-ose-csi-snapshot-controller
May 13, 2022
Merged

Updating ose-csi-snapshot-controller images to be consistent with ART#70
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
openshift-bot:art-consistency-openshift-4.11-ose-csi-snapshot-controller

Conversation

@openshift-bot
Copy link

@openshift-bot openshift-bot commented May 12, 2022

Updating ose-csi-snapshot-controller images to be consistent with ART
TLDR:
Component owners, please ensure that this PR merges as it impacts the fidelity
of your CI signal. Patch-manager / leads, this PR is a no-op from a product
perspective -- feel free to manually apply any labels (e.g. bugzilla/valid-bug) to help the
PR merge as long as tests are passing. If the PR is labeled "needs-ok-to-test", this is
to limit costs for re-testing these PRs while they wait for review. Issue /ok-to-test
to remove this tag and help the PR to merge.

Detail:
This repository is out of sync with the downstream product builds for this component.
One or more images differ from those being used by ART to create product builds. This
should be addressed to ensure that the component's CI testing is accurately
reflecting what customers will experience.

The information within the following ART component metadata is driving this alignment
request: ose-csi-snapshot-controller.yml.

The vast majority of these PRs are opened because a different Golang version is being
used to build the downstream component. ART compiles most components with the version
of Golang being used by the control plane for a given OpenShift release. Exceptions
to this convention (i.e. you believe your component must be compiled with a Golang
version independent from the control plane) must be granted by the OpenShift
architecture team and communicated to the ART team.

Roles & Responsibilities:

  • Component owners are responsible for ensuring these alignment PRs merge with passing
    tests OR that necessary metadata changes are reported to the ART team: @release-artists
    in #aos-art on Slack. If necessary, the changes required by this pull request can be
    introduced with a separate PR opened by the component team. Once the repository is aligned,
    this PR will be closed automatically.
  • Patch-manager or those with sufficient privileges within this repository may add
    any required labels to ensure the PR merges once tests are passing. Downstream builds
    are already being built with these changes. Merging this PR only improves the fidelity
    of our CI.

ART has been configured to reconcile your CI build root image (see https://docs.ci.openshift.org/docs/architecture/ci-operator/#build-root-image).
In order for your upstream .ci-operator.yaml configuration to be honored, you must set the following in your openshift/release ci-operator configuration file:

build_root:
  from_repository: true

If you have any questions about this pull request, please reach out to @art-team in the #aos-art coreos slack channel.

@openshift-bot openshift-bot added 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. 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. labels May 12, 2022
@openshift-ci openshift-ci bot requested review from dobsonj and tsmetana May 12, 2022 01:11
@openshift-ci
Copy link

openshift-ci bot commented May 12, 2022

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-bot

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

openshift-ci bot commented May 12, 2022

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-bot

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

@Phaow
Copy link

Phaow commented May 12, 2022

/test e2e-gcp-csi

@Phaow
Copy link

Phaow commented May 12, 2022

e2e-gcp-csi 1 failed seems not caused by this pr.

Create the release image "latest" containing all images built by this job

{  release "release-latest" failed: the pod ci-op-crsg4k7f/release-latest failed after 19s (failed containers: release): ContainerFailed one or more containers exited

Container release exited with code 1, reason Error
---
ator
info: Loading sha256:e991b444eddec45e78fd82c27f4e673f38d3dda84d375d0457c59c6db2642ff4 installer-artifacts
info: Loading sha256:3ef743fc7ab2ea44b1444d6bc6563e5f0cb2e2d80faee02937ea42aa5372e98d installer
info: Loading sha256:ddbc3aa2f83731fdf179390fe35c564b5ee14c6ee58540a496c5c07161ccd268 ironic-hardware-inventory-recorder
info: Loading sha256:7a8468e82d298fb1251f7c88290ab08b8c832241f933f5bfebda0f0a121d1da9 machine-config-operator
info: Loading sha256:264754d9b4b1bc01f9f95fbb6f8eb6ca9b78965bd1dd6afe9f5a709ec7fecb9b machine-api-operator
info: Loading sha256:89785359e9f9d2381d0e3a9086fdeadf2e32be4a024541b0c0b61b767c1bf542 machine-os-images
info: Loading sha256:4bfe93760e855fae291f52a96c62817766eda1867c0aa181c60da31b76700915 local-storage-static-provisioner
info: Loading sha256:1a1848a7c690ebb22b33ecbaba8e9368cb47a87d4a89998ded7678db82962468 oc-mirror
info: Loading sha256:e1188e5a0bec0a8d54d57d8ff832990cc5e9a1911e510a9378285565c50b6577 operator-lifecycle-manager
info: Loading sha256:d4cf4f276257b7ac53591f5550e6e2d553bdef62e46ceb53ed72a0761d003754 operator-marketplace
info: Loading sha256:4c8f8401518746ab538e525ea4ffbe9a9b74b9d1fa81b59910e059166b38ec17 ovirt-installer
info: Loading sha256:e0c6d52f08c78b5ac20f02618ed15188011f5d3cd63db2f6587b9de215baf358 service-ca-operator
info: Loading sha256:fc5bfe68c79205f7fbde1db730f80283169c9164929cdeb33d36cbbeab8baf62 vsphere-problem-detector
info: Loading sha256:0d66000fdc3568aa68272a7e9b23d14454a4bf15e17b928c83cf123afcf38a45 vsphere-cluster-api-controllers
info: Included 172 images from 57 input operators into the release
error: unable to create a release: operator "cluster-baremetal-operator" contained an invalid image-references file: no input image tag named "image-customization-controller"
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"k8s.io/test-infra/prow/entrypoint/run.go:80","func":"k8s.io/test-infra/prow/entrypoint.Options.Run","level":"error","msg":"Error executing test process","severity":"error","time":"2022-05-12T07:52:57Z"}
---}

@Phaow
Copy link

Phaow commented May 12, 2022

/test e2e-gcp-csi

@jsafrane
Copy link

/retest

@openshift-ci
Copy link

openshift-ci bot commented May 13, 2022

@openshift-bot: all tests passed!

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 4321c9c into openshift:master May 13, 2022
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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants