Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1695860 - Remove static name parameters from the AWS CloudFormation templates
Summary: Remove static name parameters from the AWS CloudFormation templates
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.1
Hardware: x86_64
OS: Other
Target Milestone: ---
: 4.1.0
Assignee: Stephen Cuppett
QA Contact: Johnny Liu
Depends On:
TreeView+ depends on / blocked
Reported: 2019-04-03 19:56 UTC by Kathryn Alexander
Modified: 2019-04-04 08:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Kathryn Alexander 2019-04-03 19:56:48 UTC
Description of problem: Several of the objects in the 02_cluster_infra.yaml template contain static name parameters that make it impossible to deploy another stack without modifying the template.

How reproducible:

Steps to Reproduce:
1. Deploy the infra template.
2. Deploy the infra template again to a different stack.

Actual results:
Stack deployment fails and is rolled back because the InternalServiceTargetGroup already exists:

            "StackId": "arn:aws:cloudformation:us-east-1:269733383066:stack/kalexanddns1/36628930-563a-11e9-8556-0ee7d31f28a0",
            "EventId": "InternalServiceTargetGroup-CREATE_FAILED-2019-04-03T17:59:28.072Z",
            "StackName": "kalexanddns1",
            "LogicalResourceId": "InternalServiceTargetGroup",
            "PhysicalResourceId": "",
            "ResourceType": "AWS::ElasticLoadBalancingV2::TargetGroup",
            "Timestamp": "2019-04-03T17:59:28.072Z",
            "ResourceStatus": "CREATE_FAILED",
            "ResourceStatusReason": "InternalServiceTargetGroup already exists in stack arn:aws:cloudformation:us-east-1:269733383066:stack/KatherineClusterInfra/aec15820-4a4b-11e9-afb3-0e7f598ae3ee",
            "ResourceProperties": "{\"VpcId\":\"vpc-005b5b485342f7bba\",\"Port\":\"22623\",\"TargetType\":\"ip\",\"TargetGroupAttributes\":[{\"Value\":\"60\",\"Key\":\"deregistration_delay.timeout_seconds\"}],\"Protocol\":\"TCP\",\"Name\":\"InternalServiceTargetGroup\"}"

Stephen has a fix for the template.

Comment 1 Stephen Cuppett 2019-04-03 20:12:45 UTC

Comment 2 Johnny Liu 2019-04-04 08:21:07 UTC
The PR is merged, so move this bug to ON_QA.

Comment 3 Johnny Liu 2019-04-04 08:24:27 UTC
Verified this bug with latest template, and passed.

Now target group are created with some random string in their name, when I am using 'jialiuuuuu2' as cluster name, those target group would something like:

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