Bug 1766287: Use httpd in workload YAML templates#8459
Conversation
|
@spadgett: This pull request references Bugzilla bug 1766287, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
|
/hold |
|
/hold cancel |
|
/assign @rhamilto @jcaianirh |
|
It looks like quite a few tests are using |
Yes, we need to purge all usage of hello-openshift, but that may be okay for a separate PR. |
I believe it's almost all mock data. There is one test for Deploy Image that deploys hello-openshift from quay. I'll look more closely tomorrow. |
4366ec7 to
92e851d
Compare
Use the httpd sample image in place of hello-openshift in our YAML templates. This requires that the sample images are imported on the cluster to run successfully.
92e851d to
f53efe3
Compare
|
@rhamilto @yselkowitz OK, I removed references to hello-openshift from the core console integration tests. I also updated the YAML sample for ConsoleQuickStart to no longer reference it. Hopefully this passes CI. I'll work with the plugin teams to remove references from plugin integration tests. There are many references in mock data as well, but those should be OK. I think any additional changes will need to be in follow up PRs given the number of references. @rhamilto Another look? |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhamilto, spadgett The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
4 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@spadgett: All pull requests linked via external trackers have merged:
Bugzilla bug 1766287 has been moved to the MODIFIED state. DetailsIn response to this:
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. |
All consumers have been moved to other images: openshift/cluster-ingress-operator#561 openshift/console#8459
|
hey @spadgett - would you be amenable to backporting this and the other related PRs for this BZ to 4.7? On the samples side, we've had some tricky edge cases come up with the CVO creating the in payload To help minimize the impact of ^^, I'd like to backport the removal of the hello-openshift imagestream to 4.7 (where it was introduced) with openshift/cluster-samples-operator#393 since its introduction was already marked as a mistake so to speak. But certainly I don't want to break the 4.7 console where it still references that imagestream. |
|
/cherry-pick relase-4.7 |
|
@spadgett: cannot checkout DetailsIn response to this:
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. |
|
/cherry-pick release-4.7 |
|
@spadgett: new pull request created: #10089 DetailsIn response to this:
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. |
Use the httpd sample image in place of hello-openshift in our YAML templates. This requires that the sample images are imported on the cluster to run successfully.
This is a better example as it runs a real web server and will show the Apache test page if exposed by a route.
/cc @smarterclayton