[
https://issues.apache.org/jira/browse/AMBARI-23396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
amarnath reddy pappu updated AMBARI-23396:
------------------------------------------
Description:
Steps to reproduce
1. Install the cluster with HDP 2.6.2
2. Upgrade cluster to HDP 2.6.4
3. Now try to add a host.
4. In review page you would see as below - showing HDP2.6.2 instead of 2.6.4
repo:/HDP/2.6/redhat6/HDP-2.6:baseurl http://xxxx/HDP2.6.2/HDP-centos6/centos6/
though installation seems to be happening with 2.6.4 but UI shows incorrect
information
This is misleading and customers raising tickets.
Root cause: metainfo tables were still pointing to 2.6.2 , correcting that
would resolve the issue.
was:
Steps to reproduce
1. Install the cluster with HDP 2.6.2
2. Upgrade cluster to HDP 2.6.4
3. Now try to add a host.
4. In review page you would see as below - showing HDP2.6.2 instead of 2.6.4
repo:/HDP/2.6/redhat6/HDP-2.6:baseurl http://xxxx/HDP2.6.2/HDP-centos6/centos6/
though installation seems to be happening with 2.6.4 but UI shows incorrect
information
This is misleading and customers raising tickets.
Root cause: metainfo tables were still pointing to 2.6.2 correcting that would
resolve the issue.
> Incorrect HDP version in UI after HDP upgrade
> ---------------------------------------------
>
> Key: AMBARI-23396
> URL: https://issues.apache.org/jira/browse/AMBARI-23396
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.1
> Reporter: amarnath reddy pappu
> Priority: Major
>
> Steps to reproduce
> 1. Install the cluster with HDP 2.6.2
> 2. Upgrade cluster to HDP 2.6.4
> 3. Now try to add a host.
> 4. In review page you would see as below - showing HDP2.6.2 instead of 2.6.4
> repo:/HDP/2.6/redhat6/HDP-2.6:baseurl
> http://xxxx/HDP2.6.2/HDP-centos6/centos6/
> though installation seems to be happening with 2.6.4 but UI shows incorrect
> information
> This is misleading and customers raising tickets.
> Root cause: metainfo tables were still pointing to 2.6.2 , correcting that
> would resolve the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
