Bug 1376897

Summary: Dialog : Default values are not rendered in stack service dialog
Product: Red Hat CloudForms Management Engine Reporter: Shveta <sshveta>
Component: AutomateAssignee: eclarizi
Status: CLOSED DUPLICATE QA Contact: Shveta <sshveta>
Severity: medium Docs Contact:
Priority: high    
Version: 5.6.0CC: dajohnso, gmccullo, hkataria, jhardy, jmarc, jteehan, kmorey, ldomb, mkanoor, mpovolny, obarenbo, pmcgowan, sshveta, tfitzger
Target Milestone: GA   
Target Release: 5.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: service:dialog
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-14 20:00:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Attachments:
Description Flags
blank default values none

Description Shveta 2016-09-16 19:04:48 UTC
Created attachment 1201791 [details]
blank default values

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Create a template in cloudformation -orchestration templates 
2. Create a dialog
3. Default values are not shown as in screenshot.

Actual results:


Expected results:


Additional info:
Build :   5.6.2.0.20160913114355_70e9086 

===============================
Template used : 
{
  "AWSTemplateFormatVersion" : "2010-09-09",
  "Description" : "AWS CloudFormation Sample Template DynamoDB_Table",
  "Parameters" : {
    "HaskKeyElementName" : {
      "Description" : "HashType PrimaryKey Name",
      "Type" : "String",
      "AllowedPattern" : "[a-zA-Z0-9]*",
      "Default" : "SSS",
      "MinLength": "1",
      "MaxLength": "2048",
      "ConstraintDescription" : "must contain only alphanumberic characters"
    },

    "HaskKeyElementType" : {
      "Description" : "HashType PrimaryKey Type",
      "Type" : "String",
      "Default" : "S",
      "AllowedPattern" : "[S|N]",
      "MinLength": "1",
      "MaxLength": "1",
      "ConstraintDescription" : "must be either S or N"
    },

    "ReadCapacityUnits" : {
      "Description" : "Provisioned read throughput",
      "Type" : "Number",
      "Default" : "5",
      "MinValue": "5",
      "MaxValue": "10000",
      "ConstraintDescription" : "must be between 5 and 10000"
    },

    "WriteCapacityUnits" : {
      "Description" : "Provisioned write throughput",
      "Type" : "Number",
      "Default" : "10",
      "MinValue": "5",
      "MaxValue": "10000",
      "ConstraintDescription" : "must be between 5 and 10000"
    }
  },
  "Resources" : {
    "myDynamoDBTable" : {
      "Type" : "AWS::DynamoDB::Table",
      "Properties" : {
        "AttributeDefinitions": [ {
          "AttributeName" : {"Ref" : "HaskKeyElementName"},
          "AttributeType" : {"Ref" : "HaskKeyElementType"}
        } ],
        "KeySchema": [
          { "AttributeName": {"Ref" : "HaskKeyElementName"}, "KeyType": "HASH" }
        ],
        "ProvisionedThroughput" : {
          "ReadCapacityUnits" : {"Ref" : "ReadCapacityUnits"},
          "WriteCapacityUnits" : {"Ref" : "WriteCapacityUnits"}
        }
      }
    }
  },
  "Outputs" : {
    "TableName" : {
      "Value" : {"Ref" : "myDynamoDBTable"},
      "Description" : "Table name of the newly created DynamoDB table"
    }
  }
}

Comment 3 Greg McCullough 2016-09-19 14:17:03 UTC
Shveta - Please provide the full version number (normally provided in the description).

Erik - Please work with Bill if you need help reproducing this issue.

Comment 4 Shveta 2016-09-19 18:07:17 UTC
It's there under Additional Info .
Build : 5.6.2.0.20160913114355_70e9086

Comment 6 Jeff Teehan 2016-10-03 23:34:26 UTC
I think this is the same reason why the Azure Mode value doesn't default to the default value.

Comment 7 Peter McGowan 2016-10-06 09:20:10 UTC
This seems to be the case with all service dialog elements in 5.6.2, they don't keep a default value when set

Comment 8 Jerome Marc 2016-10-07 23:12:12 UTC
Same in 5.6.2.1.20160922130607_92d5b5e

Comment 10 Dave Johnson 2016-10-14 20:00:56 UTC

*** This bug has been marked as a duplicate of bug 1383774 ***