You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2015/03/30 15:22:55 UTC
[jira] [Resolved] (AMBARI-10270) Running ambari-server setup -s
should not do anything after already setup
[ https://issues.apache.org/jira/browse/AMBARI-10270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vitaly Brodetskyi resolved AMBARI-10270.
----------------------------------------
Resolution: Fixed
Committed to trunk
> Running ambari-server setup -s should not do anything after already setup
> -------------------------------------------------------------------------
>
> Key: AMBARI-10270
> URL: https://issues.apache.org/jira/browse/AMBARI-10270
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Fix For: 2.1.0
>
> Attachments: AMBARI-10270.patch
>
>
> Users run "ambari-server setup" for their first-time setup of ambari to select JDK, service account, database, etc. They can also run "-s" to just accept the defaults and run w/o interaction.
> After first time setup, if the user accidentally calls setup with "-s" they lose all their setup (i.e. goes back to default). This can be very bad.
> After firsttime setup (whether run with or without -s), the -s option should basically do nothing to avoid users accidentally hurting their ambari-server setup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)