Description of problem: Some advanced customization steps are no longer valid in RHOSP12 using hieradata because of the way puppet manifests are applied to containers by setting FACTER_uuid=docker instead of the instance UUID as before. Namely through '/var/lib/docker-puppet/docker-puppet.sh', which is executing puppet like this, $ > FACTER_hostname=$HOSTNAME FACTER_uuid=docker /usr/bin/puppet apply --detailed-exitcodes --color=false --logdest syslog --logdest console $TAGS /etc/config.pp This will obviously make all hiera-customization to containerized-services based on the servers UUID to fail. According to this article, https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12/html-single/advanced_overcloud_customization/index#sect-Customizing_Hieradata_for_Individual_Nodes there is no mention of this, and this is how its supposed to be done. resource_registry: OS::TripleO::ComputeExtraConfigPre: /usr/share/openstack-tripleo-heat-templates/puppet/extraconfig/pre_deploy/per_node.yaml parameter_defaults: NodeDataLookup: '{"F5055C6C-477F-47FB-AFE5-95C6928C407F": {"nova::compute::vcpu_pin_set": [ "2", "3" ]}}' Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
https://github.com/openstack/tripleo-heat-templates/blob/master/docker/docker-puppet.py#L211-L240
Any progress, guys?
I've proposed this fix upstream.
@Alex: I see you switched the version to RHOSP-15 but are we backporting this patch to RHOSP-12? Should I create another BZ?
We will likely not be able to backport this to OSP12 prior to the end of the Maintenance support for OSP12 (https://access.redhat.com/support/policy/updates/openstack/platform/). We have proactively backported this to upstream Queens so it will be available in 13 in a later zstream.