You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2015/03/10 22:17:38 UTC
[jira] [Created] (AMBARI-10017) Rolling Upgrade: Expose
FinalizeUpgradeAction to API or force transition from UPGRADED to CURRENT
for cluster_version via API request. Additional fixes
Dmitry Lysnichenko created AMBARI-10017:
-------------------------------------------
Summary: Rolling Upgrade: Expose FinalizeUpgradeAction to API or force transition from UPGRADED to CURRENT for cluster_version via API request. Additional fixes
Key: AMBARI-10017
URL: https://issues.apache.org/jira/browse/AMBARI-10017
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.0.0
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 2.0.0
To simplify for the user, provide a helper call from ambari-server like so:
{code}
ambari-server set-current {ClusterName} {VersionDisplayName}
Enter Ambari login: X
Enter Ambari password: X
{code}
make sure to handle:
1) Ambari server might be http or https
2) Ambari server port
3) Ambari server might not be running
Please refer to "sync-ldap" that is currently part of ambari-server since it does similar prompting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)