[jira] [Updated] (AMBARI-18332) Blueprints: API should make available "setting" property from blueprint

[ https://issues.apache.org/jira/browse/AMBARI-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18332: --- Resolution: Fixed Status: Resolved (was: Patch Available) >

[jira] [Updated] (AMBARI-18332) Blueprints: API should make available "setting" property from blueprint

[ https://issues.apache.org/jira/browse/AMBARI-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18332: --- Attachment: rb51851.patch > Blueprints: API should make available "setting"

[jira] [Updated] (AMBARI-18332) Blueprints: API should make available "setting" property from blueprint

[ https://issues.apache.org/jira/browse/AMBARI-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18332: --- Status: Patch Available (was: Open) > Blueprints: API should make

[jira] [Updated] (AMBARI-18332) Blueprints: API should make available "setting" property from blueprint

[ https://issues.apache.org/jira/browse/AMBARI-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18332: --- Description: The following APIs do not retrieve *setting* section from the

[jira] [Updated] (AMBARI-18328) Blueprints: Log "setting" section of blueprint in ambari server log file

[ https://issues.apache.org/jira/browse/AMBARI-18328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18328: --- Resolution: Fixed Status: Resolved (was: Patch Available) >

[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)

[ https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18342: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Unit

[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)

[ https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18342: --- Attachment: rb51733 (2).patch > Unit Tests failure:

[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)

[ https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18342: --- Status: Open (was: Patch Available) > Unit Tests failure:

[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)

[ https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18342: --- Status: Patch Available (was: Open) > Unit Tests failure:

[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)

[ https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18342: --- Attachment: rb51733.patch > Unit Tests failure:

[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)

[ https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18342: --- Status: Patch Available (was: Open) > Unit Tests failure:

[jira] [Created] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)

Nahappan Somasundaram created AMBARI-18342: -- Summary: Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain) Key: AMBARI-18342 URL: https://issues.apache.org/jira/browse/AMBARI-18342

[jira] [Updated] (AMBARI-18328) Blueprints: Log "setting" section of blueprint in ambari server log file

[ https://issues.apache.org/jira/browse/AMBARI-18328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18328: --- Status: Patch Available (was: Open) > Blueprints: Log "setting" section of

[jira] [Updated] (AMBARI-18328) Blueprints: Log "setting" section of blueprint in ambari server log file

[ https://issues.apache.org/jira/browse/AMBARI-18328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18328: --- Attachment: rb51685 (1).patch > Blueprints: Log "setting" section of

[jira] [Updated] (AMBARI-18328) Blueprints: Log "setting" section of blueprint in ambari server log file

[ https://issues.apache.org/jira/browse/AMBARI-18328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18328: --- Status: Open (was: Patch Available) > Blueprints: Log "setting" section of

[jira] [Created] (AMBARI-18332) Blueprints: API should make available "setting" property from blueprint

Nahappan Somasundaram created AMBARI-18332: -- Summary: Blueprints: API should make available "setting" property from blueprint Key: AMBARI-18332 URL: https://issues.apache.org/jira/browse/AMBARI-18332

[jira] [Updated] (AMBARI-18328) Blueprints: Log "setting" section of blueprint in ambari server log file

[ https://issues.apache.org/jira/browse/AMBARI-18328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18328: --- Attachment: rb51685.patch > Blueprints: Log "setting" section of blueprint

[jira] [Updated] (AMBARI-18328) Blueprints: Log "setting" section of blueprint in ambari server log file

[ https://issues.apache.org/jira/browse/AMBARI-18328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18328: --- Status: Patch Available (was: Open) > Blueprints: Log "setting" section of

[jira] [Created] (AMBARI-18328) Blueprints: Log "setting" section of blueprint in ambari server log file

Nahappan Somasundaram created AMBARI-18328: -- Summary: Blueprints: Log "setting" section of blueprint in ambari server log file Key: AMBARI-18328 URL: https://issues.apache.org/jira/browse/AMBARI-18328

[jira] [Updated] (AMBARI-18299) Support open files ulimit for ambari-agent

[ https://issues.apache.org/jira/browse/AMBARI-18299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18299: --- Resolution: Fixed Status: Resolved (was: Patch Available) >

[jira] [Updated] (AMBARI-18299) Support open files ulimit for ambari-agent

[ https://issues.apache.org/jira/browse/AMBARI-18299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18299: --- Attachment: rb51588.patch > Support open files ulimit for ambari-agent >

[jira] [Updated] (AMBARI-18299) Support open files ulimit for ambari-agent

[ https://issues.apache.org/jira/browse/AMBARI-18299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18299: --- Status: Patch Available (was: Open) > Support open files ulimit for

[jira] [Created] (AMBARI-18299) Support open files ulimit for ambari-agent

Nahappan Somasundaram created AMBARI-18299: -- Summary: Support open files ulimit for ambari-agent Key: AMBARI-18299 URL: https://issues.apache.org/jira/browse/AMBARI-18299 Project: Ambari

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[ https://issues.apache.org/jira/browse/AMBARI-18168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18168: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Create

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[ https://issues.apache.org/jira/browse/AMBARI-18168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18168: --- Attachment: rb51144.patch > Create Atlas log4j changes for failed

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[ https://issues.apache.org/jira/browse/AMBARI-18168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18168: --- Status: Patch Available (was: Open) > Create Atlas log4j changes for

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[ https://issues.apache.org/jira/browse/AMBARI-18168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18168: --- Description: Create Atlas log4j in

[jira] [Created] (AMBARI-18168) Create Atlas log4j changes for failed notifications

Nahappan Somasundaram created AMBARI-18168: -- Summary: Create Atlas log4j changes for failed notifications Key: AMBARI-18168 URL: https://issues.apache.org/jira/browse/AMBARI-18168 Project:

[jira] [Updated] (AMBARI-18152) 'ambari-server --help' not working

[ https://issues.apache.org/jira/browse/AMBARI-18152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18152: --- Resolution: Fixed Status: Resolved (was: Patch Available) >

[jira] [Commented] (AMBARI-17747) EU/RU Kafka should come right after ZK instead of before Atlas, fix role command order

[ https://issues.apache.org/jira/browse/AMBARI-17747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15422062#comment-15422062 ] Nahappan Somasundaram commented on AMBARI-17747: [~jluniya] [~afernandez] It's been

[jira] [Resolved] (AMBARI-17747) EU/RU Kafka should come right after ZK instead of before Atlas, fix role command order

[ https://issues.apache.org/jira/browse/AMBARI-17747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram resolved AMBARI-17747. Resolution: Fixed > EU/RU Kafka should come right after ZK instead of

[jira] [Updated] (AMBARI-18152) 'ambari-server --help' not working

[ https://issues.apache.org/jira/browse/AMBARI-18152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18152: --- Attachment: rb51123.patch > 'ambari-server --help' not working >

[jira] [Updated] (AMBARI-18152) 'ambari-server --help' not working

[ https://issues.apache.org/jira/browse/AMBARI-18152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18152: --- Status: Patch Available (was: Open) > 'ambari-server --help' not working >

[jira] [Created] (AMBARI-18152) 'ambari-server --help' not working

Nahappan Somasundaram created AMBARI-18152: -- Summary: 'ambari-server --help' not working Key: AMBARI-18152 URL: https://issues.apache.org/jira/browse/AMBARI-18152 Project: Ambari

[jira] [Updated] (AMBARI-17992) Ambari should remove all references to commons-httpclient

[ https://issues.apache.org/jira/browse/AMBARI-17992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17992: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari

[jira] [Updated] (AMBARI-18030) Ambari quicklinks for Atlas points to url "http://:/#!/search?user.name=admin" by default, which seems incorrect

[ https://issues.apache.org/jira/browse/AMBARI-18030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18030: --- Status: Patch Available (was: Open) > Ambari quicklinks for Atlas points

[jira] [Updated] (AMBARI-18030) Ambari quicklinks for Atlas points to url "http://:/#!/search?user.name=admin" by default, which seems incorrect

[ https://issues.apache.org/jira/browse/AMBARI-18030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18030: --- Attachment: rb50817.patch > Ambari quicklinks for Atlas points to url >

[jira] [Created] (AMBARI-18030) Ambari quicklinks for Atlas points to url "http://:/#!/search?user.name=admin" by default, which seems incorrect

Nahappan Somasundaram created AMBARI-18030: -- Summary: Ambari quicklinks for Atlas points to url "http://:/#!/search?user.name=admin" by default, which seems incorrect Key: AMBARI-18030 URL:

[jira] [Updated] (AMBARI-17992) Ambari should remove all references to commons-httpclient

[ https://issues.apache.org/jira/browse/AMBARI-17992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17992: --- Status: Patch Available (was: Open) > Ambari should remove all references

[jira] [Updated] (AMBARI-17992) Ambari should remove all references to commons-httpclient

[ https://issues.apache.org/jira/browse/AMBARI-17992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17992: --- Attachment: rb50711.patch > Ambari should remove all references to

[jira] [Created] (AMBARI-17992) Ambari should remove all references to commons-httpclient

Nahappan Somasundaram created AMBARI-17992: -- Summary: Ambari should remove all references to commons-httpclient Key: AMBARI-17992 URL: https://issues.apache.org/jira/browse/AMBARI-17992

[jira] [Assigned] (AMBARI-17747) EU/RU Kafka should come right after ZK instead of before Atlas, fix role command order

[ https://issues.apache.org/jira/browse/AMBARI-17747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram reassigned AMBARI-17747: -- Assignee: Nahappan Somasundaram (was: Jayush Luniya) > EU/RU Kafka

[jira] [Updated] (AMBARI-17844) Update the content of various llap log4j properties

[ https://issues.apache.org/jira/browse/AMBARI-17844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17844: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Update

[jira] [Updated] (AMBARI-17844) Update the content of various llap log4j properties

[ https://issues.apache.org/jira/browse/AMBARI-17844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17844: --- Status: Patch Available (was: Open) > Update the content of various llap

[jira] [Updated] (AMBARI-17844) Update the content of various llap log4j properties

[ https://issues.apache.org/jira/browse/AMBARI-17844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17844: --- Attachment: rb50312.patch > Update the content of various llap log4j

[jira] [Created] (AMBARI-17844) Update the content of various llap log4j properties

Nahappan Somasundaram created AMBARI-17844: -- Summary: Update the content of various llap log4j properties Key: AMBARI-17844 URL: https://issues.apache.org/jira/browse/AMBARI-17844 Project:

[jira] [Updated] (AMBARI-17714) Add Service Wizard/Security wizard : Configure Identities page does not fully load after upgrade from 2.1.1 to 2.4.0

[ https://issues.apache.org/jira/browse/AMBARI-17714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17714: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Add

[jira] [Updated] (AMBARI-17714) Add Service Wizard/Security wizard : Configure Identities page does not fully load after upgrade from 2.1.1 to 2.4.0

[ https://issues.apache.org/jira/browse/AMBARI-17714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17714: --- Status: Patch Available (was: Open) > Add Service Wizard/Security wizard :

[jira] [Updated] (AMBARI-17714) Add Service Wizard/Security wizard : Configure Identities page does not fully load after upgrade from 2.1.1 to 2.4.0

[ https://issues.apache.org/jira/browse/AMBARI-17714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17714: --- Attachment: AMBARI-17714.patch > Add Service Wizard/Security wizard :

[jira] [Commented] (AMBARI-17681) Changing settings in advanced-tez-interactive-site did not ask for a HiveServerInteractive restart

[ https://issues.apache.org/jira/browse/AMBARI-17681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15374339#comment-15374339 ] Nahappan Somasundaram commented on AMBARI-17681: +1 > Changing settings in

[jira] [Resolved] (AMBARI-17350) If two users are created differing in case then no users are shown due to error

[ https://issues.apache.org/jira/browse/AMBARI-17350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram resolved AMBARI-17350. Resolution: Duplicate > If two users are created differing in case then

[jira] [Updated] (AMBARI-17593) Ambari server backup error - failure if backup size exceeds 4GB

[ https://issues.apache.org/jira/browse/AMBARI-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17593: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari

[jira] [Updated] (AMBARI-17593) Ambari server backup error - failure if backup size exceeds 4GB

[ https://issues.apache.org/jira/browse/AMBARI-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17593: --- Attachment: rb49711.patch > Ambari server backup error - failure if backup

[jira] [Updated] (AMBARI-17593) Ambari server backup error - failure if backup size exceeds 4GB

[ https://issues.apache.org/jira/browse/AMBARI-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17593: --- Status: Patch Available (was: Open) > Ambari server backup error - failure

[jira] [Created] (AMBARI-17593) Ambari server backup error - failure if backup size exceeds 4GB

Nahappan Somasundaram created AMBARI-17593: -- Summary: Ambari server backup error - failure if backup size exceeds 4GB Key: AMBARI-17593 URL: https://issues.apache.org/jira/browse/AMBARI-17593

[jira] [Updated] (AMBARI-17455) Auto restart flag should be set as "true" for Metrics Collector after upgrade to 2.4.0

[ https://issues.apache.org/jira/browse/AMBARI-17455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17455: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Auto

[jira] [Updated] (AMBARI-17455) Auto restart flag should be set as "true" for Metrics Collector after upgrade to 2.4.0

[ https://issues.apache.org/jira/browse/AMBARI-17455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17455: --- Status: Patch Available (was: Open) > Auto restart flag should be set as

[jira] [Updated] (AMBARI-17455) Auto restart flag should be set as "true" for Metrics Collector after upgrade to 2.4.0

[ https://issues.apache.org/jira/browse/AMBARI-17455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17455: --- Attachment: rb49291 (1).patch > Auto restart flag should be set as "true"

[jira] [Updated] (AMBARI-17455) Auto restart flag should be set as "true" for Metrics Collector after upgrade to 2.4.0

[ https://issues.apache.org/jira/browse/AMBARI-17455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17455: --- Attachment: (was: rb49291.patch) > Auto restart flag should be set as

[jira] [Updated] (AMBARI-17455) Auto restart flag should be set as "true" for Metrics Collector after upgrade to 2.4.0

[ https://issues.apache.org/jira/browse/AMBARI-17455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17455: --- Status: Open (was: Patch Available) > Auto restart flag should be set as

[jira] [Updated] (AMBARI-17455) Auto restart flag should be set as "true" for Metrics Collector after upgrade to 2.4.0

[ https://issues.apache.org/jira/browse/AMBARI-17455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17455: --- Status: Patch Available (was: Open) > Auto restart flag should be set as

[jira] [Updated] (AMBARI-17455) Auto restart flag should be set as "true" for Metrics Collector after upgrade to 2.4.0

[ https://issues.apache.org/jira/browse/AMBARI-17455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17455: --- Attachment: rb49291.patch > Auto restart flag should be set as "true" for

[jira] [Created] (AMBARI-17455) Auto restart flag should be set as "true" for Metrics Collector after upgrade to 2.4.0

Nahappan Somasundaram created AMBARI-17455: -- Summary: Auto restart flag should be set as "true" for Metrics Collector after upgrade to 2.4.0 Key: AMBARI-17455 URL:

[jira] [Updated] (AMBARI-17383) User names should be case insensitive

[ https://issues.apache.org/jira/browse/AMBARI-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17383: --- Resolution: Fixed Status: Resolved (was: Patch Available) > User

[jira] [Updated] (AMBARI-17383) User names should be case insensitive

[ https://issues.apache.org/jira/browse/AMBARI-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17383: --- Status: Patch Available (was: Open) > User names should be case

[jira] [Updated] (AMBARI-17383) User names should be case insensitive

[ https://issues.apache.org/jira/browse/AMBARI-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17383: --- Attachment: rb49119 (1).patch > User names should be case insensitive >

[jira] [Updated] (AMBARI-17383) User names should be case insensitive

[ https://issues.apache.org/jira/browse/AMBARI-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17383: --- Attachment: (was: rb49119.patch) > User names should be case

[jira] [Updated] (AMBARI-17383) User names should be case insensitive

[ https://issues.apache.org/jira/browse/AMBARI-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17383: --- Status: Patch Available (was: Open) > User names should be case

[jira] [Created] (AMBARI-17383) User names should be case insensitive

Nahappan Somasundaram created AMBARI-17383: -- Summary: User names should be case insensitive Key: AMBARI-17383 URL: https://issues.apache.org/jira/browse/AMBARI-17383 Project: Ambari

[jira] [Updated] (AMBARI-17350) If two users are created differing in case then no users are shown due to error

[ https://issues.apache.org/jira/browse/AMBARI-17350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17350: --- Attachment: Screen Shot 2016-06-11 at 9.17.12 PM.png > If two users are

[jira] [Created] (AMBARI-17350) If two users are created differing in case then no users are shown due to error

Nahappan Somasundaram created AMBARI-17350: -- Summary: If two users are created differing in case then no users are shown due to error Key: AMBARI-17350 URL:

[jira] [Updated] (AMBARI-17156) Ambari Agent: TestActionQueue and TestRecoveryManager python unit tests failures

[ https://issues.apache.org/jira/browse/AMBARI-17156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17156: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari

[jira] [Updated] (AMBARI-16935) Retry and recover from component install failures

[ https://issues.apache.org/jira/browse/AMBARI-16935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16935: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Retry

[jira] [Updated] (AMBARI-17156) Ambari Agent: TestActionQueue and TestRecoveryManager python unit tests failures

[ https://issues.apache.org/jira/browse/AMBARI-17156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17156: --- Status: Patch Available (was: Open) > Ambari Agent: TestActionQueue and

[jira] [Created] (AMBARI-17156) Ambari Agent: TestActionQueue and TestRecoveryManager python unit tests failures

Nahappan Somasundaram created AMBARI-17156: -- Summary: Ambari Agent: TestActionQueue and TestRecoveryManager python unit tests failures Key: AMBARI-17156 URL:

[jira] [Updated] (AMBARI-16935) Retry and recover from component install failures

[ https://issues.apache.org/jira/browse/AMBARI-16935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16935: --- Status: Patch Available (was: Open) > Retry and recover from component

[jira] [Updated] (AMBARI-16935) Retry and recover from component install failures

[ https://issues.apache.org/jira/browse/AMBARI-16935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16935: --- Attachment: rb48096.patch > Retry and recover from component install

[jira] [Created] (AMBARI-17069) Recovery Manager: Refactor desired state transitions into a state table

Nahappan Somasundaram created AMBARI-17069: -- Summary: Recovery Manager: Refactor desired state transitions into a state table Key: AMBARI-17069 URL: https://issues.apache.org/jira/browse/AMBARI-17069

[jira] [Created] (AMBARI-16935) Retry and recover from component install failures

Nahappan Somasundaram created AMBARI-16935: -- Summary: Retry and recover from component install failures Key: AMBARI-16935 URL: https://issues.apache.org/jira/browse/AMBARI-16935 Project:

[jira] [Updated] (AMBARI-15703) HostResourceProvider should include maintenance_state when a request is made directly with the host name

[ https://issues.apache.org/jira/browse/AMBARI-15703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15703: --- Resolution: Fixed Status: Resolved (was: Patch Available) >

[jira] [Updated] (AMBARI-15194) Auto-start services: Create default settings for auto start

[ https://issues.apache.org/jira/browse/AMBARI-15194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15194: --- Resolution: Fixed Status: Resolved (was: Patch Available) >

[jira] [Updated] (AMBARI-15230) Auto-start services: Move default values in ambari.properties to cluster-env.xml

[ https://issues.apache.org/jira/browse/AMBARI-15230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15230: --- Resolution: Fixed Status: Resolved (was: Patch Available) >

[jira] [Resolved] (AMBARI-16196) Add a wiki of auto-start feature

[ https://issues.apache.org/jira/browse/AMBARI-16196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram resolved AMBARI-16196. Resolution: Fixed > Add a wiki of auto-start feature >

[jira] [Updated] (AMBARI-16826) Unit Test failure: ComponentResourceProviderTest

[ https://issues.apache.org/jira/browse/AMBARI-16826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16826: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Unit

[jira] [Updated] (AMBARI-16826) Unit Test failure: ComponentResourceProviderTest

[ https://issues.apache.org/jira/browse/AMBARI-16826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16826: --- Status: Patch Available (was: Open) > Unit Test failure:

[jira] [Updated] (AMBARI-16826) Unit Test failure: ComponentResourceProviderTest

[ https://issues.apache.org/jira/browse/AMBARI-16826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16826: --- Attachment: rb47739.patch > Unit Test failure:

[jira] [Updated] (AMBARI-16751) Refresh stale host entity reference when deleting a service

[ https://issues.apache.org/jira/browse/AMBARI-16751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16751: --- Resolution: Fixed Status: Resolved (was: Patch Available) >

[jira] [Created] (AMBARI-16826) Unit Test failure: ComponentResourceProviderTest

Nahappan Somasundaram created AMBARI-16826: -- Summary: Unit Test failure: ComponentResourceProviderTest Key: AMBARI-16826 URL: https://issues.apache.org/jira/browse/AMBARI-16826 Project:

[jira] [Updated] (AMBARI-16806) AMS Collector is not automatically being configured for auto-start during blueprint deployment

[ https://issues.apache.org/jira/browse/AMBARI-16806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16806: --- Resolution: Fixed Status: Resolved (was: Patch Available) > AMS

[jira] [Updated] (AMBARI-16806) AMS Collector is not automatically being configured for auto-start during blueprint deployment

[ https://issues.apache.org/jira/browse/AMBARI-16806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16806: --- Status: Patch Available (was: In Progress) > AMS Collector is not

[jira] [Updated] (AMBARI-16806) AMS Collector is not automatically being configured for auto-start during blueprint deployment

[ https://issues.apache.org/jira/browse/AMBARI-16806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16806: --- Attachment: rb47688.patch > AMS Collector is not automatically being

[jira] [Updated] (AMBARI-16806) AMS Collector is not automatically being configured for auto-start during blueprint deployment

[ https://issues.apache.org/jira/browse/AMBARI-16806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16806: --- Description: When using blueprint to deploy a cluster, if settings section

[jira] [Updated] (AMBARI-16806) AMS Collector is not automatically being configured for auto-start during blueprint deployment

[ https://issues.apache.org/jira/browse/AMBARI-16806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16806: --- Attachment: hg2.json blueprints2.json > AMS Collector is

[jira] [Created] (AMBARI-16806) AMS Collector is not automatically being configured for auto-start during blueprint deployment

Nahappan Somasundaram created AMBARI-16806: -- Summary: AMS Collector is not automatically being configured for auto-start during blueprint deployment Key: AMBARI-16806 URL:

[jira] [Updated] (AMBARI-16806) AMS Collector is not automatically being configured for auto-start during blueprint deployment

[ https://issues.apache.org/jira/browse/AMBARI-16806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16806: --- Priority: Blocker (was: Major) > AMS Collector is not automatically being

[jira] [Updated] (AMBARI-16751) Refresh stale host entity reference when deleting a service

[ https://issues.apache.org/jira/browse/AMBARI-16751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16751: --- Status: Patch Available (was: Open) > Refresh stale host entity reference

[jira] [Updated] (AMBARI-16751) Refresh stale host entity reference when deleting a service

[ https://issues.apache.org/jira/browse/AMBARI-16751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16751: --- Status: Open (was: Patch Available) > Refresh stale host entity reference

[jira] [Updated] (AMBARI-16751) Refresh stale host entity reference when deleting a service

[ https://issues.apache.org/jira/browse/AMBARI-16751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16751: --- Attachment: (was: rb47565.patch) > Refresh stale host entity reference

[jira] [Updated] (AMBARI-16749) Auto-start services: Ambari agent should set auto_start_only to True when recovery_type is AUTO_START

[ https://issues.apache.org/jira/browse/AMBARI-16749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16749: --- Resolution: Fixed Status: Resolved (was: Patch Available) >

[jira] [Updated] (AMBARI-16751) Refresh stale host entity reference when deleting a service

[ https://issues.apache.org/jira/browse/AMBARI-16751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-16751: --- Status: Patch Available (was: In Progress) > Refresh stale host entity

<    1   2   3   4   >