Closed ausil closed 1 month ago
@ausil: This pull request references OKD-225 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.18.0" version, but no target version was set.
only touches okd so should be safe for merging
/lgtm
/assign mfrancisc
The failing image-ecosystem test is being fixed in openshift/origin#29116. But I wonder what breakage is https://github.com/openshift/origin/blob/master/test/extended/util/framework.go#L315 causing? From the OCP perspective, I'd much rather fix that test than bring additional samples back to support.
The failing image-ecosystem test is being fixed in openshift/origin#29116. But I wonder what breakage is https://github.com/openshift/origin/blob/master/test/extended/util/framework.go#L315 causing? From the OCP perspective, I'd much rather fix that test than bring additional samples back to support.
We add MySQL back to fix the breakage of that test or we remove MySQL from https://github.com/openshift/origin/blob/master/test/extended/util/framework.go#L315. @metlos are you suggesting removing MySQL from that test?
The failing image-ecosystem test is being fixed in openshift/origin#29116. But I wonder what breakage is https://github.com/openshift/origin/blob/master/test/extended/util/framework.go#L315 causing? From the OCP perspective, I'd much rather fix that test than bring additional samples back to support.
We add MySQL back to fix the breakage of that test or we remove MySQL from https://github.com/openshift/origin/blob/master/test/extended/util/framework.go#L315. @metlos are you suggesting removing MySQL from that test?
Well, even though some of the imagestreams in that test are not supported, we keep them in the assets, even though we don't update them.
So at a glance, I didn't see what breakage that test might be causing. But I assumed I didn't look deep enough in the code so I asked what breakage is being fixed by updating the unsupported image streams.
The test doesn't need to be removed, just updated as soon as we "loose" some of the image streams for good (which IMHO didn't happen yet). Loosing the image stream would only happen if we removed all its versions due to EOL.
The failing image-ecosystem test is being fixed in openshift/origin#29116. But I wonder what breakage is https://github.com/openshift/origin/blob/master/test/extended/util/framework.go#L315 causing? From the OCP perspective, I'd much rather fix that test than bring additional samples back to support.
We add MySQL back to fix the breakage of that test or we remove MySQL from https://github.com/openshift/origin/blob/master/test/extended/util/framework.go#L315. @metlos are you suggesting removing MySQL from that test?
Well, even though some of the imagestreams in that test are not supported, we keep them in the assets, even though we don't update them.
So at a glance, I didn't see what breakage that test might be causing. But I assumed I didn't look deep enough in the code so I asked what breakage is being fixed by updating the unsupported image streams.
The test doesn't need to be removed, just updated as soon as we "loose" some of the image streams for good (which IMHO didn't happen yet). Loosing the image stream would only happen if we removed all its versions due to EOL.
Right. So, we are adding MySQL back because the e2e test checks for its existence.
There may be breakage in other parts of the testsuite in origin, if we update the samples from DeploymentConfig to Deployment. I'm not sure if mysql is used in any of the tests in https://github.com/openshift/origin/tree/master/test/extended/image_ecosystem or https://github.com/openshift/origin/tree/master/test/extended/builds or anywhere else.
/test ci/prow/e2e-aws-ovn-image-ecosystem
@metlos: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test e2e-aws
/test e2e-aws-operator
/test e2e-aws-ovn-builds
/test e2e-aws-ovn-image-ecosystem
/test e2e-aws-ovn-jenkins
/test e2e-aws-ovn-upgrade
/test images
/test unit
/test verify
The following commands are available to trigger optional jobs:
/test e2e-aws-ovn-proxy
/test okd-scos-images
Use /test all
to run the following jobs that were automatically triggered:
pull-ci-openshift-cluster-samples-operator-master-e2e-aws
pull-ci-openshift-cluster-samples-operator-master-e2e-aws-operator
pull-ci-openshift-cluster-samples-operator-master-e2e-aws-ovn-image-ecosystem
pull-ci-openshift-cluster-samples-operator-master-e2e-aws-ovn-proxy
pull-ci-openshift-cluster-samples-operator-master-e2e-aws-ovn-upgrade
pull-ci-openshift-cluster-samples-operator-master-images
pull-ci-openshift-cluster-samples-operator-master-unit
pull-ci-openshift-cluster-samples-operator-master-verify
/test e2e-aws-ovn-image-ecosystem
There may be breakage in other parts of the testsuite in origin, if we update the samples from DeploymentConfig to Deployment. I'm not sure if mysql is used in any of the tests in https://github.com/openshift/origin/tree/master/test/extended/image_ecosystem or https://github.com/openshift/origin/tree/master/test/extended/builds or anywhere else.
For okd, the extended test suite is not run and yes, we do need to be aware that if we ever do - this is a potential problem to solve. But I believe as far the conformance e2es are concerned, we are good
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ausil, metlos, Prashanth684
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/retest-required
Remaining retests: 0 against base HEAD 21a101bdbd3119406f2860781f5f8a7d02c721a3 and 2 for PR HEAD b34dd1e7292379b5bcc1788249494bca0e798059 in total
@ausil: all tests passed!
Full PR test history. Your PR dashboard.
[ART PR BUILD NOTIFIER]
Distgit: ose-cluster-samples-operator This PR has been included in build ose-cluster-samples-operator-container-v4.18.0-202409260508.p0.g1810acc.assembly.stream.el9. All builds following this will include this PR.
It turns out that there is a test for particular samples being imported into the imagestreams https://github.com/openshift/origin/blob/master/test/extended/util/framework.go#L315 is the list. so lets add back mysql even though it is unsupported