Bug 851177

Summary: Changing launch-time parameters makes no effect for deployed instance.
Product: [Retired] CloudForms Cloud Engine Reporter: Milan Falešník <mfalesni>
Component: aeolus-conductorAssignee: Tomas Sedovic <tsedovic>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.1.0CC: dajohnso, morazi, srevivo
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 18:33:14 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
Images of the procedure + proof
none
/var/log/gofer/* & /var/log/audrey.log none

Description Milan Falešník 2012-08-23 12:19:55 UTC 
Description of problem:
When you have XML with services with parameters, you can change them at launch-time. But when you change them, nothing happens, original values are taken.

Version-Release number of selected component (if applicable):
aeolus-conductor-0.13.1-1.el6cf.noarch

How reproducible:
Always (at least on my machine)

Steps to Reproduce:
1. Have some deployable (blueprint) XML with services with parameters, ideally something visible well for debugging
2. Go into Administer / Content / <catalog>
3. Select desired deployable
4. Click Launch
5. Change any parameter you want
6. Click Finalize
  
Actual results:
Everything launches as normal (by first sight), but default values are taken instead of changed ones.

Expected results:
Launched instance with parameters changed.

Additional info:
Comment 1 James Laska 2012-08-23 15:37:06 UTC 
Milan ... can you clarify the steps you are performing?

You are defining an application blueprint that includes <params> with non-empty default values.  When launching the application, you input different values through the web-ui.  After launching the application, the deployment didn't use your inputed values? 

Can you attach a screenshot of the launch parameter screen?  Additionally, can you attach appropriate files from the deployment that demonstrate the values used?  I believe you need /var/log/gofer* (and perhaps another log).

Also, can you include the version of audrey-configserver being used?
Comment 2 Milan Falešník 2012-09-03 09:04:34 UTC 
Created attachment 609304 [details]
Images of the procedure + proof

pic 1) Showing the XML source
pic 2) Showing that I've removed my public key id_rsa.pub from JENKINS_SSH_KEY_LOCATION
pic 3) But the key was copied anyway (and I logged in without pw)
Comment 3 James Laska 2012-09-06 12:14:39 UTC 
This helps, thanks Milan.  There are a few more pieces of info that will still be helpful.  Can you please include the following ...

> Additionally, can you attach appropriate files from the deployment that
> demonstrate the values used?  I believe you need /var/log/gofer* (and 
> perhaps another log /var/log/audrey*).

The gofer/audrey log from the application will show the scripts blueprint scripts being run, and include any of their stdout/stderr.

> Also, can you include the version of audrey-configserver being used?
Comment 4 Milan Falešník 2012-09-06 17:48:32 UTC 
Created attachment 610443 [details]
/var/log/gofer/* & /var/log/audrey.log

Archive with:
audrey.log
gofer/agent.log