diff options
| author | Steve Milner <smilner@redhat.com> | 2017-08-15 17:57:45 -0400 |
|---|---|---|
| committer | Steve Milner <smilner@redhat.com> | 2017-08-15 18:02:28 -0400 |
| commit | cba2765d6af705f66a806c55640ea3fd8a7e34f8 (patch) | |
| tree | 4797ed69c5a963cf3206cbca73d7833bca6a97c4 /playbooks/common/openshift-glusterfs | |
| parent | bf27e05caafb41638f82a64dda7c9dc7fc3ce874 (diff) | |
| download | openshift-cba2765d6af705f66a806c55640ea3fd8a7e34f8.tar.gz openshift-cba2765d6af705f66a806c55640ea3fd8a7e34f8.tar.bz2 openshift-cba2765d6af705f66a806c55640ea3fd8a7e34f8.tar.xz openshift-cba2765d6af705f66a806c55640ea3fd8a7e34f8.zip | |
bug: container_binary_sync no longer moves upon symlinks
With origin 1.5, /usr/local/bin/oc was a symlink to
/usr/local/bin/openshift. During the container_binary_sync updated
versions of both binaries are copied to the host. First openshift is
copied to /usr/local/bin/openshift followed by copying oc to
/usr/local/bin/oc. Since oc is a symlink back to
/usr/local/bin/openshift the end result was everything linked to oc.
This change adds a check before copying a binary. If the destination is
a symlink then said symlink is removed before copying the new binary
over.
Fixed #4965
Reference: https://github.com/openshift/openshift-ansible/issues/4965
Diffstat (limited to 'playbooks/common/openshift-glusterfs')
0 files changed, 0 insertions, 0 deletions