[jira] [Created] (AMBARI-23384) PQS start fails after Ambari upgrade due to Bad file descriptor
Vivek Sharma created AMBARI-23384:
-
Summary: PQS start fails after Ambari upgrade due to Bad file
descriptor
Key: AMBARI-23384
URL: https://issues.apache.org/jira/browse/AMBARI-23384
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Vivek Sharma
Assignee: Attila Magyar
Fix For: 2.7.0
*STR*
PQS start after Ambari upgrade to 2.7.0 failed with below error:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/phoenix_queryserver.py",
line 81, in
PhoenixQueryServer().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 356, in execute
self.execute_prefix_function(self.command_name, 'post', env)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 377, in execute_prefix_function
method(env)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 419, in post_start
raise Fail("Pid file \{0} doesn't exist after starting of the
component.".format(pid_file))
resource_management.core.exceptions.Fail: Pid file
/var/run/hbase/phoenix-hbase-server.pid doesn't exist after starting of the
component.
{code}
The log says the following:
{code}
2018-03-26 16:33:13.563112 launching /base/tools/jdk1.8.0_112/bin/java -cp
/usr/hdp/current/hbase-client/conf:/etc/hadoop/conf:/grid/0/hdp/2.6.4.0-91/phoenix/bin/../phoenix-4.7.0.2.6.4.0-91-client.jar:/grid/0/hdp/2.6.4.0-91/phoenix/bin/../phoenix-4.7.0.2.6.4.0-91-queryserver.jar:/usr/hdp/2.6.4.0-91/hadoop/conf:/usr/hdp/2.6.4.0-91/hadoop/lib/*:/usr/hdp/2.6.4.0-91/hadoop/.//*:/usr/hdp/2.6.4.0-91/hadoop-hdfs/./:/usr/hdp/2.6.4.0-91/hadoop-hdfs/lib/*:/usr/hdp/2.6.4.0-91/hadoop-hdfs/.//*:/usr/hdp/2.6.4.0-91/hadoop-yarn/lib/*:/usr/hdp/2.6.4.0-91/hadoop-yarn/.//*:/usr/hdp/2.6.4.0-91/hadoop-mapreduce/lib/*:/usr/hdp/2.6.4.0-91/hadoop-mapreduce/.//*::mysql-connector-java-5.1.33-bin.jar:mysql-connector-java.jar:/grid/0/hdp/2.6.4.0-91/tez/*:/grid/0/hdp/2.6.4.0-91/tez/lib/*:/grid/0/hdp/2.6.4.0-91/tez/conf
-Dproc_phoenixserver
-Dlog4j.configuration=file:/grid/0/hdp/2.6.4.0-91/phoenix/bin/log4j.properties
-Dpsql.root.logger=INFO,DRFA -Dpsql.log.dir=/grid/0/log/hbase
-Dpsql.log.file=phoenix-hbase-server.log
org.apache.phoenix.queryserver.server.Main
close failed in file object destructor:
IOError: [Errno 9] Bad file descriptor
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/grid/0/hdp/2.6.4.0-91/phoenix/phoenix-4.7.0.2.6.4.0-91-client.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/grid/0/hdp/2.6.4.0-91/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
starting Query Server, logging to /grid/0/log/hbase/phoenix-hbase-server.log
Query Server already running, PID file found:
/var/run/hbase/phoenix-hbase-server.pid
close failed in file object destructor:
IOError: [Errno 9] Bad file descriptor
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23366) Add service advisor for SPARK2 HDP 3.0
[ https://issues.apache.org/jira/browse/AMBARI-23366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-23366: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Add service advisor for SPARK2 HDP 3.0 > -- > > Key: AMBARI-23366 > URL: https://issues.apache.org/jira/browse/AMBARI-23366 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.7.0 > > > Create and collect all recommendations/validations in service advisor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23311) Use Ambari CLI to specify which services should be setup for SSO integration
[
https://issues.apache.org/jira/browse/AMBARI-23311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated AMBARI-23311:
---
Status: Patch Available (was: Open)
> Use Ambari CLI to specify which services should be setup for SSO integration
>
>
> Key: AMBARI-23311
> URL: https://issues.apache.org/jira/browse/AMBARI-23311
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
> Labels: pull-request-available, security, sso
> Fix For: 2.7.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> Use Ambari CLI to specify which services should be setup for SSO integration.
> {noformat:title=Example}
> # ambari-server setup-sso
> Using python /usr/bin/python
> Setting up SSO authentication properties...
> Do you want to configure SSO authentication [y/n] (y)?y
> Enter Ambari Admin login: admin
> Enter Ambari Admin password: admin
> Provider URL [URL] (http://example.com):http://knox.ambari.apache.org:8080
> Public Certificate pem (stored) (empty line to finish input):
> B3NzaC1yc2EDAQABAAABAQD
> Use SSO for all services [y/n] (y)? n
> Use SSO for Ambari [y/n] (y)? y
> Use SSO for HDFS [y/n] (y)? y
> Use SSO for YARN [y/n] (y)? y
> ...
> Use SSO for ZOOKEEPER [y/n] (y)? n
> Do you want to configure advanced properties [y/n] (n) ?
> Ambari Server 'setup-sso' completed successfully.
> {noformat}
> NOTE: this will require obtaining an Ambari administrator username and
> password to GET, PUT, and POST to the Ambari REST API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23384) PQS start fails after Ambari upgrade due to Bad file descriptor
[
https://issues.apache.org/jira/browse/AMBARI-23384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23384:
Labels: pull-request-available upgrade (was: upgrade)
> PQS start fails after Ambari upgrade due to Bad file descriptor
> ---
>
> Key: AMBARI-23384
> URL: https://issues.apache.org/jira/browse/AMBARI-23384
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vivek Sharma
>Assignee: Attila Magyar
>Priority: Critical
> Labels: pull-request-available, upgrade
> Fix For: 2.7.0
>
>
> *STR*
> PQS start after Ambari upgrade to 2.7.0 failed with below error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/phoenix_queryserver.py",
> line 81, in
> PhoenixQueryServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 356, in execute
> self.execute_prefix_function(self.command_name, 'post', env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 377, in execute_prefix_function
> method(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 419, in post_start
> raise Fail("Pid file \{0} doesn't exist after starting of the
> component.".format(pid_file))
> resource_management.core.exceptions.Fail: Pid file
> /var/run/hbase/phoenix-hbase-server.pid doesn't exist after starting of the
> component.
> {code}
> The log says the following:
> {code}
> 2018-03-26 16:33:13.563112 launching /base/tools/jdk1.8.0_112/bin/java -cp
> /usr/hdp/current/hbase-client/conf:/etc/hadoop/conf:/grid/0/hdp/2.6.4.0-91/phoenix/bin/../phoenix-4.7.0.2.6.4.0-91-client.jar:/grid/0/hdp/2.6.4.0-91/phoenix/bin/../phoenix-4.7.0.2.6.4.0-91-queryserver.jar:/usr/hdp/2.6.4.0-91/hadoop/conf:/usr/hdp/2.6.4.0-91/hadoop/lib/*:/usr/hdp/2.6.4.0-91/hadoop/.//*:/usr/hdp/2.6.4.0-91/hadoop-hdfs/./:/usr/hdp/2.6.4.0-91/hadoop-hdfs/lib/*:/usr/hdp/2.6.4.0-91/hadoop-hdfs/.//*:/usr/hdp/2.6.4.0-91/hadoop-yarn/lib/*:/usr/hdp/2.6.4.0-91/hadoop-yarn/.//*:/usr/hdp/2.6.4.0-91/hadoop-mapreduce/lib/*:/usr/hdp/2.6.4.0-91/hadoop-mapreduce/.//*::mysql-connector-java-5.1.33-bin.jar:mysql-connector-java.jar:/grid/0/hdp/2.6.4.0-91/tez/*:/grid/0/hdp/2.6.4.0-91/tez/lib/*:/grid/0/hdp/2.6.4.0-91/tez/conf
> -Dproc_phoenixserver
> -Dlog4j.configuration=file:/grid/0/hdp/2.6.4.0-91/phoenix/bin/log4j.properties
> -Dpsql.root.logger=INFO,DRFA -Dpsql.log.dir=/grid/0/log/hbase
> -Dpsql.log.file=phoenix-hbase-server.log
> org.apache.phoenix.queryserver.server.Main
> close failed in file object destructor:
> IOError: [Errno 9] Bad file descriptor
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/grid/0/hdp/2.6.4.0-91/phoenix/phoenix-4.7.0.2.6.4.0-91-client.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/grid/0/hdp/2.6.4.0-91/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> starting Query Server, logging to /grid/0/log/hbase/phoenix-hbase-server.log
> Query Server already running, PID file found:
> /var/run/hbase/phoenix-hbase-server.pid
> close failed in file object destructor:
> IOError: [Errno 9] Bad file descriptor
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23311) Use Ambari CLI to specify which services should be setup for SSO integration
[
https://issues.apache.org/jira/browse/AMBARI-23311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417036#comment-16417036
]
Hudson commented on AMBARI-23311:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8925 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8925/])
[AMBARI-23311] Use Ambari CLI to specify which services should be setup
(m.magyar3:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=a8c5ce20444d4cfc88419b84b328ef2f298e3aed])
* (edit) ambari-server/src/test/python/TestAmbariServer.py
* (edit) ambari-server/src/test/python/TestServerUtils.py
* (edit) ambari-server/src/main/python/ambari_server/serverUtils.py
* (edit) ambari-server/src/main/python/ambari_server/setupSecurity.py
* (edit) ambari-server/src/main/python/ambari-server.py
* (edit) ambari-server/src/test/python/TestSetupSso.py
* (edit) ambari-server/src/main/python/ambari_server/setupSso.py
> Use Ambari CLI to specify which services should be setup for SSO integration
>
>
> Key: AMBARI-23311
> URL: https://issues.apache.org/jira/browse/AMBARI-23311
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
> Labels: pull-request-available, security, sso
> Fix For: 2.7.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> Use Ambari CLI to specify which services should be setup for SSO integration.
> {noformat:title=Example}
> # ambari-server setup-sso
> Using python /usr/bin/python
> Setting up SSO authentication properties...
> Do you want to configure SSO authentication [y/n] (y)?y
> Enter Ambari Admin login: admin
> Enter Ambari Admin password: admin
> Provider URL [URL] (http://example.com):http://knox.ambari.apache.org:8080
> Public Certificate pem (stored) (empty line to finish input):
> B3NzaC1yc2EDAQABAAABAQD
> Use SSO for all services [y/n] (y)? n
> Use SSO for Ambari [y/n] (y)? y
> Use SSO for HDFS [y/n] (y)? y
> Use SSO for YARN [y/n] (y)? y
> ...
> Use SSO for ZOOKEEPER [y/n] (y)? n
> Do you want to configure advanced properties [y/n] (n) ?
> Ambari Server 'setup-sso' completed successfully.
> {noformat}
> NOTE: this will require obtaining an Ambari administrator username and
> password to GET, PUT, and POST to the Ambari REST API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23385) When Updating A Property in the UI, Both the Old and New Properties Are Visible After Saving
Antonenko Alexander created AMBARI-23385: Summary: When Updating A Property in the UI, Both the Old and New Properties Are Visible After Saving Key: AMBARI-23385 URL: https://issues.apache.org/jira/browse/AMBARI-23385 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23385) When Updating A Property in the UI, Both the Old and New Properties Are Visible After Saving
[ https://issues.apache.org/jira/browse/AMBARI-23385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23385: Assignee: Antonenko Alexander > When Updating A Property in the UI, Both the Old and New Properties Are > Visible After Saving > > > Key: AMBARI-23385 > URL: https://issues.apache.org/jira/browse/AMBARI-23385 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23241) Log Serach UI: Routing for the UI
[ https://issues.apache.org/jira/browse/AMBARI-23241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417123#comment-16417123 ] Hudson commented on AMBARI-23241: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8926 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8926/]) AMBARI-23241 Log Search UI: Routing for the UI (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=14c2a126a474275ddb84b5cbeda2dcfbea3b2fd6]) * (add) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-breadcrumbs-resolver.service.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filter-button/filter-button.component.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/services/storage/logs-state.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/user-settings.service.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/components/filter-dropdown/filter-dropdown.component.spec.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/logs-state.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/services/tab.guard.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/store.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/mockdata/mock-data-get.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/storage/reducers.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/login-form/login-form.component.spec.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-breadcrumbs-resolver.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/app-state.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-container.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/tabs/tabs.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/history-manager.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/assets/i18n/en.json * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/main-container/main-container.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/tabs/tabs.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/tab.ts * (edit) ambari-logsearch/ambari-logsearch-web/yarn.lock * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/string.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/services/tab.guard.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-filtering-utils.service.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/utils.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.spec.ts * (delete) ambari-logsearch/ambari-logsearch-web/src/app/modules/app-load/app-load.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.html * (add) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-filtering-utils.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/app-load/app-load.module.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/app.module.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/component-generator.service.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/audit-logs-table/audit-logs-table.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/service-logs-table/service-logs-table.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/audit-logs-entries/audit-logs-entries.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/context-menu/context-menu.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/tabs/tabs.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/login-form/login-form.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/timezone-picker/timezone-picker.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/cluster-filter/cluster-filter.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/app.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-range-picker/time-range-picker.compone
[jira] [Updated] (AMBARI-23376) Create topic handler for small agent actions. Like restart_agent, clean_caches etc.
[ https://issues.apache.org/jira/browse/AMBARI-23376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23376: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Create topic handler for small agent actions. Like restart_agent, > clean_caches etc. > --- > > Key: AMBARI-23376 > URL: https://issues.apache.org/jira/browse/AMBARI-23376 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23376.patch, AMBARI-23376.patch > > Time Spent: 1h 40m > Remaining Estimate: 0h > > For bigger actions containing a lot of info or special workflow and a new > topic would be required. Small actions like restart_agent/clean_cache make > sense to be sent in one general topic -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23386) HSI Jdbc URL should handle HA mode
Miklos Gergely created AMBARI-23386: --- Summary: HSI Jdbc URL should handle HA mode Key: AMBARI-23386 URL: https://issues.apache.org/jira/browse/AMBARI-23386 Project: Ambari Issue Type: Bug Reporter: Miklos Gergely Assignee: Miklos Gergely -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23386) HSI Jdbc URL should handle HA mode
[ https://issues.apache.org/jira/browse/AMBARI-23386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23386: Labels: pull-request-available (was: ) > HSI Jdbc URL should handle HA mode > -- > > Key: AMBARI-23386 > URL: https://issues.apache.org/jira/browse/AMBARI-23386 > Project: Ambari > Issue Type: Bug >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23385) When Updating A Property in the UI, Both the Old and New Properties Are Visible After Saving
[ https://issues.apache.org/jira/browse/AMBARI-23385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23385: Labels: pull-request-available (was: ) > When Updating A Property in the UI, Both the Old and New Properties Are > Visible After Saving > > > Key: AMBARI-23385 > URL: https://issues.apache.org/jira/browse/AMBARI-23385 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23322) Missing tooltips for two fields in 'Add User' page
[ https://issues.apache.org/jira/browse/AMBARI-23322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23322: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Missing tooltips for two fields in 'Add User' page > -- > > Key: AMBARI-23322 > URL: https://issues.apache.org/jira/browse/AMBARI-23322 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > No tooltip for 'Is this user an Ambari Admin', 'Deactivate this user' in Add > user page -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23376) Create topic handler for small agent actions. Like restart_agent, clean_caches etc.
[ https://issues.apache.org/jira/browse/AMBARI-23376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417161#comment-16417161 ] Hudson commented on AMBARI-23376: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8927 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8927/]) AMBARI-23376. Create topic handler for small agent actions. Like (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=193dc1d8af65b8dff152a70f20b6033ea55ff8ed]) * (edit) ambari-agent/src/main/python/ambari_agent/Constants.py * (edit) ambari-agent/src/main/python/ambari_agent/HeartbeatThread.py * (add) ambari-agent/src/main/python/ambari_agent/listeners/AgentActionsListener.py AMBARI-23376. Create topic handler for small agent actions. Like (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c1faa6f681e19f1f5dbd62427d369620525d7b9f]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/AmbariUpdateEvent.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java * (add) ambari-server/src/main/java/org/apache/ambari/server/events/AgentActionEvent.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/DefaultMessageEmitter.java * (edit) ambari-agent/src/main/python/ambari_agent/listeners/AgentActionsListener.py AMBARI-23376. Create topic handler for small agent actions. Like (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=e5c11fa0d65ef570bf8d619bab7209efb34b2430]) * (edit) ambari-agent/src/main/python/ambari_agent/Utils.py * (edit) ambari-agent/src/main/python/ambari_agent/ExitHelper.py * (edit) ambari-agent/src/main/python/ambari_agent/main.py * (edit) ambari-agent/src/main/python/ambari_agent/AmbariAgent.py > Create topic handler for small agent actions. Like restart_agent, > clean_caches etc. > --- > > Key: AMBARI-23376 > URL: https://issues.apache.org/jira/browse/AMBARI-23376 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23376.patch, AMBARI-23376.patch > > Time Spent: 1h 40m > Remaining Estimate: 0h > > For bigger actions containing a lot of info or special workflow and a new > topic would be required. Small actions like restart_agent/clean_cache make > sense to be sent in one general topic -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23387) Ambari node views items per page
Zoltan Haindrich created AMBARI-23387: - Summary: Ambari node views items per page Key: AMBARI-23387 URL: https://issues.apache.org/jira/browse/AMBARI-23387 Project: Ambari Issue Type: Improvement Reporter: Zoltan Haindrich items per page is always 10with todays monitor sizes and such it looks like a bad default value... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23388) Hostlist view selection bug
Zoltan Haindrich created AMBARI-23388: - Summary: Hostlist view selection bug Key: AMBARI-23388 URL: https://issues.apache.org/jira/browse/AMBARI-23388 Project: Ambari Issue Type: Bug Affects Versions: 2.7.0 Reporter: Zoltan Haindrich * open hostlist view * select a node with the checkbox * top right actions list: "Selected Hosts (1)" (ok) * switch to any other view * switch back to hostlist view * node is *still* selected * top right actions list "Selected Hosts (0)" the list should be either cleared from the selection; or the action should be available -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23389) Bug DBBUG-99354 "Install Packages" button on the versions screen fails if there is a service installed which was removed
Attila Magyar created AMBARI-23389:
--
Summary: Bug DBBUG-99354 "Install Packages" button on the versions
screen fails if there is a service installed which was removed
Key: AMBARI-23389
URL: https://issues.apache.org/jira/browse/AMBARI-23389
Project: Ambari
Issue Type: Improvement
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Attila Magyar
Assignee: Attila Magyar
Fix For: 2.7.0
I've installed several services with Ambari 2.6.1 - HDP 2.6.4, then upgraded
Ambari to 2.7. After this I've added a new HDP 3.0 repo. As Slider was
installed which was removed from HDP 3.0, it displayed a white "i" in a blue
circle in the 3.0 column (see the screenshot). As I'v clicked on the "Install
Packages" button it returned an error message (see screenshot). I've checked
the log, and it seems that the absence of the Slider service caused the issue:
{code}
org.apache.ambari.server.controller.spi.SystemException: Cannot obtain stack
information for HDP-3.0
at
org.apache.ambari.server.state.stack.upgrade.RepositoryVersionHelper.buildRoleParams(RepositoryVersionHelper.java:305)
at
org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:723)
at
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:118)
at
org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createOrchestration(ClusterStackVersionResourceProvider.java:634)
at
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:118)
at
org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createOrUpdateHostVersions(ClusterStackVersionResourceProvider.java:532)
at
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:128)
at
org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:474)
at
org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:231)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:296)
at
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
at
org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:50)
at
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:163)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:127)
at
org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
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.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
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)
at
com.sun.jersey.spi.container.serv
[jira] [Updated] (AMBARI-23389) Install Packages button on the versions screen fails if there is a service installed which was removed
[
https://issues.apache.org/jira/browse/AMBARI-23389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-23389:
---
Summary: Install Packages button on the versions screen fails if there is a
service installed which was removed (was: Bug DBBUG-99354 "Install Packages"
button on the versions screen fails if there is a service installed which was
removed)
> Install Packages button on the versions screen fails if there is a service
> installed which was removed
> --
>
> Key: AMBARI-23389
> URL: https://issues.apache.org/jira/browse/AMBARI-23389
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Fix For: 2.7.0
>
>
> I've installed several services with Ambari 2.6.1 - HDP 2.6.4, then upgraded
> Ambari to 2.7. After this I've added a new HDP 3.0 repo. As Slider was
> installed which was removed from HDP 3.0, it displayed a white "i" in a blue
> circle in the 3.0 column (see the screenshot). As I'v clicked on the "Install
> Packages" button it returned an error message (see screenshot). I've checked
> the log, and it seems that the absence of the Slider service caused the issue:
> {code}
> org.apache.ambari.server.controller.spi.SystemException: Cannot obtain stack
> information for HDP-3.0
> at
> org.apache.ambari.server.state.stack.upgrade.RepositoryVersionHelper.buildRoleParams(RepositoryVersionHelper.java:305)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:723)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:118)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createOrchestration(ClusterStackVersionResourceProvider.java:634)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:118)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createOrUpdateHostVersions(ClusterStackVersionResourceProvider.java:532)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:128)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:474)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:231)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:296)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:50)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:163)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:127)
> at
> org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:120)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> 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.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> 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
[jira] [Commented] (AMBARI-23322) Missing tooltips for two fields in 'Add User' page
[ https://issues.apache.org/jira/browse/AMBARI-23322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417209#comment-16417209 ] Hudson commented on AMBARI-23322: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8928 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8928/]) AMBARI-23322. Missing tooltips for two fields in 'Add User' page (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=316322666ae32a5f9a20ab205817931d906ed71b]) * (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/scripts/i18n.config.js > Missing tooltips for two fields in 'Add User' page > -- > > Key: AMBARI-23322 > URL: https://issues.apache.org/jira/browse/AMBARI-23322 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > No tooltip for 'Is this user an Ambari Admin', 'Deactivate this user' in Add > user page -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23389) Install Packages button on the versions screen fails if there is a service installed which was removed
[
https://issues.apache.org/jira/browse/AMBARI-23389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23389:
Labels: pull-request-available (was: )
> Install Packages button on the versions screen fails if there is a service
> installed which was removed
> --
>
> Key: AMBARI-23389
> URL: https://issues.apache.org/jira/browse/AMBARI-23389
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> I've installed several services with Ambari 2.6.1 - HDP 2.6.4, then upgraded
> Ambari to 2.7. After this I've added a new HDP 3.0 repo. As Slider was
> installed which was removed from HDP 3.0, it displayed a white "i" in a blue
> circle in the 3.0 column (see the screenshot). As I'v clicked on the "Install
> Packages" button it returned an error message (see screenshot). I've checked
> the log, and it seems that the absence of the Slider service caused the issue:
> {code}
> org.apache.ambari.server.controller.spi.SystemException: Cannot obtain stack
> information for HDP-3.0
> at
> org.apache.ambari.server.state.stack.upgrade.RepositoryVersionHelper.buildRoleParams(RepositoryVersionHelper.java:305)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:723)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:118)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createOrchestration(ClusterStackVersionResourceProvider.java:634)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:118)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createOrUpdateHostVersions(ClusterStackVersionResourceProvider.java:532)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:128)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:474)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:231)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:296)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:50)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:163)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:127)
> at
> org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:120)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> 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.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> 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(WebApplic
[jira] [Updated] (AMBARI-23389) Install Packages button on the versions screen fails if there is a service installed which was removed
[
https://issues.apache.org/jira/browse/AMBARI-23389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-23389:
---
Status: Patch Available (was: Open)
> Install Packages button on the versions screen fails if there is a service
> installed which was removed
> --
>
> Key: AMBARI-23389
> URL: https://issues.apache.org/jira/browse/AMBARI-23389
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I've installed several services with Ambari 2.6.1 - HDP 2.6.4, then upgraded
> Ambari to 2.7. After this I've added a new HDP 3.0 repo. As Slider was
> installed which was removed from HDP 3.0, it displayed a white "i" in a blue
> circle in the 3.0 column (see the screenshot). As I'v clicked on the "Install
> Packages" button it returned an error message (see screenshot). I've checked
> the log, and it seems that the absence of the Slider service caused the issue:
> {code}
> org.apache.ambari.server.controller.spi.SystemException: Cannot obtain stack
> information for HDP-3.0
> at
> org.apache.ambari.server.state.stack.upgrade.RepositoryVersionHelper.buildRoleParams(RepositoryVersionHelper.java:305)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:723)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:118)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createOrchestration(ClusterStackVersionResourceProvider.java:634)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:118)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createOrUpdateHostVersions(ClusterStackVersionResourceProvider.java:532)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:128)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:474)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:231)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:296)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:50)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:163)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:127)
> at
> org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:120)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> 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.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> 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.applica
[jira] [Created] (AMBARI-23390) Dashboard: rationalize default widgets
Andrii Tkach created AMBARI-23390: - Summary: Dashboard: rationalize default widgets Key: AMBARI-23390 URL: https://issues.apache.org/jira/browse/AMBARI-23390 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.0 See screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23390) Dashboard: rationalize default widgets
[ https://issues.apache.org/jira/browse/AMBARI-23390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23390: -- Attachment: dashboard.png > Dashboard: rationalize default widgets > -- > > Key: AMBARI-23390 > URL: https://issues.apache.org/jira/browse/AMBARI-23390 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Fix For: 2.7.0 > > Attachments: dashboard.png > > > See screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23378) Closing 'Add New HDFS Namespace' wizard shows confirmation for RM HA wizard
[ https://issues.apache.org/jira/browse/AMBARI-23378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417256#comment-16417256 ] Hudson commented on AMBARI-23378: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8929 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8929/]) AMBARI-23378. Closing 'Add New HDFS Namespace' wizard shows confirmation (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=5c2f4fbb383453d81574b8e2c081a3c3a279ca60]) * (edit) ambari-web/app/routes/namenode_federation_routes.js * (edit) ambari-web/app/data/configs/wizards/federation_properties.js * (edit) ambari-web/app/messages.js > Closing 'Add New HDFS Namespace' wizard shows confirmation for RM HA wizard > --- > > Key: AMBARI-23378 > URL: https://issues.apache.org/jira/browse/AMBARI-23378 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > - Navigate to Add New HDFS Namespace wizard to enable federation > - At configure components one step had failed > - Tried to close the wizard by choosing 'x' on right hand side of the wizard > page > - Confirmation popup shows message for RM HA -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23380) Fix intermittent "No such file or directory" error in TestHostCleanup
[
https://issues.apache.org/jira/browse/AMBARI-23380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas resolved AMBARI-23380.
---
Resolution: Fixed
> Fix intermittent "No such file or directory" error in TestHostCleanup
> -
>
> Key: AMBARI-23380
> URL: https://issues.apache.org/jira/browse/AMBARI-23380
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available, unit-test
> Fix For: 2.7.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Fix intermittent "No such file or directory" error in TestHostCleanup
> {noformat}
> ==
> ERROR: test_do_cleanup_all (TestHostCleanup.TestHostCleanup)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/test/python/ambari_agent/TestHostCleanup.py",
> line 233, in test_do_cleanup_all
> self.hostcleanup.do_cleanup(propertyMap)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/main/python/ambari_agent/HostCleanup.py",
> line 168, in do_cleanup
> self.do_delete_by_owner(userIds, FOLDER_LIST)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/main/python/ambari_agent/HostCleanup.py",
> line 514, in do_delete_by_owner
> stat = os.stat(fileToCheck)
> OSError: [Errno 2] No such file or directory:
> '/tmp/symlink2120964127269148256test_link'
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23390) Dashboard: rationalize default widgets
[ https://issues.apache.org/jira/browse/AMBARI-23390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23390: Labels: pull-request-available (was: ) > Dashboard: rationalize default widgets > -- > > Key: AMBARI-23390 > URL: https://issues.apache.org/jira/browse/AMBARI-23390 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: dashboard.png > > > See screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23241) Log Serach UI: Routing for the UI
[ https://issues.apache.org/jira/browse/AMBARI-23241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-23241: --- Resolution: Done Status: Resolved (was: Patch Available) > Log Serach UI: Routing for the UI > - > > Key: AMBARI-23241 > URL: https://issues.apache.org/jira/browse/AMBARI-23241 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Original Estimate: 120h > Time Spent: 216h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23363) Streamline Application manager's UI link is not visible in Ambari-2.7.0.0
[ https://issues.apache.org/jira/browse/AMBARI-23363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk resolved AMBARI-23363. --- Resolution: Fixed Additional patch merged to trunk > Streamline Application manager's UI link is not visible in Ambari-2.7.0.0 > - > > Key: AMBARI-23363 > URL: https://issues.apache.org/jira/browse/AMBARI-23363 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 2.5h > Remaining Estimate: 0h > > SAM's UI link is not available on side bar using Ambari-2.7.0.0. > Independently, you can open SAM's UI at port (default) just fine. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23363) Streamline Application manager's UI link is not visible in Ambari-2.7.0.0
[ https://issues.apache.org/jira/browse/AMBARI-23363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417378#comment-16417378 ] Hudson commented on AMBARI-23363: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8930 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8930/]) AMBARI-23363 Streamline Application manager's UI link is not visible in (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=3b643bc591973920cec390a3018fecee55761dee]) * (edit) ambari-web/app/views/main/dashboard/widgets.js > Streamline Application manager's UI link is not visible in Ambari-2.7.0.0 > - > > Key: AMBARI-23363 > URL: https://issues.apache.org/jira/browse/AMBARI-23363 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 2.5h > Remaining Estimate: 0h > > SAM's UI link is not available on side bar using Ambari-2.7.0.0. > Independently, you can open SAM's UI at port (default) just fine. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23314) Prevent Multiple OS Entries For a Single Mpack
[
https://issues.apache.org/jira/browse/AMBARI-23314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-23314.
--
Resolution: Fixed
> Prevent Multiple OS Entries For a Single Mpack
> --
>
> Key: AMBARI-23314
> URL: https://issues.apache.org/jira/browse/AMBARI-23314
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The operating systems endpoint allows for creation and deletion of
> repositories which are associated with a single management pack:
> {code}
> PUT http://{{ambari-server}}:8080/api/v1/mpacks/1/operating_systems/redhat7
> {
> "OperatingSystems" : {
> "is_ambari_managed" : true,
> "repositories" : [
> {
> "distribution" : null,
> "components" : null,
> "unique" : true,
> "tags" : [ ],
> "base_url" :
> "http://repo.ambari.apache.org/hdpcore/centos7/HDPCORE-1.0.0-b96/foo";,
> "os_type" : "redhat7",
> "repo_id" : "HDPCORE-1.0.0-b96",
> "repo_name" : "HDPCORE",
> "mirrors_list" : null,
> "default_base_url" : null,
> "ambari_managed" : true
> },
> {
> "distribution" : null,
> "components" : null,
> "unique" : false,
> "tags" : [ ],
> "base_url" :
> "http://repo.ambari.apache.org/hdpcore/centos7/HDP-UTILS-1.1.0.22/foo";,
> "os_type" : "redhat7",
> "repo_id" : "HDP-UTILS-1.1.0.21",
> "repo_name" : "HDP-UTILS",
> "mirrors_list" : null,
> "default_base_url" : null,
> "ambari_managed" : true
> }
> ]
> }
> }
> {code}
> However, multiple PUTs causes duplicate entries for the same OS. This should
> be prevented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23391) Remove FK Relationship On Repo Versions for Services & Components
Jonathan Hurley created AMBARI-23391:
Summary: Remove FK Relationship On Repo Versions for Services &
Components
Key: AMBARI-23391
URL: https://issues.apache.org/jira/browse/AMBARI-23391
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 3.0.0
As part of AMBARI-23009, this will remove the reliance that services and
components have on the {{repo_version}} table. It will also attempt to address
some of the many, many unit test failures in the branch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23392) Duplicate websocket subscription on Configs page
Andrii Tkach created AMBARI-23392: - Summary: Duplicate websocket subscription on Configs page Key: AMBARI-23392 URL: https://issues.apache.org/jira/browse/AMBARI-23392 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.0 Steps to reproduce: # Open ambari web # Go to HDFS # Open Configs page # Leave page Actual Result: UI has subscribed to all topics again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23338) Blueprints with an installed cluster should be read-only
[ https://issues.apache.org/jira/browse/AMBARI-23338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-23338: --- Resolution: Fixed Status: Resolved (was: Patch Available) fixed on trunk. > Blueprints with an installed cluster should be read-only > > > Key: AMBARI-23338 > URL: https://issues.apache.org/jira/browse/AMBARI-23338 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Deleting a blueprint with a cluster installed can cause heartbeat issues with > agents. Such blueprints should be read-only -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23392) Duplicate websocket subscription on Configs page
[ https://issues.apache.org/jira/browse/AMBARI-23392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23392: Labels: pull-request-available (was: ) > Duplicate websocket subscription on Configs page > > > Key: AMBARI-23392 > URL: https://issues.apache.org/jira/browse/AMBARI-23392 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > > Steps to reproduce: > # Open ambari web > # Go to HDFS > # Open Configs page > # Leave page > Actual Result: UI has subscribed to all topics again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23209) Kerberos 'Edit' Properties not conforming to the new style
[ https://issues.apache.org/jira/browse/AMBARI-23209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach resolved AMBARI-23209. --- Resolution: Fixed > Kerberos 'Edit' Properties not conforming to the new style > -- > > Key: AMBARI-23209 > URL: https://issues.apache.org/jira/browse/AMBARI-23209 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: kerberos_configs.png > > Time Spent: 3h 20m > Remaining Estimate: 0h > > The 'Edit' link of Kerberos properties page does not confirm to the new UI > design styles. All the actions are buttons on this page, and it is easy to > miss the edit link. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23209) Kerberos 'Edit' Properties not conforming to the new style
[ https://issues.apache.org/jira/browse/AMBARI-23209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417432#comment-16417432 ] Andrii Tkach commented on AMBARI-23209: --- committed to trunk > Kerberos 'Edit' Properties not conforming to the new style > -- > > Key: AMBARI-23209 > URL: https://issues.apache.org/jira/browse/AMBARI-23209 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: kerberos_configs.png > > Time Spent: 3h 20m > Remaining Estimate: 0h > > The 'Edit' link of Kerberos properties page does not confirm to the new UI > design styles. All the actions are buttons on this page, and it is easy to > miss the edit link. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23393) Ambari Requests Too Much Data From Hosts When Logging In
Andrii Tkach created AMBARI-23393:
-
Summary: Ambari Requests Too Much Data From Hosts When Logging In
Key: AMBARI-23393
URL: https://issues.apache.org/jira/browse/AMBARI-23393
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Fix For: 2.7.0
When first logging into Ambari, the web client makes the following request:
GET api/v1/clusters//hosts?fields=
- Hosts/cpu_count
- Hosts/host_name
- Hosts/host_status
- Hosts/ip
- Hosts/last_agent_env
- Hosts/last_heartbeat_time
- Hosts/maintenance_state
- Hosts/ph_cpu_count
- Hosts/public_host_name
- Hosts/rack_info
- Hosts/total_mem
- alerts_summary
- host_components/HostRoles/desired_admin_state
- host_components/HostRoles/display_name
- host_components/HostRoles/maintenance_state
- host_components/HostRoles/service_name
- host_components/HostRoles/stale_configs
- host_components/HostRoles/state
- host_components/logging
- stack_versions/HostStackVersions
- stack_versions/repository_versions/RepositoryVersions/display_name
- stack_versions/repository_versions/RepositoryVersions/id
- stack_versions/repository_versions/RepositoryVersions/repository_version
In a cluster with 100 hosts, this can cause a payload of over 200MB to be
returned. The culprit seems to be the {{Hosts/last_agent_env}} property,
specifically the {{activeJavaProcs}} key. If the hosts in the cluster are
running a lot of Java processes, this can account for over 90% of the payload
(roughly 180MB). This data takes 30 or more seconds for the server to serialize
and stream to the socket.
It looks like {{Hosts/last_agent_env}} isn't even needed after initially
provisioning a host during the host checks, so it probably can be removed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23372) Hosts not populated in Assign Master Page in Move Master Wizard
[ https://issues.apache.org/jira/browse/AMBARI-23372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23372: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Hosts not populated in Assign Master Page in Move Master Wizard > --- > > Key: AMBARI-23372 > URL: https://issues.apache.org/jira/browse/AMBARI-23372 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > q -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23391) Remove FK Relationship On Repo Versions for Services & Components
[
https://issues.apache.org/jira/browse/AMBARI-23391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23391:
Labels: pull-request-available (was: )
> Remove FK Relationship On Repo Versions for Services & Components
> -
>
> Key: AMBARI-23391
> URL: https://issues.apache.org/jira/browse/AMBARI-23391
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
>
> As part of AMBARI-23009, this will remove the reliance that services and
> components have on the {{repo_version}} table. It will also attempt to
> address some of the many, many unit test failures in the branch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23209) Kerberos 'Edit' Properties not conforming to the new style
[ https://issues.apache.org/jira/browse/AMBARI-23209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417531#comment-16417531 ] Hudson commented on AMBARI-23209: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8931 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8931/]) AMBARI-23209 Kerberos 'Edit' Properties not conforming to the new style (1963907+atkach: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=508769f5cbfe67842396d2a0761eeb9a4fa8585a]) * (edit) ambari-web/app/templates/main/admin/kerberos.hbs > Kerberos 'Edit' Properties not conforming to the new style > -- > > Key: AMBARI-23209 > URL: https://issues.apache.org/jira/browse/AMBARI-23209 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: kerberos_configs.png > > Time Spent: 3h 20m > Remaining Estimate: 0h > > The 'Edit' link of Kerberos properties page does not confirm to the new UI > design styles. All the actions are buttons on this page, and it is easy to > miss the edit link. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23372) Hosts not populated in Assign Master Page in Move Master Wizard
[ https://issues.apache.org/jira/browse/AMBARI-23372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417636#comment-16417636 ] Hudson commented on AMBARI-23372: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8932 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8932/]) AMBARI-23372. Hosts not populated in Assign Master Page in Move Master (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=dd5b34d524387a359d654de6f8efe31d3f22bea6]) * (edit) ambari-web/app/views/common/form/dropdown.js > Hosts not populated in Assign Master Page in Move Master Wizard > --- > > Key: AMBARI-23372 > URL: https://issues.apache.org/jira/browse/AMBARI-23372 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > q -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23332) Recommend SSO configuration values for RANGER in the stack advisor
[
https://issues.apache.org/jira/browse/AMBARI-23332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-23332:
--
Description:
Recommend SSO configuration values for RANGER in the stack advisor.
The following values in \{{ranger-admin-site}} need to be set:
* \{{ranger.sso.enabled}}
** SSO enabled (true) or disabled (false)
* \{{ranger.sso.providerurl}}
** SSO provider url. Example:
https://KNOX_HOST:KNOX_PORT/gateway/TOPOLOGY_NAME/knoxsso/api/v1/websso
* \{{ranger.sso.publicKey}}
** SSO provider public key. The base64-encoded x509 Public key data (without
the certificate header and footer) used for SSO provider cookie verification
* \{{ranger.sso.cookiename}}
** SSO cookie name
* \{{ranger.sso.query.param.originalurl}}
** Query name for appending original url in SSO url
* \{{ranger.sso.browser.useragent}}
** SSO browser useragents (comma-delimted). Default: Mozilla,chrome
was:Recommend SSO configuration values for RANGER in the stack advisor
> Recommend SSO configuration values for RANGER in the stack advisor
> --
>
> Key: AMBARI-23332
> URL: https://issues.apache.org/jira/browse/AMBARI-23332
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.7.0
>
>
> Recommend SSO configuration values for RANGER in the stack advisor.
> The following values in \{{ranger-admin-site}} need to be set:
> * \{{ranger.sso.enabled}}
> ** SSO enabled (true) or disabled (false)
> * \{{ranger.sso.providerurl}}
> ** SSO provider url. Example:
> https://KNOX_HOST:KNOX_PORT/gateway/TOPOLOGY_NAME/knoxsso/api/v1/websso
> * \{{ranger.sso.publicKey}}
> ** SSO provider public key. The base64-encoded x509 Public key data (without
> the certificate header and footer) used for SSO provider cookie verification
> * \{{ranger.sso.cookiename}}
> ** SSO cookie name
> * \{{ranger.sso.query.param.originalurl}}
> ** Query name for appending original url in SSO url
> * \{{ranger.sso.browser.useragent}}
> ** SSO browser useragents (comma-delimted). Default: Mozilla,chrome
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23334) Provider URL validator incorrect when setting up SSO via Ambari CLI
[
https://issues.apache.org/jira/browse/AMBARI-23334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated AMBARI-23334:
---
Status: Patch Available (was: In Progress)
> Provider URL validator incorrect when setting up SSO via Ambari CLI
> ---
>
> Key: AMBARI-23334
> URL: https://issues.apache.org/jira/browse/AMBARI-23334
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> When setting the URL for the SSO provider while running {{ambari-server
> setup-sso}}, valid URLs are rejected.
> {noformat}
> [root@c7402 ~]# ambari-server setup-sso
> Using python /usr/bin/python
> Setting up SSO authentication properties...
> Do you want to configure SSO authentication [y/n] (y)?y
> Provider URL [URL]
> (http://example.com):https://c7402.ambari.apache.org:8443/gateway/knoxsso/api/v1/websso
> Invalid provider URL
> Provider URL [URL] (http://example.com):c7402.ambari.apache.org:8443
> Public Certificate pem (empty) (empty line to finish input):
> {noformat}
> Cause:
> The RegEx validating the URL is only allowing hostname and port values, when
> it should allow for absolute URLs.
> {code:java|title=ambari_server/setupSso.py:72}
> provider_url = get_validated_string_input("Provider URL [URL]
> ({0}):".format(provider_url), provider_url, REGEX_HOSTNAME_PORT,
> "Invalid provider URL",
> False){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23332) Recommend SSO configuration values for RANGER in the stack advisor
[
https://issues.apache.org/jira/browse/AMBARI-23332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-23332:
--
Description:
Recommend SSO configuration values for RANGER in the stack advisor.
The following values in {{ranger-admin-site}} need to be set:
* {{ranger.sso.enabled}}
** SSO enabled (true) or disabled (false)
* {{ranger.sso.providerurl}}
** SSO provider url. Example:
https://KNOX_HOST:KNOX_PORT/gateway/TOPOLOGY_NAME/knoxsso/api/v1/websso
* {{ranger.sso.publicKey}}
** SSO provider public key. The base64-encoded x509 Public key data (without
the certificate header and footer) used for SSO provider cookie verification
* {{ranger.sso.cookiename}}
** SSO cookie name
* {{ranger.sso.query.param.originalurl}}
** Query name for appending original url in SSO url
* {{ranger.sso.browser.useragent}}
** SSO browser useragents (comma-delimted). Default: Mozilla,chrome
was:
Recommend SSO configuration values for RANGER in the stack advisor.
The following values in \{{ranger-admin-site}} need to be set:
* \{{ranger.sso.enabled}}
** SSO enabled (true) or disabled (false)
* \{{ranger.sso.providerurl}}
** SSO provider url. Example:
https://KNOX_HOST:KNOX_PORT/gateway/TOPOLOGY_NAME/knoxsso/api/v1/websso
* \{{ranger.sso.publicKey}}
** SSO provider public key. The base64-encoded x509 Public key data (without
the certificate header and footer) used for SSO provider cookie verification
* \{{ranger.sso.cookiename}}
** SSO cookie name
* \{{ranger.sso.query.param.originalurl}}
** Query name for appending original url in SSO url
* \{{ranger.sso.browser.useragent}}
** SSO browser useragents (comma-delimted). Default: Mozilla,chrome
> Recommend SSO configuration values for RANGER in the stack advisor
> --
>
> Key: AMBARI-23332
> URL: https://issues.apache.org/jira/browse/AMBARI-23332
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.7.0
>
>
> Recommend SSO configuration values for RANGER in the stack advisor.
> The following values in {{ranger-admin-site}} need to be set:
> * {{ranger.sso.enabled}}
> ** SSO enabled (true) or disabled (false)
> * {{ranger.sso.providerurl}}
> ** SSO provider url. Example:
> https://KNOX_HOST:KNOX_PORT/gateway/TOPOLOGY_NAME/knoxsso/api/v1/websso
> * {{ranger.sso.publicKey}}
> ** SSO provider public key. The base64-encoded x509 Public key data (without
> the certificate header and footer) used for SSO provider cookie verification
> * {{ranger.sso.cookiename}}
> ** SSO cookie name
> * {{ranger.sso.query.param.originalurl}}
> ** Query name for appending original url in SSO url
> * {{ranger.sso.browser.useragent}}
> ** SSO browser useragents (comma-delimted). Default: Mozilla,chrome
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23311) Use Ambari CLI to specify which services should be setup for SSO integration
[
https://issues.apache.org/jira/browse/AMBARI-23311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated AMBARI-23311:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Use Ambari CLI to specify which services should be setup for SSO integration
>
>
> Key: AMBARI-23311
> URL: https://issues.apache.org/jira/browse/AMBARI-23311
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
> Labels: pull-request-available, security, sso
> Fix For: 2.7.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> Use Ambari CLI to specify which services should be setup for SSO integration.
> {noformat:title=Example}
> # ambari-server setup-sso
> Using python /usr/bin/python
> Setting up SSO authentication properties...
> Do you want to configure SSO authentication [y/n] (y)?y
> Enter Ambari Admin login: admin
> Enter Ambari Admin password: admin
> Provider URL [URL] (http://example.com):http://knox.ambari.apache.org:8080
> Public Certificate pem (stored) (empty line to finish input):
> B3NzaC1yc2EDAQABAAABAQD
> Use SSO for all services [y/n] (y)? n
> Use SSO for Ambari [y/n] (y)? y
> Use SSO for HDFS [y/n] (y)? y
> Use SSO for YARN [y/n] (y)? y
> ...
> Use SSO for ZOOKEEPER [y/n] (y)? n
> Do you want to configure advanced properties [y/n] (n) ?
> Ambari Server 'setup-sso' completed successfully.
> {noformat}
> NOTE: this will require obtaining an Ambari administrator username and
> password to GET, PUT, and POST to the Ambari REST API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23332) Recommend SSO configuration values for RANGER in the stack advisor
[
https://issues.apache.org/jira/browse/AMBARI-23332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-23332:
--
Description:
Recommend SSO configuration values for RANGER in the stack advisor.
The following values in {{ranger-admin-site}} need to be set:
* {{ranger.sso.enabled}}
** SSO enabled (true) or disabled (false)
* {{ranger.sso.providerurl}}
** SSO provider url. Example:
https://KNOX_HOST:KNOX_PORT/gateway/TOPOLOGY_NAME/knoxsso/api/v1/websso
* {{ranger.sso.publicKey}}
** SSO provider public key. The base64-encoded x509 Public key data (without
the certificate header and footer) used for SSO provider cookie verification
* {{ranger.sso.cookiename}}
** SSO cookie name
* {{ranger.sso.query.param.originalurl}}
** Query name for appending original url in SSO url
* {{ranger.sso.browser.useragent}}
** SSO browser useragents (comma-delimted). Default: Mozilla,chrome
Also, update the Ranger metainfo.xml file to indicate it supports SSO
configuration by Ambari
was:
Recommend SSO configuration values for RANGER in the stack advisor.
The following values in {{ranger-admin-site}} need to be set:
* {{ranger.sso.enabled}}
** SSO enabled (true) or disabled (false)
* {{ranger.sso.providerurl}}
** SSO provider url. Example:
https://KNOX_HOST:KNOX_PORT/gateway/TOPOLOGY_NAME/knoxsso/api/v1/websso
* {{ranger.sso.publicKey}}
** SSO provider public key. The base64-encoded x509 Public key data (without
the certificate header and footer) used for SSO provider cookie verification
* {{ranger.sso.cookiename}}
** SSO cookie name
* {{ranger.sso.query.param.originalurl}}
** Query name for appending original url in SSO url
* {{ranger.sso.browser.useragent}}
** SSO browser useragents (comma-delimted). Default: Mozilla,chrome
> Recommend SSO configuration values for RANGER in the stack advisor
> --
>
> Key: AMBARI-23332
> URL: https://issues.apache.org/jira/browse/AMBARI-23332
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.7.0
>
>
> Recommend SSO configuration values for RANGER in the stack advisor.
> The following values in {{ranger-admin-site}} need to be set:
> * {{ranger.sso.enabled}}
> ** SSO enabled (true) or disabled (false)
> * {{ranger.sso.providerurl}}
> ** SSO provider url. Example:
> https://KNOX_HOST:KNOX_PORT/gateway/TOPOLOGY_NAME/knoxsso/api/v1/websso
> * {{ranger.sso.publicKey}}
> ** SSO provider public key. The base64-encoded x509 Public key data (without
> the certificate header and footer) used for SSO provider cookie verification
> * {{ranger.sso.cookiename}}
> ** SSO cookie name
> * {{ranger.sso.query.param.originalurl}}
> ** Query name for appending original url in SSO url
> * {{ranger.sso.browser.useragent}}
> ** SSO browser useragents (comma-delimted). Default: Mozilla,chrome
> Also, update the Ranger metainfo.xml file to indicate it supports SSO
> configuration by Ambari
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23275) Upgrade maven dependency for jdeb and fic rpm autorequire tag value
[
https://issues.apache.org/jira/browse/AMBARI-23275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417712#comment-16417712
]
Aravindan Vijayan commented on AMBARI-23275:
[~mnpoonia] This patch fails the AMS rpm build mechanism.
Error trace
{code}
2018/03/27 21:18:42 INFO: [INFO] Creating spec file
/grid/0/jenkins/workspace/Zuul_Ambari_Build_Job/build-support/SOURCES/ambari/ambari-metrics/ambari-metrics-assembly/target/rpm/ambari-metrics-monitor/SPECS/ambari-metrics-monitor.spec
2018/03/27 21:18:42 INFO: [INFO]
2018/03/27 21:18:42 INFO: [INFO] Reactor Summary:
2018/03/27 21:18:42 INFO: [INFO]
2018/03/27 21:18:42 INFO: [INFO] ambari-utility
. SUCCESS [ 6.666 s]
2018/03/27 21:18:42 INFO: [INFO] ambari-metrics
. SUCCESS [ 0.376 s]
2018/03/27 21:18:42 INFO: [INFO] Ambari Metrics Common
.. SUCCESS [ 23.122 s]
2018/03/27 21:18:42 INFO: [INFO] Ambari Metrics Hadoop Sink
. SUCCESS [ 15.802 s]
2018/03/27 21:18:42 INFO: [INFO] Ambari Metrics Flume Sink
.. SUCCESS [ 9.891 s]
2018/03/27 21:18:42 INFO: [INFO] Ambari Metrics Kafka Sink
.. SUCCESS [ 10.945 s]
2018/03/27 21:18:42 INFO: [INFO] Ambari Metrics Storm Sink
.. SUCCESS [ 52.974 s]
2018/03/27 21:18:42 INFO: [INFO] Ambari Metrics Storm Sink (Legacy)
. SUCCESS [ 9.298 s]
2018/03/27 21:18:42 INFO: [INFO] Ambari Metrics Collector
... SUCCESS [10:13 min]
2018/03/27 21:18:42 INFO: [INFO] Ambari Metrics Monitor
. SUCCESS [ 1.980 s]
2018/03/27 21:18:42 INFO: [INFO] Ambari Metrics Grafana
. SUCCESS [ 4.086 s]
2018/03/27 21:18:42 INFO: [INFO] Ambari Metrics Host Aggregator
. SUCCESS [ 39.706 s]
2018/03/27 21:18:42 INFO: [INFO] Ambari Metrics Assembly
FAILURE [08:40 min]
2018/03/27 21:18:42 INFO: [INFO]
2018/03/27 21:18:42 INFO: [INFO] BUILD FAILURE
2018/03/27 21:18:42 INFO: [INFO]
2018/03/27 21:18:42 INFO: [INFO] Total time: 21:48 min
2018/03/27 21:18:42 INFO: [INFO] Finished at: 2018-03-27T21:18:42+00:00
2018/03/27 21:18:43 INFO: [INFO] Final Memory: 227M/1979M
2018/03/27 21:18:43 INFO: [INFO]
2018/03/27 21:18:43 INFO: [ERROR] Failed to execute goal
org.codehaus.mojo:rpm-maven-plugin:2.1.5:rpm (ambari-metrics-monitor) on
project ambari-metrics-assembly: Execution ambari-metrics-monitor of goal
org.codehaus.mojo:rpm-maven-plugin:2.1.5:rpm failed: Invalid scriptlet
declaration found - defined scriptFile does not exist:
/grid/0/jenkins/workspace/Zuul_Ambari_Build_Job/build-support/SOURCES/ambari/ambari-metrics/ambari-metrics-assembly/src/main/package/rpm/preremove.sh
-> [Help 1]
2018/03/27 21:18:43 INFO: [ERROR]
2018/03/27 21:18:43 INFO: [ERROR] To see the full stack trace of the
errors, re-run Maven with the -e switch.
2018/03/27 21:18:43 INFO: [ERROR] Re-run Maven using the -X switch to
enable full debug logging.
2018/03/27 21:18:43 INFO: [ERROR]
2018/03/27 21:18:43 INFO: [ERROR] For more information about the errors and
possible solutions, please read the following articles:
2018/03/27 21:18:43 INFO: [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
2018/03/27 21:18:43 INFO: [ERROR]
2018/03/27 21:18:43 INFO: [ERROR] After correcting the problems, you can
resume the build with the command
2018/03/27 21:18:43 INFO: [ERROR] mvn -rf :ambari-metrics-assembly
2018/03/27 21:18:44 INFO: Time Taken: 0:21:51.965004 -- executing: cd
/grid/0/jenkins/workspace/Zuul_Ambari_Build_Job/build-support/SOURCES/ambari/ambari-metrics
&& /grid/0/jenkins/tools/maven/apache-maven-3.3.9/bin/mvn -B -nsu -DskipTests
package install -Dbuild-rpm
2018/03/27 21:18:44 ERROR : Process failed
{code}
Can you please revert and submit a modified patch? You can use the following
link for testing rpm build.
https://cwiki.apache.org/confluence/display/AMBARI/Build+Instructions
> Upgrade maven dependency for jdeb and fic rpm autorequire tag value
> ---
>
> Key: AMBARI-23275
> URL: https://issues.apache.org/jira/browse/AMBARI-23275
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: trunk
>
[jira] [Assigned] (AMBARI-23275) Upgrade maven dependency for jdeb and fic rpm autorequire tag value
[ https://issues.apache.org/jira/browse/AMBARI-23275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-23275: -- Assignee: Aman Poonia > Upgrade maven dependency for jdeb and fic rpm autorequire tag value > --- > > Key: AMBARI-23275 > URL: https://issues.apache.org/jira/browse/AMBARI-23275 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Aman Poonia >Assignee: Aman Poonia >Priority: Minor > Labels: pull-request-available > Fix For: trunk > > Time Spent: 2h 50m > Remaining Estimate: 0h > > Update jdeb from 1.0.1 to 1.6 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23334) Provider URL validator incorrect when setting up SSO via Ambari CLI
[
https://issues.apache.org/jira/browse/AMBARI-23334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417775#comment-16417775
]
Hudson commented on AMBARI-23334:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8933 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8933/])
[AMBARI-23334] Using the proper regular expression to validate SSO (m.magyar3:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=7a318d95d7c142dbfd10eb4c26c2cb2d8ad89c1f])
* (edit) ambari-server/src/main/python/ambari_server/setupSso.py
* (edit) ambari-server/src/test/python/TestSetupSso.py
> Provider URL validator incorrect when setting up SSO via Ambari CLI
> ---
>
> Key: AMBARI-23334
> URL: https://issues.apache.org/jira/browse/AMBARI-23334
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> When setting the URL for the SSO provider while running {{ambari-server
> setup-sso}}, valid URLs are rejected.
> {noformat}
> [root@c7402 ~]# ambari-server setup-sso
> Using python /usr/bin/python
> Setting up SSO authentication properties...
> Do you want to configure SSO authentication [y/n] (y)?y
> Provider URL [URL]
> (http://example.com):https://c7402.ambari.apache.org:8443/gateway/knoxsso/api/v1/websso
> Invalid provider URL
> Provider URL [URL] (http://example.com):c7402.ambari.apache.org:8443
> Public Certificate pem (empty) (empty line to finish input):
> {noformat}
> Cause:
> The RegEx validating the URL is only allowing hostname and port values, when
> it should allow for absolute URLs.
> {code:java|title=ambari_server/setupSso.py:72}
> provider_url = get_validated_string_input("Provider URL [URL]
> ({0}):".format(provider_url), provider_url, REGEX_HOSTNAME_PORT,
> "Invalid provider URL",
> False){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23275) Upgrade maven dependency for jdeb and fic rpm autorequire tag value
[ https://issues.apache.org/jira/browse/AMBARI-23275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417795#comment-16417795 ] Aravindan Vijayan commented on AMBARI-23275: [~mnpoonia] I have reverted the patch. Please take a look at the RPM build failure. I will also take a look at why this is failing. In the next 2-3 days, I will be merging the AMS perf branch (https://github.com/avijayanhwx/ambari/tree/AMBARI-23100-trunk) which carries about 40 commits. Since this is an improvement JIRA, it would be great if you built and committed your patch against trunk after the merge. cc [~adoroszlai] > Upgrade maven dependency for jdeb and fic rpm autorequire tag value > --- > > Key: AMBARI-23275 > URL: https://issues.apache.org/jira/browse/AMBARI-23275 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Aman Poonia >Assignee: Aman Poonia >Priority: Minor > Labels: pull-request-available > Fix For: trunk > > Time Spent: 3h 10m > Remaining Estimate: 0h > > Update jdeb from 1.0.1 to 1.6 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23386) HSI Jdbc URL should handle HA mode
[ https://issues.apache.org/jira/browse/AMBARI-23386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417845#comment-16417845 ] Hudson commented on AMBARI-23386: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8934 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8934/]) AMBARI-23386 HSI Jdbc URL should handle HA mode (mgergely) (mgergely: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=074c01ffbdec8b11ddfac78cfa41ee4f86ac60a0]) * (edit) ambari-web/app/controllers/main/service/info/summary.js * (edit) ambari-web/app/messages.js > HSI Jdbc URL should handle HA mode > -- > > Key: AMBARI-23386 > URL: https://issues.apache.org/jira/browse/AMBARI-23386 > Project: Ambari > Issue Type: Bug >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23394) Group_list should also look for properties in cluster settings besides desired configs.
Madhuvanthi Radhakrishnan created AMBARI-23394: -- Summary: Group_list should also look for properties in cluster settings besides desired configs. Key: AMBARI-23394 URL: https://issues.apache.org/jira/browse/AMBARI-23394 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 3.0.0 The desiredconfigs contains only service configs. In the previous ambari version, it also used to have cluster-env configs but now since we have moved to cluster settings, the properties in cluster settings are not part of the desired configs. Hence, while searching for the group_list and user_list for setting in the command.json, we need to explicitly look for the properties in cluster settings as well. cc [~sshridhar], [~jluniya] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23275) Upgrade maven dependency for jdeb and fic rpm autorequire tag value
[ https://issues.apache.org/jira/browse/AMBARI-23275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417906#comment-16417906 ] Hudson commented on AMBARI-23275: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8935 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8935/]) Revert "AMBARI-23275. Upgrade jdeb and rpm-maven-plugin (#698)" (avijayan: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c6ef58d46e9b563f8f9e261107e242f018418f70]) * (edit) ambari-metrics/ambari-metrics-assembly/pom.xml * (edit) ambari-views/examples/calculator-view/pom.xml * (edit) ambari-views/examples/favorite-view/pom.xml * (edit) ambari-utility/pom.xml * (edit) ambari-views/examples/restricted-view/pom.xml * (edit) ambari-logsearch/ambari-logsearch-assembly/pom.xml * (edit) ambari-views/examples/property-view/pom.xml * (edit) ambari-metrics/ambari-metrics-flume-sink/pom.xml * (edit) ambari-views/examples/hello-spring-view/pom.xml * (edit) ambari-views/examples/helloworld-view/pom.xml * (edit) contrib/views/files/pom.xml * (edit) ambari-infra/ambari-infra-assembly/pom.xml * (edit) ambari-views/examples/phone-list-view/pom.xml * (edit) ambari-metrics/ambari-metrics-storm-sink-legacy/pom.xml * (edit) contrib/ambari-log4j/pom.xml * (edit) contrib/management-packs/pom.xml * (edit) contrib/views/jobs/pom.xml * (edit) ambari-metrics/ambari-metrics-host-monitoring/pom.xml * (edit) contrib/views/tez/pom.xml * (edit) ambari-views/examples/phone-list-upgrade-view/pom.xml * (edit) contrib/views/hive20/pom.xml * (edit) contrib/views/pom.xml * (edit) ambari-server/pom.xml * (edit) contrib/views/ambari-views-package/pom.xml * (edit) ambari-metrics/ambari-metrics-hadoop-sink/pom.xml * (edit) contrib/ambari-scom/ambari-scom-server/pom.xml * (edit) ambari-admin/pom.xml * (edit) ambari-metrics/pom.xml * (edit) ambari-web/pom.xml * (edit) ambari-serviceadvisor/pom.xml * (edit) ambari-metrics/ambari-metrics-timelineservice/pom.xml * (edit) ambari-views/examples/cluster-view/pom.xml * (edit) contrib/views/capacity-scheduler/pom.xml * (edit) contrib/views/hive-next/pom.xml * (edit) contrib/views/pig/pom.xml * (edit) ambari-metrics/ambari-metrics-storm-sink/pom.xml * (edit) ambari-views/examples/hello-servlet-view/pom.xml * (edit) ambari-metrics/ambari-metrics-kafka-sink/pom.xml * (edit) contrib/views/storm/pom.xml * (edit) ambari-views/examples/auto-cluster-view/pom.xml * (edit) ambari-views/examples/weather-view/pom.xml * (edit) contrib/ambari-scom/metrics-sink/pom.xml * (edit) pom.xml * (edit) ambari-views/examples/simple-view/pom.xml * (edit) ambari-views/examples/property-validator-view/pom.xml * (edit) ambari-agent/pom.xml * (edit) ambari-metrics/ambari-metrics-common/pom.xml * (edit) ambari-views/pom.xml > Upgrade maven dependency for jdeb and fic rpm autorequire tag value > --- > > Key: AMBARI-23275 > URL: https://issues.apache.org/jira/browse/AMBARI-23275 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Aman Poonia >Assignee: Aman Poonia >Priority: Minor > Labels: pull-request-available > Fix For: trunk > > Time Spent: 3h 10m > Remaining Estimate: 0h > > Update jdeb from 1.0.1 to 1.6 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23391) Remove FK Relationship On Repo Versions for Services & Components
[
https://issues.apache.org/jira/browse/AMBARI-23391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-23391.
--
Resolution: Fixed
> Remove FK Relationship On Repo Versions for Services & Components
> -
>
> Key: AMBARI-23391
> URL: https://issues.apache.org/jira/browse/AMBARI-23391
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As part of AMBARI-23009, this will remove the reliance that services and
> components have on the {{repo_version}} table. It will also attempt to
> address some of the many, many unit test failures in the branch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23334) Provider URL validator incorrect when setting up SSO via Ambari CLI
[
https://issues.apache.org/jira/browse/AMBARI-23334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated AMBARI-23334:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Provider URL validator incorrect when setting up SSO via Ambari CLI
> ---
>
> Key: AMBARI-23334
> URL: https://issues.apache.org/jira/browse/AMBARI-23334
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> When setting the URL for the SSO provider while running {{ambari-server
> setup-sso}}, valid URLs are rejected.
> {noformat}
> [root@c7402 ~]# ambari-server setup-sso
> Using python /usr/bin/python
> Setting up SSO authentication properties...
> Do you want to configure SSO authentication [y/n] (y)?y
> Provider URL [URL]
> (http://example.com):https://c7402.ambari.apache.org:8443/gateway/knoxsso/api/v1/websso
> Invalid provider URL
> Provider URL [URL] (http://example.com):c7402.ambari.apache.org:8443
> Public Certificate pem (empty) (empty line to finish input):
> {noformat}
> Cause:
> The RegEx validating the URL is only allowing hostname and port values, when
> it should allow for absolute URLs.
> {code:java|title=ambari_server/setupSso.py:72}
> provider_url = get_validated_string_input("Provider URL [URL]
> ({0}):".format(provider_url), provider_url, REGEX_HOSTNAME_PORT,
> "Invalid provider URL",
> False){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23395) Remove duplicates from messages.js
Jason Golieb created AMBARI-23395: - Summary: Remove duplicates from messages.js Key: AMBARI-23395 URL: https://issues.apache.org/jira/browse/AMBARI-23395 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Jason Golieb Assignee: Jason Golieb Fix For: 3.0.0 There are duplicate keys in messages.js due to merging. These must be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23396) Incorrect HDP version in UI after HDP upgrade
amarnath reddy pappu created AMBARI-23396: - Summary: Incorrect HDP version in UI after HDP upgrade Key: AMBARI-23396 URL: https://issues.apache.org/jira/browse/AMBARI-23396 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.6.1 Reporter: amarnath reddy pappu Steps to reproduce 1. Install the cluster with HDP 2.6.2 2. Upgrade cluster to HDP 2.6.4 3. Now try to add a host. 4. In review page you would see as below - showing HDP2.6.2 instead of 2.6.4 repo:/HDP/2.6/redhat6/HDP-2.6:baseurl http:///HDP2.6.2/HDP-centos6/centos6/ though installation seems to be happening with 2.6.4 but UI shows incorrect information This is misleading and customers raising tickets. Root cause: metainfo tables were still pointing to 2.6.2 correcting that would resolve the issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23396) Incorrect HDP version in UI after HDP upgrade
[ https://issues.apache.org/jira/browse/AMBARI-23396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnath reddy pappu updated AMBARI-23396: -- Description: Steps to reproduce 1. Install the cluster with HDP 2.6.2 2. Upgrade cluster to HDP 2.6.4 3. Now try to add a host. 4. In review page you would see as below - showing HDP2.6.2 instead of 2.6.4 repo:/HDP/2.6/redhat6/HDP-2.6:baseurl http:///HDP2.6.2/HDP-centos6/centos6/ though installation seems to be happening with 2.6.4 but UI shows incorrect information This is misleading and customers raising tickets. Root cause: metainfo tables were still pointing to 2.6.2 , correcting that would resolve the issue. was: Steps to reproduce 1. Install the cluster with HDP 2.6.2 2. Upgrade cluster to HDP 2.6.4 3. Now try to add a host. 4. In review page you would see as below - showing HDP2.6.2 instead of 2.6.4 repo:/HDP/2.6/redhat6/HDP-2.6:baseurl http:///HDP2.6.2/HDP-centos6/centos6/ though installation seems to be happening with 2.6.4 but UI shows incorrect information This is misleading and customers raising tickets. Root cause: metainfo tables were still pointing to 2.6.2 correcting that would resolve the issue. > Incorrect HDP version in UI after HDP upgrade > - > > Key: AMBARI-23396 > URL: https://issues.apache.org/jira/browse/AMBARI-23396 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: amarnath reddy pappu >Priority: Major > > Steps to reproduce > 1. Install the cluster with HDP 2.6.2 > 2. Upgrade cluster to HDP 2.6.4 > 3. Now try to add a host. > 4. In review page you would see as below - showing HDP2.6.2 instead of 2.6.4 > repo:/HDP/2.6/redhat6/HDP-2.6:baseurl > http:///HDP2.6.2/HDP-centos6/centos6/ > though installation seems to be happening with 2.6.4 but UI shows incorrect > information > This is misleading and customers raising tickets. > Root cause: metainfo tables were still pointing to 2.6.2 , correcting that > would resolve the issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23394) Group_list should also look for properties in cluster settings besides desired configs.
[ https://issues.apache.org/jira/browse/AMBARI-23394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23394: Labels: pull-request-available (was: ) > Group_list should also look for properties in cluster settings besides > desired configs. > --- > > Key: AMBARI-23394 > URL: https://issues.apache.org/jira/browse/AMBARI-23394 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > The desiredconfigs contains only service configs. > In the previous ambari version, it also used to have cluster-env configs but > now since we have moved to cluster settings, the properties in cluster > settings are not part of the desired configs. > Hence, while searching for the group_list and user_list for setting in the > command.json, we need to explicitly look for the properties in cluster > settings as well. > cc [~sshridhar], [~jluniya] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23397) Blueprint deployments for NameNode Federation Fail
Robert Nettleton created AMBARI-23397:
-
Summary: Blueprint deployments for NameNode Federation Fail
Key: AMBARI-23397
URL: https://issues.apache.org/jira/browse/AMBARI-23397
Project: Ambari
Issue Type: Bug
Components: ambari-sever
Affects Versions: 2.7.0
Reporter: Robert Nettleton
Assignee: Robert Nettleton
Fix For: 2.7.0
Ambari 2.7.0 will include support for HDFS NameNode Federation deployments, as
detailed in:
AMBARI-22916
Blueprint deployments that attempt to use NameNode Federation currently fail
with the following exception:
{code:java}
{u'status': 400, u'message': u'Topology validation failed:
org.apache.ambari.server.topology.InvalidTopologyException: NAMENODE HA
requires exactly 2 hosts running NAMENODE but there are: 4 Hosts:
[ctr-e138-1518143905142-139109-01-05.hwx.site,
ctr-e138-1518143905142-139109-01-06.hwx.site,
ctr-e138-1518143905142-139109-01-03.hwx.site,
ctr-e138-1518143905142-139109-01-04.hwx.site]'}{code}
The Blueprint configuration processor needs to be updated in order to properly
handle HDFS HA deployments that include Federated nameservices. This will
generally mean that HA deployments can now support more than 2 NameNode
instances.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23398) Fix merge issues in branch-feature-AMBARI-14714
Jayush Luniya created AMBARI-23398: -- Summary: Fix merge issues in branch-feature-AMBARI-14714 Key: AMBARI-23398 URL: https://issues.apache.org/jira/browse/AMBARI-23398 Project: Ambari Issue Type: Bug Components: ambari-agent, ambari-server Affects Versions: 3.0.0 Reporter: Jayush Luniya Assignee: Jayush Luniya Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23398) Fix merge issues in branch-feature-AMBARI-14714
[ https://issues.apache.org/jira/browse/AMBARI-23398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23398: Labels: pull-request-available (was: ) > Fix merge issues in branch-feature-AMBARI-14714 > --- > > Key: AMBARI-23398 > URL: https://issues.apache.org/jira/browse/AMBARI-23398 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 3.0.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23397) Blueprint deployments for NameNode Federation Fail
[
https://issues.apache.org/jira/browse/AMBARI-23397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23397:
Labels: pull-request-available (was: )
> Blueprint deployments for NameNode Federation Fail
> --
>
> Key: AMBARI-23397
> URL: https://issues.apache.org/jira/browse/AMBARI-23397
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.7.0
>Reporter: Robert Nettleton
>Assignee: Robert Nettleton
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> Ambari 2.7.0 will include support for HDFS NameNode Federation deployments,
> as detailed in:
> AMBARI-22916
> Blueprint deployments that attempt to use NameNode Federation currently fail
> with the following exception:
>
> {code:java}
> {u'status': 400, u'message': u'Topology validation failed:
> org.apache.ambari.server.topology.InvalidTopologyException: NAMENODE HA
> requires exactly 2 hosts running NAMENODE but there are: 4 Hosts:
> [ctr-e138-1518143905142-139109-01-05.hwx.site,
> ctr-e138-1518143905142-139109-01-06.hwx.site,
> ctr-e138-1518143905142-139109-01-03.hwx.site,
> ctr-e138-1518143905142-139109-01-04.hwx.site]'}{code}
>
> The Blueprint configuration processor needs to be updated in order to
> properly handle HDFS HA deployments that include Federated nameservices.
> This will generally mean that HA deployments can now support more than 2
> NameNode instances.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23397) Blueprint deployments for NameNode Federation Fail
[
https://issues.apache.org/jira/browse/AMBARI-23397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Nettleton updated AMBARI-23397:
--
Status: Patch Available (was: In Progress)
> Blueprint deployments for NameNode Federation Fail
> --
>
> Key: AMBARI-23397
> URL: https://issues.apache.org/jira/browse/AMBARI-23397
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.7.0
>Reporter: Robert Nettleton
>Assignee: Robert Nettleton
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ambari 2.7.0 will include support for HDFS NameNode Federation deployments,
> as detailed in:
> AMBARI-22916
> Blueprint deployments that attempt to use NameNode Federation currently fail
> with the following exception:
>
> {code:java}
> {u'status': 400, u'message': u'Topology validation failed:
> org.apache.ambari.server.topology.InvalidTopologyException: NAMENODE HA
> requires exactly 2 hosts running NAMENODE but there are: 4 Hosts:
> [ctr-e138-1518143905142-139109-01-05.hwx.site,
> ctr-e138-1518143905142-139109-01-06.hwx.site,
> ctr-e138-1518143905142-139109-01-03.hwx.site,
> ctr-e138-1518143905142-139109-01-04.hwx.site]'}{code}
>
> The Blueprint configuration processor needs to be updated in order to
> properly handle HDFS HA deployments that include Federated nameservices.
> This will generally mean that HA deployments can now support more than 2
> NameNode instances.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-23388) Hostlist view selection bug
[ https://issues.apache.org/jira/browse/AMBARI-23388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JaySenSharma reassigned AMBARI-23388: - Assignee: JaySenSharma > Hostlist view selection bug > --- > > Key: AMBARI-23388 > URL: https://issues.apache.org/jira/browse/AMBARI-23388 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Zoltan Haindrich >Assignee: JaySenSharma >Priority: Major > > * open hostlist view > * select a node with the checkbox > * top right actions list: "Selected Hosts (1)" (ok) > * switch to any other view > * switch back to hostlist view > * node is *still* selected > * top right actions list "Selected Hosts (0)" > the list should be either cleared from the selection; or the action should be > available -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23388) Hostlist view selection bug
[ https://issues.apache.org/jira/browse/AMBARI-23388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23388: Labels: pull-request-available (was: ) > Hostlist view selection bug > --- > > Key: AMBARI-23388 > URL: https://issues.apache.org/jira/browse/AMBARI-23388 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Zoltan Haindrich >Assignee: JaySenSharma >Priority: Major > Labels: pull-request-available > > * open hostlist view > * select a node with the checkbox > * top right actions list: "Selected Hosts (1)" (ok) > * switch to any other view > * switch back to hostlist view > * node is *still* selected > * top right actions list "Selected Hosts (0)" > the list should be either cleared from the selection; or the action should be > available -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23388) Hostlist view selection bug
[ https://issues.apache.org/jira/browse/AMBARI-23388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JaySenSharma updated AMBARI-23388: -- Status: Patch Available (was: In Progress) https://github.com/apache/ambari/pull/823 > Hostlist view selection bug > --- > > Key: AMBARI-23388 > URL: https://issues.apache.org/jira/browse/AMBARI-23388 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Zoltan Haindrich >Assignee: JaySenSharma >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > * open hostlist view > * select a node with the checkbox > * top right actions list: "Selected Hosts (1)" (ok) > * switch to any other view > * switch back to hostlist view > * node is *still* selected > * top right actions list "Selected Hosts (0)" > the list should be either cleared from the selection; or the action should be > available -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23388) Hostlist view selection bug
[ https://issues.apache.org/jira/browse/AMBARI-23388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JaySenSharma updated AMBARI-23388: -- Affects Version/s: trunk > Hostlist view selection bug > --- > > Key: AMBARI-23388 > URL: https://issues.apache.org/jira/browse/AMBARI-23388 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.7.0 >Reporter: Zoltan Haindrich >Assignee: JaySenSharma >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > * open hostlist view > * select a node with the checkbox > * top right actions list: "Selected Hosts (1)" (ok) > * switch to any other view > * switch back to hostlist view > * node is *still* selected > * top right actions list "Selected Hosts (0)" > the list should be either cleared from the selection; or the action should be > available -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23389) Install Packages button on the versions screen fails if there is a service installed which was removed
[
https://issues.apache.org/jira/browse/AMBARI-23389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-23389:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Install Packages button on the versions screen fails if there is a service
> installed which was removed
> --
>
> Key: AMBARI-23389
> URL: https://issues.apache.org/jira/browse/AMBARI-23389
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> I've installed several services with Ambari 2.6.1 - HDP 2.6.4, then upgraded
> Ambari to 2.7. After this I've added a new HDP 3.0 repo. As Slider was
> installed which was removed from HDP 3.0, it displayed a white "i" in a blue
> circle in the 3.0 column (see the screenshot). As I'v clicked on the "Install
> Packages" button it returned an error message (see screenshot). I've checked
> the log, and it seems that the absence of the Slider service caused the issue:
> {code}
> org.apache.ambari.server.controller.spi.SystemException: Cannot obtain stack
> information for HDP-3.0
> at
> org.apache.ambari.server.state.stack.upgrade.RepositoryVersionHelper.buildRoleParams(RepositoryVersionHelper.java:305)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:723)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:118)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createOrchestration(ClusterStackVersionResourceProvider.java:634)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:118)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createOrUpdateHostVersions(ClusterStackVersionResourceProvider.java:532)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:128)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:474)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:231)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:296)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:50)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:163)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:127)
> at
> org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:120)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> 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.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> 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
> c
[jira] [Resolved] (AMBARI-23384) PQS start fails after Ambari upgrade due to Bad file descriptor
[
https://issues.apache.org/jira/browse/AMBARI-23384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar resolved AMBARI-23384.
Resolution: Fixed
> PQS start fails after Ambari upgrade due to Bad file descriptor
> ---
>
> Key: AMBARI-23384
> URL: https://issues.apache.org/jira/browse/AMBARI-23384
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vivek Sharma
>Assignee: Attila Magyar
>Priority: Critical
> Labels: pull-request-available, upgrade
> Fix For: 2.7.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> *STR*
> PQS start after Ambari upgrade to 2.7.0 failed with below error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/phoenix_queryserver.py",
> line 81, in
> PhoenixQueryServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 356, in execute
> self.execute_prefix_function(self.command_name, 'post', env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 377, in execute_prefix_function
> method(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 419, in post_start
> raise Fail("Pid file \{0} doesn't exist after starting of the
> component.".format(pid_file))
> resource_management.core.exceptions.Fail: Pid file
> /var/run/hbase/phoenix-hbase-server.pid doesn't exist after starting of the
> component.
> {code}
> The log says the following:
> {code}
> 2018-03-26 16:33:13.563112 launching /base/tools/jdk1.8.0_112/bin/java -cp
> /usr/hdp/current/hbase-client/conf:/etc/hadoop/conf:/grid/0/hdp/2.6.4.0-91/phoenix/bin/../phoenix-4.7.0.2.6.4.0-91-client.jar:/grid/0/hdp/2.6.4.0-91/phoenix/bin/../phoenix-4.7.0.2.6.4.0-91-queryserver.jar:/usr/hdp/2.6.4.0-91/hadoop/conf:/usr/hdp/2.6.4.0-91/hadoop/lib/*:/usr/hdp/2.6.4.0-91/hadoop/.//*:/usr/hdp/2.6.4.0-91/hadoop-hdfs/./:/usr/hdp/2.6.4.0-91/hadoop-hdfs/lib/*:/usr/hdp/2.6.4.0-91/hadoop-hdfs/.//*:/usr/hdp/2.6.4.0-91/hadoop-yarn/lib/*:/usr/hdp/2.6.4.0-91/hadoop-yarn/.//*:/usr/hdp/2.6.4.0-91/hadoop-mapreduce/lib/*:/usr/hdp/2.6.4.0-91/hadoop-mapreduce/.//*::mysql-connector-java-5.1.33-bin.jar:mysql-connector-java.jar:/grid/0/hdp/2.6.4.0-91/tez/*:/grid/0/hdp/2.6.4.0-91/tez/lib/*:/grid/0/hdp/2.6.4.0-91/tez/conf
> -Dproc_phoenixserver
> -Dlog4j.configuration=file:/grid/0/hdp/2.6.4.0-91/phoenix/bin/log4j.properties
> -Dpsql.root.logger=INFO,DRFA -Dpsql.log.dir=/grid/0/log/hbase
> -Dpsql.log.file=phoenix-hbase-server.log
> org.apache.phoenix.queryserver.server.Main
> close failed in file object destructor:
> IOError: [Errno 9] Bad file descriptor
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/grid/0/hdp/2.6.4.0-91/phoenix/phoenix-4.7.0.2.6.4.0-91-client.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/grid/0/hdp/2.6.4.0-91/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> starting Query Server, logging to /grid/0/log/hbase/phoenix-hbase-server.log
> Query Server already running, PID file found:
> /var/run/hbase/phoenix-hbase-server.pid
> close failed in file object destructor:
> IOError: [Errno 9] Bad file descriptor
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
