Bug 1665037 - ovrit-iso-uploader fails to run
Summary: ovrit-iso-uploader fails to run
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-iso-uploader
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.3.0
: ---
Assignee: Gal Zaidman
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-10 10:59 UTC by Steve Goodman
Modified: 2019-05-08 12:31 UTC (History)
1 user (show)

Fixed In Version: ovirt-iso-uploader-4.3.0-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-08 12:31:28 UTC
oVirt Team: Integration
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1044 0 None None None 2019-05-08 12:31:29 UTC

Description Steve Goodman 2019-01-10 10:59:13 UTC 
Description of problem:
I have a 4.3 test build installed. I ran


Version-Release number of selected component (if applicable):
ovirt-iso-uploader-4.3.0-0.1.beta.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. ssh to engine
2. enter ovirt-iso-uploader or ovirt-iso-uploader --help

Actual results:
[root@vm-17-59 ~]# ovirt-iso-uploader --help
Traceback (most recent call last):
  File "/usr/bin/ovirt-iso-uploader", line 32, in <module>
    from .glfs_api import GlfsApi
ValueError: Attempted relative import in non-package
[root@vm-17-59 ~]# 



Expected results:
It'll work.
Comment 1 Sandro Bonazzola 2019-01-10 11:07:11 UTC 
This should be fixed in 4.3.0-1
Comment 2 Petr Matyáš 2019-01-23 13:40:14 UTC 
Verified on ovirt-iso-uploader-4.3.0-1.el7ev.noarch
Comment 4 errata-xmlrpc 2019-05-08 12:31:28 UTC 
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/RHEA-2019:1044
Note You need to log in before you can comment on or make changes to this bug.