firstboot hook doesn't seem to run anything

[Removed by request]

Using the same example from http://docs.openstack.org/developer/tripleo-docs/advanced_deployment/extra_config.html none of the deployed nodes seem to be executing any shell code.
Tested with version 5.4.0 on rhel 7.3 based images.

[Emilien Macchi (emilienm)]

could you maybe share your environment and more details about what exactly you're deploying?
Thanks

[Removed by request (removed3381998)]

Thanks Emillian, sorry for skipping it:
openstack overcloud deploy \
   --templates \
   --libvirt-type kvm \
   --ntp-server clock.redhat.com \
   --neutron-network-type vxlan \
   --neutron-tunnel-types vxlan \
   --control-scale 1 \
   -e /home/stack/virt/network/network-environment.yaml \ <-- like net_multiple_nics but 3 nics instead of 6
   -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
   -e /home/stack/virt/hostnames.yml \ <-- changing hostnames [1]
   -e first_boot_update_env.yaml [2]

1-
parameter_defaults:

    CephStorageHostnameFormat: 'ceph-%index%'
    ObjectStorageHostnameFormat: 'swift-%index%'
    ControllerHostnameFormat: 'controller-%index%'
    ComputeHostnameFormat: 'compute-%index%'

2-
resource_registry:
    OS::TripleO::NodeUserData: first_boot_update_hook.yaml <-- [3]

3-
heat_template_version: 2014-10-16
resources:
  userdata:
    type: OS::Heat::MultipartMime
    properties:
      parts:
      - config: {get_resource: update}
  update:
    type: OS::Heat::SoftwareConfig
    properties:
      config: |
        #!/bin/bash
        cp $0 /tmp/ <-- not there after deployment.
        echo "and I like whaaaaaaaaaaaaaaaaaaaaaaaaaaat" &> /tmp/whatwhat <-- not there after deployment.
        yum update -y &> /tmp/update.log <-- not there after deployment and doesn't seem to run at all.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE