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

Bug 862295

Summary: Improper workflow when back is selected on launch screen
Product: [Retired] CloudForms Cloud Engine Reporter: james labocki <jlabocki>
Component: aeolus-conductorAssignee: Imre Farkas <ifarkas>
Status: CLOSED ERRATA QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.1.0CC: asettle, athomas, dajohnso, dmacpher, matt.wagner, morazi, slinaber, sshveta
Target Milestone: beta4Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: aeolus-conductor-0.13.18-1.el6cf Doc Type: Bug Fix
Doc Text:
There was an improper work flow when "Back" was selected on the launch screen. The "Back" button was not aware of the navigation context and does not return the user appropriately. This bug fixes the back link on deployments#launch_new for RPM installations and now a proper workflow when the "Back" button is selected is in place.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 15:22:58 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
screen1.png
none
screen3.png
none
screen1
none
screen2
none
screen3
none
cluster_selection none

Description james labocki 2012-10-02 14:37:28 UTC
Description of problem:

There is an improper workflow when "back" is select on the launch screen if a user navigates to launch an application blueprint via the application blueprint detail screen.

How reproducible:

1. Select Administer - Content - (Choose Catalog) - (Choose Application Blueprint). You will see screen1.png.
2. Select "Launch". You will see screen2.png
3. Select "Back". You will see screen3.png when you should see screen1.png.


Version-Release number of selected component (if applicable):
1.1 beta release (09.18.12 puddle)


Expected results:
"Back" button should be aware of which context a user has navigated to the page (via monitor or administer tabs) and return the user appropriately.

Comment 1 james labocki 2012-10-02 14:37:43 UTC
Created attachment 620320 [details]
screen1.png

Comment 3 james labocki 2012-10-02 14:38:16 UTC
Created attachment 620322 [details]
screen3.png

Comment 5 Dave Johnson 2012-10-02 15:26:24 UTC
This seems related to bug 860428

Comment 6 Imre Farkas 2012-10-03 13:12:29 UTC
#860428 seems to be a bug against a correct behaviour. Previously the launch button on deployables#show redirected to second page of the workflow instead of the first one. It was fixed with #859503.

As for this issue, Conductor just simply wasn't aware from where the user arrived to deployments#launch_new.
Pull request sent for to: https://github.com/aeolusproject/conductor/pull/93

Comment 7 Imre Farkas 2012-10-03 15:11:52 UTC
The above pull request is only partially fixing it, so switching back to on_dev

Comment 8 Imre Farkas 2012-10-04 11:36:02 UTC
Pull request containing the fix for RPM installations too: https://github.com/aeolusproject/conductor/pull/97

Comment 9 Matt Wagner 2012-10-04 20:38:29 UTC
I have merged this patch to master.

There is a conflict moving it over to 1.1, which I am investigating now.

Comment 10 Matt Wagner 2012-10-04 21:00:33 UTC
Conflict issues were easily resolved.

Now on 1.1:
commit d3b12322d5d26e06e891f3624317f7e8367b33d9
Author: Imre Farkas <ifarkas>
Date:   Thu Oct 4 13:31:45 2012 +0200

    BZ #862295: fix back link on deployments#launch_new for RPM installations
    
    https://bugzilla.redhat.com/show_bug.cgi?id=862295
    (cherry picked from commit c640ee4742c1b1b6e75a19a2ab259c383be59880)

Comment 11 Imre Farkas 2012-10-05 09:25:41 UTC
Conflicts were caused because the first commit was missing, so pushed it also to 1.1. Even if I resolved the conflicts, somehow it remained in the commit message.

commit 291543126ee689ae6855bbe8b357bcb4e25b740c
Author: Imre Farkas <ifarkas>
Date:   Wed Oct 3 15:04:12 2012 +0200

    BZ #862295: fix back link on deployments#launch_new
    
    https://bugzilla.redhat.com/show_bug.cgi?id=862295
    (cherry picked from commit f1d7baf24af51c12eb2cc3bb68537bb142559719)
    
    Conflicts:
        src/app/controllers/deployments_controller.rb
        src/app/views/deployables/show.html.haml

Comment 13 Shveta 2012-10-11 00:01:34 UTC
Tested in Puddle 4 .
Flow seems to be correct now.
Catalog-- App BP --Launch
Screen1.png shows , Next sceen2.png shows 
Hit Back Button screen2.png comes , Hit Back again screen3.png shows



rpm -qa|grep aeolus
aeolus-conductor-0.13.18-1.el6cf.noarch
aeolus-conductor-daemons-0.13.18-1.el6cf.noarch
aeolus-configure-2.8.9-1.el6cf.noarch
aeolus-all-0.13.18-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-doc-0.13.18-1.el6cf.noarch
rubygem-aeolus-cli-0.7.4-1.el6cf.noarch

Comment 14 Shveta 2012-10-11 00:01:58 UTC
Created attachment 625243 [details]
screen1

Comment 15 Shveta 2012-10-11 00:02:18 UTC
Created attachment 625244 [details]
screen2

Comment 16 Shveta 2012-10-11 00:02:43 UTC
Created attachment 625245 [details]
screen3

Comment 17 Shveta 2012-10-15 20:10:16 UTC
Re-Opening this bug ..
Seeing it again ..



rpm -qa|grep aeolus
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-daemons-0.13.18-1.el6cf.noarch
rubygem-aeolus-cli-0.7.4-1.el6cf.noarch
aeolus-conductor-doc-0.13.18-1.el6cf.noarch
aeolus-all-0.13.18-1.el6cf.noarch
aeolus-configure-2.8.9-1.el6cf.noarch
aeolus-conductor-0.13.18-1.el6cf.noarch

Comment 18 Shveta 2012-10-15 20:10:42 UTC
Created attachment 627669 [details]
cluster_selection

Comment 19 Imre Farkas 2012-10-16 07:51:23 UTC
Cloud you be more specific, please? What are you seeing here? I am unable to reproduce the issue. Your attachment seems to be irrelevant to this bug as it is not showing to where does the back button redirected you.

Comment 20 Shveta 2012-10-16 16:35:03 UTC
I am Sorry it is https://bugzilla.redhat.com/show_bug.cgi?id=860428 
which i wanted to Re-open this one works .

Comment 22 errata-xmlrpc 2012-12-04 15:22:58 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-1516.html