Bug 1906732
| Summary: | Machine API proxy support should be tested | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Joel Speed <jspeed> |
| Component: | Cloud Compute | Assignee: | Joel Speed <jspeed> |
| Cloud Compute sub component: | Other Providers | QA Contact: | Milind Yadav <miyadav> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | miyadav, xtian |
| Version: | 4.7 | Keywords: | NeedsTestCase |
| Target Milestone: | --- | ||
| Target Release: | 4.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Machine API ignored proxy settings
Consequence: Machine API traffic was not routed via a configured proxy
Fix: Ensure Machine API observes proxy settings
Result: Machine API traffic now routes via a configured proxy
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-24 15:42:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Joel Speed
2020-12-11 10:16:24 UTC
Validated on - 4.7.0-0.nightly-2020-12-20-055006 Failed job links - https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.7-e2e-aws-proxy/1340538771220729856 https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.7-e2e-aws-proxy/1341010661043343360 (4.7.0-0.nightly-2020-12-21-131655) Additional Info: Moved to assigned . @miyadav I've reviewed the links you attached. Neither of these failures are related to the machine api, but rather machine config which is not affected by the changes we introduced in 4.7. I had a look through the CI search system and couldn't find failures related to the tests that were added in the linked PR since it has merged. I don't believe any further verification is required for E2E tests like this, I think this can be moved to verified? Thanks for Reviewing @Joel . I wasn't sure , if the failure were linked or not , so moved to Assigned , Can you help me with the artifacts , related to the above changes , which confirms successful results , so that in the future , i will follow better and not make incorrect resolution , as it might be backported as well . Yes we can move it to VERIFIED if it looks good . The linked changes for this PR are just tests, so, these tests run on Machine API related repositories and are part of the `e2e-<platform>-operator`. If the tests were to fail, we have a JUNIT section which would highlight the failures at the top of the test page. For the two items you linked, I took a look at the machines.json in /artifacts/e2e-aws-proxy/gather-extra/ which shows all the machines running as expected and also took a look at the machine api component logs in /artifacts/e2e-aws-proxy/gather-extra/pods/, there were no obvious errors there. This particular change won't be backported as far as I'm aware, we certainly have no plan to do so at the moment Looks like a unit test , hence moving to VERIFIED , based on no issues seen related to these. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633 |