Bug 1414496 - RHV Self Hosted OpenShift deployment failure during ansible task [launch_vms : Wait for image uploads to complete] -- TypeError: sequence item 0: expected string, int found"
Summary: RHV Self Hosted OpenShift deployment failure during ansible task [launch_vms ...
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: Installation - RHEV
Version: 1.1
Hardware: All
OS: All
Target Milestone: ---
: ---
Assignee: John Matthews
QA Contact: Sudhir Mallamprabhakara
Dan Macpherson
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-18 16:24 UTC by Landon LaSmith
Modified: 2018-02-26 19:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-02-26 19:57:13 UTC
Target Upstream Version:

Attachments (Terms of Use)
Deployment logs (12.85 MB, application/zip)
2017-01-18 16:24 UTC, Landon LaSmith
no flags Details

Description Landon LaSmith 2017-01-18 16:24:23 UTC
Created attachment 1242216 [details]
Deployment logs

Description of problem: During a RHV Self Hosted + CFME + OCP API deployment, the foreman task Actions::Fusor::Deployment::OpenShift::Deploy reported the error "ansible-RHEV returned a non-zero return code". A failure occurred during the ansible task [launch_vms : Wait for image uploads to complete]. 

Summary of the output below:

FAILED - RETRYING: TASK: launch_vms : Wait for image uploads to complete (274 retries left).

Traceback (most recent call last):
   File "/etc/qci/scripts/upload_image", line 159, in <module>
   File "/etc/qci/scripts/upload_image", line 32, in main
     if '409' not in ' '.join(e.args):
 TypeError: sequence item 0: expected string, int found 

QCI Media Version: QCI-1.1-RHEL-7-20170116.t.0

How reproducible: Unknown but encountered on a few of the automation runs

Steps to Reproduce:
1. Install QCI from ISO
2. Start RHV Self Hosted deployment

Actual results: Deployment fails during

Expected results: OpenShift image upload and deployment succeeds

Comment 1 Fabian von Feilitzsch 2017-01-18 16:42:53 UTC
This error occurred when parsing the error returned by the ovirt sdk, so there is likely another underlying issue, but I put in a fix that should at least let it raise the correct error.


Note You need to log in before you can comment on or make changes to this bug.