Bug 781627 - pushed providers builds hidden by 'Some images not pushed'
Summary: pushed providers builds hidden by 'Some images not pushed'
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
Assignee: Imre Farkas
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks: ce-sprint
TreeView+ depends on / blocked
 
Reported: 2012-01-13 21:28 UTC by Dave Johnson
Modified: 2016-09-20 05:02 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-03 14:31:47 UTC


Attachments (Terms of Use)
ss (108.09 KB, image/png)
2012-01-13 21:29 UTC, Dave Johnson
no flags Details
after, real status is hidden (54.12 KB, image/png)
2012-01-13 21:30 UTC, Dave Johnson
no flags Details

Description Dave Johnson 2012-01-13 21:28:14 UTC
Description of problem:
=================================
After 'build(ing) missing' provider images, the ui flips the status of all builds, regardless of whether they actually have been successfully pushed. All builds get a 'Some of the images are not pushed' which seems kind of weird.  I am guessing this is by choice but figured it would be good to get some clarification on this.  

1.  Setup conductor and configure for multiple providers.  
2.  Add a single provider account and build and push a image.  
3.  Add one or two more provider accounts.
4.  Notice that after 'build missing' completes, all provider builds flip to 'Some images not pushed' instead of just updating the provider(s) which do not have builds pushed.

Comment 1 Dave Johnson 2012-01-13 21:29:32 UTC
Created attachment 555150 [details]
ss

Before (I actually had both rhevm builds pushed, this was a older screenshot)

Comment 2 Dave Johnson 2012-01-13 21:30:09 UTC
Created attachment 555151 [details]
after, real status is hidden

Comment 3 wes hayutin 2012-01-24 16:46:26 UTC
QE thinks factory log and conductor should have the same names used for build/push status

Comment 4 Imre Farkas 2012-01-24 17:01:06 UTC
I can't replicate this on the current 1.0-staging branch with the steps described in Comment 1. If you can, could you specify how?

Comment 5 Dave Johnson 2012-02-03 14:31:47 UTC
Spent some time on this yesterday and was unable to reproduce, closing this out for now.


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