[jira] [Updated] (AMBARI-22988) master-key option is missing from ambari-server setup action
[
https://issues.apache.org/jira/browse/AMBARI-22988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22988:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> master-key option is missing from ambari-server setup action
>
>
> Key: AMBARI-22988
> URL: https://issues.apache.org/jira/browse/AMBARI-22988
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Kishor Ramakrishnan
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{ambari-server setup --enable-lzo-under-gpl-license}} failing with
> {{Unexpected AttibuteError}}
> {noformat}
> # ambari-server setup --enable-lzo-under-gpl-license -s
> Using python /usr/bin/python
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'disabled'
> Customize user account for ambari-server daemon [y/n] (n)?
> Adjusting ambari-server permissions and ownership...
> Checking firewall status...
> Checking JDK...
> Do you want to change Oracle JDK [y/n] (n)?
> Check JDK version for Ambari Server...
> JDK version found: 8
> Minimum JDK version is 8 for Ambari. Skipping to setup different JDK for
> Ambari Server.
> Checking GPL software agreement...
> Completing setup...
> Configuring database...
> Enter advanced database configuration [y/n] (n)?
> Configuring database...
> ERROR: Unexpected AttributeError: Values instance has no attribute
> 'master_key'
> For more info run ambari-server with -v or --verbose option
> {noformat}
> *Note*: This occurs after encrypting passwords in the
> {{ambari_server.properties}} file:
> {noformat}
> # ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> 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 'setup-security' completed successfully.
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22988) master-key option is missing from ambari-server setup action
[
https://issues.apache.org/jira/browse/AMBARI-22988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22988:
Labels: pull-request-available (was: )
> master-key option is missing from ambari-server setup action
>
>
> Key: AMBARI-22988
> URL: https://issues.apache.org/jira/browse/AMBARI-22988
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Kishor Ramakrishnan
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> {{ambari-server setup --enable-lzo-under-gpl-license}} failing with
> {{Unexpected AttibuteError}}
> {noformat}
> # ambari-server setup --enable-lzo-under-gpl-license -s
> Using python /usr/bin/python
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'disabled'
> Customize user account for ambari-server daemon [y/n] (n)?
> Adjusting ambari-server permissions and ownership...
> Checking firewall status...
> Checking JDK...
> Do you want to change Oracle JDK [y/n] (n)?
> Check JDK version for Ambari Server...
> JDK version found: 8
> Minimum JDK version is 8 for Ambari. Skipping to setup different JDK for
> Ambari Server.
> Checking GPL software agreement...
> Completing setup...
> Configuring database...
> Enter advanced database configuration [y/n] (n)?
> Configuring database...
> ERROR: Unexpected AttributeError: Values instance has no attribute
> 'master_key'
> For more info run ambari-server with -v or --verbose option
> {noformat}
> *Note*: This occurs after encrypting passwords in the
> {{ambari_server.properties}} file:
> {noformat}
> # ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> 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 'setup-security' completed successfully.
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22988) master-key option is missing from ambari-server setup action
[
https://issues.apache.org/jira/browse/AMBARI-22988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22988:
--
Status: Patch Available (was: In Progress)
> master-key option is missing from ambari-server setup action
>
>
> Key: AMBARI-22988
> URL: https://issues.apache.org/jira/browse/AMBARI-22988
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Kishor Ramakrishnan
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{ambari-server setup --enable-lzo-under-gpl-license}} failing with
> {{Unexpected AttibuteError}}
> {noformat}
> # ambari-server setup --enable-lzo-under-gpl-license -s
> Using python /usr/bin/python
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'disabled'
> Customize user account for ambari-server daemon [y/n] (n)?
> Adjusting ambari-server permissions and ownership...
> Checking firewall status...
> Checking JDK...
> Do you want to change Oracle JDK [y/n] (n)?
> Check JDK version for Ambari Server...
> JDK version found: 8
> Minimum JDK version is 8 for Ambari. Skipping to setup different JDK for
> Ambari Server.
> Checking GPL software agreement...
> Completing setup...
> Configuring database...
> Enter advanced database configuration [y/n] (n)?
> Configuring database...
> ERROR: Unexpected AttributeError: Values instance has no attribute
> 'master_key'
> For more info run ambari-server with -v or --verbose option
> {noformat}
> *Note*: This occurs after encrypting passwords in the
> {{ambari_server.properties}} file:
> {noformat}
> # ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> 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 'setup-security' completed successfully.
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
