[jira] [Commented] (AMBARI-23817) Visualizing the Encrypted zones and Erasure coded zones in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-23817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588402#comment-16588402 ] Hudson commented on AMBARI-23817: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #197 (See [https://builds.apache.org/job/Ambari-branch-2.7/197/]) AMBARI-23817 : Visualizing the Encrypted zones and Erasure coded zones (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=2d455f306c43524417de556db971dc44f4c7518a]) * (edit) contrib/views/pig/src/test/java/org/apache/ambari/view/pig/test/ScriptTestUnmanaged.java * (add) contrib/views/utils/src/test/java/org/apache/ambari/view/utils/hdfs/DummyNonHdfsFileStatus.java * (edit) contrib/views/utils/pom.xml * (edit) contrib/views/files/src/main/resources/ui/app/helpers/shorten-text.js * (edit) contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/HdfsApi.java * (edit) contrib/views/pom.xml * (edit) contrib/views/pig/src/test/java/org/apache/ambari/view/pig/test/JobTest.java * (add) contrib/views/utils/src/test/java/org/apache/ambari/view/utils/hdfs/DummyFileStatus.java * (edit) contrib/views/files/src/main/resources/ui/app/config/files-columns.js * (edit) contrib/views/pig/pom.xml * (edit) contrib/views/ambari-views-package/pom.xml * (edit) contrib/views/commons/pom.xml * (edit) contrib/views/utils/src/test/java/org/apache/ambari/view/utils/hdfs/HdfsApiTest.java * (edit) contrib/views/files/pom.xml * (edit) contrib/views/files/src/main/resources/ui/app/models/file.js * (edit) contrib/views/files/src/main/resources/ui/app/templates/components/file-row.hbs > Visualizing the Encrypted zones and Erasure coded zones in HDFS > --- > > Key: AMBARI-23817 > URL: https://issues.apache.org/jira/browse/AMBARI-23817 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-23817-trunk.patch > > Time Spent: 1h 50m > Remaining Estimate: 0h > > For hadoop 3.0 Files view should show whether a folder or file is Encrypted > or not and what Erasure coding policy is used for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23817) Visualizing the Encrypted zones and Erasure coded zones in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-23817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588400#comment-16588400 ] Hudson commented on AMBARI-23817: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9880 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9880/]) AMBARI-23817 : Visualizing the Encrypted zones and Erasure coded zones (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=31ebcd2548337621921e0606a26130c7d2f6f554]) * (edit) contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/HdfsApi.java * (edit) contrib/views/pom.xml * (edit) contrib/views/utils/src/test/java/org/apache/ambari/view/utils/hdfs/HdfsApiTest.java * (edit) contrib/views/commons/pom.xml * (edit) contrib/views/utils/pom.xml * (add) contrib/views/utils/src/test/java/org/apache/ambari/view/utils/hdfs/DummyFileStatus.java * (edit) contrib/views/pig/src/test/java/org/apache/ambari/view/pig/test/JobTest.java * (edit) contrib/views/files/src/main/resources/ui/app/helpers/shorten-text.js * (edit) contrib/views/files/src/main/resources/ui/app/config/files-columns.js * (edit) contrib/views/ambari-views-package/pom.xml * (edit) contrib/views/files/src/main/resources/ui/app/models/file.js * (edit) contrib/views/pig/pom.xml * (edit) contrib/views/pig/src/test/java/org/apache/ambari/view/pig/test/ScriptTestUnmanaged.java * (add) contrib/views/utils/src/test/java/org/apache/ambari/view/utils/hdfs/DummyNonHdfsFileStatus.java * (edit) contrib/views/files/src/main/resources/ui/app/templates/components/file-row.hbs * (edit) contrib/views/files/pom.xml > Visualizing the Encrypted zones and Erasure coded zones in HDFS > --- > > Key: AMBARI-23817 > URL: https://issues.apache.org/jira/browse/AMBARI-23817 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-23817-trunk.patch > > Time Spent: 1h 50m > Remaining Estimate: 0h > > For hadoop 3.0 Files view should show whether a folder or file is Encrypted > or not and what Erasure coding policy is used for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24520) Fix set KDC admin credentials section in enable Kerberos doc
[
https://issues.apache.org/jira/browse/AMBARI-24520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588078#comment-16588078
]
Hudson commented on AMBARI-24520:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #196 (See
[https://builds.apache.org/job/Ambari-branch-2.7/196/])
[AMBARI-24520] Fix set KDC admin credentials section in enable Kerberos
(rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c064eb16584b0e84bb2851a49f1a0549cc5f61bc])
* (edit) ambari-server/docs/security/kerberos/enabling_kerberos.md
> Fix set KDC admin credentials section in enable Kerberos doc
>
>
> Key: AMBARI-24520
> URL: https://issues.apache.org/jira/browse/AMBARI-24520
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Fix set KDC admin credentials section in enable Kerberos doc
> The current documentation at
> https://github.com/apache/ambari/blob/branch-2.7/ambari-server/docs/security/kerberos/enabling_kerberos.md#set-the-kdc-administrator-credentials
> indicates an incorrect URL for the API call.
> It should read:
> {noformat}
> http://AMBARI_SERVER:8080/api/v1/clusters/CLUSTER_NAME/credentials/kdc.admin.credential
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24522) Cannot connect to MIT KDC admin server when port is specified in kerberos-env/admin_server_host
[
https://issues.apache.org/jira/browse/AMBARI-24522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24522:
--
Status: Patch Available (was: In Progress)
> Cannot connect to MIT KDC admin server when port is specified in
> kerberos-env/admin_server_host
> ---
>
> Key: AMBARI-24522
> URL: https://issues.apache.org/jira/browse/AMBARI-24522
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, pull-request-available, regression
> Fix For: 2.7.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Cannot connect to MIT KDC admin server when port is specified in
> {{kerberos-env/admin_server_host}}. The following error is seen when
> validating the KDC admin credentials:
> {noformat}
> kinit: Server not found in Kerberos database while getting initial credentials
> {noformat}
> The reason for this is due to how the credentials are created for accessing
> the MIT KDC administration server.
> {noformat}
> kinit -c -S kadmin/
> {noformat}
> If a port was added to the {{kerberos-env/admin_server_host}} value then the
> server principal will be generated like {{kadmin/kdc.example.com:4749}}
> rather than {{kadmin/kdc.example.com}}. Therefore the server principal is not
> found.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24523) Hive and Oozie JDBC url reset after set manually
[ https://issues.apache.org/jira/browse/AMBARI-24523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24523: - Fix Version/s: (was: 2.7.1) 2.7.2 > Hive and Oozie JDBC url reset after set manually > > > Key: AMBARI-24523 > URL: https://issues.apache.org/jira/browse/AMBARI-24523 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 20m > Remaining Estimate: 0h > > JDBC urls of Hive and Oozie are reset even after being set manually when > toggling RANGER plugins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24522) Cannot connect to MIT KDC admin server when port is specified in kerberos-env/admin_server_host
[
https://issues.apache.org/jira/browse/AMBARI-24522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24522:
Labels: kerberos pull-request-available regression (was: kerberos
regression)
> Cannot connect to MIT KDC admin server when port is specified in
> kerberos-env/admin_server_host
> ---
>
> Key: AMBARI-24522
> URL: https://issues.apache.org/jira/browse/AMBARI-24522
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, pull-request-available, regression
> Fix For: 2.7.2
>
>
> Cannot connect to MIT KDC admin server when port is specified in
> {{kerberos-env/admin_server_host}}. The following error is seen when
> validating the KDC admin credentials:
> {noformat}
> kinit: Server not found in Kerberos database while getting initial credentials
> {noformat}
> The reason for this is due to how the credentials are created for accessing
> the MIT KDC administration server.
> {noformat}
> kinit -c -S kadmin/
> {noformat}
> If a port was added to the {{kerberos-env/admin_server_host}} value then the
> server principal will be generated like {{kadmin/kdc.example.com:4749}}
> rather than {{kadmin/kdc.example.com}}. Therefore the server principal is not
> found.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24520) Fix set KDC admin credentials section in enable Kerberos doc
[
https://issues.apache.org/jira/browse/AMBARI-24520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24520:
--
Fix Version/s: (was: 2.7.1)
2.7.2
> Fix set KDC admin credentials section in enable Kerberos doc
>
>
> Key: AMBARI-24520
> URL: https://issues.apache.org/jira/browse/AMBARI-24520
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Fix set KDC admin credentials section in enable Kerberos doc
> The current documentation at
> https://github.com/apache/ambari/blob/branch-2.7/ambari-server/docs/security/kerberos/enabling_kerberos.md#set-the-kdc-administrator-credentials
> indicates an incorrect URL for the API call.
> It should read:
> {noformat}
> http://AMBARI_SERVER:8080/api/v1/clusters/CLUSTER_NAME/credentials/kdc.admin.credential
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24520) Fix set KDC admin credentials section in enable Kerberos doc
[
https://issues.apache.org/jira/browse/AMBARI-24520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24520:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Fix set KDC admin credentials section in enable Kerberos doc
>
>
> Key: AMBARI-24520
> URL: https://issues.apache.org/jira/browse/AMBARI-24520
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Fix set KDC admin credentials section in enable Kerberos doc
> The current documentation at
> https://github.com/apache/ambari/blob/branch-2.7/ambari-server/docs/security/kerberos/enabling_kerberos.md#set-the-kdc-administrator-credentials
> indicates an incorrect URL for the API call.
> It should read:
> {noformat}
> http://AMBARI_SERVER:8080/api/v1/clusters/CLUSTER_NAME/credentials/kdc.admin.credential
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24522) Cannot connect to MIT KDC admin server when port is specified in kerberos-env/admin_server_host
[
https://issues.apache.org/jira/browse/AMBARI-24522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24522:
--
Fix Version/s: (was: 2.7.1)
2.7.2
> Cannot connect to MIT KDC admin server when port is specified in
> kerberos-env/admin_server_host
> ---
>
> Key: AMBARI-24522
> URL: https://issues.apache.org/jira/browse/AMBARI-24522
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, regression
> Fix For: 2.7.2
>
>
> Cannot connect to MIT KDC admin server when port is specified in
> {{kerberos-env/admin_server_host}}. The following error is seen when
> validating the KDC admin credentials:
> {noformat}
> kinit: Server not found in Kerberos database while getting initial credentials
> {noformat}
> The reason for this is due to how the credentials are created for accessing
> the MIT KDC administration server.
> {noformat}
> kinit -c -S kadmin/
> {noformat}
> If a port was added to the {{kerberos-env/admin_server_host}} value then the
> server principal will be generated like {{kadmin/kdc.example.com:4749}}
> rather than {{kadmin/kdc.example.com}}. Therefore the server principal is not
> found.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24520) Fix set KDC admin credentials section in enable Kerberos doc
[
https://issues.apache.org/jira/browse/AMBARI-24520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588023#comment-16588023
]
Hudson commented on AMBARI-24520:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9879 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9879/])
[AMBARI-24520] Fix set KDC admin credentials section in enable Kerberos
(rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=bff429c98325e97fd32868fc92b8c7a0dfa5])
* (edit) ambari-server/docs/security/kerberos/enabling_kerberos.md
> Fix set KDC admin credentials section in enable Kerberos doc
>
>
> Key: AMBARI-24520
> URL: https://issues.apache.org/jira/browse/AMBARI-24520
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Fix set KDC admin credentials section in enable Kerberos doc
> The current documentation at
> https://github.com/apache/ambari/blob/branch-2.7/ambari-server/docs/security/kerberos/enabling_kerberos.md#set-the-kdc-administrator-credentials
> indicates an incorrect URL for the API call.
> It should read:
> {noformat}
> http://AMBARI_SERVER:8080/api/v1/clusters/CLUSTER_NAME/credentials/kdc.admin.credential
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24523) Hive and Oozie JDBC url reset after set manually
[ https://issues.apache.org/jira/browse/AMBARI-24523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24523: Labels: pull-request-available (was: ) > Hive and Oozie JDBC url reset after set manually > > > Key: AMBARI-24523 > URL: https://issues.apache.org/jira/browse/AMBARI-24523 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > > JDBC urls of Hive and Oozie are reset even after being set manually when > toggling RANGER plugins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24523) Hive and Oozie JDBC url reset after set manually
Ishan Bhatt created AMBARI-24523: Summary: Hive and Oozie JDBC url reset after set manually Key: AMBARI-24523 URL: https://issues.apache.org/jira/browse/AMBARI-24523 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.1 Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.7.1 JDBC urls of Hive and Oozie are reset even after being set manually when toggling RANGER plugins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24518) Requests STOMP topic sent updates for host check request
[ https://issues.apache.org/jira/browse/AMBARI-24518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587866#comment-16587866 ] Hudson commented on AMBARI-24518: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #195 (See [https://builds.apache.org/job/Ambari-branch-2.7/195/]) AMBARI-24518. Requests STOMP topic sent updates for host check request. (jayush: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=ec968edf78a11921d0555e3e481c0ce9763d80f1]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessorImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/listeners/tasks/TaskStatusListener.java > Requests STOMP topic sent updates for host check request > > > Key: AMBARI-24518 > URL: https://issues.apache.org/jira/browse/AMBARI-24518 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Server should post only cluster related request updates to "/events/requests" > STOMP topic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24520) Fix set KDC admin credentials section in enable Kerberos doc
[
https://issues.apache.org/jira/browse/AMBARI-24520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24520:
--
Status: Patch Available (was: In Progress)
> Fix set KDC admin credentials section in enable Kerberos doc
>
>
> Key: AMBARI-24520
> URL: https://issues.apache.org/jira/browse/AMBARI-24520
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Fix set KDC admin credentials section in enable Kerberos doc
> The current documentation at
> https://github.com/apache/ambari/blob/branch-2.7/ambari-server/docs/security/kerberos/enabling_kerberos.md#set-the-kdc-administrator-credentials
> indicates an incorrect URL for the API call.
> It should read:
> {noformat}
> http://AMBARI_SERVER:8080/api/v1/clusters/CLUSTER_NAME/credentials/kdc.admin.credential
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24520) Fix set KDC admin credentials section in enable Kerberos doc
[
https://issues.apache.org/jira/browse/AMBARI-24520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24520:
Labels: pull-request-available (was: )
> Fix set KDC admin credentials section in enable Kerberos doc
>
>
> Key: AMBARI-24520
> URL: https://issues.apache.org/jira/browse/AMBARI-24520
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> Fix set KDC admin credentials section in enable Kerberos doc
> The current documentation at
> https://github.com/apache/ambari/blob/branch-2.7/ambari-server/docs/security/kerberos/enabling_kerberos.md#set-the-kdc-administrator-credentials
> indicates an incorrect URL for the API call.
> It should read:
> {noformat}
> http://AMBARI_SERVER:8080/api/v1/clusters/CLUSTER_NAME/credentials/kdc.admin.credential
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24522) Cannot connect to MIT KDC admin server when port is specified in kerberos-env/admin_server_host
Robert Levas created AMBARI-24522:
-
Summary: Cannot connect to MIT KDC admin server when port is
specified in kerberos-env/admin_server_host
Key: AMBARI-24522
URL: https://issues.apache.org/jira/browse/AMBARI-24522
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Robert Levas
Assignee: Robert Levas
Fix For: 2.7.1
Cannot connect to MIT KDC admin server when port is specified in
{{kerberos-env/admin_server_host}}. The following error is seen when
validating the KDC admin credentials:
{noformat}
kinit: Server not found in Kerberos database while getting initial credentials
{noformat}
The reason for this is due to how the credentials are created for accessing the
MIT KDC administration server.
{noformat}
kinit -c -S kadmin/
{noformat}
If a port was added to the {{kerberos-env/admin_server_host}} value then the
server principal will be generated like {{kadmin/kdc.example.com:4749}} rather
than {{kadmin/kdc.example.com}}. Therefore the server principal is not found.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24499) Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
[
https://issues.apache.org/jira/browse/AMBARI-24499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587812#comment-16587812
]
Hudson commented on AMBARI-24499:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9878 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9878/])
AMBARI-24499 blueprint support for multiple TIMELINE_READER components
(oleewere:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=5a2d63e2cc887dae8af56c97c4673e7113f7c91c])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
> Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
> -
>
> Key: AMBARI-24499
> URL: https://issues.apache.org/jira/browse/AMBARI-24499
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Nettleton
>Assignee: Balázs Bence Sári
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The BlueprintConfigurationProcessor does not current handle the case of
> multiple Yarn TIMELINE_READER instances properly.
> Generally, only a singleton instance of the TIMELINE_READER instance is
> deployed, but there might be scenarios in which customers will choose to
> deploy more than one instance, with just one instance running at a given
> time.
> Currently, deploying a Blueprint with multiple TIMELINE_READER instances
> fails with the following exception:
> {code:java}
> java.lang.IllegalArgumentException: Unable to update configuration property
> 'yarn.timeline-service.reader.webapp.address' with topology information.
> Component 'TIMELINE_READER' is mapped to an invalid number of hosts '2'.
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1945)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.updateValue(BlueprintConfigurationProcessor.java:739)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doGeneralPropertyUpdatesForClusterCreate(BlueprintConfigurationProcessor.java:641)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForClusterCreate(BlueprintConfigurationProcessor.java:443)
> at
> org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:152)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:80)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:45)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745){code}
> The BlueprintConfiguration processor should be updated to allow for more than
> one TIMELINE_READER instance to be deployed. This assumes that the Blueprint
> developer will set any Yarn properties required that point towards the
> TIMELINE_READER instance, including the usage of HOSTGROUP properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24499) Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
[
https://issues.apache.org/jira/browse/AMBARI-24499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587808#comment-16587808
]
Hudson commented on AMBARI-24499:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #194 (See
[https://builds.apache.org/job/Ambari-branch-2.7/194/])
AMBARI-24499 blueprint support for multiple TIMELINE_READER components
(oleewere:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=3f362cd09418dfe7fcc25891ff28a1e090a64c85])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
> Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
> -
>
> Key: AMBARI-24499
> URL: https://issues.apache.org/jira/browse/AMBARI-24499
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Nettleton
>Assignee: Balázs Bence Sári
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The BlueprintConfigurationProcessor does not current handle the case of
> multiple Yarn TIMELINE_READER instances properly.
> Generally, only a singleton instance of the TIMELINE_READER instance is
> deployed, but there might be scenarios in which customers will choose to
> deploy more than one instance, with just one instance running at a given
> time.
> Currently, deploying a Blueprint with multiple TIMELINE_READER instances
> fails with the following exception:
> {code:java}
> java.lang.IllegalArgumentException: Unable to update configuration property
> 'yarn.timeline-service.reader.webapp.address' with topology information.
> Component 'TIMELINE_READER' is mapped to an invalid number of hosts '2'.
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1945)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.updateValue(BlueprintConfigurationProcessor.java:739)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doGeneralPropertyUpdatesForClusterCreate(BlueprintConfigurationProcessor.java:641)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForClusterCreate(BlueprintConfigurationProcessor.java:443)
> at
> org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:152)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:80)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:45)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745){code}
> The BlueprintConfiguration processor should be updated to allow for more than
> one TIMELINE_READER instance to be deployed. This assumes that the Blueprint
> developer will set any Yarn properties required that point towards the
> TIMELINE_READER instance, including the usage of HOSTGROUP properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24521) CLONE - Requests STOMP topic sent updates for host check request
[ https://issues.apache.org/jira/browse/AMBARI-24521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587789#comment-16587789 ] Jayush Luniya commented on AMBARI-24521: [~mpapirkovskyy] filing this JIRA to commit this change to trunk too. > CLONE - Requests STOMP topic sent updates for host check request > > > Key: AMBARI-24521 > URL: https://issues.apache.org/jira/browse/AMBARI-24521 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > > Server should post only cluster related request updates to "/events/requests" > STOMP topic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24521) CLONE - Requests STOMP topic sent updates for host check request
[ https://issues.apache.org/jira/browse/AMBARI-24521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24521: --- Fix Version/s: (was: 2.7.1) 3.0.0 > CLONE - Requests STOMP topic sent updates for host check request > > > Key: AMBARI-24521 > URL: https://issues.apache.org/jira/browse/AMBARI-24521 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > > Server should post only cluster related request updates to "/events/requests" > STOMP topic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24518) Requests STOMP topic sent updates for host check request
[ https://issues.apache.org/jira/browse/AMBARI-24518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-24518. Resolution: Fixed > Requests STOMP topic sent updates for host check request > > > Key: AMBARI-24518 > URL: https://issues.apache.org/jira/browse/AMBARI-24518 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Server should post only cluster related request updates to "/events/requests" > STOMP topic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24521) CLONE - Requests STOMP topic sent updates for host check request
Jayush Luniya created AMBARI-24521: -- Summary: CLONE - Requests STOMP topic sent updates for host check request Key: AMBARI-24521 URL: https://issues.apache.org/jira/browse/AMBARI-24521 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.1 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 2.7.1 Server should post only cluster related request updates to "/events/requests" STOMP topic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24506) Upgrade: Infra Solr service is not renamed in Upgrade History table
[
https://issues.apache.org/jira/browse/AMBARI-24506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587729#comment-16587729
]
Hudson commented on AMBARI-24506:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9877 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9877/])
AMBARI-24506 - ADDENDUM - Upgrade: Infra Solr service is not renamed in
(oleewere:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=539d8ee66eafa2e8a0fa920319afb3bc2be23954])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog271.java
> Upgrade: Infra Solr service is not renamed in Upgrade History table
> ---
>
> Key: AMBARI-24506
> URL: https://issues.apache.org/jira/browse/AMBARI-24506
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra, ambari-server
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.2.0-298 and HDP version:
> 2.6.2.14-5
> # Upgrade Ambari to 2.6.2.0, HDP to 2.6.5.0
> # Upgrade Ambari to 2.7.0, HDP to 3.0.1.0
> # Go to Upgrade history page
> Upgrade history page shows empty (see attached for js error)
> Reason: upgrade_history record is not upgarade during ambari 2.7.0 upgrade
> *Workaround* (before 2.7.1):
> {code:java}
> UPDATE upgrade_history
> SET service_name = 'AMBARI_INFRA_SOLR'
> WHERE service_name = 'AMBARI_INFRA'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24506) Upgrade: Infra Solr service is not renamed in Upgrade History table
[
https://issues.apache.org/jira/browse/AMBARI-24506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587719#comment-16587719
]
Hudson commented on AMBARI-24506:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #193 (See
[https://builds.apache.org/job/Ambari-branch-2.7/193/])
AMBARI-24506 - ADDENDUM - Upgrade: Infra Solr service is not renamed in
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=0cd1b3693bef25b4d4b4cd336d879545bdc464da])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog271.java
> Upgrade: Infra Solr service is not renamed in Upgrade History table
> ---
>
> Key: AMBARI-24506
> URL: https://issues.apache.org/jira/browse/AMBARI-24506
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra, ambari-server
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.2.0-298 and HDP version:
> 2.6.2.14-5
> # Upgrade Ambari to 2.6.2.0, HDP to 2.6.5.0
> # Upgrade Ambari to 2.7.0, HDP to 3.0.1.0
> # Go to Upgrade history page
> Upgrade history page shows empty (see attached for js error)
> Reason: upgrade_history record is not upgarade during ambari 2.7.0 upgrade
> *Workaround* (before 2.7.1):
> {code:java}
> UPDATE upgrade_history
> SET service_name = 'AMBARI_INFRA_SOLR'
> WHERE service_name = 'AMBARI_INFRA'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24520) Fix set KDC admin credentials section in enable Kerberos doc
Robert Levas created AMBARI-24520:
-
Summary: Fix set KDC admin credentials section in enable Kerberos
doc
Key: AMBARI-24520
URL: https://issues.apache.org/jira/browse/AMBARI-24520
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.0
Reporter: Robert Levas
Assignee: Robert Levas
Fix For: 2.7.1
Fix set KDC admin credentials section in enable Kerberos doc
The current documentation at
https://github.com/apache/ambari/blob/branch-2.7/ambari-server/docs/security/kerberos/enabling_kerberos.md#set-the-kdc-administrator-credentials
indicates an incorrect URL for the API call.
It should read:
{noformat}
http://AMBARI_SERVER:8080/api/v1/clusters/CLUSTER_NAME/credentials/kdc.admin.credential
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24499) Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
[
https://issues.apache.org/jira/browse/AMBARI-24499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24499:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
> -
>
> Key: AMBARI-24499
> URL: https://issues.apache.org/jira/browse/AMBARI-24499
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Nettleton
>Assignee: Balázs Bence Sári
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The BlueprintConfigurationProcessor does not current handle the case of
> multiple Yarn TIMELINE_READER instances properly.
> Generally, only a singleton instance of the TIMELINE_READER instance is
> deployed, but there might be scenarios in which customers will choose to
> deploy more than one instance, with just one instance running at a given
> time.
> Currently, deploying a Blueprint with multiple TIMELINE_READER instances
> fails with the following exception:
> {code:java}
> java.lang.IllegalArgumentException: Unable to update configuration property
> 'yarn.timeline-service.reader.webapp.address' with topology information.
> Component 'TIMELINE_READER' is mapped to an invalid number of hosts '2'.
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1945)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.updateValue(BlueprintConfigurationProcessor.java:739)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doGeneralPropertyUpdatesForClusterCreate(BlueprintConfigurationProcessor.java:641)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForClusterCreate(BlueprintConfigurationProcessor.java:443)
> at
> org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:152)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:80)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:45)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745){code}
> The BlueprintConfiguration processor should be updated to allow for more than
> one TIMELINE_READER instance to be deployed. This assumes that the Blueprint
> developer will set any Yarn properties required that point towards the
> TIMELINE_READER instance, including the usage of HOSTGROUP properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24518) Requests STOMP topic sent updates for host check request
[ https://issues.apache.org/jira/browse/AMBARI-24518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24518: Labels: pull-request-available (was: ) > Requests STOMP topic sent updates for host check request > > > Key: AMBARI-24518 > URL: https://issues.apache.org/jira/browse/AMBARI-24518 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.1 > > > Server should post only cluster related request updates to "/events/requests" > STOMP topic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24499) Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
[
https://issues.apache.org/jira/browse/AMBARI-24499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balázs Bence Sári updated AMBARI-24499:
---
Status: Patch Available (was: In Progress)
> Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
> -
>
> Key: AMBARI-24499
> URL: https://issues.apache.org/jira/browse/AMBARI-24499
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Nettleton
>Assignee: Balázs Bence Sári
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The BlueprintConfigurationProcessor does not current handle the case of
> multiple Yarn TIMELINE_READER instances properly.
> Generally, only a singleton instance of the TIMELINE_READER instance is
> deployed, but there might be scenarios in which customers will choose to
> deploy more than one instance, with just one instance running at a given
> time.
> Currently, deploying a Blueprint with multiple TIMELINE_READER instances
> fails with the following exception:
> {code:java}
> java.lang.IllegalArgumentException: Unable to update configuration property
> 'yarn.timeline-service.reader.webapp.address' with topology information.
> Component 'TIMELINE_READER' is mapped to an invalid number of hosts '2'.
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1945)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.updateValue(BlueprintConfigurationProcessor.java:739)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doGeneralPropertyUpdatesForClusterCreate(BlueprintConfigurationProcessor.java:641)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForClusterCreate(BlueprintConfigurationProcessor.java:443)
> at
> org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:152)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:80)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:45)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745){code}
> The BlueprintConfiguration processor should be updated to allow for more than
> one TIMELINE_READER instance to be deployed. This assumes that the Blueprint
> developer will set any Yarn properties required that point towards the
> TIMELINE_READER instance, including the usage of HOSTGROUP properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24499) Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
[
https://issues.apache.org/jira/browse/AMBARI-24499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24499:
Labels: pull-request-available (was: )
> Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
> -
>
> Key: AMBARI-24499
> URL: https://issues.apache.org/jira/browse/AMBARI-24499
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Nettleton
>Assignee: Balázs Bence Sári
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> The BlueprintConfigurationProcessor does not current handle the case of
> multiple Yarn TIMELINE_READER instances properly.
> Generally, only a singleton instance of the TIMELINE_READER instance is
> deployed, but there might be scenarios in which customers will choose to
> deploy more than one instance, with just one instance running at a given
> time.
> Currently, deploying a Blueprint with multiple TIMELINE_READER instances
> fails with the following exception:
> {code:java}
> java.lang.IllegalArgumentException: Unable to update configuration property
> 'yarn.timeline-service.reader.webapp.address' with topology information.
> Component 'TIMELINE_READER' is mapped to an invalid number of hosts '2'.
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1945)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.updateValue(BlueprintConfigurationProcessor.java:739)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doGeneralPropertyUpdatesForClusterCreate(BlueprintConfigurationProcessor.java:641)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForClusterCreate(BlueprintConfigurationProcessor.java:443)
> at
> org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:152)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:80)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:45)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745){code}
> The BlueprintConfiguration processor should be updated to allow for more than
> one TIMELINE_READER instance to be deployed. This assumes that the Blueprint
> developer will set any Yarn properties required that point towards the
> TIMELINE_READER instance, including the usage of HOSTGROUP properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24519) Cover journal node step 5 controller
[ https://issues.apache.org/jira/browse/AMBARI-24519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24519: Labels: pull-request-available (was: ) > Cover journal node step 5 controller > > > Key: AMBARI-24519 > URL: https://issues.apache.org/jira/browse/AMBARI-24519 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24519) Cover journal node step 5 controller
[ https://issues.apache.org/jira/browse/AMBARI-24519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-24519: - Status: Patch Available (was: Open) > Cover journal node step 5 controller > > > Key: AMBARI-24519 > URL: https://issues.apache.org/jira/browse/AMBARI-24519 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24519) Cover journal node step 5 controller
Antonenko Alexander created AMBARI-24519: Summary: Cover journal node step 5 controller Key: AMBARI-24519 URL: https://issues.apache.org/jira/browse/AMBARI-24519 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Antonenko Alexander -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24519) Cover journal node step 5 controller
[ https://issues.apache.org/jira/browse/AMBARI-24519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-24519: Assignee: Antonenko Alexander > Cover journal node step 5 controller > > > Key: AMBARI-24519 > URL: https://issues.apache.org/jira/browse/AMBARI-24519 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24518) Requests STOMP topic sent updates for host check request
Myroslav Papirkovskyi created AMBARI-24518: -- Summary: Requests STOMP topic sent updates for host check request Key: AMBARI-24518 URL: https://issues.apache.org/jira/browse/AMBARI-24518 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.1 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 2.7.1 Server should post only cluster related request updates to "/events/requests" STOMP topic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24513) NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB
[
https://issues.apache.org/jira/browse/AMBARI-24513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587451#comment-16587451
]
Hudson commented on AMBARI-24513:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9876 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9876/])
[AMBARI-24513] Using current timestamp as created_time in case there is
(oleewere:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=93818f3412267ddd21ac2e5193240b71e201d2b9])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog270.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog270Test.java
> NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB
>
>
> Key: AMBARI-24513
> URL: https://issues.apache.org/jira/browse/AMBARI-24513
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB:
> {noformat}
> 2018-08-20 11:36:46,395 ERROR [main] SchemaUpgradeHelper:207 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.convertUserCreationTimeToLong(UpgradeCatalog270.java:595)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.upgradeUserTables(UpgradeCatalog270.java:342)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:318)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:970)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
> 2018-08-20 11:36:46,395 ERROR [main] SchemaUpgradeHelper:473 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:208)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.convertUserCreationTimeToLong(UpgradeCatalog270.java:595)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.upgradeUserTables(UpgradeCatalog270.java:342)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:318)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:970)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
> ... 1 more
> {noformat}
> *Cause*
> This is caused by one or more records with a {{NULL}} value in the
> {{create_time}} field.
> For example:
> ||user_id||user_name||user_type||create_time||
> |1|admin|LOCAL|NULL|
> *Workaround*
> Update the relevant records to not have a {{NULL}} in the {{create_time}}
> column.
> For example:
> {noformat}
> UPDATE users SET create_time=systimestamp WHERE create_time IS NULL;
> {noformat}
> *Solution*
> During upgrade, protect against a {{null}} value for
> {{currentUserCreateTime.getValue()}} at:
> {code:java|title=org/apache/ambari/server/upgrade/UpgradeCatalog270.java:595}
> dbAccessor.updateTable(USERS_TABLE, temporaryColumnName,
> currentUserCreateTime.getValue().getTime(),
> "WHERE " + USERS_USER_ID_COLUMN + "=" +
> currentUserCreateTime.getKey());
> {code}
> If {{currentUserCreateTime.getValue()}} is null, the current timestamp should
> be used.
> *Note:* This may be a reoccurring issue since there is no provision to ensure
> that {{create_time}} is not {{NULL}} when initializing the Ambari database:
> {code:java}
> insert into users(user_id, principal_id, user_name, user_password)
> select
> 1,1,'admin','538916f8943ec225d97a9a86a2c6ec0818c1cd400e09e03b660fdaaec4af29ddbb6f2b1033b81b00'
> from dual;{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24513) NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB
[
https://issues.apache.org/jira/browse/AMBARI-24513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587447#comment-16587447
]
Hudson commented on AMBARI-24513:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #192 (See
[https://builds.apache.org/job/Ambari-branch-2.7/192/])
AMBARI-24513. Using current timestamp as created_time in case there is
(oleewere:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=542475f62c1a77997fe38dcc7f5d404891b198e3])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog270.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog270Test.java
> NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB
>
>
> Key: AMBARI-24513
> URL: https://issues.apache.org/jira/browse/AMBARI-24513
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB:
> {noformat}
> 2018-08-20 11:36:46,395 ERROR [main] SchemaUpgradeHelper:207 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.convertUserCreationTimeToLong(UpgradeCatalog270.java:595)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.upgradeUserTables(UpgradeCatalog270.java:342)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:318)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:970)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
> 2018-08-20 11:36:46,395 ERROR [main] SchemaUpgradeHelper:473 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:208)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.convertUserCreationTimeToLong(UpgradeCatalog270.java:595)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.upgradeUserTables(UpgradeCatalog270.java:342)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:318)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:970)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
> ... 1 more
> {noformat}
> *Cause*
> This is caused by one or more records with a {{NULL}} value in the
> {{create_time}} field.
> For example:
> ||user_id||user_name||user_type||create_time||
> |1|admin|LOCAL|NULL|
> *Workaround*
> Update the relevant records to not have a {{NULL}} in the {{create_time}}
> column.
> For example:
> {noformat}
> UPDATE users SET create_time=systimestamp WHERE create_time IS NULL;
> {noformat}
> *Solution*
> During upgrade, protect against a {{null}} value for
> {{currentUserCreateTime.getValue()}} at:
> {code:java|title=org/apache/ambari/server/upgrade/UpgradeCatalog270.java:595}
> dbAccessor.updateTable(USERS_TABLE, temporaryColumnName,
> currentUserCreateTime.getValue().getTime(),
> "WHERE " + USERS_USER_ID_COLUMN + "=" +
> currentUserCreateTime.getKey());
> {code}
> If {{currentUserCreateTime.getValue()}} is null, the current timestamp should
> be used.
> *Note:* This may be a reoccurring issue since there is no provision to ensure
> that {{create_time}} is not {{NULL}} when initializing the Ambari database:
> {code:java}
> insert into users(user_id, principal_id, user_name, user_password)
> select
> 1,1,'admin','538916f8943ec225d97a9a86a2c6ec0818c1cd400e09e03b660fdaaec4af29ddbb6f2b1033b81b00'
> from dual;{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24513) NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB
[
https://issues.apache.org/jira/browse/AMBARI-24513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-24513.
---
Resolution: Fixed
> NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB
>
>
> Key: AMBARI-24513
> URL: https://issues.apache.org/jira/browse/AMBARI-24513
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB:
> {noformat}
> 2018-08-20 11:36:46,395 ERROR [main] SchemaUpgradeHelper:207 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.convertUserCreationTimeToLong(UpgradeCatalog270.java:595)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.upgradeUserTables(UpgradeCatalog270.java:342)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:318)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:970)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
> 2018-08-20 11:36:46,395 ERROR [main] SchemaUpgradeHelper:473 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:208)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.convertUserCreationTimeToLong(UpgradeCatalog270.java:595)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.upgradeUserTables(UpgradeCatalog270.java:342)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:318)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:970)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
> ... 1 more
> {noformat}
> *Cause*
> This is caused by one or more records with a {{NULL}} value in the
> {{create_time}} field.
> For example:
> ||user_id||user_name||user_type||create_time||
> |1|admin|LOCAL|NULL|
> *Workaround*
> Update the relevant records to not have a {{NULL}} in the {{create_time}}
> column.
> For example:
> {noformat}
> UPDATE users SET create_time=systimestamp WHERE create_time IS NULL;
> {noformat}
> *Solution*
> During upgrade, protect against a {{null}} value for
> {{currentUserCreateTime.getValue()}} at:
> {code:java|title=org/apache/ambari/server/upgrade/UpgradeCatalog270.java:595}
> dbAccessor.updateTable(USERS_TABLE, temporaryColumnName,
> currentUserCreateTime.getValue().getTime(),
> "WHERE " + USERS_USER_ID_COLUMN + "=" +
> currentUserCreateTime.getKey());
> {code}
> If {{currentUserCreateTime.getValue()}} is null, the current timestamp should
> be used.
> *Note:* This may be a reoccurring issue since there is no provision to ensure
> that {{create_time}} is not {{NULL}} when initializing the Ambari database:
> {code:java}
> insert into users(user_id, principal_id, user_name, user_password)
> select
> 1,1,'admin','538916f8943ec225d97a9a86a2c6ec0818c1cd400e09e03b660fdaaec4af29ddbb6f2b1033b81b00'
> from dual;{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24515) Remove dependency on JQuery 1.8.0 for Ambari Server UI
[
https://issues.apache.org/jira/browse/AMBARI-24515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587392#comment-16587392
]
Hudson commented on AMBARI-24515:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9875 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9875/])
AMBARI-24515 Remove dependency on JQuery 1.8.0 for Ambari Server UI
(1963907+atkach:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=719595427f10579e994f242b888035e9e36ce49d])
* (edit) ambari-web/api-docs/index.html
* (add) ambari-web/api-docs/lib/jquery-1.8.3.min.js
* (delete) ambari-web/api-docs/lib/jquery-1.8.0.min.js
> Remove dependency on JQuery 1.8.0 for Ambari Server UI
> --
>
> Key: AMBARI-24515
> URL: https://issues.apache.org/jira/browse/AMBARI-24515
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Remove dependency on JQuery 1.8.0 for Ambari Server UI due to security
> concerns. See
> * CVE-2012-6708 - https://nvd.nist.gov/vuln/detail/CVE-2012-6708
> * CVE-2011-4969 - https://nvd.nist.gov/vuln/detail/CVE-2011-4969
> * CVE-2015-9251 - https://nvd.nist.gov/vuln/detail/CVE-2015-9251
> It is recommended that JQuery is updated to 1.8.3+1
> Path to offending file:
> {noformat}
> ambari
> |- ambari-server-2.7.1.0-119.x86_64.rpm
> | |- usr
> | | |- lib
> | | | |- ambari-server
> | | | | |- web
> | | | | | |- api-docs
> | | | | | | |- lib
> | | | | | | | |- jquery-1.8.0.min.js
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24515) Remove dependency on JQuery 1.8.0 for Ambari Server UI
[
https://issues.apache.org/jira/browse/AMBARI-24515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587377#comment-16587377
]
Hudson commented on AMBARI-24515:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #191 (See
[https://builds.apache.org/job/Ambari-branch-2.7/191/])
AMBARI-24515 Remove dependency on JQuery 1.8.0 for Ambari Server UI
(1963907+atkach:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=5dfc47b7c3b836a8ed646dde126cadd5a9bf9636])
* (edit) ambari-web/api-docs/index.html
* (add) ambari-web/api-docs/lib/jquery-1.8.3.min.js
* (delete) ambari-web/api-docs/lib/jquery-1.8.0.min.js
> Remove dependency on JQuery 1.8.0 for Ambari Server UI
> --
>
> Key: AMBARI-24515
> URL: https://issues.apache.org/jira/browse/AMBARI-24515
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Remove dependency on JQuery 1.8.0 for Ambari Server UI due to security
> concerns. See
> * CVE-2012-6708 - https://nvd.nist.gov/vuln/detail/CVE-2012-6708
> * CVE-2011-4969 - https://nvd.nist.gov/vuln/detail/CVE-2011-4969
> * CVE-2015-9251 - https://nvd.nist.gov/vuln/detail/CVE-2015-9251
> It is recommended that JQuery is updated to 1.8.3+1
> Path to offending file:
> {noformat}
> ambari
> |- ambari-server-2.7.1.0-119.x86_64.rpm
> | |- usr
> | | |- lib
> | | | |- ambari-server
> | | | | |- web
> | | | | | |- api-docs
> | | | | | | |- lib
> | | | | | | | |- jquery-1.8.0.min.js
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24515) Remove dependency on JQuery 1.8.0 for Ambari Server UI
[
https://issues.apache.org/jira/browse/AMBARI-24515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587339#comment-16587339
]
Andrii Tkach commented on AMBARI-24515:
---
committed to trunk and branch-2.7
> Remove dependency on JQuery 1.8.0 for Ambari Server UI
> --
>
> Key: AMBARI-24515
> URL: https://issues.apache.org/jira/browse/AMBARI-24515
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Remove dependency on JQuery 1.8.0 for Ambari Server UI due to security
> concerns. See
> * CVE-2012-6708 - https://nvd.nist.gov/vuln/detail/CVE-2012-6708
> * CVE-2011-4969 - https://nvd.nist.gov/vuln/detail/CVE-2011-4969
> * CVE-2015-9251 - https://nvd.nist.gov/vuln/detail/CVE-2015-9251
> It is recommended that JQuery is updated to 1.8.3+1
> Path to offending file:
> {noformat}
> ambari
> |- ambari-server-2.7.1.0-119.x86_64.rpm
> | |- usr
> | | |- lib
> | | | |- ambari-server
> | | | | |- web
> | | | | | |- api-docs
> | | | | | | |- lib
> | | | | | | | |- jquery-1.8.0.min.js
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24515) Remove dependency on JQuery 1.8.0 for Ambari Server UI
[
https://issues.apache.org/jira/browse/AMBARI-24515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach resolved AMBARI-24515.
---
Resolution: Fixed
> Remove dependency on JQuery 1.8.0 for Ambari Server UI
> --
>
> Key: AMBARI-24515
> URL: https://issues.apache.org/jira/browse/AMBARI-24515
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Remove dependency on JQuery 1.8.0 for Ambari Server UI due to security
> concerns. See
> * CVE-2012-6708 - https://nvd.nist.gov/vuln/detail/CVE-2012-6708
> * CVE-2011-4969 - https://nvd.nist.gov/vuln/detail/CVE-2011-4969
> * CVE-2015-9251 - https://nvd.nist.gov/vuln/detail/CVE-2015-9251
> It is recommended that JQuery is updated to 1.8.3+1
> Path to offending file:
> {noformat}
> ambari
> |- ambari-server-2.7.1.0-119.x86_64.rpm
> | |- usr
> | | |- lib
> | | | |- ambari-server
> | | | | |- web
> | | | | | |- api-docs
> | | | | | | |- lib
> | | | | | | | |- jquery-1.8.0.min.js
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24517) Cover add standby step 4 controller
[ https://issues.apache.org/jira/browse/AMBARI-24517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24517: Labels: pull-request-available (was: ) > Cover add standby step 4 controller > --- > > Key: AMBARI-24517 > URL: https://issues.apache.org/jira/browse/AMBARI-24517 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24517) Cover add standby step 4 controller
Antonenko Alexander created AMBARI-24517: Summary: Cover add standby step 4 controller Key: AMBARI-24517 URL: https://issues.apache.org/jira/browse/AMBARI-24517 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Antonenko Alexander -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24517) Cover add standby step 4 controller
[ https://issues.apache.org/jira/browse/AMBARI-24517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-24517: Assignee: Antonenko Alexander > Cover add standby step 4 controller > --- > > Key: AMBARI-24517 > URL: https://issues.apache.org/jira/browse/AMBARI-24517 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24435) [Log Search UI] Remove underline text decoration from dropdowns on hover
[ https://issues.apache.org/jira/browse/AMBARI-24435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24435: --- Status: Patch Available (was: In Progress) > [Log Search UI] Remove underline text decoration from dropdowns on hover > > > Key: AMBARI-24435 > URL: https://issues.apache.org/jira/browse/AMBARI-24435 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Original Estimate: 2h > Time Spent: 20m > Remaining Estimate: 1h 40m > > The dropdown buttons have underline text decoration on mouse hover, it should > be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24507) Remove dependency on org.bouncycastle bcprov-jdk15on before version 1.6.0 for Ambari Server
[
https://issues.apache.org/jira/browse/AMBARI-24507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587263#comment-16587263
]
Hudson commented on AMBARI-24507:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #190 (See
[https://builds.apache.org/job/Ambari-branch-2.7/190/])
[AMBARI-24507] Remove dependency on org.bouncycastle bcprov-jdk15on (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=9ffd67ff3b39a8d4bdeb9a9428ae7196a3fffd48])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/ldap/service/ads/DefaultLdapConfigurationService.java
* (delete)
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderBaseTest.java
* (delete)
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderForDuplicateUserTest.java
* (delete)
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderForDNWithSpaceTest.java
* (edit) ambari-server/pom.xml
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/ldap/service/ads/detectors/GroupMemberAttrDetectorTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderTest.java
> Remove dependency on org.bouncycastle bcprov-jdk15on before version 1.6.0 for
> Ambari Server
> ---
>
> Key: AMBARI-24507
> URL: https://issues.apache.org/jira/browse/AMBARI-24507
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Remove dependency on org.bouncycastle bcprov-jdk15on before version 1.6.0 for
> Ambari Server security concerns. See
> * CVE-2018-1000180 - https://nvd.nist.gov/vuln/detail/CVE-2018-1000180
> This dependency is compiled into the apacheds-all.jar from
> {code}
>
> org.apache.directory.server
> apacheds-all
> 2.0.0-M24
>
> {code}
> The relevant parts of this need to be broken out and the offending bouncy
> castle JAR needs to be excluded as needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24435) [Log Search UI] Remove underline text decoration from dropdowns on hover
[ https://issues.apache.org/jira/browse/AMBARI-24435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24435: Labels: pull-request-available (was: ) > [Log Search UI] Remove underline text decoration from dropdowns on hover > > > Key: AMBARI-24435 > URL: https://issues.apache.org/jira/browse/AMBARI-24435 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Original Estimate: 2h > Remaining Estimate: 2h > > The dropdown buttons have underline text decoration on mouse hover, it should > be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24516) Default value for LDAP type
[ https://issues.apache.org/jira/browse/AMBARI-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587224#comment-16587224 ] Olivér Szabó commented on AMBARI-24516: --- moving it out to 2.7.2 > Default value for LDAP type > --- > > Key: AMBARI-24516 > URL: https://issues.apache.org/jira/browse/AMBARI-24516 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.2 > > > 1. Set default value for ldap type 'Generic' > 2. command line option for configuring the ldap type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24516) Default value for LDAP type
[ https://issues.apache.org/jira/browse/AMBARI-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24516: -- Fix Version/s: (was: 2.7.1) 2.7.2 > Default value for LDAP type > --- > > Key: AMBARI-24516 > URL: https://issues.apache.org/jira/browse/AMBARI-24516 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.2 > > > 1. Set default value for ldap type 'Generic' > 2. command line option for configuring the ldap type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24514) conf-select/stack-select operations can yield incorrect result with parallel_execution=1
[ https://issues.apache.org/jira/browse/AMBARI-24514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587219#comment-16587219 ] Hudson commented on AMBARI-24514: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9873 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9873/]) AMBARI-24514. conf-select/stack-select operations can yield incorrect (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=9491f1fd0232597c2e400b6b73ba1afb2dea50cc]) * (edit) ambari-common/src/main/python/resource_management/libraries/script/script.py * (edit) ambari-server/src/main/resources/stack-hooks/after-INSTALL/scripts/params.py > conf-select/stack-select operations can yield incorrect result with > parallel_execution=1 > > > Key: AMBARI-24514 > URL: https://issues.apache.org/jira/browse/AMBARI-24514 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24514.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24514) conf-select/stack-select operations can yield incorrect result with parallel_execution=1
[ https://issues.apache.org/jira/browse/AMBARI-24514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587216#comment-16587216 ] Hudson commented on AMBARI-24514: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #189 (See [https://builds.apache.org/job/Ambari-branch-2.7/189/]) AMBARI-24514. conf-select/stack-select operations can yield incorrect (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=8b5cc45c0f626b04be66c83c3a045002d603b52c]) * (edit) ambari-server/src/main/resources/stack-hooks/after-INSTALL/scripts/params.py * (edit) ambari-common/src/main/python/resource_management/libraries/script/script.py > conf-select/stack-select operations can yield incorrect result with > parallel_execution=1 > > > Key: AMBARI-24514 > URL: https://issues.apache.org/jira/browse/AMBARI-24514 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24514.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24514) conf-select/stack-select operations can yield incorrect result with parallel_execution=1
[ https://issues.apache.org/jira/browse/AMBARI-24514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24514: -- Resolution: Fixed Status: Resolved (was: Patch Available) > conf-select/stack-select operations can yield incorrect result with > parallel_execution=1 > > > Key: AMBARI-24514 > URL: https://issues.apache.org/jira/browse/AMBARI-24514 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24514.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24507) Remove dependency on org.bouncycastle bcprov-jdk15on before version 1.6.0 for Ambari Server
[
https://issues.apache.org/jira/browse/AMBARI-24507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24507:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove dependency on org.bouncycastle bcprov-jdk15on before version 1.6.0 for
> Ambari Server
> ---
>
> Key: AMBARI-24507
> URL: https://issues.apache.org/jira/browse/AMBARI-24507
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Remove dependency on org.bouncycastle bcprov-jdk15on before version 1.6.0 for
> Ambari Server security concerns. See
> * CVE-2018-1000180 - https://nvd.nist.gov/vuln/detail/CVE-2018-1000180
> This dependency is compiled into the apacheds-all.jar from
> {code}
>
> org.apache.directory.server
> apacheds-all
> 2.0.0-M24
>
> {code}
> The relevant parts of this need to be broken out and the offending bouncy
> castle JAR needs to be excluded as needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24513) NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB
[
https://issues.apache.org/jira/browse/AMBARI-24513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24513:
Labels: pull-request-available (was: )
> NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB
>
>
> Key: AMBARI-24513
> URL: https://issues.apache.org/jira/browse/AMBARI-24513
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB:
> {noformat}
> 2018-08-20 11:36:46,395 ERROR [main] SchemaUpgradeHelper:207 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.convertUserCreationTimeToLong(UpgradeCatalog270.java:595)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.upgradeUserTables(UpgradeCatalog270.java:342)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:318)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:970)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
> 2018-08-20 11:36:46,395 ERROR [main] SchemaUpgradeHelper:473 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:208)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.convertUserCreationTimeToLong(UpgradeCatalog270.java:595)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.upgradeUserTables(UpgradeCatalog270.java:342)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:318)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:970)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
> ... 1 more
> {noformat}
> *Cause*
> This is caused by one or more records with a {{NULL}} value in the
> {{create_time}} field.
> For example:
> ||user_id||user_name||user_type||create_time||
> |1|admin|LOCAL|NULL|
> *Workaround*
> Update the relevant records to not have a {{NULL}} in the {{create_time}}
> column.
> For example:
> {noformat}
> UPDATE users SET create_time=systimestamp WHERE create_time IS NULL;
> {noformat}
> *Solution*
> During upgrade, protect against a {{null}} value for
> {{currentUserCreateTime.getValue()}} at:
> {code:java|title=org/apache/ambari/server/upgrade/UpgradeCatalog270.java:595}
> dbAccessor.updateTable(USERS_TABLE, temporaryColumnName,
> currentUserCreateTime.getValue().getTime(),
> "WHERE " + USERS_USER_ID_COLUMN + "=" +
> currentUserCreateTime.getKey());
> {code}
> If {{currentUserCreateTime.getValue()}} is null, the current timestamp should
> be used.
> *Note:* This may be a reoccurring issue since there is no provision to ensure
> that {{create_time}} is not {{NULL}} when initializing the Ambari database:
> {code:java}
> insert into users(user_id, principal_id, user_name, user_password)
> select
> 1,1,'admin','538916f8943ec225d97a9a86a2c6ec0818c1cd400e09e03b660fdaaec4af29ddbb6f2b1033b81b00'
> from dual;{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24516) Default value for LDAP type
Krisztian Kasa created AMBARI-24516: --- Summary: Default value for LDAP type Key: AMBARI-24516 URL: https://issues.apache.org/jira/browse/AMBARI-24516 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.1 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 2.7.1 1. Set default value for ldap type 'Generic' 2. command line option for configuring the ldap type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24515) Remove dependency on JQuery 1.8.0 for Ambari Server UI
[
https://issues.apache.org/jira/browse/AMBARI-24515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24515:
Labels: pull-request-available (was: )
> Remove dependency on JQuery 1.8.0 for Ambari Server UI
> --
>
> Key: AMBARI-24515
> URL: https://issues.apache.org/jira/browse/AMBARI-24515
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> Remove dependency on JQuery 1.8.0 for Ambari Server UI due to security
> concerns. See
> * CVE-2012-6708 - https://nvd.nist.gov/vuln/detail/CVE-2012-6708
> * CVE-2011-4969 - https://nvd.nist.gov/vuln/detail/CVE-2011-4969
> * CVE-2015-9251 - https://nvd.nist.gov/vuln/detail/CVE-2015-9251
> It is recommended that JQuery is updated to 1.8.3+1
> Path to offending file:
> {noformat}
> ambari
> |- ambari-server-2.7.1.0-119.x86_64.rpm
> | |- usr
> | | |- lib
> | | | |- ambari-server
> | | | | |- web
> | | | | | |- api-docs
> | | | | | | |- lib
> | | | | | | | |- jquery-1.8.0.min.js
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24515) Remove dependency on JQuery 1.8.0 for Ambari Server UI
Andrii Tkach created AMBARI-24515:
-
Summary: Remove dependency on JQuery 1.8.0 for Ambari Server UI
Key: AMBARI-24515
URL: https://issues.apache.org/jira/browse/AMBARI-24515
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.1
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Fix For: 2.7.1
Remove dependency on JQuery 1.8.0 for Ambari Server UI due to security
concerns. See
* CVE-2012-6708 - https://nvd.nist.gov/vuln/detail/CVE-2012-6708
* CVE-2011-4969 - https://nvd.nist.gov/vuln/detail/CVE-2011-4969
* CVE-2015-9251 - https://nvd.nist.gov/vuln/detail/CVE-2015-9251
It is recommended that JQuery is updated to 1.8.3+1
Path to offending file:
{noformat}
ambari
|- ambari-server-2.7.1.0-119.x86_64.rpm
| |- usr
| | |- lib
| | | |- ambari-server
| | | | |- web
| | | | | |- api-docs
| | | | | | |- lib
| | | | | | | |- jquery-1.8.0.min.js
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23903) Ambari: Add-jdeb-support
[ https://issues.apache.org/jira/browse/AMBARI-23903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587136#comment-16587136 ] Hudson commented on AMBARI-23903: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9872 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9872/]) AMBARI-23903: Add jdeb support (#1642) (jayush: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=dfaaf33a9e8d01390a7ecefd5b14ea740f5ee6e7]) * (edit) ambari-metrics/ambari-metrics-host-aggregator/pom.xml * (edit) ambari-infra/pom.xml * (edit) ambari-logsearch/pom.xml * (edit) ambari-funtest/pom.xml * (edit) ambari-metrics/ambari-metrics-grafana/pom.xml > Ambari: Add-jdeb-support > > > Key: AMBARI-23903 > URL: https://issues.apache.org/jira/browse/AMBARI-23903 > Project: Ambari > Issue Type: Improvement > Components: test >Affects Versions: trunk, 2.5.2, 2.6.0, 2.7.0 >Reporter: Naresh Bhat >Priority: Major > Fix For: trunk, 3.0.0, 2.7.1 > > > utility needs tobe added jdeb support. The patch will help to generate > debian package for utility. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24514) conf-select/stack-select operations can yield incorrect result with parallel_execution=1
[ https://issues.apache.org/jira/browse/AMBARI-24514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24514: Labels: pull-request-available (was: ) > conf-select/stack-select operations can yield incorrect result with > parallel_execution=1 > > > Key: AMBARI-24514 > URL: https://issues.apache.org/jira/browse/AMBARI-24514 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24514.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24514) conf-select/stack-select operations can yield incorrect result with parallel_execution=1
Andrew Onischuk created AMBARI-24514: Summary: conf-select/stack-select operations can yield incorrect result with parallel_execution=1 Key: AMBARI-24514 URL: https://issues.apache.org/jira/browse/AMBARI-24514 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.1 Attachments: AMBARI-24514.patch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24514) conf-select/stack-select operations can yield incorrect result with parallel_execution=1
[ https://issues.apache.org/jira/browse/AMBARI-24514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24514: - Status: Patch Available (was: Open) > conf-select/stack-select operations can yield incorrect result with > parallel_execution=1 > > > Key: AMBARI-24514 > URL: https://issues.apache.org/jira/browse/AMBARI-24514 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24514.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24514) conf-select/stack-select operations can yield incorrect result with parallel_execution=1
[ https://issues.apache.org/jira/browse/AMBARI-24514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24514: - Attachment: AMBARI-24514.patch > conf-select/stack-select operations can yield incorrect result with > parallel_execution=1 > > > Key: AMBARI-24514 > URL: https://issues.apache.org/jira/browse/AMBARI-24514 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24514.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24513) NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB
Sandor Molnar created AMBARI-24513:
--
Summary: NPE when migrating users table during upgrade to Ambari
2.7.0 with Oracle DB
Key: AMBARI-24513
URL: https://issues.apache.org/jira/browse/AMBARI-24513
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.7.1
NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB:
{noformat}
2018-08-20 11:36:46,395 ERROR [main] SchemaUpgradeHelper:207 - Upgrade failed.
java.lang.NullPointerException
at
org.apache.ambari.server.upgrade.UpgradeCatalog270.convertUserCreationTimeToLong(UpgradeCatalog270.java:595)
at
org.apache.ambari.server.upgrade.UpgradeCatalog270.upgradeUserTables(UpgradeCatalog270.java:342)
at
org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:318)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:970)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
2018-08-20 11:36:46,395 ERROR [main] SchemaUpgradeHelper:473 - Exception
occurred during upgrade, failed
org.apache.ambari.server.AmbariException
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:208)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
Caused by: java.lang.NullPointerException
at
org.apache.ambari.server.upgrade.UpgradeCatalog270.convertUserCreationTimeToLong(UpgradeCatalog270.java:595)
at
org.apache.ambari.server.upgrade.UpgradeCatalog270.upgradeUserTables(UpgradeCatalog270.java:342)
at
org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:318)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:970)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
... 1 more
{noformat}
*Cause*
This is caused by one or more records with a {{NULL}} value in the
{{create_time}} field.
For example:
||user_id||user_name||user_type||create_time||
|1|admin|LOCAL|NULL|
*Workaround*
Update the relevant records to not have a {{NULL}} in the {{create_time}}
column.
For example:
{noformat}
UPDATE users SET create_time=systimestamp WHERE create_time IS NULL;
{noformat}
*Solution*
During upgrade, protect against a {{null}} value for
{{currentUserCreateTime.getValue()}} at:
{code:java|title=org/apache/ambari/server/upgrade/UpgradeCatalog270.java:595}
dbAccessor.updateTable(USERS_TABLE, temporaryColumnName,
currentUserCreateTime.getValue().getTime(),
"WHERE " + USERS_USER_ID_COLUMN + "=" +
currentUserCreateTime.getKey());
{code}
If {{currentUserCreateTime.getValue()}} is null, the current timestamp should
be used.
*Note:* This may be a reoccurring issue since there is no provision to ensure
that {{create_time}} is not {{NULL}} when initializing the Ambari database:
{code:java}
insert into users(user_id, principal_id, user_name, user_password)
select
1,1,'admin','538916f8943ec225d97a9a86a2c6ec0818c1cd400e09e03b660fdaaec4af29ddbb6f2b1033b81b00'
from dual;{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24511) CLONE - Ambari: Add rpm support
[ https://issues.apache.org/jira/browse/AMBARI-24511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587107#comment-16587107 ] Naresh Bhat commented on AMBARI-24511: -- Thank you very much [~jluniya] the trunk branch pull request is here [https://github.com/apache/ambari/pull/2125] > CLONE - Ambari: Add rpm support > --- > > Key: AMBARI-24511 > URL: https://issues.apache.org/jira/browse/AMBARI-24511 > Project: Ambari > Issue Type: Improvement > Components: test >Affects Versions: 2.7.0 > Environment: The Ambari rpm is build and tested on AArch64 machine > with CentOS Linux release 7.4.1708. >Reporter: Naresh Bhat >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The Ambari infra and logsearch packages are missing rpm support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24407) Ambari: Add rpm support
[ https://issues.apache.org/jira/browse/AMBARI-24407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587100#comment-16587100 ] Naresh Bhat commented on AMBARI-24407: -- ok sure. I will use AMBARI-24511 sorry for noise. > Ambari: Add rpm support > --- > > Key: AMBARI-24407 > URL: https://issues.apache.org/jira/browse/AMBARI-24407 > Project: Ambari > Issue Type: Improvement > Components: test >Affects Versions: 2.7.0 > Environment: The Ambari rpm is build and tested on AArch64 machine > with CentOS Linux release 7.4.1708. >Reporter: Naresh Bhat >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: 0001-ambari-Add-rpm-support.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > > The Ambari infra and logsearch packages are missing rpm support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24407) Ambari: Add rpm support
[ https://issues.apache.org/jira/browse/AMBARI-24407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587094#comment-16587094 ] Naresh Bhat commented on AMBARI-24407: -- [~jluniya] pull request for trunk [https://github.com/apache/ambari/pull/2124] Thank you very much. > Ambari: Add rpm support > --- > > Key: AMBARI-24407 > URL: https://issues.apache.org/jira/browse/AMBARI-24407 > Project: Ambari > Issue Type: Improvement > Components: test >Affects Versions: 2.7.0 > Environment: The Ambari rpm is build and tested on AArch64 machine > with CentOS Linux release 7.4.1708. >Reporter: Naresh Bhat >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: 0001-ambari-Add-rpm-support.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > > The Ambari infra and logsearch packages are missing rpm support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24512) CLONE - WebHdfs calls being made from containers to NameNode hosted on bare metal host fails
[ https://issues.apache.org/jira/browse/AMBARI-24512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24512: --- Fix Version/s: (was: 2.7.1) 3.0.0 > CLONE - WebHdfs calls being made from containers to NameNode hosted on bare > metal host fails > > > Key: AMBARI-24512 > URL: https://issues.apache.org/jira/browse/AMBARI-24512 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24454) WebHdfs calls being made from containers to NameNode hosted on bare metal host fails
[ https://issues.apache.org/jira/browse/AMBARI-24454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587088#comment-16587088 ] Jayush Luniya commented on AMBARI-24454: [~jaimin] Please use AMBARI-24512 to commit to trunk. Closing this 2.7.1 JIRA for now. > WebHdfs calls being made from containers to NameNode hosted on bare metal > host fails > > > Key: AMBARI-24454 > URL: https://issues.apache.org/jira/browse/AMBARI-24454 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24454) WebHdfs calls being made from containers to NameNode hosted on bare metal host fails
[ https://issues.apache.org/jira/browse/AMBARI-24454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-24454. Resolution: Fixed > WebHdfs calls being made from containers to NameNode hosted on bare metal > host fails > > > Key: AMBARI-24454 > URL: https://issues.apache.org/jira/browse/AMBARI-24454 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24512) CLONE - WebHdfs calls being made from containers to NameNode hosted on bare metal host fails
Jayush Luniya created AMBARI-24512: -- Summary: CLONE - WebHdfs calls being made from containers to NameNode hosted on bare metal host fails Key: AMBARI-24512 URL: https://issues.apache.org/jira/browse/AMBARI-24512 Project: Ambari Issue Type: Bug Components: ambari-agent Reporter: Jaimin Jetly Assignee: Jaimin Jetly Fix For: 2.7.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23903) Ambari: Add-jdeb-support
[ https://issues.apache.org/jira/browse/AMBARI-23903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-23903. Resolution: Fixed > Ambari: Add-jdeb-support > > > Key: AMBARI-23903 > URL: https://issues.apache.org/jira/browse/AMBARI-23903 > Project: Ambari > Issue Type: Improvement > Components: test >Affects Versions: trunk, 2.5.2, 2.6.0, 2.7.0 >Reporter: Naresh Bhat >Priority: Major > Fix For: trunk, 3.0.0, 2.7.1 > > > utility needs tobe added jdeb support. The patch will help to generate > debian package for utility. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24407) Ambari: Add rpm support
[ https://issues.apache.org/jira/browse/AMBARI-24407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-24407. Resolution: Fixed > Ambari: Add rpm support > --- > > Key: AMBARI-24407 > URL: https://issues.apache.org/jira/browse/AMBARI-24407 > Project: Ambari > Issue Type: Improvement > Components: test >Affects Versions: 2.7.0 > Environment: The Ambari rpm is build and tested on AArch64 machine > with CentOS Linux release 7.4.1708. >Reporter: Naresh Bhat >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: 0001-ambari-Add-rpm-support.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > The Ambari infra and logsearch packages are missing rpm support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24407) Ambari: Add rpm support
[ https://issues.apache.org/jira/browse/AMBARI-24407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587085#comment-16587085 ] Jayush Luniya commented on AMBARI-24407: [~nbhat] please use AMBARI-24511 for the fix for trunk. Closing this JIRA as we are going to start the release process for 2.7.1 soon. > Ambari: Add rpm support > --- > > Key: AMBARI-24407 > URL: https://issues.apache.org/jira/browse/AMBARI-24407 > Project: Ambari > Issue Type: Improvement > Components: test >Affects Versions: 2.7.0 > Environment: The Ambari rpm is build and tested on AArch64 machine > with CentOS Linux release 7.4.1708. >Reporter: Naresh Bhat >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: 0001-ambari-Add-rpm-support.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > The Ambari infra and logsearch packages are missing rpm support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24511) CLONE - Ambari: Add rpm support
Jayush Luniya created AMBARI-24511: -- Summary: CLONE - Ambari: Add rpm support Key: AMBARI-24511 URL: https://issues.apache.org/jira/browse/AMBARI-24511 Project: Ambari Issue Type: Improvement Components: test Affects Versions: 2.7.0 Environment: The Ambari rpm is build and tested on AArch64 machine with CentOS Linux release 7.4.1708. Reporter: Naresh Bhat Fix For: 2.7.1 The Ambari infra and logsearch packages are missing rpm support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24511) CLONE - Ambari: Add rpm support
[ https://issues.apache.org/jira/browse/AMBARI-24511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24511: --- Fix Version/s: (was: 2.7.1) 3.0.0 > CLONE - Ambari: Add rpm support > --- > > Key: AMBARI-24511 > URL: https://issues.apache.org/jira/browse/AMBARI-24511 > Project: Ambari > Issue Type: Improvement > Components: test >Affects Versions: 2.7.0 > Environment: The Ambari rpm is build and tested on AArch64 machine > with CentOS Linux release 7.4.1708. >Reporter: Naresh Bhat >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > The Ambari infra and logsearch packages are missing rpm support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24343) [LogSearch] Wrong (error) response format
[
https://issues.apache.org/jira/browse/AMBARI-24343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24343:
---
Fix Version/s: (was: 2.7.1)
2.7.2
> [LogSearch] Wrong (error) response format
> -
>
> Key: AMBARI-24343
> URL: https://issues.apache.org/jira/browse/AMBARI-24343
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.1
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When I call the
> {noformat}
> /shipper/input/\{clusterName}/services/\{serviceName}
> {noformat}
> api endpoint with wrong json schema the backend responses with plain text
> body instead of json or empty body.
> For example:
> {code:json}
> {
> "input": [
> {
> "type": "zookeeper",
> "rowtype": "service",
> "path": "/var/log/zookeeper/zookeeper*.log"
> }
> ],
> "filter": [
> {
> "filter": "grok",
> "conditions": {
> "fieldss": {
> "type": [
> "zookeeper"
> ]
> }
> },
> "skipOnError": false,
> "deepExtract": false,
> "post_map_values": {
> "logtime": [
> {
> "map_date": {
> "target_date_pattern": "-MM-dd HH:mm:ss,SSS"
> }
> }
> ]
> },
> "log4j_format": "%d\{ISO8601} - %-5p [%t:%C\{1}@%L] - %m%n",
> "multiline_pattern": "^(%\{TIMESTAMP_ISO8601:logtime})",
> "message_pattern":
> "(?m)^%\{TIMESTAMP_ISO8601:logtime}%\{SPACE}-%\{SPACE}%\{LOGLEVEL:level}%\{SPACE}\\[%\{DATA:thread_name}\\@%\{INT:line_number}\\]%\{SPACE}-%\{SPACE}%\{GREEDYDATA:log_message}"
> }
> ]
> }
> {code}
> Where the `fieldss` is not a valid JSON key.
> The response plain text body:
> {code:javascript}
> Unrecognized field "fieldss" (class
> org.apache.ambari.logsearch.model.common.LSServerConditions), not marked as
> ignorable (one known property: "fields"])
> at [Source: UNKNOWN; line: -1, column: -1] (through reference chain:
> org.apache.ambari.logsearch.model.common.LSServerInputConfig["filter"]->org.apache.ambari.logsearch.model.common.LSServerFilterGrok["conditions"]->org.apache.ambari.logsearch.model.common.LSServerConditions["fieldss"])
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24455) Spark service check failure after UI Deploy - non Secure with Ranger/KMS
[
https://issues.apache.org/jira/browse/AMBARI-24455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya resolved AMBARI-24455.
Resolution: Invalid
HDP-3.0 stack definition issue.
> Spark service check failure after UI Deploy - non Secure with Ranger/KMS
>
>
> Key: AMBARI-24455
> URL: https://issues.apache.org/jira/browse/AMBARI-24455
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Srikanth Janardhan
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: 2.7.1
>
>
> Spark Service check fails while UI Deploy:
> {code}
> stderr:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/service_check.py",
> line 78, in service_check
> Execute(cmd, user=params.smoke_user, path=[beeline_cmd],
> timeout=CHECK_COMMAND_TIMEOUT_DEFAULT)
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
> line 263, in action_run
> returns=self.resource.returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 314, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> ExecutionFailed: Execution of '! /usr/hdp/current/spark2-client/bin/beeline
> -u
> 'jdbc:hive2://ctr-e138-1518143905142-432870-01-04.hwx.site:10016/default'
> transportMode=binary -e '' 2>&1| awk '{print}'|grep -i -e 'Connection
> refused' -e 'Invalid URL' -e 'Error: Could not open'' returned 1.
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> Error: Could not open client transport with JDBC Uri:
> jdbc:hive2://ctr-e138-1518143905142-432870-01-04.hwx.site:10016/default:
> java.net.ConnectException: Connection refused (Connection refused)
> (state=08S01,code=0)
> Error: Could not open client transport with JDBC Uri:
> jdbc:hive2://ctr-e138-1518143905142-432870-01-04.hwx.site:10016/default:
> java.net.ConnectException: Connection refused (Connection refused)
> (state=08S01,code=0)
> The above exception was the cause of the following exception:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/service_check.py",
> line 88, in
> SparkServiceCheck().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/service_check.py",
> line 85, in service_check
> raise Fail("Connection to all Spark thrift servers servers failed")
> resource_management.core.exceptions.Fail: Connection to all Spark thrift
> servers servers failed
> stdout:
> 2018-08-10 05:22:29,576 - Using hadoop conf dir:
> /usr/hdp/3.0.1.0-73/hadoop/conf
> 2018-08-10 05:22:29,600 - Execute['curl -s -o /dev/null -w'%{http_code}'
> --negotiate -u: -k
> http://ctr-e138-1518143905142-432870-01-04.hwx.site:18081 | grep 200']
> {'logoutput': True, 'tries': 5, 'user': 'ambari-qa', 'try_sleep': 3}
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> 200
> 2018-08-10 05:22:29,794 - Execute['curl -s -o /dev/null -w'%{http_code}'
> --negotiate -u: -k
> http://ctr-e138-1518143905142-432870-01-04.hwx.site:8999/sessions | grep
> 200'] {'logoutput': True, 'tries': 3, 'user': 'ambari-qa', 'try_sleep': 1}
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> 200
> 2018-08-10 05:22:29,843 - Execute['!
> /usr/hdp/current/spark2-client/bin/beeline -u
> 'jdbc:hive2://ctr-e138-1518143905142-432870-01-04.hwx.site:10016/default'
> transportMode=binary -e '' 2>&1| awk '{print}'|grep -i -e 'Connection
> refused' -e 'Invalid URL' -e 'Error: Could not open''] {'path':
> [u'/usr/hdp/current/spark2
[jira] [Updated] (AMBARI-24192) WebSockets traffic does not work between Ambari Web UI and Ambari Server when it is accessed via Knox Proxy (UI side changes)
[ https://issues.apache.org/jira/browse/AMBARI-24192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24192: --- Fix Version/s: (was: 2.7.1) 2.7.0 > WebSockets traffic does not work between Ambari Web UI and Ambari Server when > it is accessed via Knox Proxy (UI side changes) > - > > Key: AMBARI-24192 > URL: https://issues.apache.org/jira/browse/AMBARI-24192 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > When connected via Knox proxy ambari server web socket URL should be changed > from ://: port>/api/stomp/v1/websocket to ://: port>/gateway/default/ambari/websocket -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24192) WebSockets traffic does not work between Ambari Web UI and Ambari Server when it is accessed via Knox Proxy (UI side changes)
[ https://issues.apache.org/jira/browse/AMBARI-24192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-24192. Resolution: Won't Fix Required changes are done via Knox AMBARIWS service configuration > WebSockets traffic does not work between Ambari Web UI and Ambari Server when > it is accessed via Knox Proxy (UI side changes) > - > > Key: AMBARI-24192 > URL: https://issues.apache.org/jira/browse/AMBARI-24192 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 20m > Remaining Estimate: 0h > > When connected via Knox proxy ambari server web socket URL should be changed > from ://: port>/api/stomp/v1/websocket to ://: port>/gateway/default/ambari/websocket -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23925) Zeppelin is not respecting the absolute hdfs path for notebooks
[ https://issues.apache.org/jira/browse/AMBARI-23925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-23925: --- Priority: Critical (was: Blocker) > Zeppelin is not respecting the absolute hdfs path for notebooks > --- > > Key: AMBARI-23925 > URL: https://issues.apache.org/jira/browse/AMBARI-23925 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.0 >Reporter: Supreeth Sharma >Assignee: Supreeth Sharma >Priority: Critical > Fix For: 2.7.2 > > > Zeppelin is not respecting the absolute hdfs path and picking up the > incorrect path for notebooks. > Even when user is setting 'zeppelin.notebook.dir' as > 'hdfs://ns2/zeppelin/tmp/tmp1/notebook', ambari is picking up the path as > /user/zeppelin/hdfs://ns2/zeppelin/tmp/tmp1/notebook > and due to this zeppelin service start is failing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23925) Zeppelin is not respecting the absolute hdfs path for notebooks
[ https://issues.apache.org/jira/browse/AMBARI-23925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-23925: --- Fix Version/s: (was: 2.7.1) 2.7.2 > Zeppelin is not respecting the absolute hdfs path for notebooks > --- > > Key: AMBARI-23925 > URL: https://issues.apache.org/jira/browse/AMBARI-23925 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.0 >Reporter: Supreeth Sharma >Assignee: Supreeth Sharma >Priority: Blocker > Fix For: 2.7.2 > > > Zeppelin is not respecting the absolute hdfs path and picking up the > incorrect path for notebooks. > Even when user is setting 'zeppelin.notebook.dir' as > 'hdfs://ns2/zeppelin/tmp/tmp1/notebook', ambari is picking up the path as > /user/zeppelin/hdfs://ns2/zeppelin/tmp/tmp1/notebook > and due to this zeppelin service start is failing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24118: --- Fix Version/s: (was: 2.7.1) 2.7.2 > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 2.7.2 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24507) Remove dependency on org.bouncycastle bcprov-jdk15on before version 1.6.0 for Ambari Server
[
https://issues.apache.org/jira/browse/AMBARI-24507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24507:
---
Priority: Blocker (was: Critical)
> Remove dependency on org.bouncycastle bcprov-jdk15on before version 1.6.0 for
> Ambari Server
> ---
>
> Key: AMBARI-24507
> URL: https://issues.apache.org/jira/browse/AMBARI-24507
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Remove dependency on org.bouncycastle bcprov-jdk15on before version 1.6.0 for
> Ambari Server security concerns. See
> * CVE-2018-1000180 - https://nvd.nist.gov/vuln/detail/CVE-2018-1000180
> This dependency is compiled into the apacheds-all.jar from
> {code}
>
> org.apache.directory.server
> apacheds-all
> 2.0.0-M24
>
> {code}
> The relevant parts of this need to be broken out and the offending bouncy
> castle JAR needs to be excluded as needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23817) Visualizing the Encrypted zones and Erasure coded zones in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-23817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-23817: --- Fix Version/s: (was: 2.7.1) 2.7.2 > Visualizing the Encrypted zones and Erasure coded zones in HDFS > --- > > Key: AMBARI-23817 > URL: https://issues.apache.org/jira/browse/AMBARI-23817 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-23817-trunk.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > > For hadoop 3.0 Files view should show whether a folder or file is Encrypted > or not and what Erasure coding policy is used for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24407) Ambari: Add rpm support
[ https://issues.apache.org/jira/browse/AMBARI-24407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587070#comment-16587070 ] Naresh Bhat commented on AMBARI-24407: -- My apologies. I think I forgot to give the pull request. I will double check and give it ASAP. > Ambari: Add rpm support > --- > > Key: AMBARI-24407 > URL: https://issues.apache.org/jira/browse/AMBARI-24407 > Project: Ambari > Issue Type: Improvement > Components: test >Affects Versions: 2.7.0 > Environment: The Ambari rpm is build and tested on AArch64 machine > with CentOS Linux release 7.4.1708. >Reporter: Naresh Bhat >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: 0001-ambari-Add-rpm-support.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > The Ambari infra and logsearch packages are missing rpm support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24466) Add README.md for Ambari project
[ https://issues.apache.org/jira/browse/AMBARI-24466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24466: --- Fix Version/s: (was: 2.7.1) 3.0.0 > Add README.md for Ambari project > > > Key: AMBARI-24466 > URL: https://issues.apache.org/jira/browse/AMBARI-24466 > Project: Ambari > Issue Type: Improvement >Reporter: Vivek Sharma >Assignee: Vivek Sharma >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Add README.md for Ambari project -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24457) Hiveserver2 can't connect to metastore when using OneFS
[
https://issues.apache.org/jira/browse/AMBARI-24457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya resolved AMBARI-24457.
Resolution: Fixed
> Hiveserver2 can't connect to metastore when using OneFS
> ---
>
> Key: AMBARI-24457
> URL: https://issues.apache.org/jira/browse/AMBARI-24457
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> {code}
> 2018-07-12T07:56:27,148 ERROR [pool-6-thread-3]: metastore.HiveMetaStore
> (HiveMetaStore.java:get_current_notificationEventId(7617)) - Not authorized
> to make the get_current_notificationEventId call. You can try to disable
> metastore.metastore.event.db.notification.api.auth
> org.apache.hadoop.hive.metastore.api.MetaException: User hive is not allowed
> to perform this API call
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.authorizeProxyPrivilege(HiveMetaStore.java:7655)
> ~[hive-exec-3.1.0.3.0.0.0-1628.jar:3.1.0.3.0.0.0-1628]
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.get_current_notificationEventId(HiveMetaStore.java:7615)
> [hive-exec-3.1.0.3.0.0.0-1628.jar:3.1.0.3.0.0.0-1628]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_112]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_112]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_112]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_112]
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:147)
> [hive-exec-3.1.0.3.0.0.0-1628.jar:3.1.0.3.0.0.0-1628]
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:108)
> [hive-exec-3.1.0.3.0.0.0-1628.jar:3.1.0.3.0.0.0-1628]
> at com.sun.proxy.$Proxy34.get_current_notificationEventId(Unknown
> Source) [?:?]
> at
> org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_current_notificationEventId.getResult(ThriftHiveMetastore.java:18364)
> [hive-exec-3.1.0.3.0.0.0-1628.jar:3.1.0.3.0.0.0-1628]
> at
> org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_current_notificationEventId.getResult(ThriftHiveMetastore.java:18349)
> [hive-exec-3.1.0.3.0.0.0-1628.jar:3.1.0.3.0.0.0-1628]
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
> [hive-exec-3.1.0.3.0.0.0-1628.jar:3.1.0.3.0.0.0-1628]
> at
> org.apache.hadoop.hive.metastore.TUGIBasedProcessor$1.run(TUGIBasedProcessor.java:111)
> [hive-exec-3.1.0.3.0.0.0-1628.jar:3.1.0.3.0.0.0-1628]
> at
> org.apache.hadoop.hive.metastore.TUGIBasedProcessor$1.run(TUGIBasedProcessor.java:107)
> [hive-exec-3.1.0.3.0.0.0-1628.jar:3.1.0.3.0.0.0-1628]
> at java.security.AccessController.doPrivileged(Native Method)
> [?:1.8.0_112]
> at javax.security.auth.Subject.doAs(Subject.java:422) [?:1.8.0_112]
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1688)
> [hadoop-common-3.1.0.3.0.0.0-1628.jar:?]
> at
> org.apache.hadoop.hive.metastore.TUGIBasedProcessor.process(TUGIBasedProcessor.java:119)
> [hive-exec-3.1.0.3.0.0.0-1628.jar:3.1.0.3.0.0.0-1628]
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
> [hive-exec-3.1.0.3.0.0.0-1628.jar:3.1.0.3.0.0.0-1628]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:1.8.0_112]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_112]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112]
> 2018-07-12T07:56:27,153 ERROR [pool-6-thread-3]: metastore.RetryingHMSHandler
> (RetryingHMSHandler.java:invokeInternal(201)) - org.apache.thrift.TException:
> MetaException(message:User hive is not allowed to perform this API call)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.get_current_notificationEventId(HiveMetaStore.java:7619)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInterna
[jira] [Assigned] (AMBARI-24458) Start operation is disabled for HDFS after stopping components for one namespace
[ https://issues.apache.org/jira/browse/AMBARI-24458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya reassigned AMBARI-24458: -- Assignee: Dmytro Sen > Start operation is disabled for HDFS after stopping components for one > namespace > > > Key: AMBARI-24458 > URL: https://issues.apache.org/jira/browse/AMBARI-24458 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 > Environment: ambari-server version: ambari-server-2.7.1.0-70.x86_64 > ambari-server --hash: f6d369619dc259e6ade537d6cdb3396f9e01c3dd >Reporter: Vivek Rathod >Assignee: Dmytro Sen >Priority: Major > Fix For: 2.7.2 > > Attachments: Screen Shot 2018-08-10 at 10.16.46 AM.png, Screen Shot > 2018-08-10 at 10.17.01 AM.png > > > Start operation is disabled for HDFS after stopping components for one > namespace > > STR: > 1) On hdfs service page, stop components for one namespace (ns1) > 2) Try to start them. Start button is disabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24458) Start operation is disabled for HDFS after stopping components for one namespace
[ https://issues.apache.org/jira/browse/AMBARI-24458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24458: --- Fix Version/s: (was: 2.7.1) 2.7.2 > Start operation is disabled for HDFS after stopping components for one > namespace > > > Key: AMBARI-24458 > URL: https://issues.apache.org/jira/browse/AMBARI-24458 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 > Environment: ambari-server version: ambari-server-2.7.1.0-70.x86_64 > ambari-server --hash: f6d369619dc259e6ade537d6cdb3396f9e01c3dd >Reporter: Vivek Rathod >Assignee: Dmytro Sen >Priority: Major > Fix For: 2.7.2 > > Attachments: Screen Shot 2018-08-10 at 10.16.46 AM.png, Screen Shot > 2018-08-10 at 10.17.01 AM.png > > > Start operation is disabled for HDFS after stopping components for one > namespace > > STR: > 1) On hdfs service page, stop components for one namespace (ns1) > 2) Try to start them. Start button is disabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24510) ambari-agent cannot register to server when deploy ambari-agent with web UI on python2.7
[
https://issues.apache.org/jira/browse/AMBARI-24510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587065#comment-16587065
]
yangxiaoshuo commented on AMBARI-24510:
---
Well, use command *ambari-server reset* is effective.
> ambari-agent cannot register to server when deploy ambari-agent with web UI
> on python2.7
>
>
> Key: AMBARI-24510
> URL: https://issues.apache.org/jira/browse/AMBARI-24510
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.6.2
>Reporter: yangxiaoshuo
>Priority: Minor
> Fix For: 2.6.2
>
> Attachments: image-2018-08-21-14-54-01-767.png,
> image-2018-08-21-14-54-45-813.png
>
>
> When deploy ambari-agent use web UI, there is error like that
> {code:java}
> INFO 2018-08-21 14:19:49,634 security.py:93 - SSL Connect being called..
> connecting to the server
> ERROR 2018-08-21 14:19:49,636 Controller.py:226 - Unable to connect to:
> https://hostxx:8441/agent/v1/register/hostxx
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/Controller.py", line 175, in
> registerWithServer
> ret = self.sendRequest(self.registerUrl, data)
> File "/usr/lib/ambari-agent/lib/ambari_agent/Controller.py", line 549, in
> sendRequest
> raise IOError('Request to {0} failed due to {1}'.format(url, str(exception)))
> IOError: Request to https://hostxx:8441/agent/v1/register/hostxx failed due
> to EOF occurred in violation of protocol (_ssl.c:661)
> ERROR 2018-08-21 14:19:49,637 Controller.py:227 - Error:Request to
> https://hostxx:8441/agent/v1/register/hostxx failed due to EOF occurred in
> violation of protocol (_ssl.c:661)
> WARNING 2018-08-21 14:19:49,637 Controller.py:228 - Sleeping for 28 seconds
> and then trying again
> {code}
> and creat Soft link
> {code:java}
> /usr/bin/ambari-python-wrap -> /usr/bin/python{code}
> while python version is 2.7, so I recreate a soft link to python2.6
> {code:java}
> ln -s /usr/bin/python2.6 /usr/bin/ambari-python-wrap
> {code}
> and restart ambari-server and ambari-agent, the the ambari-agent registe
> successfull.
> {code:java}
> INFO 2018-08-21 14:09:48,976 Controller.py:196 - Registration Successful
> (response id = 0){code}
> It seems to have solved the problem.But when i _*Install,Start and Test,*_
> the Progress bar donot move.And I cannot stop it.
> !image-2018-08-21-14-54-01-767.png!
> !image-2018-08-21-14-54-45-813.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24454) WebHdfs calls being made from containers to NameNode hosted on bare metal host fails
[ https://issues.apache.org/jira/browse/AMBARI-24454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587064#comment-16587064 ] Jayush Luniya commented on AMBARI-24454: [~jaimin] Why is this patch only in branch-2.7 and not in trunk? > WebHdfs calls being made from containers to NameNode hosted on bare metal > host fails > > > Key: AMBARI-24454 > URL: https://issues.apache.org/jira/browse/AMBARI-24454 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24452) [UI Deploy] LLAP queue is not created/set in YARN configs while enabling HSI
[
https://issues.apache.org/jira/browse/AMBARI-24452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya resolved AMBARI-24452.
Resolution: Fixed
> [UI Deploy] LLAP queue is not created/set in YARN configs while enabling HSI
>
>
> Key: AMBARI-24452
> URL: https://issues.apache.org/jira/browse/AMBARI-24452
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> In a cluster installed via UI deploy:
> HSI was enabled as part of UI install wizard, but in the YARN configs, the
> 'llap' queue is not added leading to deploy failures. (Hive Server
> Interactive did not start)
> {code:java}
> Failed: org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit
> application_1532935384747_0002 to YARN : Application
> application_1532935384747_0002 submitted by user hive to unknown queue: llap
> java.lang.RuntimeException: org.apache.hadoop.yarn.exceptions.YarnException:
> Failed to submit application_1532935384747_0002 to YARN : Application
> application_1532935384747_0002 submitted by user hive to unknown queue: llap
> at
> org.apache.hadoop.hive.llap.cli.LlapSliderUtils.startCluster(LlapSliderUtils.java:154)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:602)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:120)
> Caused by: org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit
> application_1532935384747_0002 to YARN : Application
> application_1532935384747_0002 submitted by user hive to unknown queue: llap
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.submitApplication(YarnClientImpl.java:304)
> at
> org.apache.hadoop.yarn.service.client.ServiceClient.submitApp(ServiceClient.java:837)
> at
> org.apache.hadoop.yarn.service.client.ServiceClient.actionCreate(ServiceClient.java:365)
> at
> org.apache.hadoop.yarn.service.client.ServiceClient.actionLaunch(ServiceClient.java:351)
> at
> org.apache.hadoop.hive.llap.cli.LlapSliderUtils.startCluster(LlapSliderUtils.java:149)
> ... 2 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24407) Ambari: Add rpm support
[ https://issues.apache.org/jira/browse/AMBARI-24407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587058#comment-16587058 ] Jayush Luniya commented on AMBARI-24407: [~nbhat] Why is this patch only in branch-2.7 and not in trunk? > Ambari: Add rpm support > --- > > Key: AMBARI-24407 > URL: https://issues.apache.org/jira/browse/AMBARI-24407 > Project: Ambari > Issue Type: Improvement > Components: test >Affects Versions: 2.7.0 > Environment: The Ambari rpm is build and tested on AArch64 machine > with CentOS Linux release 7.4.1708. >Reporter: Naresh Bhat >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: 0001-ambari-Add-rpm-support.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > The Ambari infra and logsearch packages are missing rpm support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24426) [Log Search UI] Show user friendly component names in Log Index Filter screen
[ https://issues.apache.org/jira/browse/AMBARI-24426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24426: --- Fix Version/s: (was: 2.7.1) 2.7.2 > [Log Search UI] Show user friendly component names in Log Index Filter screen > - > > Key: AMBARI-24426 > URL: https://issues.apache.org/jira/browse/AMBARI-24426 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Fix For: 2.7.2 > > Original Estimate: 6h > Remaining Estimate: 6h > > Show the user friendly component names on the screen of the Log Index Filter, > where the filter level can be set up. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
