Description of problem: When /var/lib/libra was renamed to /var/lib/stickshift, /var/lib/libra was left as a symbolic link in the migration instructions to handle apps which reference that path directly. That does not work in my test application. Related: https://www.redhat.com/openshift/community/forums/express/symlinks-to-data-dir-broke Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create an app 2. ssh in to your app 3. ls -l /var/lib/[uuid]/git Actual results: [test-rmillnertest1.rhcloud.com ~]\> ls -d /var/lib/stickshift/d4145a0230734a219a509e1214268cbb/git /var/lib/stickshift/d4145a0230734a219a509e1214268cbb/git [test-rmillnertest1.rhcloud.com ~]\> ls -d /var/lib/libra/d4145a0230734a219a509e1214268cbb/git ls: cannot access /var/lib/libra/d4145a0230734a219a509e1214268cbb/git: Permission denied Expected results: That accessing /var/lib/libra/[uuid] in production would work. Additional info: New express nodes which don't go through the migration procedure won't have the symbolic link. Maby the right thing to do is just break it now.
This was fixed in production by the ops team.
Verified it on Production by ssh to my app and #ls /var/lib/libra/c69baa9fbdee446fa8a549126ffe6ef0/git appjboss.git