[AMBARI-23694] Symlinks are not followed when requesting resources from Ambari's resources entry point

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.6.2
• Fix Version/s: 2.6.2
• Component/s: ambari-server
• Labels: pull-request-available
• Assignee: Robert Levas
• Reporter: Robert Levas
• Created: 25/Apr/18 19:53
• Updated: 26/Apr/18 22:32
• Resolved: 26/Apr/18 22:32

Description

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:

# 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

# 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"
}

When this occurs, the stack definitions from BEACON are not able to be cached by the Ambari agents.

Issue Links

• is caused by: AMBARI-23663 Ensure URLs to Ambari server resources are valid
• links to: GitHub Pull Request #1099