You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jesus Alvarez (JIRA)" <ji...@apache.org> on 2015/06/03 05:44:49 UTC
[jira] [Created] (AMBARI-11639) Ambari Admin View URL does not get
properly parsed for custom versions
Jesus Alvarez created AMBARI-11639:
--------------------------------------
Summary: Ambari Admin View URL does not get properly parsed for custom versions
Key: AMBARI-11639
URL: https://issues.apache.org/jira/browse/AMBARI-11639
Project: Ambari
Issue Type: Bug
Components: ambari-admin
Affects Versions: 2.1.0
Environment: RHEL 6.6
Reporter: Jesus Alvarez
Assignee: Jesus Alvarez
When building a custom version of ADMIN VIEW jar with new version such as "2.1.0_custom", the UI returns a 404 message upon redirect.
Upon loading ambari-server (http://node1.bigdata:8080) for the first time, the URL is redirected to:
http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0_custom/INSTANCE/# , which returns a 404 missing page.
If the URL is manually changed to http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0/INSTANCE/# , the UI loads -- though links in ambari UI remain broken.
This appears to be caused by
latestVersion = sortedMappedVersions[sortedMappedVersions.length-1];
and ambari.service.load_server_version ; each parsing version string differently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)