Bug 748064

Summary: Must change default value to launch deployable
Product: [Retired] CloudForms Cloud Engine Reporter: Joe Vlcek <jvlcek>
Component: aeolus-conductorAssignee: Tomas Sedovic <tsedovic>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, athomas, dajohnso, deltacloud-maint, dgao, ssachdev
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: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
finalize button
none
button none

Description Joe Vlcek 2011-10-21 21:26:30 UTC
Description of problem:

When attempting to launch a deployable with parameters that have default
values the values must be altered to activate the "Finalize" button
on page: Configure launch-time parameters for your deployment:


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


How reproducible:


Steps to Reproduce:
1. Create a deployable with parameters that have default
values.

e.g.:

<parameter name="JJV_test_data_01" type="scalar">
    <value>JJVTestData01</value>
</parameter>
<parameter name="JJV_test_data_02" type="scalar">
    <value>JJVTestData02</value>
</parameter>



2. Attempt to launch
3. Page :Configure launch-time parameters for your deployment:"
Is presented but the "Finalize" button is greyed out. In order
to activate it the default values presented must be altered.

Expected results:


The "Finalize" button should be activate without having to alter
any of the  values presented.

Comment 1 Tomas Sedovic 2011-11-03 12:12:20 UTC
This should be fixed as of commit: 1cbace08f671636633c5804562c3ee09721daef3

Comment 2 wes hayutin 2011-11-28 01:17:16 UTC
removing bugs from ce-sprint from the tracker.. you can find these bugs by querying the "qa whiteboard" for ce-sprint-60

Comment 3 Aziza Karol 2011-11-28 10:54:37 UTC
I recreated the issue by following above steps.

Could not see "Finalize" button activated.
see attached screenshot.

[root@dell-pe1950-02 ccpp-1322456272-3362]# rpm -qa | grep aeolus
rubygem-aeolus-image-0.1.0-6.el6.noarch
aeolus-conductor-daemons-0.6.0-3.el6.noarch
aeolus-conductor-doc-0.6.0-3.el6.noarch
aeolus-configure-2.3.0-1.el6.noarch
rubygem-aeolus-cli-0.1.0-4.el6.noarch
aeolus-all-0.6.0-3.el6.noarch
aeolus-conductor-0.6.0-3.el6.noarch

Comment 4 Aziza Karol 2011-11-28 10:55:55 UTC
Created attachment 537427 [details]
finalize button

Comment 5 Tomas Sedovic 2011-11-28 11:41:12 UTC
All the sections in the screenshot (Apache Server, Domain Configuration, Security Certificates and Network Configuration) need to be filled out.

Then the Finalize button becomes active.

Comment 6 Aziza Karol 2011-11-28 14:40:23 UTC
The "Finalize" button gets activated without having to alter
any of the  values presented.

see attached screenshot.

Also,if all the 4 sections(Apache Server, Domain Configuration,
Security Certificates and Network Configuration) is used in the deployable.xml then, then to get Finalize button to get active all this 4 sections has to be filled.


[root@dell-pe1950-02 ccpp-1322456272-3362]# rpm -qa | grep aeolus
rubygem-aeolus-image-0.1.0-6.el6.noarch
aeolus-conductor-daemons-0.6.0-3.el6.noarch
aeolus-conductor-doc-0.6.0-3.el6.noarch
aeolus-configure-2.3.0-1.el6.noarch
rubygem-aeolus-cli-0.1.0-4.el6.noarch
aeolus-all-0.6.0-3.el6.noarch
aeolus-conductor-0.6.0-3.el6.noarch

Comment 7 Aziza Karol 2011-11-28 14:41:58 UTC
Created attachment 537498 [details]
button