Skip to content

Updating ose-cluster-ingress-operator images to be consistent with ART#802

Closed
openshift-bot wants to merge 1 commit intoopenshift:masterfrom
openshift-bot:art-consistency-openshift-4.12-ose-cluster-ingress-operator
Closed

Updating ose-cluster-ingress-operator images to be consistent with ART#802
openshift-bot wants to merge 1 commit intoopenshift:masterfrom
openshift-bot:art-consistency-openshift-4.12-ose-cluster-ingress-operator

Conversation

@openshift-bot
Copy link
Contributor

@openshift-bot openshift-bot commented Jul 7, 2022

Updating ose-cluster-ingress-operator 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-cluster-ingress-operator.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 @release-artists in the #aos-art coreos slack channel.

@openshift-bot openshift-bot added 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 Jul 7, 2022
@openshift-ci openshift-ci bot requested review from frobware and rfredette July 7, 2022 11:49
@candita
Copy link
Contributor

candita commented Aug 24, 2022

/assign @Miciah

@Miciah
Copy link
Contributor

Miciah commented Sep 8, 2022

/lgtm
/approve

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

openshift-ci bot commented Sep 8, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Miciah

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 8, 2022
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 14f40c7 and 2 for PR HEAD 732fca4 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 7977871 and 1 for PR HEAD 732fca4 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD e65501a and 0 for PR HEAD 732fca4 in total

@openshift-ci-robot
Copy link
Contributor

/hold

Revision 732fca4 was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 16, 2022
@Miciah
Copy link
Contributor

Miciah commented Sep 19, 2022

e2e-gcp-ovn-serial failed with the following:

:  [sig-instrumentation][Late] Alerts shouldn't report any unexpected  alerts in firing or pending state [apigroup:config.openshift.io]  [Suite:openshift/conformance/parallel]
{  fail [github.com/onsi/ginkgo@v4.7.0-origin.0+incompatible/internal/leafnodes/runner.go:113]: Sep 15 23:57:00.440: Unexpected alerts fired or pending after the test run:  alert OVNKubernetesNorthboundDatabaseClusterMemberError fired for 30 seconds with labels: {namespace="openshift-ovn-kubernetes", severity="warning"} alert OVNKubernetesNorthboundDatabaseInboundConnectionMissing fired for 30 seconds with labels: {namespace="openshift-ovn-kubernetes", severity="warning"} alert OVNKubernetesNorthboundDatabaseOutboundConnectionMissing fired for 30 seconds with labels: {namespace="openshift-ovn-kubernetes", severity="warning"} alert OVNKubernetesSouthboundDatabaseClusterMemberError fired for 30 seconds with labels: {namespace="openshift-ovn-kubernetes", severity="warning"} alert OVNKubernetesSouthboundDatabaseInboundConnectionMissing fired for 30 seconds with labels: {namespace="openshift-ovn-kubernetes", severity="warning"} alert OVNKubernetesSouthboundDatabaseOutboundConnectionMissing fired for 30 seconds with labels: {namespace="openshift-ovn-kubernetes", severity="warning"} Ginkgo exit error 1: exit with code 1}

/test e2e-gcp-ovn-serial

@Miciah
Copy link
Contributor

Miciah commented Oct 1, 2022

/retest

@openshift-bot openshift-bot force-pushed the art-consistency-openshift-4.12-ose-cluster-ingress-operator branch from 732fca4 to 5a474a1 Compare October 2, 2022 11:19
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 2, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 2, 2022

New changes are detected. LGTM label has been removed.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 2, 2022

@openshift-bot: 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-gcp-serial 732fca4 link true /test e2e-gcp-serial
ci/prow/e2e-aws-single-node 732fca4 link false /test e2e-aws-single-node
ci/prow/e2e-aws-ovn-single-node 5a474a1 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-operator 5a474a1 link true /test e2e-aws-operator
ci/prow/e2e-aws-ovn-upgrade 5a474a1 link true /test e2e-aws-ovn-upgrade
ci/prow/e2e-gcp-ovn-serial 5a474a1 link true /test e2e-gcp-ovn-serial
ci/prow/verify 5a474a1 link true /test verify

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.

@Miciah
Copy link
Contributor

Miciah commented Oct 24, 2022

Superseded by #834.
/close

@openshift-ci openshift-ci bot closed this Oct 24, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2022

@Miciah: Closed this PR.

Details

In response to this:

Superseded by #834.
/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. 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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants