Comment 3 for bug 1382531

>> This should be fixed in the fuel-upgrade scripts because all containers read /etc/puppet/modules and /etc/puppet/manifests directly. It's possible there was a bug in the upgrade here and the symlink wasn't set up right.

We should not rewrite `/etc/puppet/modules` and `/etc/puppet/manifests` with some symlinks, because this manifests are used during the deployment of previous versions of environments.

What we can do is to make symlink to /etc/puppet/latest from the latest version of manifests, and fix start.sh in the container to run manifests and modules from this directory.