Bug 1297835
Summary: | Host install fails on Fedora 23 due to lack of dep on python2-dnf | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-host-deploy | Reporter: | Tal Nisan <tnisan> | ||||
Component: | General | Assignee: | Sandro Bonazzola <sbonazzo> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Kubica <pkubica> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | low | ||||||
Version: | master | CC: | bugs, dfediuck, lsvaty, mmucha, sbonazzo, tnisan, ylavi | ||||
Target Milestone: | ovirt-4.0.0-rc3 | Keywords: | Documentation | ||||
Target Release: | 1.5.0 | Flags: | sbonazzo:
ovirt-4.0.0?
rule-engine: planning_ack? sbonazzo: devel_ack+ pstehlik: testing_ack+ |
||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Known Issue | |||||
Doc Text: |
Fedora ONLY
Cause: dnf package manager with python 3 is used by default on Fedora >= 23
ovirt-host-deploy is executed by ovirt-engine using python2
Consequence:
Host install fails on Fedora 23 due to lack of python2-dnf and yum in the default environment
Workaround (if any):
install manually python2-dnf on the host before trying to add it to the engine
Result: host could now be added
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-07-26 10:42:32 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: | |||||||
Attachments: |
|
Host deploy fails on new Fedora 23 server host. Used the ovirt master repo Can you please try installing on the host 'python2-dnf' and then host-deploy again? I've installed 'python2-dnf' as you suggested and that indeed solved the problem Keeping in assigned, I'll move to ON_QA when creating 4.0 release notes. Release notes updated: https://github.com/oVirt/ovirt-site/pull/349 *** Bug 1349453 has been marked as a duplicate of this bug. *** This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step. If you think this bug should be verified by QE, please set its severity to high and move it back to ON_QA |
Created attachment 1113986 [details] Host deploy log Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: