[
https://issues.apache.org/jira/browse/AMBARI-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-15161:
----------------------------------------
Fix Version/s: 2.4.0
> VERSION_MISMATCH Doesn't Change Back When Component Is Corrected
> ----------------------------------------------------------------
>
> Key: AMBARI-15161
> URL: https://issues.apache.org/jira/browse/AMBARI-15161
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15161.patch
>
>
> If the database shows a {{VERSION_MISMATCH}} for a host component, correcting
> this component doesn't set the data back:
> {code:title=hostcomponentstate}
> 1 2 ZOOKEEPER_CLIENT 2.4.0.0-86 3 INSTALLED
> 1 ZOOKEEPER NONE UNKNOWN
> 2 2 ZOOKEEPER_SERVER 2.4.0.0-86 4 STARTED 1
> ZOOKEEPER NONE UNSECURED
> 3 2 ZOOKEEPER_SERVER 2.4.0.0-86 4 STARTED 2
> ZOOKEEPER NONE UNSECURED
> 4 2 ZOOKEEPER_CLIENT 2.4.0.0-86 3 INSTALLED
> 2 ZOOKEEPER NONE UNKNOWN
> 5 2 ZOOKEEPER_SERVER 2.4.0.0-86 4 STARTED 3
> ZOOKEEPER VERSION_MISMATCH UNSECURED
> {code}
> Notice that there is a {{ZOOKEEPER_SERVER}} which has had it's version
> corrected back to {{2.4.0.0-86}} but still shows as {{VERSION_MISMATCH}}
> STR:
> 1) Stop ZK on a host
> 2) {{hdp-select}} to another version
> 3) Start ZK
> 4) After {{VERSION_MISMATCH}}, stop it again, flip it back, and start it
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
