[jira] [Updated] (AMBARI-17032) Fix files mentioned by ServicePropertiesTest on latest commits

[ https://issues.apache.org/jira/browse/AMBARI-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17032: Component/s: ambari-server > Fix files mentioned by ServicePropertiesTest on

[jira] [Updated] (AMBARI-17032) Fix files mentioned by ServicePropertiesTest on latest commits

[ https://issues.apache.org/jira/browse/AMBARI-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17032: Attachment: AMBARI-17032.patch > Fix files mentioned by ServicePropertiesTest on

[jira] [Created] (AMBARI-17032) Fix files mentioned by ServicePropertiesTest on latest commits

Dmitry Lysnichenko created AMBARI-17032: --- Summary: Fix files mentioned by ServicePropertiesTest on latest commits Key: AMBARI-17032 URL: https://issues.apache.org/jira/browse/AMBARI-17032

[jira] [Updated] (AMBARI-17032) Fix files mentioned by ServicePropertiesTest on latest commits

[ https://issues.apache.org/jira/browse/AMBARI-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17032: Status: Patch Available (was: Open) > Fix files mentioned by

[jira] [Updated] (AMBARI-17068) RU failed because of old service was not stopped

[ https://issues.apache.org/jira/browse/AMBARI-17068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17068: Resolution: Fixed Status: Resolved (was: Patch Available) Committed To

[jira] [Resolved] (AMBARI-16272) Ambari Upgrade shouldn't automatically add stack configs

[ https://issues.apache.org/jira/browse/AMBARI-16272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko resolved AMBARI-16272. - Resolution: Fixed > Ambari Upgrade shouldn't automatically add stack configs >

[jira] [Created] (AMBARI-17114) DevDeploy: Ambari server is not started because of invalid config

Dmitry Lysnichenko created AMBARI-17114: --- Summary: DevDeploy: Ambari server is not started because of invalid config Key: AMBARI-17114 URL: https://issues.apache.org/jira/browse/AMBARI-17114

[jira] [Updated] (AMBARI-17114) DevDeploy: Ambari server is not started because of invalid config

[ https://issues.apache.org/jira/browse/AMBARI-17114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17114: Component/s: ambari-server > DevDeploy: Ambari server is not started because of

[jira] [Updated] (AMBARI-17114) DevDeploy: Ambari server is not started because of invalid config

[ https://issues.apache.org/jira/browse/AMBARI-17114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17114: Fix Version/s: 2.4.0 > DevDeploy: Ambari server is not started because of invalid

[jira] [Updated] (AMBARI-17112) Fixed implementation of on-ambari-upgrade support

[ https://issues.apache.org/jira/browse/AMBARI-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17112: Component/s: ambari-server > Fixed implementation of on-ambari-upgrade support >

[jira] [Updated] (AMBARI-17112) Fixed implementation of on-ambari-upgrade support

[ https://issues.apache.org/jira/browse/AMBARI-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17112: Status: Patch Available (was: Open) > Fixed implementation of on-ambari-upgrade

[jira] [Updated] (AMBARI-17114) DevDeploy: Ambari server is not started because of invalid config

[ https://issues.apache.org/jira/browse/AMBARI-17114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17114: Affects Version/s: 2.4.0 > DevDeploy: Ambari server is not started because of

[jira] [Updated] (AMBARI-17114) DevDeploy: Ambari server is not started because of invalid config

[ https://issues.apache.org/jira/browse/AMBARI-17114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17114: Status: Patch Available (was: Open) > DevDeploy: Ambari server is not started

[jira] [Updated] (AMBARI-17114) DevDeploy: Ambari server is not started because of invalid config

[ https://issues.apache.org/jira/browse/AMBARI-17114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17114: Attachment: AMBARI-17114.patch > DevDeploy: Ambari server is not started because

[jira] [Updated] (AMBARI-17112) Fixed implementation of on-ambari-upgrade support

[ https://issues.apache.org/jira/browse/AMBARI-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17112: Affects Version/s: 2.4.0 > Fixed implementation of on-ambari-upgrade support >

[jira] [Updated] (AMBARI-17112) Fixed implementation of on-ambari-upgrade support

[ https://issues.apache.org/jira/browse/AMBARI-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17112: Fix Version/s: 2.4.0 > Fixed implementation of on-ambari-upgrade support >

[jira] [Updated] (AMBARI-17114) DevDeploy: Ambari server is not started because of invalid config

[ https://issues.apache.org/jira/browse/AMBARI-17114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17114: Resolution: Fixed Status: Resolved (was: Patch Available) Committed To

[jira] [Updated] (AMBARI-17032) Fix files mentioned by ServicePropertiesTest on latest commits

[ https://issues.apache.org/jira/browse/AMBARI-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17032: Resolution: Fixed Status: Resolved (was: Patch Available) Committed To

[jira] [Updated] (AMBARI-17068) RU failed because of old service was not stopped

[ https://issues.apache.org/jira/browse/AMBARI-17068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17068: Component/s: ambari-server > RU failed because of old service was not stopped >

[jira] [Updated] (AMBARI-17068) RU failed because of old service was not stopped

[ https://issues.apache.org/jira/browse/AMBARI-17068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17068: Attachment: AMBARI-17068.patch > RU failed because of old service was not stopped

[jira] [Updated] (AMBARI-17068) RU failed because of old service was not stopped

[ https://issues.apache.org/jira/browse/AMBARI-17068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17068: Affects Version/s: 2.4.0 > RU failed because of old service was not stopped >

[jira] [Created] (AMBARI-17068) RU failed because of old service was not stopped

Dmitry Lysnichenko created AMBARI-17068: --- Summary: RU failed because of old service was not stopped Key: AMBARI-17068 URL: https://issues.apache.org/jira/browse/AMBARI-17068 Project: Ambari

[jira] [Updated] (AMBARI-17068) RU failed because of old service was not stopped

[ https://issues.apache.org/jira/browse/AMBARI-17068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17068: Fix Version/s: 2.4.0 > RU failed because of old service was not stopped >

[jira] [Updated] (AMBARI-17068) RU failed because of old service was not stopped

[ https://issues.apache.org/jira/browse/AMBARI-17068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17068: Status: Patch Available (was: Open) > RU failed because of old service was not

[jira] [Commented] (AMBARI-17112) Fixed implementation of on-ambari-upgrade support

[ https://issues.apache.org/jira/browse/AMBARI-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322602#comment-15322602 ] Dmitry Lysnichenko commented on AMBARI-17112: - Committed patc: Fixed implementation of

[jira] [Updated] (AMBARI-17026) NPE during EU at Update Target Stack step

[ https://issues.apache.org/jira/browse/AMBARI-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17026: Component/s: ambari-server > NPE during EU at Update Target Stack step >

[jira] [Updated] (AMBARI-17026) NPE during EU at Update Target Stack step

[ https://issues.apache.org/jira/browse/AMBARI-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17026: Attachment: AMBARI-17026.patch > NPE during EU at Update Target Stack step >

[jira] [Created] (AMBARI-17026) NPE during EU at Update Target Stack step

Dmitry Lysnichenko created AMBARI-17026: --- Summary: NPE during EU at Update Target Stack step Key: AMBARI-17026 URL: https://issues.apache.org/jira/browse/AMBARI-17026 Project: Ambari

[jira] [Updated] (AMBARI-17026) NPE during EU at Update Target Stack step

[ https://issues.apache.org/jira/browse/AMBARI-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17026: Status: Patch Available (was: Open) > NPE during EU at Update Target Stack step

[jira] [Updated] (AMBARI-17026) NPE during EU at Update Target Stack step

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

[jira] [Commented] (AMBARI-16272) Ambari Upgrade shouldn't automatically add stack configs

[ https://issues.apache.org/jira/browse/AMBARI-16272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314164#comment-15314164 ] Dmitry Lysnichenko commented on AMBARI-16272: - [~masatana], regarding the last failure:

[jira] [Commented] (AMBARI-15612) Add Livy to HDP 2.5 as slave component of Spark

[ https://issues.apache.org/jira/browse/AMBARI-15612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314169#comment-15314169 ] Dmitry Lysnichenko commented on AMBARI-15612: - [~jluniya], this commit breaks unit test

[jira] [Updated] (AMBARI-17187) Fix configuration xml files that don't pass validation

[ https://issues.apache.org/jira/browse/AMBARI-17187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17187: Resolution: Fixed Status: Resolved (was: Patch Available) Committed To

[jira] [Updated] (AMBARI-17187) Fix configuration xml files that don't pass validation

[ https://issues.apache.org/jira/browse/AMBARI-17187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17187: Component/s: ambari-server > Fix configuration xml files that don't pass

[jira] [Updated] (AMBARI-17187) Fix configuration xml files that don't pass validation

[ https://issues.apache.org/jira/browse/AMBARI-17187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17187: Fix Version/s: 2.4.0 > Fix configuration xml files that don't pass validation >

[jira] [Updated] (AMBARI-17187) Fix configuration xml files that don't pass validation

[ https://issues.apache.org/jira/browse/AMBARI-17187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17187: Affects Version/s: 2.4.0 > Fix configuration xml files that don't pass validation

[jira] [Updated] (AMBARI-17187) Fix configuration xml files that don't pass validation

[ https://issues.apache.org/jira/browse/AMBARI-17187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17187: Attachment: AMBARI-17187.patch > Fix configuration xml files that don't pass

[jira] [Updated] (AMBARI-17187) Fix configuration xml files that don't pass validation

[ https://issues.apache.org/jira/browse/AMBARI-17187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17187: Status: Patch Available (was: Open) > Fix configuration xml files that don't

[jira] [Created] (AMBARI-17187) Fix configuration xml files that don't pass validation

Dmitry Lysnichenko created AMBARI-17187: --- Summary: Fix configuration xml files that don't pass validation Key: AMBARI-17187 URL: https://issues.apache.org/jira/browse/AMBARI-17187 Project:

[jira] [Commented] (AMBARI-17179) Allow 'LLAP related calculations' to be done for any selected queue instead of existing for only 'llap' named queue.

[ https://issues.apache.org/jira/browse/AMBARI-17179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329220#comment-15329220 ] Dmitry Lysnichenko commented on AMBARI-17179: - [~swapanshridhar], fyi, this patch broke unit

[jira] [Updated] (AMBARI-17112) Fixed implementation of on-ambari-upgrade support

[ https://issues.apache.org/jira/browse/AMBARI-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17112: Resolution: Fixed Status: Resolved (was: Patch Available) Committed 2nd

[jira] [Assigned] (AMBARI-17198) Failure in mahout package installation upon retry is not correctly reported causing EU to fail

[ https://issues.apache.org/jira/browse/AMBARI-17198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko reassigned AMBARI-17198: --- Assignee: Dmitry Lysnichenko > Failure in mahout package installation upon

[jira] [Updated] (AMBARI-17198) Failure in mahout package installation upon retry is not correctly reported causing EU to fail

[ https://issues.apache.org/jira/browse/AMBARI-17198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17198: Resolution: Fixed Status: Resolved (was: Patch Available) Committed To

[jira] [Updated] (AMBARI-17258) Storm service check failed after Ambari upgrade

[ https://issues.apache.org/jira/browse/AMBARI-17258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17258: Status: Patch Available (was: Open) > Storm service check failed after Ambari

[jira] [Updated] (AMBARI-17258) Storm service check failed after Ambari upgrade

[ https://issues.apache.org/jira/browse/AMBARI-17258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17258: Attachment: AMBARI-17258.patch > Storm service check failed after Ambari upgrade

[jira] [Created] (AMBARI-17258) Storm service check failed after Ambari upgrade

Dmitry Lysnichenko created AMBARI-17258: --- Summary: Storm service check failed after Ambari upgrade Key: AMBARI-17258 URL: https://issues.apache.org/jira/browse/AMBARI-17258 Project: Ambari

[jira] [Updated] (AMBARI-17258) Storm service check failed after Ambari upgrade

[ https://issues.apache.org/jira/browse/AMBARI-17258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17258: Component/s: ambari-server > Storm service check failed after Ambari upgrade >

[jira] [Commented] (AMBARI-16272) Ambari Upgrade shouldn't automatically add stack configs

[ https://issues.apache.org/jira/browse/AMBARI-16272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314142#comment-15314142 ] Dmitry Lysnichenko commented on AMBARI-16272: - [~masatana], what is the branch and mvn/JDK

[jira] [Updated] (AMBARI-16955) Allow setting log level, and java opts for hive interactive/llap

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

[jira] [Updated] (AMBARI-16953) Service name shown instead of Host name on popup

[ https://issues.apache.org/jira/browse/AMBARI-16953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16953: Status: Patch Available (was: Open) > Service name shown instead of Host name on

[jira] [Updated] (AMBARI-16953) Service name shown instead of Host name on popup

[ https://issues.apache.org/jira/browse/AMBARI-16953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16953: Component/s: ambari-server > Service name shown instead of Host name on popup >

[jira] [Created] (AMBARI-16953) Service name shown instead of Host name on popup

Dmitry Lysnichenko created AMBARI-16953: --- Summary: Service name shown instead of Host name on popup Key: AMBARI-16953 URL: https://issues.apache.org/jira/browse/AMBARI-16953 Project: Ambari

[jira] [Updated] (AMBARI-16953) Service name shown instead of Host name on popup

[ https://issues.apache.org/jira/browse/AMBARI-16953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16953: Attachment: AMBARI-16953.patch > Service name shown instead of Host name on popup

[jira] [Updated] (AMBARI-16953) Service name shown instead of Host name on popup

[ https://issues.apache.org/jira/browse/AMBARI-16953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16953: Affects Version/s: 2.4.0 > Service name shown instead of Host name on popup >

[jira] [Updated] (AMBARI-16954) SERVICE_CHECK Upgrade pre-check does not throw error when its expected to

[ https://issues.apache.org/jira/browse/AMBARI-16954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16954: Status: Patch Available (was: Open) > SERVICE_CHECK Upgrade pre-check does not

[jira] [Updated] (AMBARI-16954) SERVICE_CHECK Upgrade pre-check does not throw error when its expected to

[ https://issues.apache.org/jira/browse/AMBARI-16954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16954: Attachment: AMBARI-16954.patch > SERVICE_CHECK Upgrade pre-check does not throw

[jira] [Created] (AMBARI-16954) SERVICE_CHECK Upgrade pre-check does not throw error when its expected to

Dmitry Lysnichenko created AMBARI-16954: --- Summary: SERVICE_CHECK Upgrade pre-check does not throw error when its expected to Key: AMBARI-16954 URL: https://issues.apache.org/jira/browse/AMBARI-16954

[jira] [Updated] (AMBARI-16955) Allow setting log level, and java opts for hive interactive/llap

[ https://issues.apache.org/jira/browse/AMBARI-16955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16955: Affects Version/s: 2.4.0 > Allow setting log level, and java opts for hive

[jira] [Updated] (AMBARI-16955) Allow setting log level, and java opts for hive interactive/llap

[ https://issues.apache.org/jira/browse/AMBARI-16955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16955: Fix Version/s: 2.4.0 > Allow setting log level, and java opts for hive

[jira] [Updated] (AMBARI-16955) Allow setting log level, and java opts for hive interactive/llap

[ https://issues.apache.org/jira/browse/AMBARI-16955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16955: Component/s: ambari-server > Allow setting log level, and java opts for hive

[jira] [Updated] (AMBARI-16955) Allow setting log level, and java opts for hive interactive/llap

[ https://issues.apache.org/jira/browse/AMBARI-16955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16955: Status: Patch Available (was: Open) > Allow setting log level, and java opts for

[jira] [Created] (AMBARI-16955) Allow setting log level, and java opts for hive interactive/llap

Dmitry Lysnichenko created AMBARI-16955: --- Summary: Allow setting log level, and java opts for hive interactive/llap Key: AMBARI-16955 URL: https://issues.apache.org/jira/browse/AMBARI-16955

[jira] [Updated] (AMBARI-16955) Allow setting log level, and java opts for hive interactive/llap

[ https://issues.apache.org/jira/browse/AMBARI-16955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16955: Attachment: AMBARI-16955.patch > Allow setting log level, and java opts for hive

[jira] [Updated] (AMBARI-16954) SERVICE_CHECK Upgrade pre-check does not throw error when its expected to

[ https://issues.apache.org/jira/browse/AMBARI-16954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16954: Affects Version/s: 2.4.0 > SERVICE_CHECK Upgrade pre-check does not throw error

[jira] [Updated] (AMBARI-16954) SERVICE_CHECK Upgrade pre-check does not throw error when its expected to

[ https://issues.apache.org/jira/browse/AMBARI-16954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16954: Fix Version/s: 2.4.0 > SERVICE_CHECK Upgrade pre-check does not throw error when

[jira] [Updated] (AMBARI-16953) Service name shown instead of Host name on popup

[ https://issues.apache.org/jira/browse/AMBARI-16953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16953: Resolution: Fixed Status: Resolved (was: Patch Available) Committed To

[jira] [Updated] (AMBARI-16272) Ambari Upgrade shouldn't automatically add stack configs

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

[jira] [Updated] (AMBARI-17334) Registering 2.5 HDP repo URLs throwing 500 error in the backend

[ https://issues.apache.org/jira/browse/AMBARI-17334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17334: Resolution: Fixed Status: Resolved (was: Patch Available) Committed To

[jira] [Updated] (AMBARI-17334) Registering 2.5 HDP repo URLs throwing 500 error in the backend

[ https://issues.apache.org/jira/browse/AMBARI-17334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17334: Status: Patch Available (was: Open) > Registering 2.5 HDP repo URLs throwing 500

[jira] [Updated] (AMBARI-17334) Registering 2.5 HDP repo URLs throwing 500 error in the backend

[ https://issues.apache.org/jira/browse/AMBARI-17334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17334: Component/s: ambari-server > Registering 2.5 HDP repo URLs throwing 500 error in

[jira] [Updated] (AMBARI-17370) After registering 2.5 HDP repo, it is hidden on UI

[ https://issues.apache.org/jira/browse/AMBARI-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17370: Affects Version/s: 2.4.0 > After registering 2.5 HDP repo, it is hidden on UI >

[jira] [Updated] (AMBARI-17370) After registering 2.5 HDP repo, it is hidden on UI

[ https://issues.apache.org/jira/browse/AMBARI-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17370: Fix Version/s: 2.4.0 > After registering 2.5 HDP repo, it is hidden on UI >

[jira] [Updated] (AMBARI-17370) After registering 2.5 HDP repo, it is hidden on UI

[ https://issues.apache.org/jira/browse/AMBARI-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17370: Attachment: AMBARI-17370.patch > After registering 2.5 HDP repo, it is hidden on

[jira] [Updated] (AMBARI-17370) After registering 2.5 HDP repo, it is hidden on UI

[ https://issues.apache.org/jira/browse/AMBARI-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17370: Component/s: ambari-server > After registering 2.5 HDP repo, it is hidden on UI >

[jira] [Updated] (AMBARI-17370) After registering 2.5 HDP repo, it is hidden on UI

[ https://issues.apache.org/jira/browse/AMBARI-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17370: Status: Patch Available (was: Open) > After registering 2.5 HDP repo, it is

[jira] [Created] (AMBARI-17370) After registering 2.5 HDP repo, it is hidden on UI

Dmitry Lysnichenko created AMBARI-17370: --- Summary: After registering 2.5 HDP repo, it is hidden on UI Key: AMBARI-17370 URL: https://issues.apache.org/jira/browse/AMBARI-17370 Project: Ambari

[jira] [Updated] (AMBARI-17370) After registering 2.5 HDP repo, it is hidden on UI

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

[jira] [Updated] (AMBARI-17258) Storm service check failed after Ambari upgrade

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

[jira] [Updated] (AMBARI-16954) SERVICE_CHECK Upgrade pre-check does not throw error when its expected to

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

[jira] [Assigned] (AMBARI-17200) Tez, Pig, Hive, MapReduce service checks will fail on non standard queue names

[ https://issues.apache.org/jira/browse/AMBARI-17200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko reassigned AMBARI-17200: --- Assignee: Dmitry Lysnichenko > Tez, Pig, Hive, MapReduce service checks

[jira] [Updated] (AMBARI-17200) Tez, Pig, Hive, MapReduce service checks will fail on non standard queue names

[ https://issues.apache.org/jira/browse/AMBARI-17200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17200: Resolution: Fixed Status: Resolved (was: Patch Available) Committed To

[jira] [Updated] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser

[ https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17427: Resolution: Fixed Status: Resolved (was: Patch Available) committed To

[jira] [Updated] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser

[ https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17427: Affects Version/s: 2.4.0 > Support Atlas in kerberized environment, submit

[jira] [Updated] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser

[ https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17427: Fix Version/s: 2.4.0 > Support Atlas in kerberized environment, submit Service

[jira] [Created] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser

Dmitry Lysnichenko created AMBARI-17427: --- Summary: Support Atlas in kerberized environment, submit Service Check as smokeuser Key: AMBARI-17427 URL: https://issues.apache.org/jira/browse/AMBARI-17427

[jira] [Updated] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser

[ https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17427: Status: Patch Available (was: Open) > Support Atlas in kerberized environment,

[jira] [Updated] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser

[ https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17427: Attachment: AMBARI-17427.patch > Support Atlas in kerberized environment, submit

[jira] [Updated] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser

[ https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17427: Component/s: ambari-server > Support Atlas in kerberized environment, submit

[jira] [Updated] (AMBARI-17300) RU: YARN service check failed during RU

[ https://issues.apache.org/jira/browse/AMBARI-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17300: Component/s: ambari-server > RU: YARN service check failed during RU >

[jira] [Updated] (AMBARI-17300) RU: YARN service check failed during RU

[ https://issues.apache.org/jira/browse/AMBARI-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17300: Affects Version/s: 2.4.0 > RU: YARN service check failed during RU >

[jira] [Updated] (AMBARI-17300) RU: YARN service check failed during RU

[ https://issues.apache.org/jira/browse/AMBARI-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17300: Fix Version/s: 2.4.0 > RU: YARN service check failed during RU >

[jira] [Created] (AMBARI-17300) RU: YARN service check failed during RU

Dmitry Lysnichenko created AMBARI-17300: --- Summary: RU: YARN service check failed during RU Key: AMBARI-17300 URL: https://issues.apache.org/jira/browse/AMBARI-17300 Project: Ambari

[jira] [Updated] (AMBARI-17300) RU: YARN service check failed during RU

[ https://issues.apache.org/jira/browse/AMBARI-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17300: Attachment: AMBARI-17300.patch > RU: YARN service check failed during RU >

[jira] [Updated] (AMBARI-17300) RU: YARN service check failed during RU

[ https://issues.apache.org/jira/browse/AMBARI-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17300: Status: Patch Available (was: Open) > RU: YARN service check failed during RU >

[jira] [Updated] (AMBARI-15355) After EU from 2.2 -> 2.3 HBase region server started failed with memory error

[ https://issues.apache.org/jira/browse/AMBARI-15355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-15355: Attachment: AMBARI-15355.patch > After EU from 2.2 -> 2.3 HBase region server

[jira] [Updated] (AMBARI-15355) After EU from 2.2 -> 2.3 HBase region server started failed with memory error

[ https://issues.apache.org/jira/browse/AMBARI-15355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-15355: Fix Version/s: 2.2.2 > After EU from 2.2 -> 2.3 HBase region server started

[jira] [Created] (AMBARI-15405) HDP 2.3.4 package install through Ambari on SLES11 hosts fails

Dmitry Lysnichenko created AMBARI-15405: --- Summary: HDP 2.3.4 package install through Ambari on SLES11 hosts fails Key: AMBARI-15405 URL: https://issues.apache.org/jira/browse/AMBARI-15405

[jira] [Updated] (AMBARI-15405) HDP 2.3.4 package install through Ambari on SLES11 hosts fails

[ https://issues.apache.org/jira/browse/AMBARI-15405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-15405: Component/s: ambari-server > HDP 2.3.4 package install through Ambari on SLES11

[jira] [Updated] (AMBARI-15355) After EU from 2.2 -> 2.3 HBase region server started failed with memory error

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

[jira] [Commented] (AMBARI-14751) Ambari not setting hdp.version in config files

[ https://issues.apache.org/jira/browse/AMBARI-14751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201260#comment-15201260 ] Dmitry Lysnichenko commented on AMBARI-14751: - [~ndimiduk], There should be something like

  1   2   3   4   5   6   7   8   9   10   >