Region: Error in applying manifest in Region 2 configuration

[Wendy Mitchell]

Brief Description
-----------------
Error in applying manifest in Region 2 configuration (IPv6, Region2 configuration)
(sm.pp hat caused "Deprovision OpenStack - Glance Registry" to be called twice. )

Severity
--------
Standard

Steps to Reproduce
------------------
1. Installed Region1 lab
2. Attempted install the 1st controller of Region2 lab (using IPv6)

Expected Behavior
------------------
Expected install of the controller and puppet manifests to successfully apply

Actual Behavior
----------------
Puppet.log indicates an error
see error in lagtest_puppet.log starting here

2018-11-14T17:55:13.431 Debug: 2018-11-14 17:55:12 +0000 hiera(): Found platform::sm::params::infra_ip_multicast in system
2018-11-14T17:55:13.433 Error: 2018-11-14 17:55:12 +0000 Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Exec[Deprovision OpenStack - Glance Registry (service-group-member)]
is already declared in file /usr/share/puppet/modules/platform/manifests/sm.pp:503; cannot redeclare at /usr/share/puppet/modules/platform/manifests/sm.pp:564 at /usr/share/puppet/modules/platform/manifests/sm.pp:564:7 on node controller-0.wrs.com

Reproducibility
---------------
Reproducible

System Configuration
--------------------
multiregion lab, Region2 controller configuration

Branch/Pull Time/Commit
-----------------------
Master as of: 2018-11-13_20-18-0

Timestamp/Logs
--------------
see inline puppet.log error above

[Ghada Khalil (gkhalil)]

Targeting stx.2019.03; affects region config

[Ghada Khalil (gkhalil)]

Marking as Low / not release gating as there are no plans to support regions in the next StarlingX release.

[Ramaswamy Subramanian (rsubrama)]

No progress on this bug for more than 2 years. Candidate for closure. This bug may not be applicable in the latest StarlingX releases. If this issue is still relevant, please add the steps to reproduce in the latest release.

If there is no update, this issue is targeted to be closed by 30th Nov.

[Ramaswamy Subramanian (rsubrama)]

Changing the status to 'Won't Fix' as there is no activity.