[AMBARI-17031] Atlas Integration : Deploying HA Blueprint with Atlas does not work

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Assignee: Tom Beerbower
• Reporter: Tom Beerbower
• Created: 03/Jun/16 15:39
• Updated: 20/Oct/16 19:43
• Resolved: 07/Jun/16 20:07

Description

When deploying a blueprint that specified ha enabled (atlas.server.ha.enabled=true), the atlas.server.address.id1, atlas.server.address.id2 (etc) needs to be replaced with the hostnames for the host group. This does not occur today, instead the atlas.server.address.id1 is tokenized with (for example): atlas.server.host.id1: "server_hosts", which is not quite correct. I believe the blueprint runtime generator needs to create the proper entries with a different token that is replaced with each host where Atlas server is deployed.

Issue Links

• is duplicated by: AMBARI-14887 Atlas Integration : Fix Atlas-Kafka properties for Blueprints
• links to: code review and patch