Bug 977914 - Dangling symlink in openshift-origin-cartridge-perl package
Dangling symlink in openshift-origin-cartridge-perl package
Product: OpenShift Origin
Classification: Red Hat
Component: Containers (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Luke Meyer
libra bugs
Depends On:
Blocks: 977919
  Show dependency treegraph
Reported: 2013-06-25 11:05 EDT by Jason DeTiberus
Modified: 2015-05-14 19:12 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 977919 (view as bug list)
Last Closed: 2013-07-22 11:12:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jason DeTiberus 2013-06-25 11:05:34 EDT
Description of problem:
openshift-origin-cartridge-perl has a dangling symlink: File usr/libexec/openshift/cartridges/v2/perl/versions/5.10/metadata is a dangling symlink (to ../shared/metadata/) on noarch

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. Install package
2. ls -l usr/libexec/openshift/cartridges/v2/perl/versions/5.10/metadata

Actual results:
ls shows broken symlink

Expected results:
symlink should not exist

Additional info:
This looks to be left over from early v2 work where there was a versions/shared/metadata directory that no longer exists.
Comment 1 openshift-github-bot 2013-07-18 15:24:07 EDT
Commit pushed to master at https://github.com/openshift/origin-server

<perl cart> bug 977914 remove broken symlinks
Comment 2 Meng Bo 2013-07-19 01:20:30 EDT
Checked on devenv_3527, issue fixed.

[root@ip-10-154-153-202 5.10]# pwd
[root@ip-10-154-153-202 5.10]# ls -al
total 8
drwxr-xr-x. 2 root root 4096 Jul 18 19:13 .
drwxr-xr-x. 4 root root 4096 Jul 18 19:13 ..
lrwxrwxrwx. 1 root root   14 Jul 18 19:13 etc -> ../shared/etc/

Note You need to log in before you can comment on or make changes to this bug.