Bug 1725734
Summary: | [downstream clone] ovirt-imageio-proxy should use apache's pki | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Marian Jankular <mjankula> |
Component: | ovirt-imageio-proxy | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED ERRATA | QA Contact: | Petr Matyáš <pmatyas> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.2.8 | CC: | aefrat, amashah, bugs, damion.brown, derez, didi, mtessun, nsoffer, tnisan |
Target Milestone: | ovirt-4.3.6 | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1637809 | Environment: | |
Last Closed: | 2019-10-10 15:37:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1637809 | ||
Bug Blocks: | 1385617 |
Description
Marian Jankular
2019-07-01 11:06:26 UTC
Re-targeting to 4.3.6 not being identified as blocker for 4.3.5. Hi Yedidyah, Can you please provide a clear scenario on how to verify this bug? (In reply to Avihai from comment #5) > Hi Yedidyah, > > Can you please provide a clear scenario on how to verify this bug? Something like: 1. Setup an engine, host(s), storage 2. Import the engine's CA cert to your browser (preferably a new browser profile for testing) 3. Verify that image upload from the UI works 4. Follow the procedure to use a 3rd-party CA [1] 5. Restart ovirt-imageio-proxy 6. Import the 3rd-party CA to your browser 7. Verify that image upload works 8. For extra points: Follow the rename procedure [2], try image upload, and open more bugs if needed. Once you do that, you also verify bug 1385617. There, we'll add step 5 above to the procedure [1]. For creating a CA for testing, if you do not know/have other means, you can see bug 1687301 which I helped you verify. [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/administration_guide/appe-red_hat_enterprise_virtualization_and_ssl#Replacing_the_Manager_CA_Certificate [2] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/administration_guide/chap-utilities#sect-The_oVirt_Engine_Rename_Tool (In reply to Yedidyah Bar David from comment #6) > For creating a CA for testing, if you do not know/have other means, you can > see bug 1687301 which I helped you verify. (Well, not you, but Yosi, who is the qe owner of both...) Verified on ovirt-engine-4.3.6.3-0.1.el7.noarch sync2jira sync2jira 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, 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/RHBA-2019:3015 |