Hide Forgot
Description of problem: Seen instance where a push failed which generate duplicate FAILED qpid events Tue Jul 26 15:35:29 2011 NOTIC com.redhat.imagefactory:BuildAdaptorStatusEvent broker=localhost:5672 addr="{u'_object_name': 'build_adaptor:push_image:9e057e18-2279-46f6-999b-3c554a414ff3', u'_agent_name': 'redhat.com:imagefactory:4d63a7ff-3caa-4cf3-a3ac-7c32a8d726dd'}" event=STATUS new_status=FAILED old_status=PUSHING Tue Jul 26 15:35:29 2011 NOTIC com.redhat.imagefactory:BuildAdaptorStatusEvent broker=localhost:5672 addr="{u'_object_name': 'build_adaptor:push_image:9e057e18-2279-46f6-999b-3c554a414ff3', u'_agent_name': 'redhat.com:imagefactory:4d63a7ff-3caa-4cf3-a3ac-7c32a8d726dd'}" event=STATUS new_status=FAILED old_status=FAILED Version-Release number of selected component (if applicable): [root@hp-dl2x170g6-01 nodes]# rpm -qa | grep factory rubygem-image_factory_console-0.4.0-1.el6.noarch rubygem-imagefactory-console-0.4.0-1.el6.noarch imagefactory-0.4.1-1.el6.noarch Steps to Reproduce: 1. configure conductor for rhevm, do not add a provider account 2. build template 3. push image to rhevm
to clarify when it fails.. you get two messages that it failed.
making sure all the bugs are at the right version for future queries
good 2 go in imagefactory-0.7.0-1.fc15.noarch
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