[jira] [Updated] (AMBARI-18520) Ambari usernames should not be converted to lowercase before storing in the DB.

[ https://issues.apache.org/jira/browse/AMBARI-18520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18520: --- Summary: Ambari usernames should not be converted to lowercase before storin

[jira] [Created] (AMBARI-18520) Ambari usernames should not be stored in lowercase in the DB.

Nahappan Somasundaram created AMBARI-18520: -- Summary: Ambari usernames should not be stored in lowercase in the DB. Key: AMBARI-18520 URL: https://issues.apache.org/jira/browse/AMBARI-18520 P

[jira] [Updated] (AMBARI-18426) Active ambari server check required in ambari server JAR

[ https://issues.apache.org/jira/browse/AMBARI-18426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18426: --- Fix Version/s: 2.5.0 > Active ambari server check required in ambari server

[jira] [Updated] (AMBARI-18426) Active ambari server check required in ambari server JAR

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

[jira] [Updated] (AMBARI-18426) Active ambari server check required in ambari server JAR

[ https://issues.apache.org/jira/browse/AMBARI-18426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18426: --- Status: Patch Available (was: In Progress) > Active ambari server check req

[jira] [Updated] (AMBARI-18426) Active ambari server check required in ambari server JAR

[ https://issues.apache.org/jira/browse/AMBARI-18426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18426: --- Attachment: rb52128.patch > Active ambari server check required in ambari se

[jira] [Created] (AMBARI-18426) Active ambari server check required in ambari server JAR

Nahappan Somasundaram created AMBARI-18426: -- Summary: Active ambari server check required in ambari server JAR Key: AMBARI-18426 URL: https://issues.apache.org/jira/browse/AMBARI-18426 Project

[jira] [Updated] (AMBARI-18413) RecoveryManager may be logging too often

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

[jira] [Updated] (AMBARI-18413) RecoveryManager may be logging too often

[ https://issues.apache.org/jira/browse/AMBARI-18413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18413: --- Status: Patch Available (was: Open) > RecoveryManager may be logging too of

[jira] [Updated] (AMBARI-18413) RecoveryManager may be logging too often

[ https://issues.apache.org/jira/browse/AMBARI-18413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18413: --- Attachment: rb51969.patch > RecoveryManager may be logging too often > -

[jira] [Created] (AMBARI-18413) RecoveryManager may be logging too often

Nahappan Somasundaram created AMBARI-18413: -- Summary: RecoveryManager may be logging too often Key: AMBARI-18413 URL: https://issues.apache.org/jira/browse/AMBARI-18413 Project: Ambari

[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) > Bluepri

[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 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: --- Description: The following APIs do not retrieve *setting* section from the b

[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) > Bluepri

[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 Te

[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: test_update_open_files_u

[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: test_update_open_

[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: test_update_open_

[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: test_update_open_files_ulimi

[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: test_update_open_

[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 bluepri

[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 i

[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) > Support

[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 ambari-

[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 notificati

[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 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: --- Description: Create Atlas log4j in ambari-server/src/main/resources/common-

[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: Amb

[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) > '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: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari

[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&focusedCommentId=15422062#comment-15422062 ] Nahappan Somasundaram commented on AMBARI-17747: [~jluniya] [~afernandez

[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 befo

[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 Iss

[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 to

[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 > "ht

[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: https://issue

[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 t

[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 commons-h

[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 Projec

[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 s

[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 lo

[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 propert

[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: Amb

[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 Ser

[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 : Config

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

Nahappan Somasundaram created AMBARI-17714: -- Summary: Add Service Wizard/Security wizard : Configure Identities page does not fully load after upgrade from 2.1.1 to 2.4.0 Key: AMBARI-17714 URL: https://is

[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&focusedCommentId=15374339#comment-15374339 ] Nahappan Somasundaram commented on AMBARI-17681: +1 > Changing settings

[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 no

[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 s

[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 re

[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 "t

[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" fo

[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 "t

[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 "t

[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 "t

[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 Me

[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: https://issues.apache.org/jira/browse/AM

[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 na

[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 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: --- Status: Open (was: Patch Available) > 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: 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 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: --- Status: Patch Available (was: Open) > 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: rb49119.patch > User names should be case insensitive >

[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 crea

[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: https://issues.apache.org/jira/browse/AMBARI-17

[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 a

[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: --- Attachment: rb48526.patch > Ambari Agent: TestActionQueue and TestRecoveryMa

[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 Tes

[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: https://issues.apache.org/jira/browse/AMBARI-1

[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 inst

[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 failure

[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: Ambar

[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) > HostRes

[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) > Auto-st

[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) > Auto-st

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

[ https://issues.apache.org/jira/browse/AMBARI-16196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298728#comment-15298728 ] Nahappan Somasundaram commented on AMBARI-16196: The Wiki is available h

[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 > ---

<    1   2   3   4   5   >