You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2018/08/01 12:30:00 UTC

[jira] [Resolved] (AMBARI-24120) cluster version is in invalid state

     [ https://issues.apache.org/jira/browse/AMBARI-24120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrii Tkach resolved AMBARI-24120.
-----------------------------------
    Resolution: Fixed

> cluster version is in invalid state
> -----------------------------------
>
>                 Key: AMBARI-24120
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24120
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.6.2
>            Reporter: amarnath reddy pappu
>            Assignee: Andrii Tkach
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.7.1
>
>         Attachments: Screen Shot 2018-06-15 at 9.40.16 AM.png
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Steps to reproduce:
> 1. Make sure you have stable cluster
> 2. add a new host - and make sure it fails with the installation at the end step.
> 3. Now go to "stack and versions" screen - you will see the cluster in kind of messed up state.
> Usually customers may not see the 3rd step right after adding the host and if they observe after few days then it gives very wrong impression that cluster is it messed up state though it is not.
> Output for host_version
> {noformat}
> select * from host_version where host_id in ( 301, 551) and repo_version_id = 102
> '901','102','301','CURRENT'
> '1052','102','551','OUT_OF_SYNC'
> 2nd row is problematic one.
> {noformat}
> Workaround:
> Remove the host and add it again and make sure installation is not failing
> or
> change the status of host_version to 'CURRENT'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)