Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Fri, 9 Aug 2013 19:22:48 +0000 (UTC)
From: "Tom Beerbower (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12662924.1376075095998.35073.1376076168496@arcas>
In-Reply-To: <JIRA.12662924.1376075095998@arcas>
References: <JIRA.12662924.1376075095998@arcas>
Subject: [jira] [Commented] (AMBARI-2859) Can't setup ambari-server after
 encrypt-passwords
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tom Beerbower commented on AMBARI-2859:
---------------------------------------

Tested with patch ...

{code}
ambari-server encrypt-passwords
Using python  /usr/bin/python2.6
Setting up password encryption...
Please provide master key for locking the credential store: 
Re-enter master key: 
Do you want to persist master key. If you choose not to persist, you need to provide the Master Key while starting the ambari server as an env variable named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key. Persist [y/n] (y)? y
Adjusting ambari-server permissions and ownership...
Ambari Server 'encrypt-passwords' completed successfully.
{code}
                
> Can't setup ambari-server after encrypt-passwords
> -------------------------------------------------
>
>                 Key: AMBARI-2859
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2859
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>         Attachments: AMBARI-2859.patch
>
>
> root@ip-10-236-130-247 ~# ambari-server setup
> Using python /usr/bin/python2.6
> Initializing...
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'enabled'
> SELinux mode is 'permissive'
> WARNING: SELinux is set to 'permissive' mode and temporarily disabled.
> OK to continue y/n ?
> Ambari-server daemon is configured to run under user 'root'. Change this setting y/n ?
> Adjusting ambari-server permissions and ownership...
> Checking iptables...
> iptables is disabled now. please reenable later.
> Checking JDK...
> JCE Policy archive already exists, using /var/lib/ambari-server/resources/jce_policy-6.zip
> Completing setup...
> Configuring database...
> Enter advanced database configuration y/n ?
> Default properties detected. Using built-in database.
> Enter current Master Key:
> Checking PostgreSQL...
> Running initdb: This may take upto a minute.
> About to start PostgreSQL
> Configuring local database...
> Traceback (most recent call last):
> File "/usr/sbin/ambari-server.py", line 3722, in <module>
> main()
> File "/usr/sbin/ambari-server.py", line 3540, in main
> setup(options)
> File "/usr/sbin/ambari-server.py", line 1953, in setup
> retcode = setup_db(args)
> File "/usr/sbin/ambari-server.py", line 862, in setup_db
> configure_database_username_password(args)
> File "/usr/sbin/ambari-server.py", line 1314, in configure_database_username_password
> args.database_password = decrypt_password_for_alias(JDBC_RCA_PASSWORD_ALIAS)
> File "/usr/sbin/ambari-server.py", line 2615, in decrypt_password_for_alias
> return get_encrypted_password(alias, password, properties)
> NameError: global name 'password' is not defined

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira