Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 72D5C173BB for ; Mon, 30 Mar 2015 13:22:58 +0000 (UTC) Received: (qmail 67139 invoked by uid 500); 30 Mar 2015 13:22:55 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 67111 invoked by uid 500); 30 Mar 2015 13:22:55 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 67020 invoked by uid 99); 30 Mar 2015 13:22:55 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Mar 2015 13:22:55 +0000 Date: Mon, 30 Mar 2015 13:22:55 +0000 (UTC) From: "Vitaly Brodetskyi (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBARI-10270) Running ambari-server setup -s should not do anything after already setup MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)