Bug 1392312
Summary: | ovirt-host-deploy with dnf packager fails to use a proxy | ||
---|---|---|---|
Product: | [oVirt] otopi | Reporter: | Yedidyah Bar David <didi> |
Component: | Plugins.packagers | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED WONTFIX | QA Contact: | Lukas Svaty <lsvaty> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | master | CC: | bugs, pasik |
Target Milestone: | --- | Flags: | sbonazzo:
ovirt-4.5?
|
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-12-16 07:58:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Yedidyah Bar David
2016-11-07 07:39:09 UTC
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0. If you think this bug should block 4.3.0 please re-target and set blocker flag. didi is this still reproducible? It's been some time since I last tried to use a proxy for this. Since I did provide a workaround, I do not mind closing for now. I still think it's a relevant flow, but if I am the only one trying it, perhaps it's not that important... In 4.4 we are not going to use ovirt-host-deploy anymore, moving to ansible based deploy. |