[jira] [Updated] (AMBARI-22472) AMBARI-22472. Ambari Upgrade 2.5 -> 2.6 : Update NodeManager's HSI identity 'llap_zk_hive' and 'llap_task_hive' to use '/HIVE/HIVE_SERVER/hive_server_hive' reference in
[ https://issues.apache.org/jira/browse/AMBARI-22472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22472: - Attachment: AMBARI-22472.1.patch > AMBARI-22472. Ambari Upgrade 2.5 -> 2.6 : Update NodeManager's HSI identity > 'llap_zk_hive' and 'llap_task_hive' to use > '/HIVE/HIVE_SERVER/hive_server_hive' reference instead of creating the same > identity again. > -- > > Key: AMBARI-22472 > URL: https://issues.apache.org/jira/browse/AMBARI-22472 > Project: Ambari > Issue Type: Bug >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Attachments: AMBARI-22472.1.patch, AMBARI-22472.patch, Screen Shot > 2017-11-17 at 11.44.41 PM.png, Screen Shot 2017-11-17 at 11.44.55 PM.png > > > **Background:** > YARN NodeManager currently has: > - 2 identities in 2.5 stack, namely : > **'/HIVE/HIVE_SERVER/hive_server_hive'** and **'llap_zk_hive'**. > -- **/HIVE/HIVE_SERVER/hive_server_hive** is a reference from HIVE_SERVER, > whereas > -- **llap_zk_hive** creates same principal as above in a separate keytab file. > - and 3 identities in 2.6 stack: > *'/HIVE/HIVE_SERVER/hive_server_hive'* and *'llap_zk_hive'*. > -- **/HIVE/HIVE_SERVER/hive_server_hive** is a reference from HIVE_SERVER, > whereas > -- **llap_zk_hive** and **llap_task_hive** creates same principal as above in > a separate keytab file. > **Issue:** Recreating same identities in different files creates issues while > AMbari upgrade from 2.5 to 2.6, as the *llap_zk_hive* are not > refreshed/updated after the upgrade. Thus, HSI fails to come up. > **Fix:** > **For HDP 2.5:** Make **llap_zk_hive** point as a reference pointing to > /HIVE/HIVE_SERVER/hive_server_hive, so that we have one identity getting > created only at one place and one keytab file. > **For HDP 2.6:** Make **llap_zk_hive** and **llap_task_hive** point as a > reference pointing to /HIVE/HIVE_SERVER/hive_server_hive, so that we have one > identity getting created only at one place and one keytab file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-22472) AMBARI-22472. Ambari Upgrade 2.5 -> 2.6 : Update NodeManager's HSI identity 'llap_zk_hive' and 'llap_task_hive' to use '/HIVE/HIVE_SERVER/hive_server_hive' refer
[
https://issues.apache.org/jira/browse/AMBARI-22472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257929#comment-16257929
]
Swapan Shridhar edited comment on AMBARI-22472 at 11/21/17 6:21 AM:
*TESTING:*
|| Ambari 2.5, before upgrade:
||
{code:title=From /etc/hive2/cong/conf.server/hive-site.xml}
hive.llap.daemon.keytab.file
/etc/security/keytabs/hive.service.keytab
hive.llap.daemon.service.principal
hive/_h...@example.com
hive.llap.zk.sm.keytab.file
/etc/security/keytabs/hive.llap.zk.sm.keytab
hive.llap.zk.sm.principal
hive/_h...@example.com
{code}
||Upgrade to Ambari-2.6
||
{code:title=Logs: Ambari Server Upgrade}
[root@swap-qqq-1 ~]# ambari-server upgrade
Using python /usr/bin/python
Upgrading ambari-server
INFO: Upgrade Ambari Server
INFO: Updating Ambari Server properties in ambari.properties ...
INFO: Updating Ambari Server properties in ambari-env.sh ...
WARNING: Original file ambari-env.sh kept
INFO: Fixing database objects owner
Ambari Server configured for Embedded Postgres. Confirm you have made a backup
of the Ambari Server database [y/n] (y)? y
INFO: Upgrading database schema
INFO: Return code from schema upgrade command, retcode = 0
INFO: Schema upgrade completed
Adjusting ambari-server permissions and ownership...
Ambari Server 'upgrade' completed successfully.
[root@swap-qqq-1 ~]#
[root@swap-qqq-1 ~]#
[root@swap-qqq-1 ~]#
[root@swap-qqq-1 ~]#
[root@swap-qqq-1 ~]# ambari-server --version
2.6.0.0-267
[root@swap-qqq-1 ~]#
{code}
{code:title=Logs : Updating Kerberos descriptors}
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:673 - Updating YARN's
HSI Kerberos Descriptor
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:685 - Retrieved
HIVE->HIVE_SERVER kerberos descriptor. Name = hive_server_hive
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:700 - Retrieved
YARN->NODEMANAGER kerberos descriptor to be updated. Name = llap_zk_hive
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:709 - Updated
'llap_zk_hive' identity descriptor reference =
'/HIVE/HIVE_SERVER/hive_server_hive'
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:712 - Updated
'llap_zk_hive' principal descriptor value = ''
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:717 - Updated
'llap_zk_hive' keytab descriptor file = ''
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:720 - Updated
'llap_zk_hive' keytab descriptor owner name = ''
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:722 - Updated
'llap_zk_hive' keytab descriptor owner access = ''
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:724 - Updated
'llap_zk_hive' keytab descriptor group name = ''
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:726 - Updated
'llap_zk_hive' keytab descriptor group access = ''
18 Nov 2017 07:25:54,004 INFO [main] UpgradeCatalog260:730 - Updated
'isYarnKerberosDescUpdated' = true
{code}
{code:title=Logs : Updated HSI config 'hive.llap.zk.sm.keytab.file'}
18 Nov 2017 07:25:54,073 INFO [main] UpgradeCatalog260:767 - Updated HSI
config 'hive.llap.zk.sm.keytab.file' = /etc/security/keytabs/hive.service.keytab
{code}
*From UI :*
Changed hive.llap.zk.sm.keytab.file :
[^Screen Shot 2017-11-17 at 11.44.41 PM.png]
HSI up :
[^Screen Shot 2017-11-17 at 11.44.55 PM.png]
|| UT test runs for Ambari 2.6 and HDP 2.6 (which
includes llap_zk_hive and llap_task_hive):||
{code:title=UpgradeCatalog260Test::testUpdateKerberosDescriptorArtifact()}
2017-11-20 13:09:45,366 INFO [main] upgrade.AbstractUpgradeCatalog
(AbstractUpgradeCatalog.java:updateConfigurationPropertiesForCluster(573)) -
Applying configuration with tag 'version1511212185365' and configType
'ranger-kms-audit' to cluster 'cl1'
2017-11-20 13:09:45,367 INFO [main] upgrade.AbstractUpgradeCatalog
(AbstractUpgradeCatalog.java:updateConfigurationPropertiesForCluster(595)) -
cluster 'cl1' changed by: 'ambari-upgrade'; type='ranger-kms-audit'
tag='version2' from='version1'
2017-11-20 13:09:45,367 INFO [main] upgrade.UpgradeCatalog260
(UpgradeCatalog260.java:fixYarnHsiKerberosDescriptorAndSiteConfig(675)) -
Updating YARN's HSI Kerberos Descriptor
2017-11-20 13:09:45,368 INFO [main] upgrade.UpgradeCatalog260
(UpgradeCatalog260.java:fixYarnHsiKerberosDescriptorAndSiteConfig(687)) -
Retrieved HIVE->HIVE_SERVER kerberos descriptor. Name = hive_server_hive
2017-11-20 13:09:45,368 INFO [main] upgrade.UpgradeCatalog260
(UpgradeCatalog260.java:fixYarnHsiKerberosDescriptorAndSiteConfig(707)) -
Retrieved YARN->NODEMANAGER kerberos descriptor to be updated. Name =
llap_zk_hive
2017
[jira] [Comment Edited] (AMBARI-22472) AMBARI-22472. Ambari Upgrade 2.5 -> 2.6 : Update NodeManager's HSI identity 'llap_zk_hive' and 'llap_task_hive' to use '/HIVE/HIVE_SERVER/hive_server_hive' refer
[
https://issues.apache.org/jira/browse/AMBARI-22472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257929#comment-16257929
]
Swapan Shridhar edited comment on AMBARI-22472 at 11/21/17 1:03 AM:
*TESTING:*
|| Ambari 2.5, before upgrade:
||
{code:title=From /etc/hive2/cong/conf.server/hive-site.xml}
hive.llap.daemon.keytab.file
/etc/security/keytabs/hive.service.keytab
hive.llap.daemon.service.principal
hive/_h...@example.com
hive.llap.zk.sm.keytab.file
/etc/security/keytabs/hive.llap.zk.sm.keytab
hive.llap.zk.sm.principal
hive/_h...@example.com
{code}
||Upgrade to Ambari-2.6
||
{code:title=Logs: Ambari Server Upgrade}
[root@swap-qqq-1 ~]# ambari-server upgrade
Using python /usr/bin/python
Upgrading ambari-server
INFO: Upgrade Ambari Server
INFO: Updating Ambari Server properties in ambari.properties ...
INFO: Updating Ambari Server properties in ambari-env.sh ...
WARNING: Original file ambari-env.sh kept
INFO: Fixing database objects owner
Ambari Server configured for Embedded Postgres. Confirm you have made a backup
of the Ambari Server database [y/n] (y)? y
INFO: Upgrading database schema
INFO: Return code from schema upgrade command, retcode = 0
INFO: Schema upgrade completed
Adjusting ambari-server permissions and ownership...
Ambari Server 'upgrade' completed successfully.
[root@swap-qqq-1 ~]#
[root@swap-qqq-1 ~]#
[root@swap-qqq-1 ~]#
[root@swap-qqq-1 ~]#
[root@swap-qqq-1 ~]# ambari-server --version
2.6.0.0-267
[root@swap-qqq-1 ~]#
{code}
{code:title=Logs : Updating Kerberos descriptors}
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:673 - Updating YARN's
HSI Kerberos Descriptor
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:685 - Retrieved
HIVE->HIVE_SERVER kerberos descriptor. Name = hive_server_hive
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:700 - Retrieved
YARN->NODEMANAGER kerberos descriptor to be updated. Name = llap_zk_hive
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:709 - Updated
'llap_zk_hive' identity descriptor reference =
'/HIVE/HIVE_SERVER/hive_server_hive'
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:712 - Updated
'llap_zk_hive' principal descriptor value = ''
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:717 - Updated
'llap_zk_hive' keytab descriptor file = ''
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:720 - Updated
'llap_zk_hive' keytab descriptor owner name = ''
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:722 - Updated
'llap_zk_hive' keytab descriptor owner access = ''
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:724 - Updated
'llap_zk_hive' keytab descriptor group name = ''
18 Nov 2017 07:25:54,003 INFO [main] UpgradeCatalog260:726 - Updated
'llap_zk_hive' keytab descriptor group access = ''
18 Nov 2017 07:25:54,004 INFO [main] UpgradeCatalog260:730 - Updated
'isYarnKerberosDescUpdated' = true
{code}
{code:title=Logs : Updated HSI config 'hive.llap.zk.sm.keytab.file'}
18 Nov 2017 07:25:54,073 INFO [main] UpgradeCatalog260:767 - Updated HSI
config 'hive.llap.zk.sm.keytab.file' = /etc/security/keytabs/hive.service.keytab
{code}
*From UI :*
Changed hive.llap.zk.sm.keytab.file :
[^Screen Shot 2017-11-17 at 11.44.41 PM.png]
HSI up :
[^Screen Shot 2017-11-17 at 11.44.55 PM.png]
|| UT test runs for Ambari 2.6 and HDP 2.6 (which
includes llap_zk_hive and llap_task_hive):||
{code:title=UpgradeCatalog260Test::testUpdateKerberosDescriptorArtifact()}
2017-11-20 13:09:45,366 INFO [main] upgrade.AbstractUpgradeCatalog
(AbstractUpgradeCatalog.java:updateConfigurationPropertiesForCluster(573)) -
Applying configuration with tag 'version1511212185365' and configType
'ranger-kms-audit' to cluster 'cl1'
2017-11-20 13:09:45,367 INFO [main] upgrade.AbstractUpgradeCatalog
(AbstractUpgradeCatalog.java:updateConfigurationPropertiesForCluster(595)) -
cluster 'cl1' changed by: 'ambari-upgrade'; type='ranger-kms-audit'
tag='version2' from='version1'
2017-11-20 13:09:45,367 INFO [main] upgrade.UpgradeCatalog260
(UpgradeCatalog260.java:fixYarnHsiKerberosDescriptorAndSiteConfig(675)) -
Updating YARN's HSI Kerberos Descriptor
2017-11-20 13:09:45,368 INFO [main] upgrade.UpgradeCatalog260
(UpgradeCatalog260.java:fixYarnHsiKerberosDescriptorAndSiteConfig(687)) -
Retrieved HIVE->HIVE_SERVER kerberos descriptor. Name = hive_server_hive
2017-11-20 13:09:45,368 INFO [main] upgrade.UpgradeCatalog260
(UpgradeCatalog260.java:fixYarnHsiKerberosDescriptorAndSiteConfig(707)) -
Retrieved YARN->NODEMANAGER kerberos descriptor to be updated. Name =
llap_zk_hive
2017
[jira] [Updated] (AMBARI-22472) AMBARI-22472. Ambari Upgrade 2.5 -> 2.6 : Update NodeManager's HSI identity 'llap_zk_hive' and 'llap_task_hive' to use '/HIVE/HIVE_SERVER/hive_server_hive' reference in
[ https://issues.apache.org/jira/browse/AMBARI-22472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22472: - Description: **Background:** YARN NodeManager currently has: - 2 identities in 2.5 stack, namely : **'/HIVE/HIVE_SERVER/hive_server_hive'** and **'llap_zk_hive'**. -- **/HIVE/HIVE_SERVER/hive_server_hive** is a reference from HIVE_SERVER, whereas -- **llap_zk_hive** creates same principal as above in a separate keytab file. - and 3 identities in 2.6 stack: *'/HIVE/HIVE_SERVER/hive_server_hive'* and *'llap_zk_hive'*. -- **/HIVE/HIVE_SERVER/hive_server_hive** is a reference from HIVE_SERVER, whereas -- **llap_zk_hive** and **llap_task_hive** creates same principal as above in a separate keytab file. **Issue:** Recreating same identities in different files creates issues while AMbari upgrade from 2.5 to 2.6, as the *llap_zk_hive* are not refreshed/updated after the upgrade. Thus, HSI fails to come up. **Fix:** **For HDP 2.5:** Make **llap_zk_hive** point as a reference pointing to /HIVE/HIVE_SERVER/hive_server_hive, so that we have one identity getting created only at one place and one keytab file. **For HDP 2.6:** Make **llap_zk_hive** and **llap_task_hive** point as a reference pointing to /HIVE/HIVE_SERVER/hive_server_hive, so that we have one identity getting created only at one place and one keytab file. was: *Background:* YARN NodeManager currently have 2 identities in 2.5 and 2.6 stack, namely : *'/HIVE/HIVE_SERVER/hive_server_hive'* and *'llap_zk_hive'*. - */HIVE/HIVE_SERVER/hive_server_hive* is a reference from HIVE_SERVER, whereas - *llap_zk_hive* creates same principal as above in a separate keytab file. *Issue:* Recreating same identities in different files creates issues while *Ambari upgrade from 2.5 to 2.6*, as the *llap_zk_hive* are not refreshed/updated after the upgrade. Thus, HSI fails to come up. > AMBARI-22472. Ambari Upgrade 2.5 -> 2.6 : Update NodeManager's HSI identity > 'llap_zk_hive' and 'llap_task_hive' to use > '/HIVE/HIVE_SERVER/hive_server_hive' reference instead of creating the same > identity again. > -- > > Key: AMBARI-22472 > URL: https://issues.apache.org/jira/browse/AMBARI-22472 > Project: Ambari > Issue Type: Bug >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Attachments: AMBARI-22472.patch, Screen Shot 2017-11-17 at 11.44.41 > PM.png, Screen Shot 2017-11-17 at 11.44.55 PM.png > > > **Background:** > YARN NodeManager currently has: > - 2 identities in 2.5 stack, namely : > **'/HIVE/HIVE_SERVER/hive_server_hive'** and **'llap_zk_hive'**. > -- **/HIVE/HIVE_SERVER/hive_server_hive** is a reference from HIVE_SERVER, > whereas > -- **llap_zk_hive** creates same principal as above in a separate keytab file. > - and 3 identities in 2.6 stack: > *'/HIVE/HIVE_SERVER/hive_server_hive'* and *'llap_zk_hive'*. > -- **/HIVE/HIVE_SERVER/hive_server_hive** is a reference from HIVE_SERVER, > whereas > -- **llap_zk_hive** and **llap_task_hive** creates same principal as above in > a separate keytab file. > **Issue:** Recreating same identities in different files creates issues while > AMbari upgrade from 2.5 to 2.6, as the *llap_zk_hive* are not > refreshed/updated after the upgrade. Thus, HSI fails to come up. > **Fix:** > **For HDP 2.5:** Make **llap_zk_hive** point as a reference pointing to > /HIVE/HIVE_SERVER/hive_server_hive, so that we have one identity getting > created only at one place and one keytab file. > **For HDP 2.6:** Make **llap_zk_hive** and **llap_task_hive** point as a > reference pointing to /HIVE/HIVE_SERVER/hive_server_hive, so that we have one > identity getting created only at one place and one keytab file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22472) AMBARI-22472. Ambari Upgrade 2.5 -> 2.6 : Update NodeManager's HSI identity 'llap_zk_hive' and 'llap_task_hive' to use '/HIVE/HIVE_SERVER/hive_server_hive' reference in
[ https://issues.apache.org/jira/browse/AMBARI-22472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22472: - Summary: AMBARI-22472. Ambari Upgrade 2.5 -> 2.6 : Update NodeManager's HSI identity 'llap_zk_hive' and 'llap_task_hive' to use '/HIVE/HIVE_SERVER/hive_server_hive' reference instead of creating the same identity again. (was: Ambari Upgrade 2.5 -> 2.6 : Update NodeManager's HSI identity 'llap_zk_hive' to use '/HIVE/HIVE_SERVER/hive_server_hive' reference instead of creating the same identity again.) > AMBARI-22472. Ambari Upgrade 2.5 -> 2.6 : Update NodeManager's HSI identity > 'llap_zk_hive' and 'llap_task_hive' to use > '/HIVE/HIVE_SERVER/hive_server_hive' reference instead of creating the same > identity again. > -- > > Key: AMBARI-22472 > URL: https://issues.apache.org/jira/browse/AMBARI-22472 > Project: Ambari > Issue Type: Bug >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Attachments: AMBARI-22472.patch, Screen Shot 2017-11-17 at 11.44.41 > PM.png, Screen Shot 2017-11-17 at 11.44.55 PM.png > > > *Background:* > YARN NodeManager currently have 2 identities in 2.5 and 2.6 stack, namely : > *'/HIVE/HIVE_SERVER/hive_server_hive'* and *'llap_zk_hive'*. > - */HIVE/HIVE_SERVER/hive_server_hive* is a reference from HIVE_SERVER, > whereas > - *llap_zk_hive* creates same principal as above in a separate keytab file. > *Issue:* Recreating same identities in different files creates issues while > *Ambari upgrade from 2.5 to 2.6*, as the *llap_zk_hive* are not > refreshed/updated after the upgrade. Thus, HSI fails to come up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22487) New endpoint service_config_version for creating new config versions via service endpoint instead of cluster update
Madhuvanthi Radhakrishnan created AMBARI-22487: -- Summary: New endpoint service_config_version for creating new config versions via service endpoint instead of cluster update Key: AMBARI-22487 URL: https://issues.apache.org/jira/browse/AMBARI-22487 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 3.0.0 We should modify the service config versions API to support creation of new service config versions and entirely get rid of desired cluster configs. New APIs Create new service config version POST api/v2/clusters//servicegroups//services//configurations/service_config_versions -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22485) Allow Ambari to support non-kerberos SASL mechanisms for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-22485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya reassigned AMBARI-22485: -- Assignee: Yolanda M. Davis > Allow Ambari to support non-kerberos SASL mechanisms for Kafka > -- > > Key: AMBARI-22485 > URL: https://issues.apache.org/jira/browse/AMBARI-22485 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.0 >Reporter: Yolanda M. Davis >Assignee: Yolanda M. Davis > Attachments: AMBARI-22485-branch-2.6.patch > > > Currently AMBARI support's SASL and SSL as the security options for Kafka. > Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other > mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP > system into Kafka. > Also another important option is SASL_SSL. > We need to expose necessary configs in Ambari to enable these mechanisms for > users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22485) Allow Ambari to support non-kerberos SASL mechanisms for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-22485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yolanda M. Davis updated AMBARI-22485: -- Attachment: (was: AMBARI-22485.patch) > Allow Ambari to support non-kerberos SASL mechanisms for Kafka > -- > > Key: AMBARI-22485 > URL: https://issues.apache.org/jira/browse/AMBARI-22485 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.0 >Reporter: Yolanda M. Davis > Attachments: AMBARI-22485-branch-2.6.patch > > > Currently AMBARI support's SASL and SSL as the security options for Kafka. > Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other > mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP > system into Kafka. > Also another important option is SASL_SSL. > We need to expose necessary configs in Ambari to enable these mechanisms for > users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22485) Allow Ambari to support non-kerberos SASL mechanisms for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-22485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yolanda M. Davis updated AMBARI-22485: -- Attachment: AMBARI-22485-branch-2.6.patch > Allow Ambari to support non-kerberos SASL mechanisms for Kafka > -- > > Key: AMBARI-22485 > URL: https://issues.apache.org/jira/browse/AMBARI-22485 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.0 >Reporter: Yolanda M. Davis > Attachments: AMBARI-22485-branch-2.6.patch > > > Currently AMBARI support's SASL and SSL as the security options for Kafka. > Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other > mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP > system into Kafka. > Also another important option is SASL_SSL. > We need to expose necessary configs in Ambari to enable these mechanisms for > users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22485) Allow Ambari to support non-kerberos SASL mechanisms for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-22485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yolanda M. Davis updated AMBARI-22485: -- Attachment: AMBARI-22485.patch > Allow Ambari to support non-kerberos SASL mechanisms for Kafka > -- > > Key: AMBARI-22485 > URL: https://issues.apache.org/jira/browse/AMBARI-22485 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.0 >Reporter: Yolanda M. Davis > Attachments: AMBARI-22485.patch > > > Currently AMBARI support's SASL and SSL as the security options for Kafka. > Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other > mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP > system into Kafka. > Also another important option is SASL_SSL. > We need to expose necessary configs in Ambari to enable these mechanisms for > users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22337) each service should be able to implement server actions, package them add a jar to be loaded during EU
[ https://issues.apache.org/jira/browse/AMBARI-22337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259793#comment-16259793 ] Di Li commented on AMBARI-22337: build failures were Python tests that are not part of the changes made by this JIRA. > each service should be able to implement server actions, package them add a > jar to be loaded during EU > -- > > Key: AMBARI-22337 > URL: https://issues.apache.org/jira/browse/AMBARI-22337 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk, 2.6.1 > > Attachments: AMBARI-22337-v2.patch, AMBARI-22337-v3.patch, > AMBARI-22337.patch > > > xsi:type="server_action" tasks defined in EU/RU upgrade pack xml files > currently can only classes from Ambari source code. This limites the server > action that custom services / services from mpacks can perform. This JIRA > proposes a way to allow each service to implement server action classes, > package them in a jar to be loaded during EU > 1. Each service can have a server_actions (support stack inheritance) such as > /var/lib/ambari-server/resources/stacks/HDP/2.5/services/ZOOKEEPER/server_actions. > >a) The dir contains jar for the server action classes. > > /var/lib/ambari-server/resources/stacks/HDP/2.5/services/ZOOKEEPER/server_actions > [root@~ server_actions]# ll > total 8 > -rw-r--r-- 1 root root 7510 Oct 30 10:49 test_full.jar > 2. upgrade pack can then invoke the server action as shown below > > > > class="org.apache.ambari.server.serveraction.upgrades.SATestWithoutService"/> > > > > title="Parame > terizing Zookeeper Log4J Properties"> > class="org.apache.ambari.server.serveraction.upgrades.SATestWithService"> > zkpr test > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22337) each service should be able to implement server actions, package them add a jar to be loaded during EU
[ https://issues.apache.org/jira/browse/AMBARI-22337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22337: --- Fix Version/s: 2.6.1 > each service should be able to implement server actions, package them add a > jar to be loaded during EU > -- > > Key: AMBARI-22337 > URL: https://issues.apache.org/jira/browse/AMBARI-22337 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk, 2.6.1 > > Attachments: AMBARI-22337-v2.patch, AMBARI-22337-v3.patch, > AMBARI-22337.patch > > > xsi:type="server_action" tasks defined in EU/RU upgrade pack xml files > currently can only classes from Ambari source code. This limites the server > action that custom services / services from mpacks can perform. This JIRA > proposes a way to allow each service to implement server action classes, > package them in a jar to be loaded during EU > 1. Each service can have a server_actions (support stack inheritance) such as > /var/lib/ambari-server/resources/stacks/HDP/2.5/services/ZOOKEEPER/server_actions. > >a) The dir contains jar for the server action classes. > > /var/lib/ambari-server/resources/stacks/HDP/2.5/services/ZOOKEEPER/server_actions > [root@~ server_actions]# ll > total 8 > -rw-r--r-- 1 root root 7510 Oct 30 10:49 test_full.jar > 2. upgrade pack can then invoke the server action as shown below > > > > class="org.apache.ambari.server.serveraction.upgrades.SATestWithoutService"/> > > > > title="Parame > terizing Zookeeper Log4J Properties"> > class="org.apache.ambari.server.serveraction.upgrades.SATestWithService"> > zkpr test > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22136) Enable server_action tasks defined in EU/RU upgrade pack xml files to take parameters
[ https://issues.apache.org/jira/browse/AMBARI-22136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22136: --- Fix Version/s: 2.6.1 > Enable server_action tasks defined in EU/RU upgrade pack xml files to take > parameters > - > > Key: AMBARI-22136 > URL: https://issues.apache.org/jira/browse/AMBARI-22136 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk, 2.6.1 > > Attachments: AMBARI-22136.patch > > > xsi:type="server_action" tasks defined in EU/RU upgrade pack xml files > currently can only take impClass name, message, scope and summary as > parameters. Since no custom parameters can pass in, each server_action is > basically a special case where all stack/service information must be > hardcoded in the Java logic. > This JIRA proposes a way to pass in custom parameters as shown below > (multiple "parameter" elements). This will allow developers to create general > cased server_action that behaves accordingly to parameters passed in. > class="org.apache.ambari.server.serveraction.upgrades.VerifyExtensionLinkAction"> > a > b > MyStack > 1.2 > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22471) "yum remove snappy" deletes ambari-metrics-collector
[ https://issues.apache.org/jira/browse/AMBARI-22471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259785#comment-16259785 ] Hudson commented on AMBARI-22471: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8416 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8416/]) AMBARI-22471 : 'yum remove snappy' deletes ambari-metrics-collector. (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9910c49716d3d31eae665ab1ba0f8fbafd33c1bf]) * (edit) ambari-metrics/ambari-metrics-assembly/pom.xml > "yum remove snappy" deletes ambari-metrics-collector > > > Key: AMBARI-22471 > URL: https://issues.apache.org/jira/browse/AMBARI-22471 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.6.1 > > Attachments: AMBARI-22471.patch > > > There appears to be an invalid dependency in the packaging of snappy. > Ambari-metrics-collector has snappy as a dependency. Yum remove snappy should > fail since it is a dependency but, instead, it removes > ambari-metrics-collector (but shouldn't). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22337) each service should be able to implement server actions, package them add a jar to be loaded during EU
[ https://issues.apache.org/jira/browse/AMBARI-22337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259780#comment-16259780 ] Aravindan Vijayan commented on AMBARI-22337: [~dili] I see that this has been pushed into branch-2.6. Is this needed for 2.6? If yes, can we update the fix version accordingly? > each service should be able to implement server actions, package them add a > jar to be loaded during EU > -- > > Key: AMBARI-22337 > URL: https://issues.apache.org/jira/browse/AMBARI-22337 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22337-v2.patch, AMBARI-22337-v3.patch, > AMBARI-22337.patch > > > xsi:type="server_action" tasks defined in EU/RU upgrade pack xml files > currently can only classes from Ambari source code. This limites the server > action that custom services / services from mpacks can perform. This JIRA > proposes a way to allow each service to implement server action classes, > package them in a jar to be loaded during EU > 1. Each service can have a server_actions (support stack inheritance) such as > /var/lib/ambari-server/resources/stacks/HDP/2.5/services/ZOOKEEPER/server_actions. > >a) The dir contains jar for the server action classes. > > /var/lib/ambari-server/resources/stacks/HDP/2.5/services/ZOOKEEPER/server_actions > [root@~ server_actions]# ll > total 8 > -rw-r--r-- 1 root root 7510 Oct 30 10:49 test_full.jar > 2. upgrade pack can then invoke the server action as shown below > > > > class="org.apache.ambari.server.serveraction.upgrades.SATestWithoutService"/> > > > > title="Parame > terizing Zookeeper Log4J Properties"> > class="org.apache.ambari.server.serveraction.upgrades.SATestWithService"> > zkpr test > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22471) "yum remove snappy" deletes ambari-metrics-collector
[ https://issues.apache.org/jira/browse/AMBARI-22471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259774#comment-16259774 ] Hudson commented on AMBARI-22471: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #469 (See [https://builds.apache.org/job/Ambari-branch-2.6/469/]) AMBARI-22471 : 'yum remove snappy' deletes ambari-metrics-collector. (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=17f89c01f2153498e09997d00b528cb83ceec4f5]) * (edit) ambari-metrics/ambari-metrics-assembly/pom.xml > "yum remove snappy" deletes ambari-metrics-collector > > > Key: AMBARI-22471 > URL: https://issues.apache.org/jira/browse/AMBARI-22471 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.6.1 > > Attachments: AMBARI-22471.patch > > > There appears to be an invalid dependency in the packaging of snappy. > Ambari-metrics-collector has snappy as a dependency. Yum remove snappy should > fail since it is a dependency but, instead, it removes > ambari-metrics-collector (but shouldn't). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22337) each service should be able to implement server actions, package them add a jar to be loaded during EU
[ https://issues.apache.org/jira/browse/AMBARI-22337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259775#comment-16259775 ] Hudson commented on AMBARI-22337: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #469 (See [https://builds.apache.org/job/Ambari-branch-2.6/469/]) AMBARI-22337 each service should be able to implement server actions, (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=eecd8513a304641617cc8602f5805eee8aaf3c69]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/ServiceModuleTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceDirectory.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerActionExecutor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerExtensionTest.java * (edit) ambari-server/pom.xml > each service should be able to implement server actions, package them add a > jar to be loaded during EU > -- > > Key: AMBARI-22337 > URL: https://issues.apache.org/jira/browse/AMBARI-22337 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22337-v2.patch, AMBARI-22337-v3.patch, > AMBARI-22337.patch > > > xsi:type="server_action" tasks defined in EU/RU upgrade pack xml files > currently can only classes from Ambari source code. This limites the server > action that custom services / services from mpacks can perform. This JIRA > proposes a way to allow each service to implement server action classes, > package them in a jar to be loaded during EU > 1. Each service can have a server_actions (support stack inheritance) such as > /var/lib/ambari-server/resources/stacks/HDP/2.5/services/ZOOKEEPER/server_actions. > >a) The dir contains jar for the server action classes. > > /var/lib/ambari-server/resources/stacks/HDP/2.5/services/ZOOKEEPER/server_actions > [root@~ server_actions]# ll > total 8 > -rw-r--r-- 1 root root 7510 Oct 30 10:49 test_full.jar > 2. upgrade pack can then invoke the server action as shown below > > > > class="org.apache.ambari.server.serveraction.upgrades.SATestWithoutService"/> > > > > title="Parame > terizing Zookeeper Log4J Properties"> > class="org.apache.ambari.server.serveraction.upgrades.SATestWithService"> > zkpr test > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22469) Ambari upgrade failed
[
https://issues.apache.org/jira/browse/AMBARI-22469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259744#comment-16259744
]
Hadoop QA commented on AMBARI-22469:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898511/AMBARI-22469.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12699//console
This message is automatically generated.
> Ambari upgrade failed
> -
>
> Key: AMBARI-22469
> URL: https://issues.apache.org/jira/browse/AMBARI-22469
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22469.patch
>
>
> Ambari upgrade would fail for all Ambari view servers.
> Steps to reproduce:
> 1. Install Ambari 2.5.2 and setup it as view server. (it you don't set up it
> up as view server also it fails)
> 2. now install 2.6.0
> 3. run ambari-server upgrade
> it fails out with below exception.
> {noformat}
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException:
> Unable to find any CURRENT repositories.
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:203)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:418)
> Caused by: org.apache.ambari.server.AmbariException: Unable to find any
> CURRENT repositories.
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:510)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:194)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:200)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {noformat}
> For some reason we are checking cluster_version table entries and throwing up
> above exception.
> {noformat}
> In UpgradeCatalog260.java
> public int getCurrentVersionID() throws AmbariException, SQLException {
> List currentVersionList =
> dbAccessor.getIntColumnValues(CLUSTER_VERSION_TABLE, REPO_VERSION_ID_COLUMN,
> new String[]{STATE_COLUMN}, new String[]{CURRENT}, false);
> if (currentVersionList.isEmpty()) {
> throw new AmbariException("Unable to find any CURRENT repositories.");
> } else if (currentVersionList.size() != 1) {
> throw new AmbariException("The following repositories were found to be
> CURRENT: ".concat(StringUtils.join(currentVersionList, ",")));
> }
> return currentVersionList.get(0);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22486) Conditionally Rebuild MapReduce and Tez Tarballs with LZO if Enabled
[ https://issues.apache.org/jira/browse/AMBARI-22486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-22486: - Due Date: 20/Nov/17 > Conditionally Rebuild MapReduce and Tez Tarballs with LZO if Enabled > > > Key: AMBARI-22486 > URL: https://issues.apache.org/jira/browse/AMBARI-22486 > Project: Ambari > Issue Type: Task >Affects Versions: 2.6.1 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Fix For: 2.6.1 > > > If LZO is enabled and has been opted-in, then the Tez and MapReduce tarballs > should have LZO added to them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22470) Refine Metric Definition Service and AD Query service.
[ https://issues.apache.org/jira/browse/AMBARI-22470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22470: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-3.0-ams. > Refine Metric Definition Service and AD Query service. > -- > > Key: AMBARI-22470 > URL: https://issues.apache.org/jira/browse/AMBARI-22470 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 3.0.0 > > Attachments: AMBARI-22470-2.patch > > > * Metric definition service - integration with LevelDB. > * Metric definition service - integration with Metrics Collector > * AD Query Service - Ability to retrieve anomaly data from Phoenix. > * Fix pom.xml issues. > * Startup metric definition and query services during server start. > * Remove phoenix connection code from ambari-metrics-common collector and AD > service modules. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22337) each service should be able to implement server actions, package them add a jar to be loaded during EU
[ https://issues.apache.org/jira/browse/AMBARI-22337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259658#comment-16259658 ] Di Li commented on AMBARI-22337: pushed to branch-2.6 as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=eecd8513a304641617cc8602f5805eee8aaf3c69 > each service should be able to implement server actions, package them add a > jar to be loaded during EU > -- > > Key: AMBARI-22337 > URL: https://issues.apache.org/jira/browse/AMBARI-22337 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22337-v2.patch, AMBARI-22337-v3.patch, > AMBARI-22337.patch > > > xsi:type="server_action" tasks defined in EU/RU upgrade pack xml files > currently can only classes from Ambari source code. This limites the server > action that custom services / services from mpacks can perform. This JIRA > proposes a way to allow each service to implement server action classes, > package them in a jar to be loaded during EU > 1. Each service can have a server_actions (support stack inheritance) such as > /var/lib/ambari-server/resources/stacks/HDP/2.5/services/ZOOKEEPER/server_actions. > >a) The dir contains jar for the server action classes. > > /var/lib/ambari-server/resources/stacks/HDP/2.5/services/ZOOKEEPER/server_actions > [root@~ server_actions]# ll > total 8 > -rw-r--r-- 1 root root 7510 Oct 30 10:49 test_full.jar > 2. upgrade pack can then invoke the server action as shown below > > > > class="org.apache.ambari.server.serveraction.upgrades.SATestWithoutService"/> > > > > title="Parame > terizing Zookeeper Log4J Properties"> > class="org.apache.ambari.server.serveraction.upgrades.SATestWithService"> > zkpr test > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22486) Conditionally Rebuild MapReduce and Tez Tarballs with LZO if Enabled
Jonathan Hurley created AMBARI-22486: Summary: Conditionally Rebuild MapReduce and Tez Tarballs with LZO if Enabled Key: AMBARI-22486 URL: https://issues.apache.org/jira/browse/AMBARI-22486 Project: Ambari Issue Type: Task Affects Versions: 2.6.1 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Priority: Blocker Fix For: 2.6.1 If LZO is enabled and has been opted-in, then the Tez and MapReduce tarballs should have LZO added to them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22458) SNMP Trap should have sysuptime field filled
[ https://issues.apache.org/jira/browse/AMBARI-22458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-22458: - Summary: SNMP Trap should have sysuptime field filled (was: NMP Trap should have sysuptime field filled) > SNMP Trap should have sysuptime field filled > > > Key: AMBARI-22458 > URL: https://issues.apache.org/jira/browse/AMBARI-22458 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: amarnath reddy pappu >Assignee: Jonathan Hurley > > Currently Ambari SNMP traps does not have sysuptime field - some of the SNMP > processing tool/application drops (considers invalid)the traps if it does > not find sysuptime field. > RFC https://tools.ietf.org/search/rfc3416 does not say whether it is > required/option field - but customers expecting that Ambari should fill this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22471) "yum remove snappy" deletes ambari-metrics-collector
[ https://issues.apache.org/jira/browse/AMBARI-22471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-22471. Resolution: Fixed Pushed to branch-2.6 and trunk. > "yum remove snappy" deletes ambari-metrics-collector > > > Key: AMBARI-22471 > URL: https://issues.apache.org/jira/browse/AMBARI-22471 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.6.1 > > Attachments: AMBARI-22471.patch > > > There appears to be an invalid dependency in the packaging of snappy. > Ambari-metrics-collector has snappy as a dependency. Yum remove snappy should > fail since it is a dependency but, instead, it removes > ambari-metrics-collector (but shouldn't). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22470) Refine Metric Definition Service and AD Query service.
[ https://issues.apache.org/jira/browse/AMBARI-22470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22470: --- Status: Patch Available (was: Open) > Refine Metric Definition Service and AD Query service. > -- > > Key: AMBARI-22470 > URL: https://issues.apache.org/jira/browse/AMBARI-22470 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 3.0.0 > > Attachments: AMBARI-22470-2.patch > > > * Metric definition service - integration with LevelDB. > * Metric definition service - integration with Metrics Collector > * AD Query Service - Ability to retrieve anomaly data from Phoenix. > * Fix pom.xml issues. > * Startup metric definition and query services during server start. > * Remove phoenix connection code from ambari-metrics-common collector and AD > service modules. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22470) Refine Metric Definition Service and AD Query service.
[ https://issues.apache.org/jira/browse/AMBARI-22470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22470: --- Attachment: AMBARI-22470-2.patch > Refine Metric Definition Service and AD Query service. > -- > > Key: AMBARI-22470 > URL: https://issues.apache.org/jira/browse/AMBARI-22470 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 3.0.0 > > Attachments: AMBARI-22470-2.patch > > > * Metric definition service - integration with LevelDB. > * Metric definition service - integration with Metrics Collector > * AD Query Service - Ability to retrieve anomaly data from Phoenix. > * Fix pom.xml issues. > * Startup metric definition and query services during server start. > * Remove phoenix connection code from ambari-metrics-common collector and AD > service modules. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22471) "yum remove snappy" deletes ambari-metrics-collector
[ https://issues.apache.org/jira/browse/AMBARI-22471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259570#comment-16259570 ] Dmytro Sen commented on AMBARI-22471: - +1 > "yum remove snappy" deletes ambari-metrics-collector > > > Key: AMBARI-22471 > URL: https://issues.apache.org/jira/browse/AMBARI-22471 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.6.1 > > Attachments: AMBARI-22471.patch > > > There appears to be an invalid dependency in the packaging of snappy. > Ambari-metrics-collector has snappy as a dependency. Yum remove snappy should > fail since it is a dependency but, instead, it removes > ambari-metrics-collector (but shouldn't). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22469) Ambari upgrade failed
[
https://issues.apache.org/jira/browse/AMBARI-22469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-22469:
Attachment: AMBARI-22469.patch
> Ambari upgrade failed
> -
>
> Key: AMBARI-22469
> URL: https://issues.apache.org/jira/browse/AMBARI-22469
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22469.patch
>
>
> Ambari upgrade would fail for all Ambari view servers.
> Steps to reproduce:
> 1. Install Ambari 2.5.2 and setup it as view server. (it you don't set up it
> up as view server also it fails)
> 2. now install 2.6.0
> 3. run ambari-server upgrade
> it fails out with below exception.
> {noformat}
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException:
> Unable to find any CURRENT repositories.
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:203)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:418)
> Caused by: org.apache.ambari.server.AmbariException: Unable to find any
> CURRENT repositories.
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:510)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:194)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:200)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {noformat}
> For some reason we are checking cluster_version table entries and throwing up
> above exception.
> {noformat}
> In UpgradeCatalog260.java
> public int getCurrentVersionID() throws AmbariException, SQLException {
> List currentVersionList =
> dbAccessor.getIntColumnValues(CLUSTER_VERSION_TABLE, REPO_VERSION_ID_COLUMN,
> new String[]{STATE_COLUMN}, new String[]{CURRENT}, false);
> if (currentVersionList.isEmpty()) {
> throw new AmbariException("Unable to find any CURRENT repositories.");
> } else if (currentVersionList.size() != 1) {
> throw new AmbariException("The following repositories were found to be
> CURRENT: ".concat(StringUtils.join(currentVersionList, ",")));
> }
> return currentVersionList.get(0);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22469) Ambari upgrade failed
[
https://issues.apache.org/jira/browse/AMBARI-22469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-22469:
Status: Patch Available (was: Open)
> Ambari upgrade failed
> -
>
> Key: AMBARI-22469
> URL: https://issues.apache.org/jira/browse/AMBARI-22469
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22469.patch
>
>
> Ambari upgrade would fail for all Ambari view servers.
> Steps to reproduce:
> 1. Install Ambari 2.5.2 and setup it as view server. (it you don't set up it
> up as view server also it fails)
> 2. now install 2.6.0
> 3. run ambari-server upgrade
> it fails out with below exception.
> {noformat}
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException:
> Unable to find any CURRENT repositories.
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:203)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:418)
> Caused by: org.apache.ambari.server.AmbariException: Unable to find any
> CURRENT repositories.
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:510)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:194)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:200)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {noformat}
> For some reason we are checking cluster_version table entries and throwing up
> above exception.
> {noformat}
> In UpgradeCatalog260.java
> public int getCurrentVersionID() throws AmbariException, SQLException {
> List currentVersionList =
> dbAccessor.getIntColumnValues(CLUSTER_VERSION_TABLE, REPO_VERSION_ID_COLUMN,
> new String[]{STATE_COLUMN}, new String[]{CURRENT}, false);
> if (currentVersionList.isEmpty()) {
> throw new AmbariException("Unable to find any CURRENT repositories.");
> } else if (currentVersionList.size() != 1) {
> throw new AmbariException("The following repositories were found to be
> CURRENT: ".concat(StringUtils.join(currentVersionList, ",")));
> }
> return currentVersionList.get(0);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-22469) Ambari upgrade failed
[
https://issues.apache.org/jira/browse/AMBARI-22469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko reassigned AMBARI-22469:
---
Assignee: Dmitry Lysnichenko
> Ambari upgrade failed
> -
>
> Key: AMBARI-22469
> URL: https://issues.apache.org/jira/browse/AMBARI-22469
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.1
>
>
> Ambari upgrade would fail for all Ambari view servers.
> Steps to reproduce:
> 1. Install Ambari 2.5.2 and setup it as view server. (it you don't set up it
> up as view server also it fails)
> 2. now install 2.6.0
> 3. run ambari-server upgrade
> it fails out with below exception.
> {noformat}
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException:
> Unable to find any CURRENT repositories.
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:203)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:418)
> Caused by: org.apache.ambari.server.AmbariException: Unable to find any
> CURRENT repositories.
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:510)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:194)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:200)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {noformat}
> For some reason we are checking cluster_version table entries and throwing up
> above exception.
> {noformat}
> In UpgradeCatalog260.java
> public int getCurrentVersionID() throws AmbariException, SQLException {
> List currentVersionList =
> dbAccessor.getIntColumnValues(CLUSTER_VERSION_TABLE, REPO_VERSION_ID_COLUMN,
> new String[]{STATE_COLUMN}, new String[]{CURRENT}, false);
> if (currentVersionList.isEmpty()) {
> throw new AmbariException("Unable to find any CURRENT repositories.");
> } else if (currentVersionList.size() != 1) {
> throw new AmbariException("The following repositories were found to be
> CURRENT: ".concat(StringUtils.join(currentVersionList, ",")));
> }
> return currentVersionList.get(0);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22469) Ambari upgrade failed
[
https://issues.apache.org/jira/browse/AMBARI-22469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-22469:
Fix Version/s: 2.6.1
> Ambari upgrade failed
> -
>
> Key: AMBARI-22469
> URL: https://issues.apache.org/jira/browse/AMBARI-22469
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.1
>
>
> Ambari upgrade would fail for all Ambari view servers.
> Steps to reproduce:
> 1. Install Ambari 2.5.2 and setup it as view server. (it you don't set up it
> up as view server also it fails)
> 2. now install 2.6.0
> 3. run ambari-server upgrade
> it fails out with below exception.
> {noformat}
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException:
> Unable to find any CURRENT repositories.
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:203)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:418)
> Caused by: org.apache.ambari.server.AmbariException: Unable to find any
> CURRENT repositories.
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:510)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:194)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:200)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {noformat}
> For some reason we are checking cluster_version table entries and throwing up
> above exception.
> {noformat}
> In UpgradeCatalog260.java
> public int getCurrentVersionID() throws AmbariException, SQLException {
> List currentVersionList =
> dbAccessor.getIntColumnValues(CLUSTER_VERSION_TABLE, REPO_VERSION_ID_COLUMN,
> new String[]{STATE_COLUMN}, new String[]{CURRENT}, false);
> if (currentVersionList.isEmpty()) {
> throw new AmbariException("Unable to find any CURRENT repositories.");
> } else if (currentVersionList.size() != 1) {
> throw new AmbariException("The following repositories were found to be
> CURRENT: ".concat(StringUtils.join(currentVersionList, ",")));
> }
> return currentVersionList.get(0);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[
https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259459#comment-16259459
]
Hadoop QA commented on AMBARI-22479:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898484/AMBARI-22479.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.AmbariManagementControllerTest
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12698//console
This message is automatically generated.
> After removing force_delete_components option hosts are not deleted
> ---
>
> Key: AMBARI-22479
> URL: https://issues.apache.org/jira/browse/AMBARI-22479
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-22479.patch
>
>
> After removing force_delete_components from bulk host delete request BE
> returns "hosts not stopped error" even though the components have been stopped
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22485) Allow Ambari to support non-kerberos SASL mechanisms for Kafka
Yolanda M. Davis created AMBARI-22485: - Summary: Allow Ambari to support non-kerberos SASL mechanisms for Kafka Key: AMBARI-22485 URL: https://issues.apache.org/jira/browse/AMBARI-22485 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.6.0 Reporter: Yolanda M. Davis Currently AMBARI support's SASL and SSL as the security options for Kafka. Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP system into Kafka. Also another important option is SASL_SSL. We need to expose necessary configs in Ambari to enable these mechanisms for users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22484) Stack advisor should disallow lzo enable without accepting license agreement
Myroslav Papirkovskyi created AMBARI-22484: -- Summary: Stack advisor should disallow lzo enable without accepting license agreement Key: AMBARI-22484 URL: https://issues.apache.org/jira/browse/AMBARI-22484 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Priority: Critical Fix For: 2.6.1 If the user adds com.hadoop.compression.lzo.LzoCodec to core-site property io.compression.codec.lzo.class and the ambari.properties does not have the allow GPL software install flag, throw validation error -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22483) Add SAM StackFeatures to HDP StackFeatures - DB Storage Support
Yolanda M. Davis created AMBARI-22483:
-
Summary: Add SAM StackFeatures to HDP StackFeatures - DB Storage
Support
Key: AMBARI-22483
URL: https://issues.apache.org/jira/browse/AMBARI-22483
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.6.0
Reporter: Yolanda M. Davis
Fix For: 2.6.1
{
"name": "sam_db_file_storage",
"description": "DB based file storage in SAM",
"min_version": "2.6.3.0"
}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22482) Use case and service based mpack selection
Jason Golieb created AMBARI-22482: - Summary: Use case and service based mpack selection Key: AMBARI-22482 URL: https://issues.apache.org/jira/browse/AMBARI-22482 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Jason Golieb Assignee: Jason Golieb Fix For: 3.0.0 Enable selection of mpacks to install via use cases or by direct service selection. This includes switching between "basic" and "advanced" selection modes. Basic mode allows selection of use cases only. Advanced mode allows selection of mpacks and/or services directly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22481) Make Ambari LDAP configuration API consistent with existing API
Robert Levas created AMBARI-22481:
-
Summary: Make Ambari LDAP configuration API consistent with
existing API
Key: AMBARI-22481
URL: https://issues.apache.org/jira/browse/AMBARI-22481
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Critical
Fix For: 3.0.0
Make Ambari configuration API consistent with existing API.
The current API entry point (as of AMBARI-21307) to set and test the LDAP
configuration is {{/api/v1/ldapconfigs}}. This should be more inline with the
existing entry point for Ambari server related data...
{{/api/v1/services/AMBARI/components/AMBARI_SERVER}}.
The new API entry point for Ambari server related configuration data should be
{{/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations}}. For the
LDAP-specific configuration, the configuration category is
*_"ldap-configuration"_*.
See AMBARI-22418 for examples on setting and getting this configuration.
For testing the configuration, the following directives should be used:
* {{op=test-connection}}
* {{op=test-attributes}}
* {{op=detect-attributes}}
For example:
*Test the connection for a new set of data*
{noformat:title=URL}
POST
/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations?op=test-connection
{noformat}
{code:title=Payload}
{
"Configuration": {
"category" : "ldap-configuration",
"properties": {
"ambari.ldap.connectivity.server.host": "ldap.forumsys.com",
"ambari.ldap.connectivity.server.port": "389",
"ambari.ldap.connectivity.anonymous_bind": "true",
"ambari.ldap.attributes.user.search_base": "dc=example,dc=com",
"ambari.ldap.attributes.user.object_class": "person",
"ambari.ldap.attributes.user.name_attr": "uid",
"ambari.ldap.attributes.group.object_class": "groupOfUniqueNames",
"ambari.ldap.attributes.group.name_attr": "cn",
"ambari.ldap.attributes.group.member_attr": "uniqueMember",
"ambari.ldap.attributes.group.search_base": "dc=example,dc=com"
}
}
}
{code}
*Test the connection for an updated set of data*
{noformat:title=URL}
PUT
/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration?op=test-connection
{noformat}
{code:title=Payload}
{
"Configuration": {
"category" : "ldap-configuration",
"properties": {
"ambari.ldap.connectivity.server.host": "new.ldap.host.com"
}
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22480) Validate blueprint does not allow lzo enable without setup with license agreement
Myroslav Papirkovskyi created AMBARI-22480: -- Summary: Validate blueprint does not allow lzo enable without setup with license agreement Key: AMBARI-22480 URL: https://issues.apache.org/jira/browse/AMBARI-22480 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 2.6.1 Blueprint validation should fail if LZO is enabled and GPL license is not accepted on server setup. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22418) Make Ambari configuration API consistent with existing API.
[
https://issues.apache.org/jira/browse/AMBARI-22418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22418:
--
Description:
Make Ambari configuration API consistent with existing API.
The current API entry point (as of AMBARI-21307) is {{/api/v1/ambariconfigs}}.
This should be more inline with the existing entry point for Ambari server
related data... {{/api/v1/services/AMBARI/components/AMBARI_SERVER}}.
The new API entry point for Ambari server related configuration data should be
{{/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations}}.
Example Rest API calls:
*Create/Set configuration*
Used to create a new or explicitly set properties an existing Ambari Server
configuration
{noformat:title=URL}
POST /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
{noformat}
{code:title=Payload}
{
"Configuration": {
"category" : "ldap-configuration",
"properties": {
"ambari.ldap.connectivity.server.host": "ldap.forumsys.com",
"ambari.ldap.connectivity.server.port": "389",
"ambari.ldap.connectivity.anonymous_bind": "true",
"ambari.ldap.attributes.user.search_base": "dc=example,dc=com",
"ambari.ldap.attributes.user.object_class": "person",
"ambari.ldap.attributes.user.name_attr": "uid",
"ambari.ldap.attributes.group.object_class": "groupOfUniqueNames",
"ambari.ldap.attributes.group.name_attr": "cn",
"ambari.ldap.attributes.group.member_attr": "uniqueMember",
"ambari.ldap.attributes.group.search_base": "dc=example,dc=com"
}
}
}
{code}
*Update configuration*
Used to update existing properties or add new properties to an existing Ambari
Server configuration
{noformat:title=URL}
PUT
/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
{noformat}
{code:title=Payload}
{
"Configuration": {
"properties": {
"ambari.ldap.connectivity.server.host": "ldap.forumsys.com",
"ambari.ldap.connectivity.server.port": "389",
"ambari.ldap.connectivity.anonymous_bind": "true",
"ambari.ldap.attributes.user.search_base": "dc=example,dc=com",
"ambari.ldap.attributes.user.object_class": "person",
"ambari.ldap.attributes.user.name_attr": "uid",
"ambari.ldap.attributes.group.object_class": "groupOfUniqueNames",
"ambari.ldap.attributes.group.name_attr": "cn",
"ambari.ldap.attributes.group.member_attr": "uniqueMember",
"ambari.ldap.attributes.group.search_base": "dc=example,dc=com"
}
}
}
{code}
*Delete configuration*
Deletes an existing Ambari Server configuration
{noformat:title=URL}
DELETE
/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
{noformat}
*Get configurations*
Used to retrieve a list of the existing Ambari Server configurations
{noformat:title=URL}
GET /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
{noformat}
{code:title=Response}
{
"href" :
"http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations";,
"items" : [
{
"href" :
"http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration";,
"Configuration" : {
"category" : "ldap-configuration",
"component_name" : "AMBARI_SERVER",
"service_name" : "AMBARI"
}
}
]
}
{code}
*Get configuration*
Used to retrieve a the details about an existing Ambari Server configuration
{noformat:title=URL}
GET
/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
{noformat}
{code:title=Response}
{
"href" :
"http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration";,
"Configuration" : {
"category" : "ldap-configuration",
"component_name" : "AMBARI_SERVER",
"service_name" : "AMBARI",
"properties" : {
"ambari.ldap.connectivity.server.host": "ldap.forumsys.com",
"ambari.ldap.connectivity.server.port": "389",
"ambari.ldap.connectivity.anonymous_bind": "true",
"ambari.ldap.attributes.user.search_base": "dc=example,dc=com",
"ambari.ldap.attributes.user.object_class": "person",
"ambari.ldap.attributes.user.name_attr": "uid",
"ambari.ldap.attributes.group.object_class": "groupOfUniqueNames",
"ambari.ldap.attributes.group.name_attr": "cn",
"ambari.ldap.attributes.group.member_attr": "uniqueMember",
"ambari.ldap.attributes.group.search_base": "dc=example,dc=com"
}
}
}
{code}
was:
Make Ambari configuration API consistent with existing API.
The current API entry point (as of AMBARI-21307) is {{/api/v1/ambariconfigs}}.
This should be more inline with the existing entry point for Ambari server
related data... {{/api/v1/services/AMBARI/components/AMBARI_SERVER}}
[jira] [Commented] (AMBARI-22393) UI changes for prompting user during registration failure for new OS family
[
https://issues.apache.org/jira/browse/AMBARI-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259374#comment-16259374
]
Hadoop QA commented on AMBARI-22393:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898494/AMBARI-22393.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12697//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12697//console
This message is automatically generated.
> UI changes for prompting user during registration failure for new OS family
> ---
>
> Key: AMBARI-22393
> URL: https://issues.apache.org/jira/browse/AMBARI-22393
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-server, ambari-web
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22393.patch
>
>
> This task will include UI related template changes for the Ambari repository
> url prompt.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Edit cluster name
[ https://issues.apache.org/jira/browse/AMBARI-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259329#comment-16259329 ] Andrii Tkach commented on AMBARI-22478: --- committed to trunk > Ambari 3.0: Implement new design for Admin View: Edit cluster name > -- > > Key: AMBARI-22478 > URL: https://issues.apache.org/jira/browse/AMBARI-22478 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22478.patch, Save Cluster Name.png > > > The cluster name can be changed by interacting with the cluster name field. > Color for the text box is: #fdfbdd. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Edit cluster name
[ https://issues.apache.org/jira/browse/AMBARI-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22478: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari 3.0: Implement new design for Admin View: Edit cluster name > -- > > Key: AMBARI-22478 > URL: https://issues.apache.org/jira/browse/AMBARI-22478 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22478.patch, Save Cluster Name.png > > > The cluster name can be changed by interacting with the cluster name field. > Color for the text box is: #fdfbdd. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22393) UI changes for prompting user during registration failure for new OS family
[ https://issues.apache.org/jira/browse/AMBARI-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22393: --- Status: Patch Available (was: In Progress) Resubmitting with test failure fixes on behalf of [~Sonia] > UI changes for prompting user during registration failure for new OS family > --- > > Key: AMBARI-22393 > URL: https://issues.apache.org/jira/browse/AMBARI-22393 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server, ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22393.patch > > > This task will include UI related template changes for the Ambari repository > url prompt. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22393) UI changes for prompting user during registration failure for new OS family
[ https://issues.apache.org/jira/browse/AMBARI-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22393: --- Attachment: AMBARI-22393.patch > UI changes for prompting user during registration failure for new OS family > --- > > Key: AMBARI-22393 > URL: https://issues.apache.org/jira/browse/AMBARI-22393 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server, ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22393.patch > > > This task will include UI related template changes for the Ambari repository > url prompt. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22393) UI changes for prompting user during registration failure for new OS family
[ https://issues.apache.org/jira/browse/AMBARI-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22393: --- Status: In Progress (was: Patch Available) > UI changes for prompting user during registration failure for new OS family > --- > > Key: AMBARI-22393 > URL: https://issues.apache.org/jira/browse/AMBARI-22393 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server, ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > > This task will include UI related template changes for the Ambari repository > url prompt. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22393) UI changes for prompting user during registration failure for new OS family
[ https://issues.apache.org/jira/browse/AMBARI-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22393: --- Attachment: (was: AMBARI-22393.patch) > UI changes for prompting user during registration failure for new OS family > --- > > Key: AMBARI-22393 > URL: https://issues.apache.org/jira/browse/AMBARI-22393 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server, ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > > This task will include UI related template changes for the Ambari repository > url prompt. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Edit cluster name
[
https://issues.apache.org/jira/browse/AMBARI-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259322#comment-16259322
]
Hadoop QA commented on AMBARI-22478:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898489/AMBARI-22478.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12696//console
This message is automatically generated.
> Ambari 3.0: Implement new design for Admin View: Edit cluster name
> --
>
> Key: AMBARI-22478
> URL: https://issues.apache.org/jira/browse/AMBARI-22478
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22478.patch, Save Cluster Name.png
>
>
> The cluster name can be changed by interacting with the cluster name field.
> Color for the text box is: #fdfbdd.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[ https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259293#comment-16259293 ] Dmytro Sen commented on AMBARI-22479: - failure is not related to the patch > After removing force_delete_components option hosts are not deleted > --- > > Key: AMBARI-22479 > URL: https://issues.apache.org/jira/browse/AMBARI-22479 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 3.0.0 > > Attachments: AMBARI-22479.patch > > > After removing force_delete_components from bulk host delete request BE > returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[
https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259284#comment-16259284
]
Hadoop QA commented on AMBARI-22479:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898484/AMBARI-22479.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12695//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12695//console
This message is automatically generated.
> After removing force_delete_components option hosts are not deleted
> ---
>
> Key: AMBARI-22479
> URL: https://issues.apache.org/jira/browse/AMBARI-22479
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-22479.patch
>
>
> After removing force_delete_components from bulk host delete request BE
> returns "hosts not stopped error" even though the components have been stopped
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Edit cluster name
[ https://issues.apache.org/jira/browse/AMBARI-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259280#comment-16259280 ] Aleksandr Kovalenko commented on AMBARI-22478: -- +1 for the patch > Ambari 3.0: Implement new design for Admin View: Edit cluster name > -- > > Key: AMBARI-22478 > URL: https://issues.apache.org/jira/browse/AMBARI-22478 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22478.patch, Save Cluster Name.png > > > The cluster name can be changed by interacting with the cluster name field. > Color for the text box is: #fdfbdd. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Edit cluster name
[ https://issues.apache.org/jira/browse/AMBARI-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22478: -- Attachment: AMBARI-22478.patch > Ambari 3.0: Implement new design for Admin View: Edit cluster name > -- > > Key: AMBARI-22478 > URL: https://issues.apache.org/jira/browse/AMBARI-22478 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22478.patch, Save Cluster Name.png > > > The cluster name can be changed by interacting with the cluster name field. > Color for the text box is: #fdfbdd. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Edit cluster name
[ https://issues.apache.org/jira/browse/AMBARI-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22478: -- Attachment: (was: AMBARI-22478.patch) > Ambari 3.0: Implement new design for Admin View: Edit cluster name > -- > > Key: AMBARI-22478 > URL: https://issues.apache.org/jira/browse/AMBARI-22478 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: Save Cluster Name.png > > > The cluster name can be changed by interacting with the cluster name field. > Color for the text box is: #fdfbdd. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[ https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22479: Attachment: (was: screenshot-1.png) > After removing force_delete_components option hosts are not deleted > --- > > Key: AMBARI-22479 > URL: https://issues.apache.org/jira/browse/AMBARI-22479 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 3.0.0 > > Attachments: AMBARI-22479.patch > > > After removing force_delete_components from bulk host delete request BE > returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[
https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259240#comment-16259240
]
Hadoop QA commented on AMBARI-22479:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898485/screenshot-1.png
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12694//console
This message is automatically generated.
> After removing force_delete_components option hosts are not deleted
> ---
>
> Key: AMBARI-22479
> URL: https://issues.apache.org/jira/browse/AMBARI-22479
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-22479.patch, screenshot-1.png
>
>
> After removing force_delete_components from bulk host delete request BE
> returns "hosts not stopped error" even though the components have been stopped
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[ https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22479: Status: Patch Available (was: In Progress) > After removing force_delete_components option hosts are not deleted > --- > > Key: AMBARI-22479 > URL: https://issues.apache.org/jira/browse/AMBARI-22479 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 3.0.0 > > Attachments: AMBARI-22479.patch, screenshot-1.png > > > After removing force_delete_components from bulk host delete request BE > returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[ https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22479: Attachment: AMBARI-22479.patch > After removing force_delete_components option hosts are not deleted > --- > > Key: AMBARI-22479 > URL: https://issues.apache.org/jira/browse/AMBARI-22479 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 3.0.0 > > Attachments: AMBARI-22479.patch, screenshot-1.png > > > After removing force_delete_components from bulk host delete request BE > returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[ https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22479: Attachment: screenshot-1.png > After removing force_delete_components option hosts are not deleted > --- > > Key: AMBARI-22479 > URL: https://issues.apache.org/jira/browse/AMBARI-22479 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 3.0.0 > > Attachments: AMBARI-22479.patch, screenshot-1.png > > > After removing force_delete_components from bulk host delete request BE > returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
Dmytro Sen created AMBARI-22479: --- Summary: After removing force_delete_components option hosts are not deleted Key: AMBARI-22479 URL: https://issues.apache.org/jira/browse/AMBARI-22479 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Blocker Fix For: 3.0.0 After removing force_delete_components from bulk host delete request BE returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Edit cluster name
[
https://issues.apache.org/jira/browse/AMBARI-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259232#comment-16259232
]
Hadoop QA commented on AMBARI-22478:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898480/AMBARI-22478.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12693//console
This message is automatically generated.
> Ambari 3.0: Implement new design for Admin View: Edit cluster name
> --
>
> Key: AMBARI-22478
> URL: https://issues.apache.org/jira/browse/AMBARI-22478
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22478.patch, Save Cluster Name.png
>
>
> The cluster name can be changed by interacting with the cluster name field.
> Color for the text box is: #fdfbdd.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Edit cluster name
[ https://issues.apache.org/jira/browse/AMBARI-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22478: -- Status: Patch Available (was: Open) > Ambari 3.0: Implement new design for Admin View: Edit cluster name > -- > > Key: AMBARI-22478 > URL: https://issues.apache.org/jira/browse/AMBARI-22478 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22478.patch, Save Cluster Name.png > > > The cluster name can be changed by interacting with the cluster name field. > Color for the text box is: #fdfbdd. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Edit cluster name
[ https://issues.apache.org/jira/browse/AMBARI-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22478: -- Attachment: AMBARI-22478.patch > Ambari 3.0: Implement new design for Admin View: Edit cluster name > -- > > Key: AMBARI-22478 > URL: https://issues.apache.org/jira/browse/AMBARI-22478 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22478.patch, Save Cluster Name.png > > > The cluster name can be changed by interacting with the cluster name field. > Color for the text box is: #fdfbdd. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Update cluster rename
Andrii Tkach created AMBARI-22478: - Summary: Ambari 3.0: Implement new design for Admin View: Update cluster rename Key: AMBARI-22478 URL: https://issues.apache.org/jira/browse/AMBARI-22478 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 3.0.0 The cluster name can be changed by interacting with the cluster name field. Color for the text box is: #fdfbdd. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Edit cluster name
[ https://issues.apache.org/jira/browse/AMBARI-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22478: -- Attachment: Save Cluster Name.png > Ambari 3.0: Implement new design for Admin View: Edit cluster name > -- > > Key: AMBARI-22478 > URL: https://issues.apache.org/jira/browse/AMBARI-22478 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: Save Cluster Name.png > > > The cluster name can be changed by interacting with the cluster name field. > Color for the text box is: #fdfbdd. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Edit cluster name
[ https://issues.apache.org/jira/browse/AMBARI-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22478: -- Summary: Ambari 3.0: Implement new design for Admin View: Edit cluster name (was: Ambari 3.0: Implement new design for Admin View: Update cluster rename) > Ambari 3.0: Implement new design for Admin View: Edit cluster name > -- > > Key: AMBARI-22478 > URL: https://issues.apache.org/jira/browse/AMBARI-22478 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: Save Cluster Name.png > > > The cluster name can be changed by interacting with the cluster name field. > Color for the text box is: #fdfbdd. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22477) Log Search UI: implement access logs table
[ https://issues.apache.org/jira/browse/AMBARI-22477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259201#comment-16259201 ] Hudson commented on AMBARI-22477: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8414 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8414/]) AMBARI-22477 Log Search UI: implement access logs table. (ababiichuk) (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cc535c841f28ea50cf659ada8e573e84141146ac]) * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/audit-logs-table/audit-logs-table.component.less * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/audit-logs-table/audit-logs-table.component.spec.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/classes/components/logs-table-component.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/service-logs-table/service-logs-table.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/mock-data.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/classes/components/logs-table-component.spec.ts * (delete) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-list/logs-list.component.html * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/service-logs-table/service-logs-table.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.ts * (delete) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-list/logs-list.component.ts * (delete) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-list/logs-list.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/auth.service.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/mock-api-data.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-container.service.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/service-logs-table/service-logs-table.component.less * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/audit-logs-table/audit-logs-table.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.html * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/audit-logs-table/audit-logs-table.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/audit-log.ts * (delete) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-list/logs-list.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/app.module.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/service-logs-table/service-logs-table.component.html > Log Search UI: implement access logs table > -- > > Key: AMBARI-22477 > URL: https://issues.apache.org/jira/browse/AMBARI-22477 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-22477.patch > > > Add layout for audit logs table -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22393) UI changes for prompting user during registration failure for new OS family
[
https://issues.apache.org/jira/browse/AMBARI-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259199#comment-16259199
]
Hadoop QA commented on AMBARI-22393:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898444/AMBARI-22393.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12692//artifact/patch-work/testrun_ambari-web.txt]
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12692//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12692//console
This message is automatically generated.
> UI changes for prompting user during registration failure for new OS family
> ---
>
> Key: AMBARI-22393
> URL: https://issues.apache.org/jira/browse/AMBARI-22393
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-server, ambari-web
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22393.patch
>
>
> This task will include UI related template changes for the Ambari repository
> url prompt.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22477) Log Search UI: implement access logs table
[ https://issues.apache.org/jira/browse/AMBARI-22477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22477: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Log Search UI: implement access logs table > -- > > Key: AMBARI-22477 > URL: https://issues.apache.org/jira/browse/AMBARI-22477 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-22477.patch > > > Add layout for audit logs table -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22477) Log Search UI: implement access logs table
[
https://issues.apache.org/jira/browse/AMBARI-22477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259163#comment-16259163
]
Hadoop QA commented on AMBARI-22477:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898467/AMBARI-22477.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12690//console
This message is automatically generated.
> Log Search UI: implement access logs table
> --
>
> Key: AMBARI-22477
> URL: https://issues.apache.org/jira/browse/AMBARI-22477
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22477.patch
>
>
> Add layout for audit logs table
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22253) Cluster creation using v2 blueprints
[ https://issues.apache.org/jira/browse/AMBARI-22253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-22253: --- Summary: Cluster creation using v2 blueprints (was: Modify TopologyManager to create service groups) > Cluster creation using v2 blueprints > > > Key: AMBARI-22253 > URL: https://issues.apache.org/jira/browse/AMBARI-22253 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22477) Log Search UI: implement access logs table
[ https://issues.apache.org/jira/browse/AMBARI-22477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22477: -- Attachment: AMBARI-22477.patch > Log Search UI: implement access logs table > -- > > Key: AMBARI-22477 > URL: https://issues.apache.org/jira/browse/AMBARI-22477 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-22477.patch > > > Add layout for audit logs table -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22477) Log Search UI: implement access logs table
[ https://issues.apache.org/jira/browse/AMBARI-22477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22477: -- Status: Patch Available (was: Open) > Log Search UI: implement access logs table > -- > > Key: AMBARI-22477 > URL: https://issues.apache.org/jira/browse/AMBARI-22477 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-22477.patch > > > Add layout for audit logs table -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22477) Log Search UI: implement access logs table
Andrii Babiichuk created AMBARI-22477: - Summary: Log Search UI: implement access logs table Key: AMBARI-22477 URL: https://issues.apache.org/jira/browse/AMBARI-22477 Project: Ambari Issue Type: Task Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 3.0.0 Add layout for audit logs table -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22426) Push down Logger instances
[
https://issues.apache.org/jira/browse/AMBARI-22426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22426:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Push down Logger instances
> --
>
> Key: AMBARI-22426
> URL: https://issues.apache.org/jira/browse/AMBARI-22426
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-22426.patch
>
>
> {{Logger}} prepends classname and line number to log messages. Reusing
> {{Logger}} from other classes makes it more difficult to understand where the
> log message is coming from. This includes {{Logger}} instances inherited
> from parent classes.
> {noformat:title=example}
> 13 Nov 2017 11:55:13,571 INFO [ambari-client-thread-36]
> AbstractResourceProvider:525 - Creating Cluster 'TEST' based on blueprint
> 'blue'.
> 13 Nov 2017 11:55:13,623 ERROR [ambari-client-thread-36]
> BaseManagementHandler:79 - Caught a runtime exception while attempting to
> create a resource: null
> {noformat}
> In the above example, log is written from {{ClusterResourceProvider}} and
> {{CreateHandler}}, respectively, but one needs to search the source code for
> the messages to find this out.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22467) YARN, MapReduce2, Hive, and Oozie Should Conditionally Install LZO
[
https://issues.apache.org/jira/browse/AMBARI-22467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-22467:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-feature-AMBARI-22457
> YARN, MapReduce2, Hive, and Oozie Should Conditionally Install LZO
> --
>
> Key: AMBARI-22467
> URL: https://issues.apache.org/jira/browse/AMBARI-22467
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.6.1
>
> Attachments: AMBARI-22467.patch
>
>
> Changes Summary:
> - Do not install lzo if GPL license if not accepted, instead give out
> logger.warning and skip
> - Remove installation of lzo from metainfo.xml. Since we need to install lzo
> on restart if lzo is enabled/license accepted, we still need to do this in
> Python code. No need to duplicate.
> Clients will also use that code during install.
> - Move function get_lzo_packages to lzo_utils.py
> - Add code for Yarn, MR2, Hive to install lzo, edit existing code to install
> lzo for HDFS,Oozie to use lzo_utils.py
> Notes:
> - Impl is Patch Upgrade friendly as uses the same code to detect
> {stack_version} as all the other packages. That code (not implemented here)
> gets version depending component specific repo info not stack specific.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22393) UI changes for prompting user during registration failure for new OS family
[ https://issues.apache.org/jira/browse/AMBARI-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259022#comment-16259022 ] Yussuf Shaikh commented on AMBARI-22393: Uploaded patch file on behalf of [~Sonia] > UI changes for prompting user during registration failure for new OS family > --- > > Key: AMBARI-22393 > URL: https://issues.apache.org/jira/browse/AMBARI-22393 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server, ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22393.patch > > > This task will include UI related template changes for the Ambari repository > url prompt. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22393) UI changes for prompting user during registration failure for new OS family
[ https://issues.apache.org/jira/browse/AMBARI-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22393: --- Attachment: AMBARI-22393.patch > UI changes for prompting user during registration failure for new OS family > --- > > Key: AMBARI-22393 > URL: https://issues.apache.org/jira/browse/AMBARI-22393 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server, ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22393.patch > > > This task will include UI related template changes for the Ambari repository > url prompt. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22393) UI changes for prompting user during registration failure for new OS family
[ https://issues.apache.org/jira/browse/AMBARI-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22393: --- Status: Patch Available (was: In Progress) > UI changes for prompting user during registration failure for new OS family > --- > > Key: AMBARI-22393 > URL: https://issues.apache.org/jira/browse/AMBARI-22393 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server, ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22393.patch > > > This task will include UI related template changes for the Ambari repository > url prompt. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22473) shell.process_executor races process exit
[ https://issues.apache.org/jira/browse/AMBARI-22473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258924#comment-16258924 ] Jonathan Matthew commented on AMBARI-22473: --- Where are the tests for the ambari-commons shell module? It'd be fairly easy to write a test for this - just use process_executor to run something like python -c 'import os; import time; os.close(1); time.sleep(1)' expecting the return code to be 0. I ran into this trying to install an ambari cluster on an Ubuntu image running on Joyent Triton (see https://docs.joyent.com/public-cloud/instances/infrastructure/images). This bug causes the watchdog thread to try to kill the process, and that was hanging forever, likely due to bad interactions between fork/exec and threads. Fixing process_executor to wait for the process to exit allowed the install to complete successfully. > shell.process_executor races process exit > - > > Key: AMBARI-22473 > URL: https://issues.apache.org/jira/browse/AMBARI-22473 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.6.0 >Reporter: Jonathan Matthew > Attachments: > 0001-AMBARI-22473-shell.process_executor-races-process-ex.patch > > > By calling cmd.poll(), shell.process_executor assumes that the subcommand > will have exited once it has finished reading from its stdout pipe. This > isn't necessarily the case, so it should call cmd.wait() instead. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
