[jira] [Updated] (AMBARI-24121) Duration for a failed BG Operation is incorrect

[ https://issues.apache.org/jira/browse/AMBARI-24121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Molnar updated AMBARI-24121: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Duration for a failed

[jira] [Commented] (AMBARI-23945) Infra Solr migration: use less params for migration steps (make it easier to use)

[ https://issues.apache.org/jira/browse/AMBARI-23945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518743#comment-16518743 ] Hudson commented on AMBARI-23945: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9499 (See

[jira] [Updated] (AMBARI-24156) Remove RepositoryVersionEntity and Begin Switching Checks To Use UpgradePlan

[ https://issues.apache.org/jira/browse/AMBARI-24156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24156: Labels: pull-request-available (was: ) > Remove RepositoryVersionEntity and Begin

[jira] [Updated] (AMBARI-24156) Remove RepositoryVersionEntity and Begin Switching Checks To Use UpgradePlan

[ https://issues.apache.org/jira/browse/AMBARI-24156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-24156: - Description: This commit includes the following changes: - Final removal of all

[jira] [Created] (AMBARI-24156) Remove RepositoryVersionEntity and Begin Switching Checks To Use UpgradePlan

Jonathan Hurley created AMBARI-24156: Summary: Remove RepositoryVersionEntity and Begin Switching Checks To Use UpgradePlan Key: AMBARI-24156 URL: https://issues.apache.org/jira/browse/AMBARI-24156

[jira] [Resolved] (AMBARI-24131) Unable to Perform Rolling Restarts Because of Outdated Postgres Driver

[ https://issues.apache.org/jira/browse/AMBARI-24131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley resolved AMBARI-24131. -- Resolution: Fixed > Unable to Perform Rolling Restarts Because of Outdated Postgres

[jira] [Commented] (AMBARI-24154) DB Connectivity Warnings for oozie & hive show up even after tests are passed

[ https://issues.apache.org/jira/browse/AMBARI-24154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518563#comment-16518563 ] Hudson commented on AMBARI-24154: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9498 (See

[jira] [Commented] (AMBARI-24121) Duration for a failed BG Operation is incorrect

[ https://issues.apache.org/jira/browse/AMBARI-24121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518561#comment-16518561 ] Hudson commented on AMBARI-24121: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9498 (See

[jira] [Commented] (AMBARI-24153) Customize Service step issues

[ https://issues.apache.org/jira/browse/AMBARI-24153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518566#comment-16518566 ] Hudson commented on AMBARI-24153: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9498 (See

[jira] [Commented] (AMBARI-24155) Ranger and KMS tab still present in Customize ServicesPage even after going back and deselecting them from Choose ServicesPage

[ https://issues.apache.org/jira/browse/AMBARI-24155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518562#comment-16518562 ] Hudson commented on AMBARI-24155: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9498 (See

[jira] [Commented] (AMBARI-24141) Rolling restarts not working when Kerberos Auto sign in is enabled for Ambari

[ https://issues.apache.org/jira/browse/AMBARI-24141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518533#comment-16518533 ] Hudson commented on AMBARI-24141: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9497 (See

[jira] [Updated] (AMBARI-24155) Ranger and KMS tab still present in Customize ServicesPage even after going back and deselecting them from Choose ServicesPage

[ https://issues.apache.org/jira/browse/AMBARI-24155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-24155: - Resolution: Fixed Status: Resolved (was: Patch Available) > Ranger and KMS tab still

[jira] [Resolved] (AMBARI-24153) Customize Service step issues

[ https://issues.apache.org/jira/browse/AMBARI-24153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-24153. -- Resolution: Fixed > Customize Service step issues > - > >

[jira] [Resolved] (AMBARI-24154) DB Connectivity Warnings for oozie & hive show up even after tests are passed

[ https://issues.apache.org/jira/browse/AMBARI-24154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-24154. -- Resolution: Fixed > DB Connectivity Warnings for oozie & hive show up even after tests are

[jira] [Updated] (AMBARI-24150) Install wizard stuck at Assign Slaves and Clients page

[ https://issues.apache.org/jira/browse/AMBARI-24150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-24150: - Fix Version/s: (was: trunk) 2.7.0 > Install wizard stuck at Assign

[jira] [Resolved] (AMBARI-24150) Install wizard stuck at Assign Slaves and Clients page

[ https://issues.apache.org/jira/browse/AMBARI-24150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-24150. -- Resolution: Fixed > Install wizard stuck at Assign Slaves and Clients page >

[jira] [Updated] (AMBARI-24121) Duration for a failed BG Operation is incorrect

[ https://issues.apache.org/jira/browse/AMBARI-24121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Molnar updated AMBARI-24121: --- Status: Patch Available (was: Open) > Duration for a failed BG Operation is incorrect >

[jira] [Resolved] (AMBARI-24141) Rolling restarts not working when Kerberos Auto sign in is enabled for Ambari

[ https://issues.apache.org/jira/browse/AMBARI-24141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas resolved AMBARI-24141. --- Resolution: Fixed > Rolling restarts not working when Kerberos Auto sign in is enabled for

[jira] [Resolved] (AMBARI-24095) Update usage of StackService data model due to change in ID format

[ https://issues.apache.org/jira/browse/AMBARI-24095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Golieb resolved AMBARI-24095. --- Resolution: Fixed > Update usage of StackService data model due to change in ID format >

[jira] [Resolved] (AMBARI-24140) Use name, version, and registry ID when registering mpacks

[ https://issues.apache.org/jira/browse/AMBARI-24140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Golieb resolved AMBARI-24140. --- Resolution: Fixed > Use name, version, and registry ID when registering mpacks >

[jira] [Resolved] (AMBARI-24137) Mpack display for a service showing NULL

[ https://issues.apache.org/jira/browse/AMBARI-24137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Golieb resolved AMBARI-24137. --- Resolution: Fixed > Mpack display for a service showing NULL >

[jira] [Commented] (AMBARI-24150) Install wizard stuck at Assign Slaves and Clients page

[ https://issues.apache.org/jira/browse/AMBARI-24150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518336#comment-16518336 ] Hudson commented on AMBARI-24150: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9496 (See

[jira] [Updated] (AMBARI-24155) Ranger and KMS tab still present in Customize ServicesPage even after going back and deselecting them from Choose ServicesPage

[ https://issues.apache.org/jira/browse/AMBARI-24155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24155: -- Status: Patch Available (was: Open) > Ranger and KMS tab still present in Customize

[jira] [Updated] (AMBARI-24155) Ranger and KMS tab still present in Customize ServicesPage even after going back and deselecting them from Choose ServicesPage

[ https://issues.apache.org/jira/browse/AMBARI-24155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24155: Labels: pull-request-available (was: ) > Ranger and KMS tab still present in Customize

[jira] [Created] (AMBARI-24155) Ranger and KMS tab still present in Customize ServicesPage even after going back and deselecting them from Choose ServicesPage

Andrii Babiichuk created AMBARI-24155: - Summary: Ranger and KMS tab still present in Customize ServicesPage even after going back and deselecting them from Choose ServicesPage Key: AMBARI-24155 URL:

[jira] [Commented] (AMBARI-24143) Logs not indexed with default configuration for many components when custom service accounts are used

[ https://issues.apache.org/jira/browse/AMBARI-24143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518149#comment-16518149 ] Hudson commented on AMBARI-24143: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9495 (See

[jira] [Updated] (AMBARI-24154) DB Connectivity Warnings for oozie & hive show up even after tests are passed

[ https://issues.apache.org/jira/browse/AMBARI-24154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24154: Labels: pull-request-available (was: ) > DB Connectivity Warnings for oozie & hive show

[jira] [Created] (AMBARI-24154) DB Connectivity Warnings for oozie & hive show up even after tests are passed

Antonenko Alexander created AMBARI-24154: Summary: DB Connectivity Warnings for oozie & hive show up even after tests are passed Key: AMBARI-24154 URL: https://issues.apache.org/jira/browse/AMBARI-24154

[jira] [Updated] (AMBARI-24154) DB Connectivity Warnings for oozie & hive show up even after tests are passed

[ https://issues.apache.org/jira/browse/AMBARI-24154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-24154: - Description: During initial installation, if both hive and oozie are

[jira] [Assigned] (AMBARI-24154) DB Connectivity Warnings for oozie & hive show up even after tests are passed

[ https://issues.apache.org/jira/browse/AMBARI-24154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-24154: Assignee: Antonenko Alexander > DB Connectivity Warnings for oozie &

[jira] [Updated] (AMBARI-24055) INFRA_SOLR START failed

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

[jira] [Updated] (AMBARI-24143) Logs not indexed with default configuration for many components when custom service accounts are used

[ https://issues.apache.org/jira/browse/AMBARI-24143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24143: Resolution: Fixed Status: Resolved (was: Patch Available) > Logs not indexed

[jira] [Updated] (AMBARI-24143) Logs not indexed with default configuration for many components when custom service accounts are used

[ https://issues.apache.org/jira/browse/AMBARI-24143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24143: Status: Patch Available (was: In Progress) > Logs not indexed with default

[jira] [Updated] (AMBARI-24153) Customize Service step issues

[ https://issues.apache.org/jira/browse/AMBARI-24153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24153: Labels: pull-request-available (was: ) > Customize Service step issues >

[jira] [Updated] (AMBARI-24153) Customize Service step issues

[ https://issues.apache.org/jira/browse/AMBARI-24153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-24153: -- Description: There are some issues in Step 7 of the Installer Wizard 1. Even if there are

[jira] [Updated] (AMBARI-24153) Customize Service step issues

[ https://issues.apache.org/jira/browse/AMBARI-24153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-24153: -- Attachment: screencapture-104-196-91-59-8080-2018-06-19-06_36_27 (1).png

[jira] [Created] (AMBARI-24153) Customize Service step issues

Andrii Tkach created AMBARI-24153: - Summary: Customize Service step issues Key: AMBARI-24153 URL: https://issues.apache.org/jira/browse/AMBARI-24153 Project: Ambari Issue Type: Bug

[jira] [Commented] (AMBARI-9016) Ambari API uses HTTP Header Content-Type:text/plain when the content is JSON.

[ https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518079#comment-16518079 ] Sean Roberts commented on AMBARI-9016: -- For reference, this is due to ambari-server API explicitly

[jira] [Updated] (AMBARI-24149) Agent fails to auto-start HDFS when using LZO

[ https://issues.apache.org/jira/browse/AMBARI-24149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24149: Labels: pull-request-available (was: ) > Agent fails to auto-start HDFS when using LZO

[jira] [Updated] (AMBARI-24149) Agent fails to auto-start HDFS when using LZO

[ https://issues.apache.org/jira/browse/AMBARI-24149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24149: - Attachment: AMBARI-24149.patch > Agent fails to auto-start HDFS when using LZO >

[jira] [Updated] (AMBARI-24149) Agent fails to auto-start HDFS when using LZO

[ https://issues.apache.org/jira/browse/AMBARI-24149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24149: - Status: Patch Available (was: Open) > Agent fails to auto-start HDFS when using LZO >

[jira] [Commented] (AMBARI-23945) Infra Solr migration: use less params for migration steps (make it easier to use)

[ https://issues.apache.org/jira/browse/AMBARI-23945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518043#comment-16518043 ] Hudson commented on AMBARI-23945: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9494 (See

[jira] [Assigned] (AMBARI-24152) Ambari Workflow Manager (wfmanager) sends plaintext content over API. JSON is expected.

[ https://issues.apache.org/jira/browse/AMBARI-24152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat reassigned AMBARI-24152: --- Assignee: venkat > Ambari Workflow Manager (wfmanager) sends plaintext content over API. JSON is

[jira] [Assigned] (AMBARI-9016) Ambari API uses HTTP Header Content-Type:text/plain when the content is JSON.

[ https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat reassigned AMBARI-9016: -- Assignee: venkat > Ambari API uses HTTP Header Content-Type:text/plain when the content is JSON. >

[jira] [Updated] (AMBARI-24152) Ambari Workflow Manager (wfmanager) sends plaintext content over API. JSON is expected.

[ https://issues.apache.org/jira/browse/AMBARI-24152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Roberts updated AMBARI-24152: -- Summary: Ambari Workflow Manager (wfmanager) sends plaintext content over API. JSON is

[jira] [Created] (AMBARI-24152) Ambari Workflow Manager (wfmanager) sends plaintext content when it should send json

Sean Roberts created AMBARI-24152: - Summary: Ambari Workflow Manager (wfmanager) sends plaintext content when it should send json Key: AMBARI-24152 URL: https://issues.apache.org/jira/browse/AMBARI-24152

[jira] [Created] (AMBARI-24151) Kafka Broker doesn't produce stdout/stderr (e.g. Kerberos debug) when started via Ambari

Vipin Rathor created AMBARI-24151: - Summary: Kafka Broker doesn't produce stdout/stderr (e.g. Kerberos debug) when started via Ambari Key: AMBARI-24151 URL: https://issues.apache.org/jira/browse/AMBARI-24151

[jira] [Updated] (AMBARI-24150) Install wizard stuck at Assign Slaves and Clients page

[ https://issues.apache.org/jira/browse/AMBARI-24150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24150: Labels: pull-request-available (was: ) > Install wizard stuck at Assign Slaves and

[jira] [Created] (AMBARI-24150) Install wizard stuck at Assign Slaves and Clients page

Ishan Bhatt created AMBARI-24150: Summary: Install wizard stuck at Assign Slaves and Clients page Key: AMBARI-24150 URL: https://issues.apache.org/jira/browse/AMBARI-24150 Project: Ambari

[jira] [Updated] (AMBARI-24149) Agent fails to auto-start HDFS when using LZO

[ https://issues.apache.org/jira/browse/AMBARI-24149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-24149: --- Summary: Agent fails to auto-start HDFS when using LZO (was: Cannot auto-start