[jira] [Updated] (AMBARI-22753) Fix existing unit tests after STOMP protocol implementation
[ https://issues.apache.org/jira/browse/AMBARI-22753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22753: Labels: pull-request-available (was: ) > Fix existing unit tests after STOMP protocol implementation > --- > > Key: AMBARI-22753 > URL: https://issues.apache.org/jira/browse/AMBARI-22753 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > > Fix failing unit tests -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22805) Blueprints do not handle some failures properly
[
https://issues.apache.org/jira/browse/AMBARI-22805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22805:
---
Status: Patch Available (was: In Progress)
> Blueprints do not handle some failures properly
> ---
>
> Key: AMBARI-22805
> URL: https://issues.apache.org/jira/browse/AMBARI-22805
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: blueprints, pull-request-available
> Fix For: 2.6.2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Failures in the cluster configuration task and topology host tasks during
> blueprint cluster deployment or upscaling are not visible via request status.
> The logical request stays PENDING even after Ambari Server gave up retrying.
> Both the fact that it no longer makes progress and any reason of the failure
> can be seen only in {{ambari-server.log}}.
> Some ways to reproduce (all via blueprints):
> * Create cluster with ZooKeeper and HDFS, but omit the NAMENODE component
> * Create a secure cluster with wrong Kerberos credentials
> * Create a secure cluster without storing Kerberos credentials, restart
> Ambari Server, add a new node
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22792) Refactor agent-side kerberos code
[ https://issues.apache.org/jira/browse/AMBARI-22792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331225#comment-16331225 ] Hudson commented on AMBARI-22792: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8615 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8615/]) AMBARI-22792. Refactor agent-side kerberos code - import fix (echekanskiy: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=74389dd6e1f55168205df52bb74507aebb801a04]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java > Refactor agent-side kerberos code > - > > Key: AMBARI-22792 > URL: https://issues.apache.org/jira/browse/AMBARI-22792 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-20860) BE: Improve User Account Management
[
https://issues.apache.org/jira/browse/AMBARI-20860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas resolved AMBARI-20860.
---
Resolution: Fixed
> BE: Improve User Account Management
>
>
> Key: AMBARI-20860
> URL: https://issues.apache.org/jira/browse/AMBARI-20860
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: authentication, security
> Fix For: 3.0.0
>
>
> Update the backend for improved user management.
> User management tables in the DB should be:
> *{{users}}*
> ||Name||Type||Description||
> |user_id|INTEGER|Internal unique identifier|
> |principal_id|INTEGER|Foreign key from adminprincipal table|
> |user_name|VARCHAR|Unique, case-insensitive, login identifier expected to be
> used when logging into Ambari|
> |create_time|TIMESTAMP|Creation time for this account in Ambari|
> |active|BOOLEAN|Active/not active flag|
> |consecutive_failed_auth_attemps|INTEGER|The number a failed authorization
> attempts since the last successful authentication|
> |active_widgets_layout|VARCHAR| |
> |display_name|VARCHAR|Cosmetic name value to show the user in user interfaces|
> |local_username|VARCHAR|Case-sensitive username to use when impersonating
> user in facilities like Ambari Views|
> * Primary Key: {{user_id}}
> * Foreign Key: {{principal_id}} -> {{adminprincipal.principal_id}}
> *{{user_authentication}}*
> ||Name||Type||Description||
> |user_authentication_id|INTEGER|Primary key for this table|
> |user_id|INTEGER|Foreign key from users table|
> |authentication_type|VARCHAR|Type of authentication system - LOCAL, LDAP,
> KERBEROS, JTW, PAM, etc...
> |authentication_key|VARCHAR|Type-specific key (or identifier):
> * LOCAL: the user's password (digest)
> * LDAP: the user’s distinguished name
> * KERBEROS: the user’s principal
> * etc...|
> |create_time|TIMESTAMP|Creation time of this record
> |update_time|TIMESTAMP|Update time for this record, can be used to enforce
> password retention times|
> * Primary Key: {{user_authentication_id}}
> * Foreign Key: {{user_id}} -> {{users.user_id}}
> Java code needs to change accordingly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22577) Migrate user data for upgrade to improved user account management
[
https://issues.apache.org/jira/browse/AMBARI-22577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22577:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Migrate user data for upgrade to improved user account management
> -
>
> Key: AMBARI-22577
> URL: https://issues.apache.org/jira/browse/AMBARI-22577
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Attachments: AMBARI-22577_branch-feature-AMBARI-20859_01.patch,
> AMBARI-22577_branch-feature-AMBARI-20859_02.patch,
> user_management_db_schema_upgrade.png
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Migrate data from the {{users}} table (pre-Ambari 3.0.0) to the updated
> {{users}} table and {{user_authentication}} tables.
> See [^user_management_db_schema_upgrade.png]
> !user_management_db_schema_upgrade.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-22812) Fix checkstyle error in UpgradeCatalog300Test
[
https://issues.apache.org/jira/browse/AMBARI-22812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas resolved AMBARI-22812.
---
Resolution: Fixed
> Fix checkstyle error in UpgradeCatalog300Test
> -
>
> Key: AMBARI-22812
> URL: https://issues.apache.org/jira/browse/AMBARI-22812
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Fix checkstyle error in UpgradeCatalog300Test
> {noformat}
> [ERROR]
> .../ambari/ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java:20:
> Using the '.*' form of import should be avoided -
> org.apache.ambari.server.upgrade.UpgradeCatalog300.*. [AvoidStarImport]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22812) Fix checkstyle error in UpgradeCatalog300Test
[
https://issues.apache.org/jira/browse/AMBARI-22812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331077#comment-16331077
]
Hudson commented on AMBARI-22812:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8614 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8614/])
AMBARI-22812. Fix checkstyle error in UpgradeCatalog300Test (#148)
(6454655+adoroszlai:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=cd5fdaa4be9108800c9eea7cf1a1c715bfefb192])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java
> Fix checkstyle error in UpgradeCatalog300Test
> -
>
> Key: AMBARI-22812
> URL: https://issues.apache.org/jira/browse/AMBARI-22812
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Fix checkstyle error in UpgradeCatalog300Test
> {noformat}
> [ERROR]
> .../ambari/ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java:20:
> Using the '.*' form of import should be avoided -
> org.apache.ambari.server.upgrade.UpgradeCatalog300.*. [AvoidStarImport]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-21613) Dynamically determine what keytab files have been distributed
[ https://issues.apache.org/jira/browse/AMBARI-21613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-21613: Labels: pull-request-available (was: ) > Dynamically determine what keytab files have been distributed > - > > Key: AMBARI-21613 > URL: https://issues.apache.org/jira/browse/AMBARI-21613 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: 3.0.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Attachments: AMBARI-21613.patch > > > Dynamically determine what keytab files have been distributed to hosts. A > custom command should be available via the KERBEROS_CLIENT to query for the > keytab files installed on the relevant host. The communication between the > Ambari server and the agents should generate data needed to determine what > keytab files exist. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22812) Fix checkstyle error in UpgradeCatalog300Test
[
https://issues.apache.org/jira/browse/AMBARI-22812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22812:
Labels: pull-request-available (was: )
> Fix checkstyle error in UpgradeCatalog300Test
> -
>
> Key: AMBARI-22812
> URL: https://issues.apache.org/jira/browse/AMBARI-22812
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
>
> Fix checkstyle error in UpgradeCatalog300Test
> {noformat}
> [ERROR]
> .../ambari/ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java:20:
> Using the '.*' form of import should be avoided -
> org.apache.ambari.server.upgrade.UpgradeCatalog300.*. [AvoidStarImport]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22812) Fix checkstyle error in UpgradeCatalog300Test
[
https://issues.apache.org/jira/browse/AMBARI-22812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22812:
--
Description:
Fix checkstyle error in UpgradeCatalog300Test
{noformat}
[ERROR]
.../ambari/ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java:20:
Using the '.*' form of import should be avoided -
org.apache.ambari.server.upgrade.UpgradeCatalog300.*. [AvoidStarImport]
{noformat}
was:
Fix checkstyle error in UpgradeCatalog300Test
{noformat}
[ERROR]
/Users/rlevas/github/ambari/ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java:20:
Using the '.*' form of import should be avoided -
org.apache.ambari.server.upgrade.UpgradeCatalog300.*.
[AvoidStarImport]{noformat}
> Fix checkstyle error in UpgradeCatalog300Test
> -
>
> Key: AMBARI-22812
> URL: https://issues.apache.org/jira/browse/AMBARI-22812
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Fix For: 3.0.0
>
>
> Fix checkstyle error in UpgradeCatalog300Test
> {noformat}
> [ERROR]
> .../ambari/ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java:20:
> Using the '.*' form of import should be avoided -
> org.apache.ambari.server.upgrade.UpgradeCatalog300.*. [AvoidStarImport]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22812) Fix checkstyle error in UpgradeCatalog300Test
Robert Levas created AMBARI-22812:
-
Summary: Fix checkstyle error in UpgradeCatalog300Test
Key: AMBARI-22812
URL: https://issues.apache.org/jira/browse/AMBARI-22812
Project: Ambari
Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Robert Levas
Assignee: Robert Levas
Fix For: 3.0.0
Fix checkstyle error in UpgradeCatalog300Test
{noformat}
[ERROR]
/Users/rlevas/github/ambari/ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java:20:
Using the '.*' form of import should be avoided -
org.apache.ambari.server.upgrade.UpgradeCatalog300.*.
[AvoidStarImport]{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22665) Livy2 Does Not Start On HDP 2.6.0 to 2.6.3
[
https://issues.apache.org/jira/browse/AMBARI-22665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330936#comment-16330936
]
Hudson commented on AMBARI-22665:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-22665 - Livy2 Does Not Start On HDP 2.6.0 to 2.6.3 (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=df19a69364b470b063e0790847af640c99262daa])
* (edit)
ambari-server/src/main/resources/custom_actions/scripts/install_packages.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
> Livy2 Does Not Start On HDP 2.6.0 to 2.6.3
> --
>
> Key: AMBARI-22665
> URL: https://issues.apache.org/jira/browse/AMBARI-22665
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.2
>
> Attachments: AMBARI-22665.patch
>
>
> Livy2 was added as a component in HDP 2.6, starting with HDP 2.6.0.0.
> However, there was no stack-select or conf-select support for some reason.
> stack-select and conf-select was built into HDP 2.6.4.0.
> Ambari added {{livy2}} as a known conf-select to the HDP 2.6 stack. On
> deployments of HDP 2.6.4+, this is correct and the server can properly start.
> However, when using Ambari to deploy Livy2 on HDP 2.6.0 - 2.6.3, we see the
> following:
> {code}
> 2017-12-18 14:53:52,711 - Checking to see which directories will be created
> for livy2 on version 2.6.0.0-334
> 2017-12-18 14:53:52,711 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'dry-run-create', '--package', 'livy2', '--stack-version', '2.6.0.0-334',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-12-18 14:53:52,734 - call returned (1, 'livy2 not installed or incorrect
> package name', '')
> 2017-12-18 14:53:52,735 - Creating /etc/livy2/2.6.0.0-334/0 if it does not
> exist
> 2017-12-18 14:53:52,736 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'create-conf-dir', '--package', 'livy2', '--stack-version', '2.6.0.0-334',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-12-18 14:53:52,765 - call returned (1, 'livy2 not installed or incorrect
> package name', '')
> 2017-12-18 14:53:52,766 - checked_call[('ambari-python-wrap',
> '/usr/bin/conf-select', 'set-conf-dir', '--package', 'livy2',
> '--stack-version', '2.6.0.0-334', '--conf-version', '0')] {'logoutput':
> False, 'sudo': True, 'quiet': False}
> 2017-12-18 14:53:52,795 - Could not select the directory for package livy2.
> Error: Execution of 'ambari-python-wrap /usr/bin/conf-select set-conf-dir
> --package livy2 --stack-version 2.6.0.0-334 --conf-version 0' returned 1.
> livy2 not installed or incorrect package name
> 2017-12-18 14:53:52,796 - /etc/livy2/conf is a directory - it must be
> converted into a symlink
> {code}
> Essentially, Ambari is trying to setup the configuration pointers, but it is
> ignoring the dry-run result code. At the end of the day, we end up with Livy2
> not starting b/c we're manipulated the configuration pointers, but
> {{conf-select}} failed to properly create a versioned configuration directory.
> The solution is to check the dry-run result code and do nothing if
> conf-select doesn't support the package.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22647) Rafactor: Package Log Search and Log Feeder into jars + cleanup start scripts
[ https://issues.apache.org/jira/browse/AMBARI-22647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330931#comment-16330931 ] Hudson commented on AMBARI-22647: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-22647. Rafactor: Package Log Search and Log Feeder into jars + (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=26a33e545b89243daecef21bdf0e2798412e49e8]) * (add) ambari-logsearch/ambari-logsearch-logfeeder/src/main/scripts/logfeeder-env.sh * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeederCommandLine.java * (edit) ambari-logsearch/docker/test-config/logsearch/logsearch.properties * (add) ambari-logsearch/ambari-logsearch-assembly/src/main/package/rpm/portal/postinstall.sh * (edit) ambari-logsearch/ambari-logsearch-server/build.xml * (edit) ambari-logsearch/docker/Dockerfile * (add) ambari-logsearch/ambari-logsearch-assembly/src/main/package/rpm/logfeeder/postremove.sh * (edit) ambari-logsearch/docker/docker-compose.yml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/params.py * (edit) ambari-logsearch/docker/logsearch-logfeeder.yml * (edit) ambari-logsearch/docker/test-config/logsearch/logsearch-env.sh * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/setup_logsearch.py * (edit) ambari-logsearch/docker/all.yml * (edit) ambari-logsearch/docker/test-config/logsearch/logsearch-https.properties * (edit) ambari-logsearch/ambari-logsearch-assembly/src/main/package/deb/logfeeder/postinst * (delete) ambari-logsearch/ambari-logsearch-server/src/main/scripts/run.sh * (edit) ambari-logsearch/ambari-logsearch-assembly/src/main/package/deb/portal/postrm * (add) ambari-logsearch/ambari-logsearch-logfeeder/src/main/scripts/logfeeder.sh * (edit) ambari-logsearch/ambari-logsearch-logfeeder/run.sh * (edit) ambari-logsearch/ambari-logsearch-server/README.md * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/logfeeder.py * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-env.xml * (edit) ambari-server/src/test/python/stacks/2.4/configs/default.json * (edit) ambari-logsearch/ambari-logsearch-assembly/src/main/package/deb/portal/postinst * (edit) ambari-server/src/test/python/stacks/2.4/LOGSEARCH/test_logfeeder.py * (delete) ambari-logsearch/ambari-logsearch-logfeeder/src/main/package/deb/control/postinst * (edit) ambari-logsearch/docker/logsearch-server.yml * (delete) ambari-logsearch/ambari-logsearch-logfeeder/src/main/package/deb/control/control * (add) ambari-logsearch/ambari-logsearch-server/src/main/scripts/logsearch-env.sh * (delete) ambari-logsearch/ambari-logsearch-logfeeder/src/main/package/deb/control/prerm * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/logsearch.py * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/logsearch-env.sh.j2 * (edit) ambari-logsearch/ambari-logsearch-server/run.sh * (delete) ambari-logsearch/ambari-logsearch-logfeeder/src/main/scripts/run.sh * (edit) ambari-logsearch/docker/bin/start.sh * (edit) ambari-logsearch/ambari-logsearch-logfeeder/build.xml * (add) ambari-logsearch/ambari-logsearch-assembly/src/main/package/rpm/logfeeder/preinstall.sh * (delete) ambari-logsearch/ambari-logsearch-server/src/main/scripts/stop.sh * (edit) ambari-logsearch/docker/test-config/logfeeder/logfeeder.properties * (add) ambari-logsearch/ambari-logsearch-assembly/src/main/package/rpm/portal/preinstall.sh * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/setup_logfeeder.py * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeeder.java * (edit) ambari-logsearch/ambari-logsearch-server/pom.xml * (edit) ambari-logsearch/ambari-logsearch-assembly/pom.xml * (edit) ambari-server/src/test/python/stacks/2.0.6/hooks/after-INSTALL/test_after_install.py * (edit) ambari-logsearch/docker/test-config/logfeeder/logfeeder-env.sh * (delete) ambari-logsearch/ambari-logsearch-logfeeder/build.properties * (add) ambari-logsearch/ambari-logsearch-assembly/src/main/package/rpm/logfeeder/postinstall.sh * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/LogSearch.java * (edit) ambari-server/src/main/resources/stack-hooks/after-INSTALL/scripts/params.py * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/ConfigHandler.java * (edit) ambari-server/src/test/python/stacks/2.4/LOGSEARCH/test_logsearch.py * (delete) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/logsearch_common.py * (delete)
[jira] [Commented] (AMBARI-22663) Log Search UI: incorrect caption for graph gap in weeks
[ https://issues.apache.org/jira/browse/AMBARI-22663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330930#comment-16330930 ] Hudson commented on AMBARI-22663: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-22663 Log Search UI: incorrect caption for graph gap in weeks. (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=2244d973833ba1ce12bb73dc861ced618f3b9344]) * (edit) ambari-logsearch/ambari-logsearch-web/src/assets/i18n/en.json > Log Search UI: incorrect caption for graph gap in weeks > --- > > Key: AMBARI-22663 > URL: https://issues.apache.org/jira/browse/AMBARI-22663 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22663.patch > > > There's a text reflecting the gap between values of the graph. It's incorrect > when the unit is week (caption is not defined). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22651) Unable to add/change role for user
[ https://issues.apache.org/jira/browse/AMBARI-22651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330925#comment-16330925 ] Hudson commented on AMBARI-22651: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-22651 Unable to add/change role for user. (atkach) (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=ada1ea543059521b1e93abd208583ae85affd162]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/userManagement/modals/groupCreate.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/userManagement/modals/userCreate.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/userManagement/userEdit.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/userManagement/groupEdit.html > Unable to add/change role for user > -- > > Key: AMBARI-22651 > URL: https://issues.apache.org/jira/browse/AMBARI-22651 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22651.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22522) Livy server fails to start during downgrade due to absence of 'conf' directory
[
https://issues.apache.org/jira/browse/AMBARI-22522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330935#comment-16330935
]
Hudson commented on AMBARI-22522:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-22522 - Livy server fails to start during downgrade due to (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=9e9f68f2835d702b0c297b8a9c700f49b05f8475])
* (edit)
ambari-server/src/main/resources/custom_actions/scripts/install_packages.py
> Livy server fails to start during downgrade due to absence of 'conf' directory
> --
>
> Key: AMBARI-22522
> URL: https://issues.apache.org/jira/browse/AMBARI-22522
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22522.patch
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.4.3.0-30 and HDP version:
> 2.5.5.0-157
> # Upgrade Ambari to 2.6.1.0-43
> # Start EU to 2.6.4.0-36 and downgrade at final step
> *Result*
> Observed during downgrade that Livy server start failed with below error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/livy_server.py",
> line 141, in
> LivyServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 970, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/livy_server.py",
> line 61, in start
> self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 120, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/livy_server.py",
> line 51, in configure
> setup_livy(env, 'server', upgrade_type=upgrade_type, action = 'config')
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/setup_livy.py",
> line 56, in setup_livy
> mode=0644,
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 166, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 120, in action_create
> raise Fail("Applying %s failed, parent directory %s doesn't exist" %
> (self.resource, dirname))
> resource_management.core.exceptions.Fail: Applying
> File['/usr/hdp/current/livy-server/conf/livy-env.sh'] failed, parent
> directory /usr/hdp/current/livy-server/conf doesn't exist
> {code}
> On livy node, observed the following:
> {code}
> root@ctr-e134-1499953498516-324773-01-07:/usr/hdp/current/livy-server# ls
> -la /usr/hdp/current/livy-server/
> total 40
> drwxr-xr-x 8 root root 4096 Nov 20 23:49 .
> drwxr-xr-x 42 root root 4096 Nov 21 00:05 ..
> drwxr-xr-x 2 root root 4096 Nov 20 23:43 bin
> lrwxrwxrwx 1 root root14 Apr 21 2017 conf -> /etc/livy/conf
> drwxr-xr-x 3 root root 4096 Nov 20 23:43 etc
> drwxr-xr-x 2 root root 12288 Nov 20 23:43 jars
> drwxr-xr-x 2 livy livy 4096 Nov 20 23:49 logs
> drwxr-xr-x 2 root root 4096 Nov 20 23:43 repl-jars
> drwxr-xr-x 2 root root 4096 Nov 20 23:43 rsc-jars
> ===
> root@ctr-e134-1499953498516-324773-01-07:~# ls -la /etc/livy/
> total 16
> drwxr-xr-x 4 root root 4096 Nov 21 04:32 .
> drwxr-xr-x 120 root root 4096 Nov 21 03:26 ..
> drwxr-xr-x 3 root root 4096 Nov 21 03:30 2.6.4.0-36
> lrwxrwxrwx 1 root root 21 Nov 21 04:32 conf -> /usr/hdp/current/livy
> drwxr-xr-x 2 root root 4096 Nov 20 23:49 conf.backup
> {code}
> Looks like there is no directory '/etc/livy/2.5.5.0-157/0'
> From downgrade wizard, found that 'Set Version on All Hosts' Upgrade group
> printed the following for livy:
> {code}
> 2017-11-21 04:32:08,022 - Link['/etc/livy/conf'] {'to':
> '/usr/hdp/current/livy'}
> 2017-11-21 04:32:08,022 - Link['/etc/livy/conf'] replacing old symlink to
> /grid/0/hdp/current/livy
> 2017-11-21 04:32:08,022 - Warning: linking to nonexistent location
> /usr/hdp/current/livy
> 2017-11-21
[jira] [Commented] (AMBARI-22571) Handle passwords/sensitive data in Ambari configuration properties
[
https://issues.apache.org/jira/browse/AMBARI-22571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330937#comment-16330937
]
Hudson commented on AMBARI-22571:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-22571. Handle passwords/sensitive data in Ambari configuration (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=297e5b9f81e64dcd46f736f3f10609ecbc1cd7d6])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RootServiceComponentConfigurationResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/api/services/RootServiceComponentConfiguration.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RootServiceComponentConfigurationResourceProviderTest.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AmbariServerConfigurationUtils.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AmbariServerConfigurationHandler.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AmbariServerLDAPConfigurationHandler.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RootServiceComponentConfigurationHandler.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/ldap/domain/AmbariLdapConfigurationKeys.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/configuration/ConfigurationPropertyType.java
* (edit) ambari-server/pom.xml
> Handle passwords/sensitive data in Ambari configuration properties
> --
>
> Key: AMBARI-22571
> URL: https://issues.apache.org/jira/browse/AMBARI-22571
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Minor
> Labels: config, security
> Fix For: trunk
>
> Attachments: AMBARI_22571_trunk_01.patch
>
>
> Passwords and other sensitive data stored as values to properties in Ambari
> configurations need to be masked or not stored in cleartext.
> For example,
> {{ldap-configuration/ambari.ldap.connectivity.trust_store.password}} and
> ldap-{{configuration/ambari.ldap.connectivity.bind_password}}.
> If the Ambari credential store is enabled (which might be by default as of
> Ambari 3.0.0), the sensitive date can be stored there like we do when
> sensitive data is to be stored in the ambari.properties file - see
> {{org.apache.ambari.server.security.encryption.CredentialStoreService}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22648) zeppelin server keytab missing from zeppelin-site.xml
[ https://issues.apache.org/jira/browse/AMBARI-22648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330926#comment-16330926 ] Hudson commented on AMBARI-22648: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-22648: zeppelin server keytab missing from zeppelin-site.xml (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=67b06423b8872e67c7ec75b73f2ac415f55914ca]) * (edit) ambari-server/src/test/python/stacks/2.6/configs/default.json * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/package/scripts/master.py > zeppelin server keytab missing from zeppelin-site.xml > - > > Key: AMBARI-22648 > URL: https://issues.apache.org/jira/browse/AMBARI-22648 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.6.0 >Reporter: Bikas Saha >Assignee: Bikas Saha >Priority: Critical > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22648.1.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22657) Oozie service check failed during 4th digit PU
[
https://issues.apache.org/jira/browse/AMBARI-22657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330927#comment-16330927
]
Hudson commented on AMBARI-22657:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-22657 Oozie service check failed during 4th digit PU (dgrinenko)
(rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=bb218447638066e2329be8ef437d603cede63ca5])
* (edit)
ambari-server/src/main/resources/stacks/HDP/3.0/properties/stack_packages.json
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_packages.json
> Oozie service check failed during 4th digit PU
> --
>
> Key: AMBARI-22657
> URL: https://issues.apache.org/jira/browse/AMBARI-22657
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.6.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.6.2
>
> Attachments: AMBARI-22657-trunk.patch, AMBARI-22657.patch
>
>
> {code}
> SEVERE: The web application [/oozie] created a ThreadLocal with key of type
> [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@724836f5]) and a value
> of type [org.apache.hadoop.fs.FileSystem.Statistics.StatisticsData] (value
> [1884 bytes read, 0 bytes written, 23 read ops, 0 large read ops, 0 write
> ops]) but failed to remove it when the web application was stopped. This is
> very likely to create a memory leak.
> Dec 04, 2017 2:40:26 AM org.apache.catalina.loader.WebappClassLoader
> checkThreadLocalMapForLeaks
> SEVERE: The web application [/oozie] created a ThreadLocal with key of type
> [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@a9aa286]) and a value
> of type [org.apache.hadoop.fs.FileSystem.Statistics.StatisticsData] (value
> [1046 bytes read, 0 bytes written, 0 read ops, 0 large read ops, 0 write
> ops]) but failed to remove it when the web application was stopped. This is
> very likely to create a memory leak.
> Dec 04, 2017 2:40:26 AM org.apache.catalina.loader.WebappClassLoader
> checkThreadLocalMapForLeaks
> SEVERE: The web application [/oozie] created a ThreadLocal with key of type
> [org.apache.oozie.util.XLog$Info$1] (value
> [org.apache.oozie.util.XLog$Info$1@e4a9a09]) and a value of type
> [org.apache.oozie.util.XLog.Info] (value
> [org.apache.oozie.util.XLog$Info@511b97d4]) but failed to remove it when the
> web application was stopped. This is very likely to create a memory leak.
> Dec 04, 2017 2:40:26 AM org.apache.catalina.loader.WebappClassLoader
> checkThreadLocalMapForLeaks
> SEVERE: The web application [/oozie] created a ThreadLocal with key of type
> [org.apache.oozie.util.XLog$Info$1] (value
> [org.apache.oozie.util.XLog$Info$1@e4a9a09]) and a value of type
> [org.apache.oozie.util.XLog.Info] (value
> [org.apache.oozie.util.XLog$Info@3349e2ee]) but failed to remove it when the
> web application was stopped. This is very likely to create a memory leak.
> Dec 04, 2017 2:40:26 AM org.apache.catalina.loader.WebappClassLoader
> checkThreadLocalMapForLeaks
> SEVERE: The web application [/oozie] created a ThreadLocal with key of type
> [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@724836f5]) and a value
> of type [org.apache.hadoop.fs.FileSystem.Statistics.StatisticsData] (value
> [1884 bytes read, 0 bytes written, 23 read ops, 0 large read ops, 0 write
> ops]) but failed to remove it when the web application was stopped. This is
> very likely to create a memory leak.
> Dec 04, 2017 2:40:27 AM org.apache.catalina.core.StandardContext
> resourcesStart
> SEVERE: Error starting static Resources
> java.lang.IllegalArgumentException: Document base
> /usr/hdp/current/oozie-client/oozie-server/webapps/oozie does not exist or is
> not a readable directory
> at
> org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:142)
> at
> org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4390)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4563)
> at
> org.apache.catalina.startup.HostConfig.checkResources(HostConfig.java:1287)
> at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1385)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:307)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at
> org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1393)
> at
> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1657)
> at
>
[jira] [Commented] (AMBARI-21219) Update LDAP Authentication process to work with improved user management facility
[ https://issues.apache.org/jira/browse/AMBARI-21219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330917#comment-16330917 ] Hudson commented on AMBARI-21219: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-21219. Update LDAP Authentication process to work with improved (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=637c521972cb3a064bd108e97a1007be10d7ef09]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderTest.java * (edit) ambari-server/docs/configuration/index.md * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/configuration/ConfigurationTest.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthentication.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UserDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/ldap/service/AmbariLdapConfigurationProvider.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariAuthenticationTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/TestUsers.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AuthorizationHelperTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderForDuplicateUserTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/LdapServerProperties.java > Update LDAP Authentication process to work with improved user management > facility > -- > > Key: AMBARI-21219 > URL: https://issues.apache.org/jira/browse/AMBARI-21219 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-21219_branch-feature-AMBARI-20859_01.patch, > AMBARI-21219_branch-feature-AMBARI-20859_02.patch > > > Update LDAP Authentication process to work with improved user management > facility -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22661) Storm service check fails with StormAtlasHook CNF after cluster deploy
[ https://issues.apache.org/jira/browse/AMBARI-22661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330929#comment-16330929 ] Hudson commented on AMBARI-22661: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-22661 Storm service check fails with StormAtlasHook CNF after (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=d5120aab0f3a13769b8f8e366b689169872a2ec4]) * (edit) ambari-common/src/main/python/resource_management/libraries/functions/setup_atlas_hook.py > Storm service check fails with StormAtlasHook CNF after cluster deploy > -- > > Key: AMBARI-22661 > URL: https://issues.apache.org/jira/browse/AMBARI-22661 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: 2.6.2 > > Attachments: AMBARI-22661.patch > > > STR: > deploy cluster with HDFS, YARN, Tez, Hive, HBase, Pig, ZK, Storm, Ambari > Infra, Atlas, Kafka, Slider using at least 5 hosts > make sure that Supervisor , Atlas and Clients r on different hosts. > Supervisor is the host, where most likely would run Storm SC. > Check Storm SC > Storm SC failed as Atlas class loader were not linked in storm extlib > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22659) unable to proceed with cluster install after component install fails
[
https://issues.apache.org/jira/browse/AMBARI-22659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330928#comment-16330928
]
Hudson commented on AMBARI-22659:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-22659. unable to proceed with cluster install after component (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=72035ef381603119398c0b02e0eb71f1e497fe7d])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/HostVersionDAOTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostVersionEntity.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostVersionDAO.java
> unable to proceed with cluster install after component install fails
>
>
> Key: AMBARI-22659
> URL: https://issues.apache.org/jira/browse/AMBARI-22659
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Blocker
> Fix For: 3.0.0
>
>
> Unable go back in install wizard if install was finished at one of hosts.
> {code}
> Request
> URL:http://ambari:8080/api/v1/stacks/HDP/versions/2.6/repository_versions/1
> {
> "status" : 500,
> "message" : "org.apache.ambari.server.controller.spi.SystemException:
> Repository version can't be deleted as it is used by the following hosts:
> CURRENT on sanjay-divgi-test-2.openstacklocal,
> sanjay-divgi-test-5.openstacklocal, sanjay-divgi-test-1.openstacklocal,
> sanjay-divgi-test-4.openstacklocal"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22585) Fix the wording on IPA integration requirements in the Enable Kerberos Wizard
[
https://issues.apache.org/jira/browse/AMBARI-22585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330918#comment-16330918
]
Hudson commented on AMBARI-22585:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-22585. Fix the wording on IPA integration requirements in the (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=3c129fca785a671a29cd23b03903163fdd2f8390])
* (edit) ambari-web/app/messages.js
> Fix the wording on IPA integration requirements in the Enable Kerberos Wizard
> -
>
> Key: AMBARI-22585
> URL: https://issues.apache.org/jira/browse/AMBARI-22585
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: freeipa, kerberos
> Fix For: 3.0.0
>
> Attachments: AMBARI-22585_trunk_01.patch
>
>
> Fix the wording of the IPA requirements in the Enable Kerberos Wizard to read
> as follows
> * All cluster hosts are joined to the IPA domain and hosts are registered in
> DNS
> * A password policy is in place that sets no expiry for created principals
> * If you do not plan on using Ambari to manage the krb5.conf, ensure the
> following is set in each krb5.conf file in your cluster: default_ccache_name
> = /tmp/krb5cc_%{uid}
> * The Java Cryptography Extensions (JCE) have been setup on the Ambari Server
> host and all hosts in the cluster
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22639) Log Feeder refactor: integrate with spring boot
[ https://issues.apache.org/jira/browse/AMBARI-22639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330924#comment-16330924 ] Hudson commented on AMBARI-22639: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-22639. Log Feeder refactor: integrate with spring boot (oleewere) (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=4a668f0b69426f7a2c4379e0930fea739a1b6c0b]) * (delete) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/SSLUtil.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputManager.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/resources/log4j.xml * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputS3File.java * (add) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/ApplicationConfig.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/filter/FilterGrok.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/metrics/MetricsManager.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeederCommandLine.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/output/OutputKafkaTest.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/pom.xml * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/filter/FilterKeyValueTest.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/input/InputManagerTest.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/metrics/MetricsManagerTest.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/output/OutputS3FileTest.java * (add) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/MetricsCollectorConfig.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/InputSimulate.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/loglevelfilter/LogLevelFilterHandler.java * (edit) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/LogSearchConfigLogFeeder.java * (edit) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/LogSearchConfigFactory.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputHDFSFile.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputSolr.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/output/OutputSolrTest.java * (delete) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/logconfig/LogConfigHandlerTest.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputKafka.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/resources/log-samples/shipper-conf/input.config-sample.json * (add) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/InputSimulateConfig.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeeder.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/filter/FilterKeyValue.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputFile.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/resources/logfeeder.properties * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/AbstractInputFile.java * (delete) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/LogFeederPropertiesUtil.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/InputManager.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/input/InputFileTest.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/ConfigItem.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/Input.java *
[jira] [Commented] (AMBARI-22675) LogSearch Title Bar Fixes
[ https://issues.apache.org/jira/browse/AMBARI-22675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330940#comment-16330940 ] Hudson commented on AMBARI-22675: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-22675 LogSearch Title Bar Fixes. (Istvan Tobias via ababiichuk) (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=b74b05c22f4dec6791e53944a0f6385625e33362]) * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/main-container/main-container.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/app.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/app.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/main-container/main-container.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/main-container/main-container.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.ts > LogSearch Title Bar Fixes > - > > Key: AMBARI-22675 > URL: https://issues.apache.org/jira/browse/AMBARI-22675 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Istvan Tobias >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22675.patch > > > The top LogSearch Title bar is currently fixed in size and shown during > scrolling. It's better to have a limited set of search controls displayed in > the LogSearch title bar, to provide a way to show the existing search, and > also allow the user to modify the search while in the middle of searching > results. > The search bar instead of the title bar should be sticky at the top. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22577) Migrate user data for upgrade to improved user account management
[
https://issues.apache.org/jira/browse/AMBARI-22577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330941#comment-16330941
]
Hudson commented on AMBARI-22577:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-22577. Migrate user data for upgrade to improved user account (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=5ba3cd3a599bf01676b49d048fdae2889bbb0e03])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderForDNWithSpaceTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UserAuthenticationEntity.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UserAuthenticationDAO.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog300.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/DBAccessorImplTest.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessor.java
> Migrate user data for upgrade to improved user account management
> -
>
> Key: AMBARI-22577
> URL: https://issues.apache.org/jira/browse/AMBARI-22577
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Attachments: AMBARI-22577_branch-feature-AMBARI-20859_01.patch,
> AMBARI-22577_branch-feature-AMBARI-20859_02.patch,
> user_management_db_schema_upgrade.png
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Migrate data from the {{users}} table (pre-Ambari 3.0.0) to the updated
> {{users}} table and {{user_authentication}} tables.
> See [^user_management_db_schema_upgrade.png]
> !user_management_db_schema_upgrade.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22628) YARN Shuffle Service Can't Be Found On Client-Only Nodes After New Cluster Install
[
https://issues.apache.org/jira/browse/AMBARI-22628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330921#comment-16330921
]
Hudson commented on AMBARI-22628:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-22628 - YARN Shuffle Service Can't Be Found On Client-Only Nodes
(rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=15d8d1a1485ec5e5441c31566ef8a16632d6046f])
* (edit)
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/OrmTestHelper.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* (edit)
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelperTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapperTest.java
> YARN Shuffle Service Can't Be Found On Client-Only Nodes After New Cluster
> Install
> --
>
> Key: AMBARI-22628
> URL: https://issues.apache.org/jira/browse/AMBARI-22628
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Kishor Ramakrishnan
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22628.patch
>
>
> Installing a new cluster can create values in yarn-site.xml which have
> {{None}} specified in the classpath for Spark
> {code:java}
>
> yarn.nodemanager.aux-services.spark2_shuffle.classpath
> /usr/hdp/None/spark2/aux/*
>
>
> yarn.nodemanager.aux-services.spark_shuffle.classpath
> /usr/hdp/None/spark/aux/*
>
>
>
> yarn.timeline-service.entity-group-fs-store.group-id-plugin-classpath
> /usr/hdp/None/spark/hdpLib/*
>
> {code}
> The cause for this is that YARN Clients on hosts without daemons never get a
> restart command after the initial {{yarn-site.xml}}, and can never fill in
> the correct values. This causes problems when jobs are run on these nodes:
> {code}
> 2017-12-04 10:16:41,789 INFO service.AbstractService
> (AbstractService.java:noteFailure(272)) - Service
> org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices failed
> in state INITED; cause: java.lang.ClassNotFoundException:
> org.apache.spark.network.yarn.YarnShuffleService
> java.lang.ClassNotFoundException:
> org.apache.spark.network.yarn.YarnShuffleService
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22572) During cluster installation bower cannot resolve angularjs version
[ https://issues.apache.org/jira/browse/AMBARI-22572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330919#comment-16330919 ] Hudson commented on AMBARI-22572: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) Revert "AMBARI-22572. During cluster installation bower cannot resolve (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=a8a7c1d35e5f1ea580620125637fc7c3a3e675f2]) * (edit) ambari-admin/src/main/resources/ui/admin-web/bower.json > During cluster installation bower cannot resolve angularjs version > -- > > Key: AMBARI-22572 > URL: https://issues.apache.org/jira/browse/AMBARI-22572 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.6.1 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22572.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330923#comment-16330923 ] Hudson commented on AMBARI-22635: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-22635. Ambari should create a dummy core-site.xml for Ranger (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=e99867a0b4efb2955b82b9116dd3720a3ea8507a]) * (edit) ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py * (edit) ambari-server/src/main/resources/common-services/KNOX/0.5.0.3.0/package/scripts/setup_ranger_knox.py * (edit) ambari-server/src/main/resources/common-services/STORM/1.0.1.3.0/package/scripts/setup_ranger_storm.py * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/scripts/setup_ranger_kafka.py * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/setup_ranger_storm.py * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/setup_ranger_kafka.py * (edit) ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/setup_ranger_knox.py AMBARI-22635: Addendum fix Ambari should create a dummy core-site.xml (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=35247b1f4cbcf7bbe06b419494e82c8ad15e8fbf]) * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/setup_ranger_kafka.py > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0, 2.6.1 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22635-branch-2.6.1.patch, > AMBARI-22635-branch-2.6.2.patch, AMBARI-22635-branch-2.6.patch, > AMBARI-22635-trunk.1-addendum.patch, AMBARI-22635-trunk.1.patch, > AMBARI-22635-trunk.patch > > > For Ranger plugins to work properly in kerberised environments where HDFS is > not installed. We need to create a core-site.xml for Storm and Kafka plugins > so that the plugins can work to fetch latest policies from with kerberised > calls from Ranger. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22655) Livy/Livy2 Unable To Start Due to Address Already In Use
[
https://issues.apache.org/jira/browse/AMBARI-22655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330934#comment-16330934
]
Hudson commented on AMBARI-22655:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-22655 - Livy/Livy2 Unable To Start Due to Address Already In Use
(rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=f4e1a2bff9b93f28ddc5fa958739a81fe3148aa5])
* (edit)
ambari-server/src/main/resources/stacks/HDP/3.0/properties/stack_packages.json
* (edit)
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/livy2_service.py
* (edit) ambari-server/src/test/python/stacks/2.5/SPARK/test_spark_livy.py
* (edit)
ambari-server/src/main/resources/common-services/SPARK/2.2.0/package/scripts/livy_service.py
* (edit)
ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/livy_service.py
* (edit) ambari-server/src/test/python/stacks/2.6/SPARK2/test_spark_livy2.py
* (edit)
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/setup_livy2.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_packages.json
> Livy/Livy2 Unable To Start Due to Address Already In Use
>
>
> Key: AMBARI-22655
> URL: https://issues.apache.org/jira/browse/AMBARI-22655
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.2
>
>
> While restarting Livy and Livy2 on a non-root cluster, the following is seen:
> {code}
> 17/12/14 14:36:23 WARN LivyConf: The configuration key
> livy.repl.enableHiveContext has been deprecated as of Livy 0.4 and may be
> removed in the future. Please use the new key livy.repl.enable-hive-context
> instead.
> 17/12/14 14:36:23 WARN LivyConf: The configuration key
> livy.server.csrf_protection.enabled has been deprecated as of Livy 0.4 and
> may be removed in the future. Please use the new key
> livy.server.csrf-protection.enabled instead.
> 17/12/14 14:36:23 INFO AccessManager: AccessControlManager acls
> disabled;users with view permission: ;users with modify permission: ;users
> with super permission: cstm-zeppelin;other allowed users: *
> 17/12/14 14:36:28 INFO LineBufferedStream: stdout: Welcome to
> 17/12/14 14:36:28 INFO LineBufferedStream: stdout: __
> 17/12/14 14:36:28 INFO LineBufferedStream: stdout: / __/__ ___ _/
> /__
> 17/12/14 14:36:28 INFO LineBufferedStream: stdout: _\ \/ _ \/ _ `/ __/
> '_/
> 17/12/14 14:36:28 INFO LineBufferedStream: stdout:/___/ .__/\_,_/_/
> /_/\_\ version 2.2.0.2.6.4.0-73
> 17/12/14 14:36:28 INFO LineBufferedStream: stdout: /_/
> 17/12/14 14:36:28 INFO LineBufferedStream: stdout:
> 17/12/14 14:36:28 INFO LineBufferedStream: stdout: Using Scala version
> 2.11.8, OpenJDK 64-Bit Server VM, 1.8.0_131
> 17/12/14 14:36:28 INFO LineBufferedStream: stdout: Branch HEAD
> 17/12/14 14:36:28 INFO LineBufferedStream: stdout: Compiled by user jenkins
> on 2017-12-13T19:08:32Z
> 17/12/14 14:36:28 INFO LineBufferedStream: stdout: Revision
> a24017869f5450397136ee8b11be818e7cd3facb
> 17/12/14 14:36:28 INFO LineBufferedStream: stdout: Url
> g...@github.com:hortonworks/spark2.git
> 17/12/14 14:36:28 INFO LineBufferedStream: stdout: Type --help for more
> information.
> 17/12/14 14:36:29 WARN NativeCodeLoader: Unable to load native-hadoop library
> for your platform... using builtin-java classes where applicable
> 17/12/14 14:36:31 INFO AHSProxy: Connecting to Application History server at
> nat-yc-r7-ovvs-ambari-autostart-4-re-2.openstacklocal/172.22.121.144:10200
> 17/12/14 14:36:32 WARN DomainSocketFactory: The short-circuit local reads
> feature cannot be used because libhadoop cannot be loaded.
> 17/12/14 14:36:33 INFO StateStore$: Using FileSystemStateStore for recovery.
> 17/12/14 14:36:33 INFO BatchSessionManager: Recovered 0 batch sessions. Next
> session id: 0
> 17/12/14 14:36:33 INFO InteractiveSessionManager: Recovered 0 interactive
> sessions. Next session id: 0
> 17/12/14 14:36:33 INFO InteractiveSessionManager: Heartbeat watchdog thread
> started.
> 17/12/14 14:36:33 INFO LivyServer: SPNEGO auth enabled (principal =
> HTTP/nat-yc-r7-ovvs-ambari-autostart-4-re-3.openstacklo...@example.com)
> 17/12/14 14:36:33 INFO LivyServer: CSRF protection is enabled.
> 17/12/14 14:36:34 INFO KerberosAuthenticationHandler: Login using keytab
> /etc/security/keytabs/spnego.service.keytab, for principal
> HTTP/nat-yc-r7-ovvs-ambari-autostart-4-re-3.openstacklo...@example.com
> 17/12/14 14:36:34 INFO KerberosAuthenticationHandler: Map server:
> nat-yc-r7-ovvs-ambari-autostart-4-re-3.openstacklocal to
[jira] [Commented] (AMBARI-22638) yarn.timeline-service property enabled overriding preset secure blueprint config for the same
[
https://issues.apache.org/jira/browse/AMBARI-22638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330922#comment-16330922
]
Hudson commented on AMBARI-22638:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-22638. yarn.timeline-service property enabled overriding preset (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=da6a201058b9c94aaf413621d615483ae177c36e])
* (edit)
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/kerberos.json
> yarn.timeline-service property enabled overriding preset secure blueprint
> config for the same
> -
>
> Key: AMBARI-22638
> URL: https://issues.apache.org/jira/browse/AMBARI-22638
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Kishor Ramakrishnan
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22638.trunk.001.patch
>
>
> yarn.timeline-service property enabled overriding preset secure blueprint
> config for the same.
> Configuration in yarn-site in blueprint
> {code:java}
> "yarn.timeline-service.enabled": "false"
> {code}
> The same config resolved in TOPOLOGY_RESOLVED yarn-site to
> {code:java}
> "yarn.timeline-service.enabled": "true"
> {code}
> Configuration recommendation strategy in while cluster deploy template is
> ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES
> {code:java}
> "config_recommendation_strategy": "ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES",
> {code}
> Expected behavior: The config yarn.timeline-service.enabled should have
> persisted the value "false" even after deploy.
> Actual behavior: Flag "yarn.timeline-service.enabled" is toggled to "true"
> while resolving configs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22670) Ambari 3.0: Implement new design for Admin View: Integrate visual-search box
[ https://issues.apache.org/jira/browse/AMBARI-22670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330938#comment-16330938 ] Hudson commented on AMBARI-22670: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-22670 Ambari 3.0: Implement new design for Admin View: Integrate (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=72657b6f3888654266a4359089bf9ea8b6c97b6b]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/ambariViews/viewsList.html * (add) ambari-admin/src/main/resources/ui/admin-web/app/scripts/directives/comboSearch.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/remoteClusters/list.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/list.html * (add) ambari-admin/src/main/resources/ui/admin-web/app/styles/combo-search.css * (add) ambari-admin/src/main/resources/ui/admin-web/test/unit/controllers/ambariViews/ViewsListCtrl_test.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/index.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/ambariViews/ViewsListCtrl.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/styles/main.css * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/remoteClusters/RemoteClustersListCtrl.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsListCtrl.js * (add) ambari-admin/src/main/resources/ui/admin-web/test/unit/directives/comboSearch_test.js * (add) ambari-admin/src/main/resources/ui/admin-web/app/views/directives/comboSearch.html > Ambari 3.0: Implement new design for Admin View: Integrate visual-search box > > > Key: AMBARI-22670 > URL: https://issues.apache.org/jira/browse/AMBARI-22670 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22670.patch > > > * Integrate visual-search box > * Remove titles from above the table > * Hide pagination when total number of items less than 10 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22566) Upgrade Angular for Ambari Admin View
[ https://issues.apache.org/jira/browse/AMBARI-22566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330920#comment-16330920 ] Hudson commented on AMBARI-22566: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) Revert "AMBARI-22566. Upgrade Angular for Ambari Admin View (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=c2e5d091319fc51b7e95ddd14befe778ac70a2c0]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/app.js * (edit) ambari-admin/src/main/resources/ui/admin-web/bower.json * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsEditCtrl.js * (edit) ambari-admin/src/main/resources/ui/admin-web/package.json > Upgrade Angular for Ambari Admin View > - > > Key: AMBARI-22566 > URL: https://issues.apache.org/jira/browse/AMBARI-22566 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22566.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22644) Node Managers fail to start after Spark2 is patched due to CNF YarnShuffleService
[
https://issues.apache.org/jira/browse/AMBARI-22644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330933#comment-16330933
]
Hudson commented on AMBARI-22644:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-22644 - Node Managers fail to start after Spark2 is patched due (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7749e655e74c7bb4e3ada6b92943730c5e1b6e76])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/services/YARN/configuration/yarn-site.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/yarn-site.xml
* (edit)
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/params_linux.py
> Node Managers fail to start after Spark2 is patched due to CNF
> YarnShuffleService
> -
>
> Key: AMBARI-22644
> URL: https://issues.apache.org/jira/browse/AMBARI-22644
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.2
>
>
> *STR*
> # Deploy HDP-2.6.4.0 cluster with Ambari-2.6.1.0-114
> # Apply HBase patch Upgrade on the cluster (this step is optional)
> # Then apply Spark2 patch Upgrade on the cluster
> # Restart Node Managers
> *Result*
> NM restart fails with below error:
> {code}
> 2017-12-10 07:17:02,559 INFO impl.MetricsSystemImpl
> (MetricsSystemImpl.java:shutdown(606)) - NodeManager metrics system shutdown
> complete.
> 2017-12-10 07:17:02,559 FATAL nodemanager.NodeManager
> (NodeManager.java:initAndStartNodeManager(549)) - Error starting NodeManager
> org.apache.hadoop.service.ServiceStateException:
> java.lang.ClassNotFoundException:
> org.apache.spark.network.yarn.YarnShuffleService
> at
> org.apache.hadoop.service.ServiceStateException.convert(ServiceStateException.java:59)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:172)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.serviceInit(ContainerManagerImpl.java:245)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceInit(NodeManager.java:291)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:546)
> at
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:594)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.spark.network.yarn.YarnShuffleService
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxiliaryServiceWithCustomClassLoader.getInstance(AuxiliaryServiceWithCustomClassLoader.java:169)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices.serviceInit(AuxServices.java:131)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> ... 8 more
> 2017-12-10 07:17:02,562 INFO nodemanager.NodeManager
> (LogAdapter.java:info(45)) - SHUTDOWN_MSG:
> {code}
> The spark properties are correctly being written out as per AMBARI-22525.
> Initially, we had defined Spark properties for ATS like this:
> {code}
> yarn.nodemanager.aux-services.spark_shuffle.classpath
> {{stack_root}}/${hdp.version}/spark/aux/*
> {code}
> When YARN upgrades without Spark, we run into AMBARI-22525. Seems like the
> shuffle classes are installed as part of RPM dependencies, but not the
> SparkATSPlugin.
> So:
> - If we use YARN's version for the Spark classes, then ATS can't find
>
[jira] [Commented] (AMBARI-22640) HBase Cannot Find LZO Classes After Being Patched
[
https://issues.apache.org/jira/browse/AMBARI-22640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330932#comment-16330932
]
Hudson commented on AMBARI-22640:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-22640 - HBase Cannot Find LZO Classes After Being Patched (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=10711361ba2d158500b82b30662f2c062da1fee2])
* (edit)
ambari-server/src/main/resources/common-services/HBASE/2.0.0.3.0/package/scripts/hbase.py
* (edit)
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/hbase.py
> HBase Cannot Find LZO Classes After Being Patched
> -
>
> Key: AMBARI-22640
> URL: https://issues.apache.org/jira/browse/AMBARI-22640
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22640.patch
>
>
> After patching HBase where LZO compression is being used, the following is
> seen:
> {code}
> 2017-12-10 22:31:09,244|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|Exception in thread "main"
> java.lang.RuntimeException: java.lang.ClassNotFoundException:
> com.hadoop.compression.lzo.LzoCodec
> 2017-12-10 22:31:09,245|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> org.apache.hadoop.hbase.io.compress.Compression$Algorithm$1.buildCodec(Compression.java:130)
> 2017-12-10 22:31:09,245|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> org.apache.hadoop.hbase.io.compress.Compression$Algorithm$1.getCodec(Compression.java:116)
> 2017-12-10 22:31:09,245|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> org.apache.hadoop.hbase.io.compress.Compression$Algorithm.getCompressor(Compression.java:301)
> 2017-12-10 22:31:09,245|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> org.apache.hadoop.hbase.io.encoding.HFileBlockDefaultEncodingContext.(HFileBlockDefaultEncodingContext.java:90)
> 2017-12-10 22:31:09,245|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> org.apache.hadoop.hbase.io.hfile.HFileBlock$Writer.(HFileBlock.java:853)
> 2017-12-10 22:31:09,246|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> org.apache.hadoop.hbase.io.hfile.HFileWriterV2.finishInit(HFileWriterV2.java:121)
> 2017-12-10 22:31:09,246|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> org.apache.hadoop.hbase.io.hfile.HFileWriterV2.(HFileWriterV2.java:113)
> 2017-12-10 22:31:09,246|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> org.apache.hadoop.hbase.io.hfile.HFileWriterV3.(HFileWriterV3.java:67)
> 2017-12-10 22:31:09,246|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> org.apache.hadoop.hbase.io.hfile.HFileWriterV3$WriterFactoryV3.createWriter(HFileWriterV3.java:59)
> 2017-12-10 22:31:09,246|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> org.apache.hadoop.hbase.io.hfile.HFile$WriterFactory.create(HFile.java:325)
> 2017-12-10 22:31:09,246|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> org.apache.hadoop.hbase.util.CompressionTest.doSmokeTest(CompressionTest.java:127)
> 2017-12-10 22:31:09,247|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> org.apache.hadoop.hbase.util.CompressionTest.main(CompressionTest.java:160)
> 2017-12-10 22:31:09,247|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|Caused by:
> java.lang.ClassNotFoundException: com.hadoop.compression.lzo.LzoCodec
> 2017-12-10 22:31:09,247|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> 2017-12-10 22:31:09,247|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> 2017-12-10 22:31:09,247|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> 2017-12-10 22:31:09,248|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
> java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> 2017-12-10 22:31:09,248|INFO|MainThread|machine.py:164 -
> run()||GUID=37b565a7-e164-4641-b335-19884c614ffd|at
>
[jira] [Commented] (AMBARI-22672) Error on add version view in web admin
[ https://issues.apache.org/jira/browse/AMBARI-22672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330939#comment-16330939 ] Hudson commented on AMBARI-22672: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-22672. Error on add version view in web admin (alexantonenko) (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=e077bd2793826205eb5a300dde25eb75569c3cfd]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js > Error on add version view in web admin > -- > > Key: AMBARI-22672 > URL: https://issues.apache.org/jira/browse/AMBARI-22672 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22672.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-21222) Update LDAP sync process to work with improved user management facility
[ https://issues.apache.org/jira/browse/AMBARI-21222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330916#comment-16330916 ] Hudson commented on AMBARI-21222: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-21222. Update LDAP sync process to work with improved user (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=d459d1304e5efd1c9d64a65342ecf0696b9d329f]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UserAuthenticationDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/ldap/LdapBatchDto.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulator.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UserPrivilegeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UserAuthenticationEntity.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulatorTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java > Update LDAP sync process to work with improved user management facility > --- > > Key: AMBARI-21222 > URL: https://issues.apache.org/jira/browse/AMBARI-21222 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-21222_branch-feature-AMBARI-20859_01.patch > > > Update LDAP sync process to work with improved user management facility -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-21680) Prevent users from authenticating if they exceed a configured number of login failures
[ https://issues.apache.org/jira/browse/AMBARI-21680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330911#comment-16330911 ] Hudson commented on AMBARI-21680: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-21680. Prevent users from authenticating if they exceed a (amagyar: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=3cefb74cdae3a836ee1896a30dca713e44b95f98]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariLocalUserProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationEventHandlerImpl.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js * (add) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/TooManyLoginFailuresException.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/User.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/users/UsersShowCtrl.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UserResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLocalUserProviderTest.java * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/users/show.html * (edit) ambari-server/docs/configuration/index.md * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/UserRequest.java > Prevent users from authenticating if they exceed a configured number of login > failures > -- > > Key: AMBARI-21680 > URL: https://issues.apache.org/jira/browse/AMBARI-21680 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-21680.patch > > > Prevent users from authenticating if they exceed a configured number of login > failures, which is set as a configuration in the ambari.properties file - > authentication.max.failures. > After a users successfully authenticates, check the value of > org.apache.ambari.server.orm.entities.UserEntity#getConsecutiveFailures. > If it exceeds the value set in authentication.max.failures, then fail > authentication. Else allow authentication to proceed. > If failing authentication due to being "locked out", do not indicate this to > the user; however an Ambari server log message will be useful. > The normal "authentication failed" message should be returned as to not give > away any information about a user's authentication. > If a special "locked out" message is shown, then a hacker will be able to > attempt a brute force attack on a user's account since the returned error > message will be different if they eventually succeed in guessing the password. > To "unlock" the user, a user administrator (a user with the > AMBARI.MANAGE_USERS authorization) needs to reset the user's consecutive > failure count to 0. > By default the authentication.max.failures should be 10; however 0 should > indicate that no lockout is desired. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-21221) Update Pam Authentication process to work with improved user management facility
[ https://issues.apache.org/jira/browse/AMBARI-21221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330914#comment-16330914 ] Hudson commented on AMBARI-21221: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-21221. Update Pam Authentication process to work with improved (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=d6b271e6bbcafbe57831890c9f8aa5386a57c8c3]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/InvalidUsernamePasswordCombinationException.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java * (add) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/pam/AmbariPamAuthenticationProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariBasicAuthenticationFilter.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariLocalAuthenticationProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/pam/PamAuthenticationFactory.java * (edit) ambari-server/docs/configuration/index.md * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/jwt/AmbariJwtAuthenticationProvider.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariPamAuthenticationProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/TooManyLoginFailuresException.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/kerberos/AmbariKerberosAuthenticationFilter.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariPamAuthenticationProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationException.java * (add) ambari-server/src/test/java/org/apache/ambari/server/security/authentication/pam/AmbariPamAuthenticationProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AccountDisabledException.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/jwt/AmbariJwtAuthenticationFilter.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/UserNotFoundException.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/PamAuthenticationException.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationEventHandlerImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationProvider.java > Update Pam Authentication process to work with improved user management > facility > - > > Key: AMBARI-21221 > URL: https://issues.apache.org/jira/browse/AMBARI-21221 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-21221_branch-feature-AMBARI-20859_01.patch > > > Update Pam Authentication process to work with improved user management > facility -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-21217) Update JWT Authentication process to work with improved user management facility
[ https://issues.apache.org/jira/browse/AMBARI-21217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330913#comment-16330913 ] Hudson commented on AMBARI-21217: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-21217. Update JWT Authentication process to work with improved (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=553e4f9d25573c54860d08b0494caefd77398977]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (add) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/jwt/JwtAuthenticationToken.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariUserAuthorizationFilter.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationFilter.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/jwt/JwtAuthenticationPropertiesTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AbstractAuthenticationProviderTest.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariUserAuthentication.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariPamAuthenticationProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationEventHandlerImpl.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/jwt/JwtAuthentication.java * (add) ambari-server/src/test/java/org/apache/ambari/server/security/authentication/jwt/AmbariJwtAuthenticationFilterTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/AmbariErrorHandler.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/SecurityHelperImplTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariLocalAuthenticationProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariLocalAuthenticationProvider.java * (add) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariUserAuthentication.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariBasicAuthenticationFilter.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/UserNotFoundException.java * (add) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/jwt/JwtAuthenticationProperties.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AuthorizationHelperTest.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/jwt/JwtAuthenticationFilterTest.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/jwt/JwtAuthenticationProperties.java * (edit) ambari-server/src/main/resources/webapp/WEB-INF/spring-security.xml * (delete) ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariJWTAuthenticationFilterTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/jwt/AmbariJwtAuthenticationFilter.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulator.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariJWTAuthenticationFilter.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/kerberos/AmbariKerberosAuthenticationFilter.java * (add) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/jwt/AmbariJwtAuthenticationProvider.java * (add) ambari-server/src/test/java/org/apache/ambari/server/security/authentication/jwt/JwtAuthenticationPropertiesTest.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/jwt/JwtAuthenticationFilter.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariPamAuthenticationProviderTest.java > Update JWT Authentication process to work with improved user management > facility > > > Key: AMBARI-21217 > URL: https://issues.apache.org/jira/browse/AMBARI-21217 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert
[jira] [Commented] (AMBARI-21216) Add support for consecutive login failure accounting
[
https://issues.apache.org/jira/browse/AMBARI-21216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330909#comment-16330909
]
Hudson commented on AMBARI-21216:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-21216. Add support for consecutive login failure accounting (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=f760516c24478b19d4e579cb67702d9d43251eaa])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authentication/UserNotFoundException.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UserEntity.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/audit/event/LoginAuditEvent.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariJWTAuthenticationFilterTest.java
* (edit) ambari-server/src/main/resources/webapp/WEB-INF/spring-security.xml
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderForDNWithSpaceTest.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/security/authentication/InvalidUsernamePasswordCombinationException.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/audit/LoginAuditEventTest.java
* (delete)
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/InvalidUsernamePasswordCombinationException.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/jwt/JwtAuthenticationFilter.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authentication/kerberos/AmbariKerberosAuthenticationFilter.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariBasicAuthenticationFilter.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (add)
ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationEventHandler.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationException.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariBasicAuthenticationFilterTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariLocalUserProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariJWTAuthenticationFilter.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/internal/AmbariInternalAuthenticationProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationProviderDisableUserTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authentication/kerberos/AmbariKerberosAuthenticationFilterTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthoritiesPopulator.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLocalUserProviderTest.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationEventHandlerImpl.java
> Add support for consecutive login failure accounting
>
>
> Key: AMBARI-21216
> URL: https://issues.apache.org/jira/browse/AMBARI-21216
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: AMBARI-21216_branch-feature-AMBARI-20859_01.patch,
> AMBARI-21216_branch-feature-AMBARI-20859_02.patch,
> AMBARI-21216_branch-feature-AMBARI-20859_03.patch
>
>
> Add support for consecutive login failure accounting where as log-in failures
> should increment the {{users.consecutive_failures}} and
[jira] [Commented] (AMBARI-21223) Update Kerberos Authentication process to work with improved user management facility
[ https://issues.apache.org/jira/browse/AMBARI-21223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330915#comment-16330915 ] Hudson commented on AMBARI-21223: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-21223. Update Kerberos Authentication process to work with (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=ceead22412dc4385fe837884594e5aad57b884d7]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UserAuthenticationEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/kerberos/AmbariAuthToLocalUserDetailsService.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AbstractAuthenticationProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/pam/AmbariPamAuthenticationProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationProvider.java * (edit) ambari-server/src/main/python/ambari_server/kerberos_setup.py * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authentication/jwt/AmbariJwtAuthenticationFilterTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariLocalAuthenticationProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/jwt/AmbariJwtAuthenticationProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authentication/kerberos/AmbariAuthToLocalUserDetailsServiceTest.java * (edit) ambari-server/src/main/python/ambari-server.py * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authentication/pam/AmbariPamAuthenticationProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/kerberos/AmbariKerberosAuthenticationProperties.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/configuration/ConfigurationTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserAuthenticationSourceResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UserAuthenticationDAO.java > Update Kerberos Authentication process to work with improved user management > facility > - > > Key: AMBARI-21223 > URL: https://issues.apache.org/jira/browse/AMBARI-21223 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-21223_branch-feature-AMBARI-20859_01.patch > > > Update Kerberos Authentication process to work with improved user management > facility -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-20861) BE: Extend Ambari REST API to Support User Account Management Improvements
[ https://issues.apache.org/jira/browse/AMBARI-20861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330910#comment-16330910 ] Hudson commented on AMBARI-20861: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-20861. BE: Extend Ambari REST API to Support User Account (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=317905e40e0b4b384809ad7d900a09d97827f599]) * (add) ambari-server/docs/api/v1/user-get.md * (add) ambari-server/docs/api/v1/authentication-source-create.md * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/UserRequestUpdateUserSwagger.java * (add) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserAuthenticationSourceResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/resources/UserResourceDefinitionTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/BaseService.java * (add) ambari-server/docs/api/v1/user-create.md * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractControllerResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UserAuthenticationDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/users/UserService.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/UserAuthenticationSourceRequestCreateSwagger.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestImplTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UserResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/UserAuthenticationSourceResponse.java * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UserAuthenticationSourceResourceProvider.java * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/UserRequestCreateUsersSwagger.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/resources/UserResourceDefinition.java * (add) ambari-server/docs/api/v1/user-resources.md * (edit) ambari-server/docs/api/v1/index.md * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/UserAuthenticationSourceRequest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java * (add) ambari-server/docs/api/v1/authentication-source-resources.md * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserResourceProviderTest.java * (add) ambari-server/docs/api/v1/authentication-source-delete.md * (add) ambari-server/docs/api/v1/user-list.md * (add) ambari-server/docs/api/v1/user-update.md * (add) ambari-server/src/main/java/org/apache/ambari/server/api/services/users/UserAuthenticationSourceService.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/ResourceProviderFactory.java * (add) ambari-server/docs/api/v1/authentication-source-update.md * (add) ambari-server/docs/api/v1/user-delete.md * (edit) ambari-server/docs/api/generated/swagger.json * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/UserRequestCreateUserSwagger.java * (add) ambari-server/docs/api/v1/authentication-source-get.md * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/UserResponse.java * (edit) ambari-server/docs/api/generated/index.html * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/TestAuthenticationFactory.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UserAuthenticationEntity.java * (add) ambari-server/docs/api/v1/authentication-source-list.md * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/UserRequest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/TestUsers.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserResourceProviderDBTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/UserAuthenticationSourceRequestUpdateSwagger.java * (edit) ambari-server/src/main/resources/properties.json > BE: Extend Ambari REST API to Support User Account Management Improvements > -- > > Key: AMBARI-20861 > URL: https://issues.apache.org/jira/browse/AMBARI-20861 > Project: Ambari > Issue Type: Task >
[jira] [Commented] (AMBARI-21220) Update Local Authentication process to work with improved user management facility
[ https://issues.apache.org/jira/browse/AMBARI-21220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330912#comment-16330912 ] Hudson commented on AMBARI-21220: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-21220. Update Local Authentication process to work with improved (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=e1699b09265e54392ec246a17deec5043f76f54a]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationEventHandlerImpl.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariLocalUserProvider.java * (edit) ambari-server/docs/configuration/index.md * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (add) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariLocalAuthenticationProvider.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationProviderDisableUserTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java * (add) ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariLocalAuthenticationProviderTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationProvider.java * (add) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AccountDisabledException.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLocalUserProviderTest.java * (add) ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AbstractAuthenticationProviderTest.java > Update Local Authentication process to work with improved user management > facility > -- > > Key: AMBARI-21220 > URL: https://issues.apache.org/jira/browse/AMBARI-21220 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-21220_branch-feature-AMBARI-20859_01.patch, > AMBARI-21220_branch-feature-AMBARI-20859_02.patch > > > Update Local Authentication process to work with improved user management > facility -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-21147) Update Database Access Layer to Support New Database Schema for Improved User Account Management
[ https://issues.apache.org/jira/browse/AMBARI-21147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330908#comment-16330908 ] Hudson commented on AMBARI-21147: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-21147. Update Database Access Layer to Support New Database (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=f76c87a699dad1b5a85f6fc13fd76b82818c6e58]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/internal/AmbariInternalAuthenticationProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserPrivilegeResourceProviderTest.java * (edit) ambari-server/docs/api/generated/swagger.json * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariUserAuthenticationFilterTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/kerberos/AmbariKerberosAuthenticationProperties.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariUserAuthorizationFilter.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulatorTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariJWTAuthenticationFilter.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ActiveWidgetLayoutResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UserResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilter.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/GroupPrivilegeResourceProviderTest.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/UserType.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariPamAuthenticationProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UserDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementController.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariPamAuthenticationProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UserEntity.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ActiveWidgetLayoutResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLocalUserProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/jwt/JwtAuthenticationFilterTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/ResourceProviderFactory.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/UserResponse.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/orm/OrmTestHelper.java * (add) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UserAuthenticationDAO.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariJWTAuthenticationFilterTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthoritiesPopulator.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderForDNWithSpaceTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProvider.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/jwt/AuthenticationJwtUserNotFoundException.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/TestUsers.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/UsersTest.java * (edit)
[jira] [Commented] (AMBARI-20907) Create Database Schema for Improved User Account Management
[
https://issues.apache.org/jira/browse/AMBARI-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330907#comment-16330907
]
Hudson commented on AMBARI-20907:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-20907. Create Database Schema for Improved User Account (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7460cebf90e8f77b3b14457a64423ebc3ba028cc])
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
> Create Database Schema for Improved User Account Management
> ---
>
> Key: AMBARI-20907
> URL: https://issues.apache.org/jira/browse/AMBARI-20907
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: user_management
> Fix For: 3.0.0
>
> Attachments: AMBARI-20907_branch-feature-AMBARI-20859.patch,
> AMBARI-20907_branch-feature-AMBARI-20859_02.patch
>
>
> User management tables in the DB should be:
> *{{users}}*
> ||Name||Type||Description||
> |user_id|INTEGER|Internal unique identifier|
> |principal_id|INTEGER|Foreign key from adminprincipal table|
> |user_name|VARCHAR|Unique, case-insensitive, login identifier expected to be
> used when logging into Ambari|
> |active|BOOLEAN|Active/not active flag|
> |consecutive_failures|INTEGER|The number a failed authorization attempts
> since the last successful authentication|
> |active_widgets_layout|VARCHAR| |
> |display_name|VARCHAR|Cosmetic name value to show the user in user interfaces|
> |local_username|VARCHAR|Case-sensitive username to use when impersonating
> user in facilities like Ambari Views|
> |create_time|TIMESTAMP|Creation time for this account in Ambari|
> * Primary Key: {{user_id}}
> * Foreign Key: {{principal_id}} -> {{adminprincipal.principal_id}}
> *{{user_authentication}}*
> ||Name||Type||Description||
> |user_authentication_id|INTEGER|Primary key for this table|
> |user_id|INTEGER|Foreign key from users table|
> |authentication_type|VARCHAR|Type of authentication system - LOCAL, LDAP,
> KERBEROS, JTW, PAM, etc...
> |authentication_key|VARCHAR|Type-specific key (or identifier):
> * LOCAL: the user's password (digest)
> * LDAP: the user’s distinguished name
> * KERBEROS: the user’s principal
> * etc...|
> |create_time|TIMESTAMP|Creation time of this record
> |update_time|TIMESTAMP|Update time for this record, can be used to enforce
> password retention times|
> * Primary Key: {{user_authentication_id}}
> * Foreign Key: {{user_id}} -> {{users.user_id}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22805) Blueprints do not handle some failures properly
[
https://issues.apache.org/jira/browse/AMBARI-22805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22805:
Labels: blueprints pull-request-available (was: blueprints)
> Blueprints do not handle some failures properly
> ---
>
> Key: AMBARI-22805
> URL: https://issues.apache.org/jira/browse/AMBARI-22805
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: blueprints, pull-request-available
> Fix For: 2.6.2
>
>
> Failures in the cluster configuration task and topology host tasks during
> blueprint cluster deployment or upscaling are not visible via request status.
> The logical request stays PENDING even after Ambari Server gave up retrying.
> Both the fact that it no longer makes progress and any reason of the failure
> can be seen only in {{ambari-server.log}}.
> Some ways to reproduce (all via blueprints):
> * Create cluster with ZooKeeper and HDFS, but omit the NAMENODE component
> * Create a secure cluster with wrong Kerberos credentials
> * Create a secure cluster without storing Kerberos credentials, restart
> Ambari Server, add a new node
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22725) Expose Conditional Elements For Tasks on Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-22725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22725:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Expose Conditional Elements For Tasks on Upgrade
>
>
> Key: AMBARI-22725
> URL: https://issues.apache.org/jira/browse/AMBARI-22725
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Attachments: AMBARI-22725.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Some upgrade tasks, such as configuration tasks, need to leverage the
> conditional elements which change the flow of control if the cluster is
> Kerberized (or based on other configuration values). For example, today we
> have this:
> {code:java}
> title="Calculating Proxy Properties under kms-site">
>
>class="org.apache.ambari.server.serveraction.upgrades.RangerKmsProxyConfig"/>
> {code}
>
> Where {{condition}} elements can be added to an {{execute-stage}} or a
> {{group}}. However, since {{execute-stage}} may only contain one task, it
> makes doing this work on a per-task level impossible. This particularly
> impacts the {{processing}} element. We want something like this:
> {code:java}
>
>
>
> {code}
>
> So that {{task}} elements defined in the {{pre-upgrade}} section of
> {{processing}} can also be conditionally invoked.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22803) Update Hadoop RPC Encryption Properties During Kerberization and Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-22803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22803:
-
Affects Version/s: (was: 3.0.0)
2.6.2
> Update Hadoop RPC Encryption Properties During Kerberization and Upgrade
>
>
> Key: AMBARI-22803
> URL: https://issues.apache.org/jira/browse/AMBARI-22803
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.2
>
>
> Clients should have the ability to choose encrypted communication over RPC
> when talking to core hadoop components. Today, the properties that control
> this are:
> - {{core-site.xml : hadoop.rpc.protection = authentication}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
> The new value of {{privacy}} enables clients to choose an encrypted means of
> communication. By keeping {{authentication}} first, it will be taken as the
> default mechanism so that wire encryption is not automatically enabled by
> accident.
> The following properties should be changed to add {{privacy}}:
> - {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
> The following are cases when this needs to be performed:
> - During Kerberization, the above two properties should be automatically
> reconfigured.
> - During a stack upgrade to any version of HDP 2.6, they should be
> automatically merged
> Blueprint deployment is not a scenario being covered here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22803) Update Hadoop RPC Encryption Properties During Kerberization and Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-22803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22803:
-
Fix Version/s: (was: 3.0.0)
2.6.2
> Update Hadoop RPC Encryption Properties During Kerberization and Upgrade
>
>
> Key: AMBARI-22803
> URL: https://issues.apache.org/jira/browse/AMBARI-22803
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.2
>
>
> Clients should have the ability to choose encrypted communication over RPC
> when talking to core hadoop components. Today, the properties that control
> this are:
> - {{core-site.xml : hadoop.rpc.protection = authentication}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
> The new value of {{privacy}} enables clients to choose an encrypted means of
> communication. By keeping {{authentication}} first, it will be taken as the
> default mechanism so that wire encryption is not automatically enabled by
> accident.
> The following properties should be changed to add {{privacy}}:
> - {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
> The following are cases when this needs to be performed:
> - During Kerberization, the above two properties should be automatically
> reconfigured.
> - During a stack upgrade to any version of HDP 2.6, they should be
> automatically merged
> Blueprint deployment is not a scenario being covered here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22751) JS error at Review step on Move Master wizard
[
https://issues.apache.org/jira/browse/AMBARI-22751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330542#comment-16330542
]
Pravin Dsilva commented on AMBARI-22751:
[~nc...@hortonworks.com] This issue prevents me from testing the
multi-architecture cluster (hybrid) setup as I am unable to move services for
some test scenarios. Is there somebody who could look at this?
> JS error at Review step on Move Master wizard
> -
>
> Key: AMBARI-22751
> URL: https://issues.apache.org/jira/browse/AMBARI-22751
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Sneha Kanekar
>Priority: Major
>
> JS error is seen at Review step while moving services from one host to
> another. The error message is as follows:
> {code:borderStyle=solid}
> Uncaught TypeError: this.get(...).someProperty is not a function
> at eval (eval at (app.js:194640), :1:22)
> at Class. (app.js:194640)
> at ComputedPropertyPrototype.get (vendor.js:14954)
> at get (vendor.js:13360)
> at Class._classStringForProperty (vendor.js:24661)
> at Class. (vendor.js:24592)
> at Array.forEach ()
> at forEach (vendor.js:12450)
> at Class._applyClassNameBindings (vendor.js:24559)
> at Class.applyAttributesToBuffer (vendor.js:25133)
> {code}
> This error occurs as this.get('mainView.columns') is undefined:
> {code:borderStyle=solid}
> var isFilterActive = this.get('mainView.columns').someProperty('selected');
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-9016) API not taking or responding with application/json
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330539#comment-16330539
]
Thomas Decaux commented on AMBARI-9016:
---
It looks like something else is doing the JSON decode before:
{code:java}
18 Jan 2018 14:47:36,681 ERROR [ambari-client-thread-27] ContainerResponse:419
- The RuntimeException could not be mapped to a response, re-throwing to the
HTTP container
com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected
a string but was BEGIN_ARRAY at line 1 column 2
at com.google.gson.Gson.fromJson(Gson.java:806)
at com.google.gson.Gson.fromJson(Gson.java:761)
at
org.apache.ambari.server.api.GsonJsonProvider.readFrom(GsonJsonProvider.java:60)
at
com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
at
com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
at
com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:203)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409){code}
> API not taking or responding with application/json
> --
>
> Key: AMBARI-9016
> URL: https://issues.apache.org/jira/browse/AMBARI-9016
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Sean Roberts
>Priority: Minor
> Labels: newbie
>
> The stack advisor API does not accept application/json even though it
> expects JSON files.
> And it responds with "text/plain" even though the content it is sending is
> JSON.
> This breaks most any http library or application. Such as those made to work
> with RESTful APIs.
> The API does not accept JSON and when it responds with JSON it says it's
> "text/plain":
> {code}
> $ curl -v -u admin\
> -H "Content-Type: application/json" -H x-requested-by:useless \
> http://localhost:8080/api/v1/stacks/HDP/versions/2.4/recommendations -d
> @temp.json
> < HTTP/1.1 500 Server Error
> < Content-Type: text/plain; charset=ISO-8859-1
> {
> "status": 500,
> "message": "Server Error"
> }
> {code}
> Meanwhile it accepts JSON as text/plain and still responds with "text/plain"
> even though it is sending JSON:
> {code}
> $ curl -v -u admin\
> -H "Content-Type: test/plain" -H x-requested-by:useless \
> http://localhost:8080/api/v1/stacks/HDP/versions/2.4/recommendations -d
> @temp.json
> > POST /api/v1/stacks/HDP/versions/2.4/recommendations HTTP/1.1
> > Content-Type: test/plain
> < HTTP/1.1 200 OK
> < Content-Type: text/plain
> {
> "resources" : [
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.4/recommendations/8;,
> ... snipped the rest of the JSON since it's not needed ...
> {code}
> This is the file that was sent:
> {code}
> $ cat temp.json
> {
> "recommend" : "configurations",
> "services" : [
> "AMBARI_METRICS","HDFS","HIVE","MAPREDUCE2","PIG","TEZ","YARN","ZOOKEEPER" ],
> "hosts" : [
> "ip-10-0-1-159.ec2.internal","ip-10-0-1-31.ec2.internal","ip-10-0-1-32.ec2.internal","ip-10-0-1-33.ec2.internal"
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22810) Rewrite TestActionQueue
[ https://issues.apache.org/jira/browse/AMBARI-22810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22810: Labels: pull-request-available (was: ) > Rewrite TestActionQueue > --- > > Key: AMBARI-22810 > URL: https://issues.apache.org/jira/browse/AMBARI-22810 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Attachments: AMBARI-22810.patch > > > Because of branch-3.0-perf changes ActionQueue had some big chunks completely > rewritten. > Which causes all TestActionQueue unit tests to fail. > For these changes the TestActionQueue tests have to be rewritten as well. Some > deleted due to already non-existant functionality like the one related to > status commands execution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22809) Tez shown in red in the left nav for no apparent reason
[ https://issues.apache.org/jira/browse/AMBARI-22809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22809: - Status: Patch Available (was: Open) > Tez shown in red in the left nav for no apparent reason > --- > > Key: AMBARI-22809 > URL: https://issues.apache.org/jira/browse/AMBARI-22809 > Project: Ambari > Issue Type: Bug > Components: ambari-client >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Tez is showing in red because it is in "INSTALLED" state, but it is client > only service. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22811) Rewrite tests for alert types on branch-3.0-perf
[ https://issues.apache.org/jira/browse/AMBARI-22811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22811: - Status: Patch Available (was: Open) > Rewrite tests for alert types on branch-3.0-perf > > > Key: AMBARI-22811 > URL: https://issues.apache.org/jira/browse/AMBARI-22811 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22811.patch > > > Configuration synching as well as some other config aspects changes in alerts > in scope of branch-3.0-perf. The tests are currently failing. Have to reflect > the changes in UT. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22811) Rewrite tests for alert types on branch-3.0-perf
[ https://issues.apache.org/jira/browse/AMBARI-22811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22811: - Attachment: AMBARI-22811.patch > Rewrite tests for alert types on branch-3.0-perf > > > Key: AMBARI-22811 > URL: https://issues.apache.org/jira/browse/AMBARI-22811 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22811.patch > > > Configuration synching as well as some other config aspects changes in alerts > in scope of branch-3.0-perf. The tests are currently failing. Have to reflect > the changes in UT. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22810) Rewrite TestActionQueue
[ https://issues.apache.org/jira/browse/AMBARI-22810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22810: - Attachment: AMBARI-22810.patch > Rewrite TestActionQueue > --- > > Key: AMBARI-22810 > URL: https://issues.apache.org/jira/browse/AMBARI-22810 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22810.patch > > > Because of branch-3.0-perf changes ActionQueue had some big chunks completely > rewritten. > Which causes all TestActionQueue unit tests to fail. > For these changes the TestActionQueue tests have to be rewritten as well. Some > deleted due to already non-existant functionality like the one related to > status commands execution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22811) Rewrite tests for alert types on branch-3.0-perf
Andrew Onischuk created AMBARI-22811: Summary: Rewrite tests for alert types on branch-3.0-perf Key: AMBARI-22811 URL: https://issues.apache.org/jira/browse/AMBARI-22811 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 3.0.0 Configuration synching as well as some other config aspects changes in alerts in scope of branch-3.0-perf. The tests are currently failing. Have to reflect the changes in UT. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22810) Rewrite TestActionQueue
[ https://issues.apache.org/jira/browse/AMBARI-22810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22810: - Status: Patch Available (was: Open) > Rewrite TestActionQueue > --- > > Key: AMBARI-22810 > URL: https://issues.apache.org/jira/browse/AMBARI-22810 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22810.patch > > > Because of branch-3.0-perf changes ActionQueue had some big chunks completely > rewritten. > Which causes all TestActionQueue unit tests to fail. > For these changes the TestActionQueue tests have to be rewritten as well. Some > deleted due to already non-existant functionality like the one related to > status commands execution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22810) Rewrite TestActionQueue
Andrew Onischuk created AMBARI-22810: Summary: Rewrite TestActionQueue Key: AMBARI-22810 URL: https://issues.apache.org/jira/browse/AMBARI-22810 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 3.0.0 Attachments: AMBARI-22810.patch Because of branch-3.0-perf changes ActionQueue had some big chunks completely rewritten. Which causes all TestActionQueue unit tests to fail. For these changes the TestActionQueue tests have to be rewritten as well. Some deleted due to already non-existant functionality like the one related to status commands execution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22809) Tez shown in red in the left nav for no apparent reason
[ https://issues.apache.org/jira/browse/AMBARI-22809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22809: Labels: pull-request-available (was: ) > Tez shown in red in the left nav for no apparent reason > --- > > Key: AMBARI-22809 > URL: https://issues.apache.org/jira/browse/AMBARI-22809 > Project: Ambari > Issue Type: Bug > Components: ambari-client >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > Tez is showing in red because it is in "INSTALLED" state, but it is client > only service. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22809) Tez shown in red in the left nav for no apparent reason
Antonenko Alexander created AMBARI-22809: Summary: Tez shown in red in the left nav for no apparent reason Key: AMBARI-22809 URL: https://issues.apache.org/jira/browse/AMBARI-22809 Project: Ambari Issue Type: Bug Components: ambari-client Affects Versions: 3.0.0 Reporter: Antonenko Alexander Fix For: 3.0.0 Tez is showing in red because it is in "INSTALLED" state, but it is client only service. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22809) Tez shown in red in the left nav for no apparent reason
[ https://issues.apache.org/jira/browse/AMBARI-22809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-22809: Assignee: Antonenko Alexander > Tez shown in red in the left nav for no apparent reason > --- > > Key: AMBARI-22809 > URL: https://issues.apache.org/jira/browse/AMBARI-22809 > Project: Ambari > Issue Type: Bug > Components: ambari-client >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 3.0.0 > > > Tez is showing in red because it is in "INSTALLED" state, but it is client > only service. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22808) Ambari-Web: Fix randomly failing unit tests
[ https://issues.apache.org/jira/browse/AMBARI-22808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22808: Labels: pull-request-available (was: ) > Ambari-Web: Fix randomly failing unit tests > --- > > Key: AMBARI-22808 > URL: https://issues.apache.org/jira/browse/AMBARI-22808 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22808) Ambari-Web: Fix randomly failing unit tests
Andrii Tkach created AMBARI-22808: - Summary: Ambari-Web: Fix randomly failing unit tests Key: AMBARI-22808 URL: https://issues.apache.org/jira/browse/AMBARI-22808 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22807) Admin View: Add/Delete Group succeeds, but the group table does not refresh automatically
[ https://issues.apache.org/jira/browse/AMBARI-22807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22807: - Status: Patch Available (was: Open) > Admin View: Add/Delete Group succeeds, but the group table does not refresh > automatically > - > > Key: AMBARI-22807 > URL: https://issues.apache.org/jira/browse/AMBARI-22807 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22807) Admin View: Add/Delete Group succeeds, but the group table does not refresh automatically
[ https://issues.apache.org/jira/browse/AMBARI-22807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22807: Labels: pull-request-available (was: ) > Admin View: Add/Delete Group succeeds, but the group table does not refresh > automatically > - > > Key: AMBARI-22807 > URL: https://issues.apache.org/jira/browse/AMBARI-22807 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22807) Admin View: Add/Delete Group succeeds, but the group table does not refresh automatically
[ https://issues.apache.org/jira/browse/AMBARI-22807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-22807: Assignee: Antonenko Alexander > Admin View: Add/Delete Group succeeds, but the group table does not refresh > automatically > - > > Key: AMBARI-22807 > URL: https://issues.apache.org/jira/browse/AMBARI-22807 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22807) Admin View: Add/Delete Group succeeds, but the group table does not refresh automatically
Antonenko Alexander created AMBARI-22807: Summary: Admin View: Add/Delete Group succeeds, but the group table does not refresh automatically Key: AMBARI-22807 URL: https://issues.apache.org/jira/browse/AMBARI-22807 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: 3.0.0 Reporter: Antonenko Alexander Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22792) Refactor agent-side kerberos code
[ https://issues.apache.org/jira/browse/AMBARI-22792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330375#comment-16330375 ] Hudson commented on AMBARI-22792: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8612 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8612/]) AMBARI-22792. Refactor agent-side kerberos code (echekanskiy) (echekanskiy: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=1a6548a69970446bda994e89b76cc9cee92860c6]) * (delete) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/package/scripts/utils.py * (edit) ambari-server/src/test/python/stacks/2.2/KERBEROS/test_kerberos_client.py * (add) ambari-common/src/main/python/ambari_commons/kerberos/utils.py * (edit) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/package/scripts/kerberos_client.py * (edit) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/package/scripts/service_check.py * (delete) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/package/scripts/utils.py * (add) ambari-common/src/main/python/ambari_commons/kerberos/__init__.py * (edit) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_client.py * (edit) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/package/scripts/params.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/ConfigureAmbariIdentitiesServerAction.java * (delete) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_common.py * (edit) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/package/scripts/service_check.py * (add) ambari-common/src/main/python/ambari_commons/kerberos/kerberos_common.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java * (delete) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/package/scripts/kerberos_common.py > Refactor agent-side kerberos code > - > > Key: AMBARI-22792 > URL: https://issues.apache.org/jira/browse/AMBARI-22792 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22806) Unable to delete files from HDFS using Ambari File View when Ambari Views is accessed via Knox
[ https://issues.apache.org/jira/browse/AMBARI-22806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22806: Labels: pull-request-available (was: ) > Unable to delete files from HDFS using Ambari File View when Ambari Views is > accessed via Knox > -- > > Key: AMBARI-22806 > URL: https://issues.apache.org/jira/browse/AMBARI-22806 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 3.0.0, 2.5.0, 2.6.0 > Environment: Unable to delete files from HDFS using Ambari File View > when Ambari Views is accessed via Knox >Reporter: venkat >Assignee: venkat >Priority: Blocker > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
