Bug 1872080: move templates to RHEL/CentOS/UBI 8 imagestream tags

[yselkowitz]

This also updates Fuse samples to 7.7.

/assign @gabemontero

[openshift-ci-robot]

@yselkowitz: This pull request references Bugzilla bug 1872080, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.6.0) matches configured target release for branch (4.6.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1872080: move templates to RHEL/CentOS/UBI 8 imagestream tags

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.

[gabemontero]

/approve

waiting on at least some of the multitude of e2e's to come back prior to LGTM

[gabemontero]

There is a problem with the mariadb imagestream @yselkowitz pulling registry.redhat.io/rhel8/mariadb-103:latest in e2e-aws-image-ecosystem.

    - conditions:
      - generation: 2
        lastTransitionTime: "2020-09-03T16:20:25Z"
        message: you may not have access to the container image "registry.redhat.io/rhel8/mariadb-103:latest"
        reason: Unauthorized
        status: "False"
        type: ImportSuccess
      items: null
      tag: 10.3-el8

I can pull it locally so it appears to be a registry.redhat.io flake. I've heard through the grapevine there have been issues pulling images from there today in other PRs / e2e's

We are going to have to wade through those before getting this merged.

[gabemontero]

/retest

[yselkowitz]

Found an issue with dancer-ex
/hold

[gabemontero]

seeing if any of the okd e2e's pass (ignoring the still pending upstream dancer-ex change)

/retest

[yselkowitz]

Looks like not. What's the problem?

[gabemontero]

hey @vrutkovs .... in the last week or so we've seen the OKD e2e's across the board fail with various install/bootstrap types of failures?

Is this a known situation?

If not, can you take a look at some of the recent failures here and see if some mitigations can be initiated?

If the outlook for fixing this is not "soon", I'm going to be inclined to change the OKD e2e's for samples operator to optional, and override the failures for this PR.

thanks

[yselkowitz]

/retest

[yselkowitz]

I've pulled in the dotnet template removal from the library, and the dancer template update in advance. New problem or something wrong with the latest changes?

[yselkowitz]

Resynced from the library, picking up the dotnet and dancer changes.
/hold cancel

[gabemontero]

for the non-okd's there looks to be CI level unhappiness and the e2e's are not getting off the ground ... we'll just have to wait those out.

if we don't hear from @vrutkovs by this afternoon US eastern time I'll probably pull the trigger on making those OKD jobs optional.

[yselkowitz]

Looks like the overall issues have been sorted out, only the OKD tests show as failing now.

[yselkowitz]

And it looks like the OKD tests are already optional, there is no (Required) next to any of them.

[vrutkovs]

OKD install is broken, feel free to /skip those - we'll verify imagestreams are correct later

[gabemontero]

OKD install is broken, feel free to /skip those - we'll verify imagestreams are correct later

thanks @vrutkovs

I now also see the jobs are marked optional in openshift/release

/skip ci/prow/okd-e2e-aws

[gabemontero]

/override ci/prow/okd-e2e-aws

[openshift-ci-robot]

@gabemontero: Overrode contexts on behalf of gabemontero: ci/prow/okd-e2e-aws

In response to this:

/override ci/prow/okd-e2e-aws

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.

[gabemontero]

/override ci/prow/okd-e2e-aws-builds
/override ci/prow/okd-e2e-aws-image-ecosystem
/override ci/prow/okd-e2e-aws-jenkins
/override ci/prow/okd-e2e-aws-operator
/override ci/prow/okd-e2e-aws-upgrade
/override ci/prow/okd-unit

[openshift-ci-robot]

@gabemontero: Overrode contexts on behalf of gabemontero: ci/prow/okd-e2e-aws-builds, ci/prow/okd-e2e-aws-image-ecosystem, ci/prow/okd-e2e-aws-jenkins, ci/prow/okd-e2e-aws-operator, ci/prow/okd-e2e-aws-upgrade, ci/prow/okd-unit

In response to this:

/override ci/prow/okd-e2e-aws-builds
/override ci/prow/okd-e2e-aws-image-ecosystem
/override ci/prow/okd-e2e-aws-jenkins
/override ci/prow/okd-e2e-aws-operator
/override ci/prow/okd-e2e-aws-upgrade
/override ci/prow/okd-unit

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.

[gabemontero]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gabemontero, yselkowitz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [gabemontero]

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]

@yselkowitz: Some pull requests linked via external trackers have merged:

• operator-framework/operator-registry#426
• operator-framework/operator-marketplace#331
• operator-framework/operator-lifecycle-manager#1738
• openshift/whereabouts-cni#28

The following pull requests linked via external trackers have not merged:

• openshift/vertical-pod-autoscaler-operator#34 is open

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state.

Bugzilla bug 1872080 has not been moved to the MODIFIED state.

In response to this:

Bug 1872080: move templates to RHEL/CentOS/UBI 8 imagestream tags

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.