[jira] [Commented] (AMBARI-10270) Running ambari-server setup -s should not do anything after already setup

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-10270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386894#comment-14386894 ] 

Hudson commented on AMBARI-10270:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #2145 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2145/])
AMBARI-10270. Running ambari-server setup -s should not do anything after already setup.(vbrodetskyi) (vbrodetskyi: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f15fce5bb379cd0fa3540964fbb0c0e94fa47900)
* ambari-server/src/main/python/ambari_server/serverSetup.py


> 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)