Robert Levas created AMBARI-23695:
-------------------------------------
Summary: Symlinks are not followed when requesting resources from
Ambari's resources entry point
Key: AMBARI-23695
URL: https://issues.apache.org/jira/browse/AMBARI-23695
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.2
Reporter: Robert Levas
Assignee: Robert Levas
Fix For: 2.6.2
Symlinks are not followed when requesting resources from Ambari's resources
entry point.
For example if the Beacon mpack is installed, a symlink is made from
/var/lib/ambari-server/resources/mpacks/beacon-engine.mpack-1.1.0.0/addon-services/BEACON/1.1.0
to /var/lib/ambari-server/resources/stacks/HDP/2.6/services/BEACON:
{noformat}
# ls -ltr /var/lib/ambari-server/resources/stacks/HDP/2.6/services/BEACON
lrwxrwxrwx 1 root root 95 Apr 25 07:03
/var/lib/ambari-server/resources/stacks/HDP/2.6/services/BEACON ->
/var/lib/ambari-server/resources/mpacks/beacon-engine.mpack-1.1.0.0/addon-services/BEACON/1.1.0
{noformat}
{noformat}
# curl -i -X GET
http://c7401.ambari.apache.org:8080/resources/stacks/HDP/2.6/services/BEACON/metainfo.xml
HTTP/1.1 404 Not Found
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Pragma: no-cache
Content-Type: text/plain;charset=ISO-8859-1
Content-Length: 45
{
"status": 404,
"message": "Not Found"
}
{noformat}
When this occurs, the stack definitions from BEACON are not able to be cached
by the Ambari agents.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
