Bug 746791 - rhevm push fails with 'timeout' value is not an integer
Summary: rhevm push fails with 'timeout' value is not an integer
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: imagefactory
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Ian McLeod
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-17 19:23 UTC by Dave Johnson
Modified: 2012-05-15 20:17 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 20:17:14 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0588 0 normal SHIPPED_LIVE new packages: imagefactory 2012-05-15 22:31:27 UTC

Description Dave Johnson 2011-10-17 19:23:37 UTC
Description of problem:
===================================
aeolus-image push fails with the following error in /var/log/imagefactory.log.  This occurs based on a changed in iwhd which needs to trickle down into factory.  See additional information for a workaround.

2011-10-17 14:20:54,636 DEBUG imgfac.builders.BaseBuilder.RHEL6_rhevm_Builder pid(4383) Message: Executing external RHEV-M push command (['/usr/bin/dc-rhev-image', '/tmp/tmpRX0si3'])
2011-10-17 14:20:54,707 DEBUG imgfac.builders.BaseBuilder.RHEL6_rhevm_Builder pid(4383) Message: Exception caught in ImageFactory
2011-10-17 14:20:54,708 DEBUG imgfac.builders.BaseBuilder.RHEL6_rhevm_Builder pid(4383) Message: Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/imgfac/builders/Fedora_rhevm_Builder.py", line 188, in push_image
    self.rhevm_push_image_upload(target_image_id, provider, credentials)
  File "/usr/lib/python2.6/site-packages/imgfac/builders/Fedora_rhevm_Builder.py", line 257, in rhevm_push_image_upload
    (stdout, stderr, retcode) = subprocess_check_output(rhevm_push_command)
  File "/usr/lib/python2.6/site-packages/imgfac/builders/Fedora_rhevm_Builder.py", line 46, in subprocess_check_output
    raise ImageFactoryException("'%s' failed(%d): %s\nstdout: %s" % (cmd, retcode, stderr, stdout))
ImageFactoryException: '/usr/bin/dc-rhev-image /tmp/tmpRX0si3' failed(1): None
stdout: ERROR configuration /tmp/tmpRX0si3: `timeout' value is not an integer


2011-10-17 14:20:54,708 DEBUG imgfac.BuildJob.BuildAdaptor pid(4383) Message: Raising event with agent handler (<ImageFactoryAgent(Thread-1, initial)>), changed status from PUSHING to FAILED

Version-Release number of selected component (if applicable):
===============================================================
imagefactory-0.7.0-1.el6.noarch
imagefactory-jeosconf-ec2-fedora-0.1.0-1.el6.noarch
imagefactory-jeosconf-ec2-rhel-0.1.0-1.el6.noarch
iwhd-0.990-1.el6.x86_64
rubygem-imagefactory-console-0.5.0-4.20110824113238gitd9debef.el6.noarch


Additional info:
===========================================

 So edit, 
 /usr/lib/python2.6/site-packages/imgfac/builders/Fedora_rhevm_Builder.py
 (or, possibly, python 2.7 depending on your test host)
 find the line that reads:
         provider_data['image'] = image_link
 Add a line directly below
 provider_data['timeout'] = 1800
 Then restart factory and try again

Comment 2 Ian McLeod 2011-10-17 20:31:31 UTC
This is a result of a change in the JSON that dc-rhev-image expects.

In the short term it should be possible to work around this without code changes by adding a "timeout" value to the rhev-m provider definition to include a KV pair like this:

"timeout": 1800

I will update Factory to default to this value if it is not specified.  This change will be in 0.8.0.

Comment 3 Ian McLeod 2011-10-21 13:53:53 UTC
This is fixed here:

https://github.com/aeolusproject/imagefactory/commit/e04a8d079976a1bf3049559b6aaffad5e8812a54

This will be in 0.8.0

Comment 4 Dave Johnson 2011-10-26 19:44:54 UTC
good 2 go in imagefactory-0.8.0-1.fc15.noarch

timeout value now being set inside push json

Comment 7 errata-xmlrpc 2012-05-15 20:17:14 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.

http://rhn.redhat.com/errata/RHEA-2012-0588.html


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