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

Bug 840869

Summary: "Push is about to start" is displayed for mock even after push complete.
Product: [Retired] CloudForms Cloud Engine Reporter: Aziza Karol <akarol>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 1.1.0CC: dajohnso
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 17:59:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
msg none

Description Aziza Karol 2012-07-17 12:50:06 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.From UI, build an image for mock provider
2.click on Push.

  
Actual results:
"Push is about to start" is displayed for mock even after push complete.see attached scrrenshot.


Expected results:
This message should not be displayed after push complete

Additional info:
rpm -qa | grep  aeolus
aeolus-conductor-doc-0.11.0-0.20120717094514gitd67759c.fc16.noarch
aeolus-configure-2.7.0-0.20120717054408gitcc8302d.fc16.noarch
aeolus-conductor-devel-0.11.0-0.20120717094514gitd67759c.fc16.noarch
rubygem-aeolus-cli-0.6.0-0.20120717054338gite2a391a.fc16.noarch
aeolus-conductor-0.11.0-0.20120717094514gitd67759c.fc16.noarch
aeolus-all-0.11.0-0.20120717094514gitd67759c.fc16.noarch
aeolus-conductor-daemons-0.11.0-0.20120717094514gitd67759c.fc16.noarch
rubygem-aeolus-image-0.6.0-0.20120717054438git05a815a.fc16.noarch
Comment 1 Aziza Karol 2012-07-17 12:51:47 UTC 
Created attachment 598628 [details]
msg
Comment 2 Dave Johnson 2012-08-07 20:17:31 UTC 
Aziza, can you comment on the behavior of the other providers please
Comment 3 Aziza Karol 2012-08-08 12:56:06 UTC 
This behavior is only for mock provider.
For other providers like ec2, rhevm, vpshere it works fine.