You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Georgios Andrianakis (JIRA)" <ji...@apache.org> on 2017/11/08 11:22:00 UTC
[jira] [Updated] (AMBARI-22381) UI does not display correct
versions in 'Stack and Versions' when multiple "same" HDP versions exist
[ https://issues.apache.org/jira/browse/AMBARI-22381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Georgios Andrianakis updated AMBARI-22381:
------------------------------------------
Description:
Essentially when multiple versions of HDP exist, for example 2.6.0, 2.6.2 and 2.6.3 have been installed at various times, the UI in *Admin* / *Stacks and Versions* displays incorrect version numbers, both for installed and candidate services.
In the example case mentioned above, Ambari Web was displaying the service versions that corresponded to HDP 2.6.0 (which was the oldest of the 2.6 HDP platforms that had been installed).
I believe that the root of the issue is the Javascript function _loadServiceVersionFromVersionDefinitionsSuccessCallback_.
In that function a Stack is chosen only based on the truncated version (2.6 in the example).
I essentially side-stepped the problem by deleting the database records in various tables that corresponded to HDP 2.6.0 and HDP 2.6.2.
was:
Essentially when multiple versions of HDP exist, for example 2.6.0, 2.6.2 and 2.6.3 have been installed at various times, the UI in *Admin* / *Stacks and Versions* displays incorrect version numbers, both for installed and candidate services.
In the example case mentioned above, Ambari Web was displaying the service versions that corresponded to HDP 2.6.0 (which was the oldest of the 2.6 HDP platforms that had been installed).
I believe that the root of the issue is the javascript function _loadServiceVersionFromVersionDefinitionsSuccessCallback_.
In that function a Stack is chosen only based on the truncated version (2.6 in the example).
I essentially side-stepped the problem by deleting the database records in various tables that corresponded to HDP 2.6.0 and HDP 2.6.2.
> UI does not display correct versions in 'Stack and Versions' when multiple "same" HDP versions exist
> ----------------------------------------------------------------------------------------------------
>
> Key: AMBARI-22381
> URL: https://issues.apache.org/jira/browse/AMBARI-22381
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.6.0
> Reporter: Georgios Andrianakis
> Priority: Minor
>
> Essentially when multiple versions of HDP exist, for example 2.6.0, 2.6.2 and 2.6.3 have been installed at various times, the UI in *Admin* / *Stacks and Versions* displays incorrect version numbers, both for installed and candidate services.
> In the example case mentioned above, Ambari Web was displaying the service versions that corresponded to HDP 2.6.0 (which was the oldest of the 2.6 HDP platforms that had been installed).
> I believe that the root of the issue is the Javascript function _loadServiceVersionFromVersionDefinitionsSuccessCallback_.
> In that function a Stack is chosen only based on the truncated version (2.6 in the example).
> I essentially side-stepped the problem by deleting the database records in various tables that corresponded to HDP 2.6.0 and HDP 2.6.2.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)