Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1354336

Summary: we use python-paramiko instead of python2-paramiko
Product: [oVirt] ovirt-release Reporter: Yedidyah Bar David <didi>
Component: GeneralAssignee: Yedidyah Bar David <didi>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: master-002CC: bugs, lsvaty, sbonazzo
Target Milestone: ovirt-4.0.1Keywords: Rebase, ZStream
Target Release: 4.0.1Flags: sbonazzo: ovirt-4.0.z?
rule-engine: planning_ack+
sbonazzo: devel_ack+
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Rebase: Enhancements Only
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-26 11:06: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:

Description Yedidyah Bar David 2016-07-11 07:06:50 UTC
Description of problem:

$Subject.

Recently epel's packaging was changed [1] to follow fedora python packaging guidelines [2], and since then builds python2-paramiko.

We should provide python2-paramiko in ovirt-release, and either change all the packages requiring it to require the new name, or provide our own python-paramiko that depends on python2-paramiko.

(Partial?) list of packages that require python-paramiko:
ovirt-engine-setup-base
ovirt-hosted-engine-setup
lago

[1] http://pkgs.fedoraproject.org/cgit/rpms/python-paramiko.git/commit/?h=epel7&id=8b748cfcb17a28b360237711b00bab5f05dcf696
[2] https://fedoraproject.org/wiki/Packaging:Python

Comment 1 Yedidyah Bar David 2016-07-11 07:20:49 UTC
Fedora's guidelines do tell to also Provide: python-paramiko, and the package does. So at least for now it's just a change in the ovirt-release package.

Comment 2 Sandro Bonazzola 2016-07-11 07:45:45 UTC
Markins as rebase on new python-paramiko.

Comment 3 Lukas Svaty 2016-07-26 11:06:32 UTC
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