So, there's two possible solutions to this:
First one is to use relative paths, not absolute, then the rendered file should be found in the swift container:
cat > ~/swap.yaml <<EOF resource_registry: OS::TripleO::AllNodesExtraConfig: extraconfig/all_nodes/swap-partition.yaml EOF
The other solution (which I've not yet tested) is matbu's patch for https://bugs.launchpad.net/tripleo/+bug/1624727 which I think should allow local resolution of the absolute path. (see https://review.openstack.org/#/c/379547/)
So, there's two possible solutions to this:
First one is to use relative paths, not absolute, then the rendered file should be found in the swift container:
cat > ~/swap.yaml <<EOF :AllNodesExtraC onfig: extraconfig/ all_nodes/ swap-partition. yaml
resource_registry:
OS::TripleO:
EOF
The other solution (which I've not yet tested) is matbu's patch for https:/ /bugs.launchpad .net/tripleo/ +bug/1624727 which I think should allow local resolution of the absolute path. (see https:/ /review. openstack. org/#/c/ 379547/)