[
https://issues.apache.org/jira/browse/AMBARI-24120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565287#comment-16565287
]
Hudson commented on AMBARI-24120:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #97 (See
[https://builds.apache.org/job/Ambari-branch-2.7/97/])
AMBARI-24120 cluster version is in invalid state (1963907+atkach:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=2538eb07849b81ba93c15b3829e660b558baa7a5])
* (edit)
ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_box.hbs
* (edit) ambari-web/app/styles/stack_versions.less
* (edit) ambari-web/app/templates/main/admin/stack_upgrade/versions.hbs
* (edit)
ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js
* (edit) ambari-web/app/messages.js
* (edit)
ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_column.hbs
* (edit) ambari-web/app/models/stack_version/repository_version.js
* (edit) ambari-web/app/views/main/admin/stack_upgrade/versions_view.js
* (edit)
ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_box_view_test.js
* (edit)
ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js
* (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js
> 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)
