Could not fetch contents for file:///usr/share/openstack-tripleo-heat-templates/extraconfig/tasks/post_puppet_pacemaker.yaml

[Carlos Camacho]

Description
===========

After convert post_puppet_pacemaker.yaml to post_puppet_pacemaker.j2.yaml we are starting to see
that master CI job multinode-upgrades-nv fails with: Could not fetch contents for file:///usr/share/openstack-tripleo-heat-templates/extraconfig/tasks/post_puppet_pacemaker.yaml

Also multinode-upgrades in https://review.openstack.org/#/c/462037/ fails with the same error on stable/ocata.

Fixes related to similar bugs
=============================

https://review.openstack.org/#/c/383825/
https://review.openstack.org/#/c/379547/

[Carlos Camacho (ccamacho)]

From IRC chat, seems to be a CI issue.
--templates /opt/stack/new/ocata//usr/share/openstack-tripleo-heat-templates
-e /usr/share/openstack-tripleo-heat-templates/ci/environments/multinode.yaml

we're mixing the path prefix for before/after t-h-t locations and tripleoclient matches that prefix to calculate the relative paths

[Carlos Camacho (ccamacho)]

JUst one more update:
(02:34:27 PM) shardy: ccamacho: so go ahead - basically we need to ensure all paths match --templates foo
(02:34:40 PM) shardy: and the same when we switch --templates during the upgrade

[Carlos Camacho (ccamacho)]

Checking some path tests here: https://review.openstack.org/#/c/462570/ I'll update it correctly

[Carlos Camacho (ccamacho)]

Fix proposed: https://review.openstack.org/#/c/462570/

[Carlos Camacho (ccamacho)]

This issue affects only to CI.

[Steven Hardy (shardy)]

AFAICT the patch we landed didn't fix this, CI is still failing in the same way because we reference the "old" path during the upgrade, result from here:

http://logs.openstack.org/56/437956/46/check/gate-tripleo-ci-centos-7-scenario001-multinode-upgrades-nv/b9fc137/console.html#_2017-05-15_05_44_09_336894

2017-05-15 05:44:09.336894 | tripleo.sh -- Upgrade command arguments: -e /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml --libvirt-type=qemu -t 90 -e /usr/share/openstack-tripleo-heat-templates/environments/deployed-server-environment.yaml -e /opt/stack/new/ocata/usr/share/openstack-tripleo-heat-templates/ci/environments/scenario001-multinode.yaml --compute-scale 0 --overcloud-ssh-user jenkins --validation-errors-nonfatal -e /usr/share/openstack-tripleo-heat-templates/environments/deployed-server-bootstrap-environment-centos.yaml --libvirt-type=qemu -t 90 -r /opt/stack/new/tripleo-ci/test-environments/upgrade_roles_data.yaml --overcloud-ssh-user jenkins --validation-errors-nonfatal -e /usr/share/openstack-tripleo-heat-templates/environments/low-memory-usage.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/deployed-server-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/services/sahara.yaml -e /usr/share/openstack-tripleo-heat-templates/ci/environments/scenario001-multinode.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/major-upgrade-composable-steps.yaml -e /home/jenkins/init-repo.yaml --templates /usr/share/openstack-tripleo-heat-templates

2017-05-15 05:45:04.098328 | Deploying templates in the directory /tmp/tripleoclient-VR9qpX/tripleo-heat-templates
2017-05-15 05:45:05.346680 | Could not fetch contents for file:///opt/stack/new/ocata/usr/share/openstack-tripleo-heat-templates/extraconfig/tasks/post_puppet_pacemaker.yaml

[Steven Hardy (shardy)]

So I think the problem is the patch we landed only fixed the paths for the initial deploy, the same problem exists when we switch the path to perform the upgrade.

I posted https://review.openstack.org/464667 which aims to fix it

[Carlos Camacho (ccamacho)]

The error reported was slightly different, it was failing before with:

Could not fetch contents for file:///usr/share/openstack-tripleo-heat-templates/extraconfig/tasks/post_puppet_pacemaker.yaml

Now it fails with:

No such file or directory: '/stack/new/ocata/usr/share/openstack-tripleo-heat-templates/environments/deployed-server-environment.yaml'>

I'll check the paths again.