Bug 788719 - when build/push finishes, ajax should enable push/launch button
Summary: when build/push finishes, ajax should enable push/launch button
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
Assignee: Petr Blaho
QA Contact: Martin Kočí
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-08 21:49 UTC by Dave Johnson
Modified: 2012-05-15 22:36 UTC (History)
6 users (show)

Fixed In Version: v0.8.0-34
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 22:36:22 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0583 0 normal SHIPPED_LIVE new packages: aeolus-conductor 2012-05-15 22:31:59 UTC

Description Dave Johnson 2012-02-08 21:49:13 UTC
Description of problem:
==============================
Right now the user has to refresh the component outline details page once a build is completed in order to push, thinking that ajax should enable this button.

The same is true for deployables, when a push finishes, the launch button should become enabled without having to refresh.

Comment 1 Petr Blaho 2012-02-22 13:56:41 UTC
First part works on master branch
"Right now the user has to refresh the component outline details page once a
build is completed in order to push, thinking that ajax should enable this
button."


Patch for other part sent to list:

https://fedorahosted.org/pipermail/aeolus-devel/2012-February/009095.html

Comment 2 Petr Blaho 2012-02-22 16:16:20 UTC
Pushed in:

commit 683c749754c73e162b951530776a846d73e8a24a
Author: Petr Blaho <pblaho>
Date:   Wed Feb 22 14:02:59 2012 +0100

    Enable or disable launch button on deployables show page
    
    via ajax update according to build results
    
    https://bugzilla.redhat.com/show_bug.cgi?id=788719

Comment 3 Dave Johnson 2012-02-24 03:52:11 UTC
Noticed on component outline detail page, the push all button doesn't seem to "appear" once the build completes...

Seems like everything else is good to go though, Martin can decide though.

Comment 4 Dave Johnson 2012-02-24 14:50:53 UTC
Martin has left it up to me, I'll open up a new bug for the push all button

good to go in conductor-v0.8.0-34

Comment 5 Dave Johnson 2012-03-02 18:59:36 UTC
I am starting to see this again on the application blueprint page, I have to refresh the page inorder for the launch button to become available after a push completes.

Comment 6 Petr Blaho 2012-03-05 13:51:47 UTC
Just tested it and works for me.

Did it updates "Some of the component outlines are not pushed" text to "All Component Outlines are pushed and recent." on Component Outline page after push?

Comment 7 Petr Blaho 2012-03-05 19:25:23 UTC
Dave and me have discovered that this works for /catalogs/:catalog_id/deployables/:id but does not work for /deployables/:id .

In fact there is defined routers for /catalogs/:catalog_id/deployables/:id path in backbone/routers.js but not for /deployables/:id .

I will provide patch that handles that.

Comment 9 Petr Blaho 2012-03-05 21:01:39 UTC
Pushed:

commit 57543cd7f6a4d21a47542c33ab53b60e25c55053
Author: Petr Blaho <pblaho>
Date:   Mon Mar 5 20:50:08 2012 +0100

    Enable ajax update via backbone on /deployables/:id
    
    https://bugzilla.redhat.com/show_bug.cgi?id=788719

Comment 11 Shveta 2012-03-07 05:30:26 UTC
launch button is enabled as soon as build/push is finished

Checked both for :/catalogs/:catalog_id/deployables/:id 
and               /deployables/:id 



rpm -qa|grep aeolus
aeolus-conductor-doc-0.8.0-41.el6.noarch
aeolus-conductor-daemons-0.8.0-41.el6.noarch
rubygem-aeolus-cli-0.3.0-13.el6.noarch
aeolus-all-0.8.0-41.el6.noarch
aeolus-conductor-0.8.0-41.el6.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-configure-2.5.0-18.el6.noarch

Comment 12 errata-xmlrpc 2012-05-15 22:36:22 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-0583.html


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