[jira] [Created] (AMBARI-25024) Integrate add service API with StackAdvisor's Configuration recommendations
Balázs Bence Sári created AMBARI-25024: -- Summary: Integrate add service API with StackAdvisor's Configuration recommendations Key: AMBARI-25024 URL: https://issues.apache.org/jira/browse/AMBARI-25024 Project: Ambari Issue Type: Task Affects Versions: 2.7.1 Reporter: Balázs Bence Sári Assignee: Balázs Bence Sári Fix For: trunk This work involves integrating with the StackAdvisor's recommendations for configuration for the "Add Service" request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25023) Admin View cannot be Deployed Due to META-INF Ordering
[
https://issues.apache.org/jira/browse/AMBARI-25023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-25023:
Labels: pull-request-available (was: )
> Admin View cannot be Deployed Due to META-INF Ordering
> --
>
> Key: AMBARI-25023
> URL: https://issues.apache.org/jira/browse/AMBARI-25023
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.8.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
> The new build process which was changed in AMBARI-24804 is causing JARs to be
> built slightly differently:
> {code:title=unzip -l ambari-admin-2.7.3.0.0.jar | grep META-INF}
> 0 12-07-2018 10:53 META-INF/
> 133 12-07-2018 10:53 META-INF/MANIFEST.MF
> 0 12-07-2018 10:53 META-INF/maven/
> 0 12-07-2018 10:53 META-INF/maven/org.apache.ambari/
> 0 12-07-2018 10:53 META-INF/maven/org.apache.ambari/ambari-admin/
> 0 12-05-2018 14:31
> META-INF/maven/org.apache.ambari/ambari-admin/pom.xml
> 118 12-07-2018 10:53
> META-INF/maven/org.apache.ambari/ambari-admin/pom.properties
> {code}
> {code:title=unzip -l ambari-admin-3.0.0.0-SNAPSHOT.jar | grep META-INF}
> 473 12-07-2018 11:37 META-INF/MANIFEST.MF
> 0 12-07-2018 11:37 META-INF/
> 0 12-07-2018 11:37 META-INF/maven/
> 0 12-07-2018 11:37 META-INF/maven/org.apache.ambari/
> 0 12-07-2018 11:37 META-INF/maven/org.apache.ambari/ambari-admin/
> 106 12-07-2018 11:37
> META-INF/maven/org.apache.ambari/ambari-admin/pom.properties
> 11358 12-07-2018 11:37 META-INF/LICENSE
> 5060 12-07-2018 11:37
> META-INF/maven/org.apache.ambari/ambari-admin/pom.xml
> 267 12-07-2018 11:37 META-INF/DEPENDENCIES
> 165 12-07-2018 11:37 META-INF/NOTICE
> {code}
> Since the file {{META-INF/MANIFEST.MF}} appears before {{META-INF}}, it
> exposes a bug in the {{ViewExtractor}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-25023) Admin View cannot be Deployed Due to META-INF Ordering
Jonathan Hurley created AMBARI-25023:
Summary: Admin View cannot be Deployed Due to META-INF Ordering
Key: AMBARI-25023
URL: https://issues.apache.org/jira/browse/AMBARI-25023
Project: Ambari
Issue Type: Bug
Components: ambari-admin
Affects Versions: 2.8.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.8.0
The new build process which was changed in AMBARI-24804 is causing JARs to be
built slightly differently:
{code:title=unzip -l ambari-admin-2.7.3.0.0.jar | grep META-INF}
0 12-07-2018 10:53 META-INF/
133 12-07-2018 10:53 META-INF/MANIFEST.MF
0 12-07-2018 10:53 META-INF/maven/
0 12-07-2018 10:53 META-INF/maven/org.apache.ambari/
0 12-07-2018 10:53 META-INF/maven/org.apache.ambari/ambari-admin/
0 12-05-2018 14:31
META-INF/maven/org.apache.ambari/ambari-admin/pom.xml
118 12-07-2018 10:53
META-INF/maven/org.apache.ambari/ambari-admin/pom.properties
{code}
{code:title=unzip -l ambari-admin-3.0.0.0-SNAPSHOT.jar | grep META-INF}
473 12-07-2018 11:37 META-INF/MANIFEST.MF
0 12-07-2018 11:37 META-INF/
0 12-07-2018 11:37 META-INF/maven/
0 12-07-2018 11:37 META-INF/maven/org.apache.ambari/
0 12-07-2018 11:37 META-INF/maven/org.apache.ambari/ambari-admin/
106 12-07-2018 11:37
META-INF/maven/org.apache.ambari/ambari-admin/pom.properties
11358 12-07-2018 11:37 META-INF/LICENSE
5060 12-07-2018 11:37
META-INF/maven/org.apache.ambari/ambari-admin/pom.xml
267 12-07-2018 11:37 META-INF/DEPENDENCIES
165 12-07-2018 11:37 META-INF/NOTICE
{code}
Since the file {{META-INF/MANIFEST.MF}} appears before {{META-INF}}, it exposes
a bug in the {{ViewExtractor}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-25022) Allow DB setup with password from file
Doroszlai, Attila created AMBARI-25022:
--
Summary: Allow DB setup with password from file
Key: AMBARI-25022
URL: https://issues.apache.org/jira/browse/AMBARI-25022
Project: Ambari
Issue Type: Improvement
Components: ambari-server
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Fix For: 2.8.0
Unattended {{ambari-server setup}} for remote DB requires that all parameters
including the password be specified on the command-line. It would be more safe
to allow passing the password from a file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-25021) ambari-server setup fails without local Postgres even for remote DBs
Doroszlai, Attila created AMBARI-25021:
--
Summary: ambari-server setup fails without local Postgres even for
remote DBs
Key: AMBARI-25021
URL: https://issues.apache.org/jira/browse/AMBARI-25021
Project: Ambari
Issue Type: Improvement
Components: ambari-server
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Fix For: 2.8.0
The call to setup Ambari Server with a remote DB fails if Ambari Server host
doesn't have Postgres installed.
{noformat:title=ambari-server setup -s --database mysql --databasehost db
--databaseport=3306 --databasename ambari --databaseusername=ambari
--databasepassword=bigdata}
Using python /usr/bin/python
Setup ambari-server
Traceback (most recent call last):
File "/usr/sbin/ambari-server.py", line 45, in
from ambari_server.serverSetup import reset, setup, setup_jce_policy,
setup_jdbc
File "/usr/lib/ambari-server/lib/ambari_server/serverSetup.py", line 89, in
JDBC_DB_OPTION_VALUES = get_supported_jdbc_drivers()
File "/usr/lib/ambari-server/lib/ambari_server/serverSetup.py", line 86, in
get_supported_jdbc_drivers
factory = DBMSConfigFactory()
File "/usr/lib/ambari-server/lib/ambari_server/dbConfiguration.py", line 390,
in __init__
from ambari_server.dbConfiguration_linux import createPGConfig,
createOracleConfig, createMySQLConfig, \
File "/usr/lib/ambari-server/lib/ambari_server/dbConfiguration_linux.py",
line 348, in
class PGConfig(LinuxDBMSConfig):
File "/usr/lib/ambari-server/lib/ambari_server/dbConfiguration_linux.py",
line 378, in PGConfig
raise FatalException(1, "Cannot find postgresql-setup script.")
ambari_commons.exceptions.FatalException: 'Fatal exception: Cannot find
postgresql-setup script., exit code 1'
{noformat}
The {{ambari-server}} package has dependency on {{postgresql-server}}. Still,
it would be nice not to fail unnecessarily.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-25020) Allow unattended mpack install with purge
Doroszlai, Attila created AMBARI-25020:
--
Summary: Allow unattended mpack install with purge
Key: AMBARI-25020
URL: https://issues.apache.org/jira/browse/AMBARI-25020
Project: Ambari
Issue Type: Improvement
Components: ambari-server
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Fix For: 2.8.0
The question that pops up if {{purge}} is specified prevents installing mpacks
without user input. The default answer is "no", which gets automatically
selected in {{silent}} mode, causing the installation to be cancelled.
{noformat:title=ambari-server install-mpack --purge --silent --verbose
--mpack=...}
...
CAUTION: You have specified the --purge option with
--purge-list=['stack-definitions', 'mpacks']. This will replace all existing
stack definitions, management packs currently installed.
Are you absolutely sure you want to perform the purge [yes/no]? (no)
ERROR: Exiting with exit code 1.
REASON: Management pack installation cancelled by user
{noformat}
The default answer should be "no" for regular mode, but "yes" for silent mode,
to make unattended install possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24833) Log Feeder: send logs to cloud storage (gcs/s3 etc.)
[ https://issues.apache.org/jira/browse/AMBARI-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713178#comment-16713178 ] Hudson commented on AMBARI-24833: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #77 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/77/]) AMBARI-24833. Get rid of custom time based triggering policy (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=26485f24e5f72f1d1c801f72bc718927c3daed12]) * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/CloudStorageLoggerFactory.java * (delete) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/CustomTimeBasedTriggeringPolicy.java * (edit) ambari-logsearch-logfeeder/src/main/resources/logfeeder.properties > Log Feeder: send logs to cloud storage (gcs/s3 etc.) > > > Key: AMBARI-24833 > URL: https://issues.apache.org/jira/browse/AMBARI-24833 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25017) [Log Search UI] Replace Log Search favicon with Ambari's favicon
[ https://issues.apache.org/jira/browse/AMBARI-25017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713080#comment-16713080 ] Hudson commented on AMBARI-25017: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #76 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/76/]) [AMBARI-25017] [Log Search UI] Replace Log Search favicon with Ambari's (github: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=1e8350c62ad9c5b9b21140f8b5bc55292c864251]) * (edit) ambari-logsearch-web/src/favicon.ico > [Log Search UI] Replace Log Search favicon with Ambari's favicon > > > Key: AMBARI-25017 > URL: https://issues.apache.org/jira/browse/AMBARI-25017 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 0.5h > Remaining Estimate: 0.5h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24996) Hostname update command does not work if the new hostnames contain the old hostnames also
[ https://issues.apache.org/jira/browse/AMBARI-24996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko resolved AMBARI-24996. - Resolution: Fixed > Hostname update command does not work if the new hostnames contain the old > hostnames also > - > > Key: AMBARI-24996 > URL: https://issues.apache.org/jira/browse/AMBARI-24996 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h > Remaining Estimate: 0h > > In AMBARI-24840, we made a fix so that the uppercase hostnames are taken care > of. > Another issue related to hostnames change is about duplicate hostnames. If > the hostnames file contains the pre-existing hostnames, the update process > fails with exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25017) [Log Search UI] Replace Log Search favicon with Ambari's favicon
[ https://issues.apache.org/jira/browse/AMBARI-25017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-25017: --- Resolution: Fixed Status: Resolved (was: Patch Available) > [Log Search UI] Replace Log Search favicon with Ambari's favicon > > > Key: AMBARI-25017 > URL: https://issues.apache.org/jira/browse/AMBARI-25017 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 0.5h > Remaining Estimate: 0.5h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25017) [Log Search UI] Replace Log Search favicon with Ambari's favicon
[ https://issues.apache.org/jira/browse/AMBARI-25017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713072#comment-16713072 ] ASF GitHub Bot commented on AMBARI-25017: - tobias-istvan closed pull request #60: [AMBARI-25017] [Log Search UI] Replace Log Search favicon with Ambari's favicon URL: https://github.com/apache/ambari-logsearch/pull/60 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/ambari-logsearch-web/src/favicon.ico b/ambari-logsearch-web/src/favicon.ico index 62604cb19f..4b7044d78c 100644 Binary files a/ambari-logsearch-web/src/favicon.ico and b/ambari-logsearch-web/src/favicon.ico differ This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [Log Search UI] Replace Log Search favicon with Ambari's favicon > > > Key: AMBARI-25017 > URL: https://issues.apache.org/jira/browse/AMBARI-25017 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 0.5h > Remaining Estimate: 0.5h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25017) [Log Search UI] Replace Log Search favicon with Ambari's favicon
[ https://issues.apache.org/jira/browse/AMBARI-25017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713061#comment-16713061 ] ASF GitHub Bot commented on AMBARI-25017: - asfgit commented on issue #60: [AMBARI-25017] [Log Search UI] Replace Log Search favicon with Ambari's favicon URL: https://github.com/apache/ambari-logsearch/pull/60#issuecomment-445288669 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/119/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [Log Search UI] Replace Log Search favicon with Ambari's favicon > > > Key: AMBARI-25017 > URL: https://issues.apache.org/jira/browse/AMBARI-25017 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 0.5h > Remaining Estimate: 0.5h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25019) Update Ambari audit logger to handle proxied users
Dmitry Lysnichenko created AMBARI-25019: --- Summary: Update Ambari audit logger to handle proxied users Key: AMBARI-25019 URL: https://issues.apache.org/jira/browse/AMBARI-25019 Project: Ambari Issue Type: Task Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Update Ambari audit logger to handle proxied users. All logging should be able to specify the authenticated proxy user as well as the proxied user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25019) Update Ambari audit logger to handle proxied users
[ https://issues.apache.org/jira/browse/AMBARI-25019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-25019: Affects Version/s: 2.8.0 > Update Ambari audit logger to handle proxied users > -- > > Key: AMBARI-25019 > URL: https://issues.apache.org/jira/browse/AMBARI-25019 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Major > Fix For: 2.8.0 > > > Update Ambari audit logger to handle proxied users. > All logging should be able to specify the authenticated proxy user as well as > the proxied user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25019) Update Ambari audit logger to handle proxied users
[ https://issues.apache.org/jira/browse/AMBARI-25019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25019: Labels: pull-request-available (was: ) > Update Ambari audit logger to handle proxied users > -- > > Key: AMBARI-25019 > URL: https://issues.apache.org/jira/browse/AMBARI-25019 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Update Ambari audit logger to handle proxied users. > All logging should be able to specify the authenticated proxy user as well as > the proxied user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25019) Update Ambari audit logger to handle proxied users
[ https://issues.apache.org/jira/browse/AMBARI-25019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-25019: Fix Version/s: 2.8.0 > Update Ambari audit logger to handle proxied users > -- > > Key: AMBARI-25019 > URL: https://issues.apache.org/jira/browse/AMBARI-25019 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Major > Fix For: 2.8.0 > > > Update Ambari audit logger to handle proxied users. > All logging should be able to specify the authenticated proxy user as well as > the proxied user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25019) Update Ambari audit logger to handle proxied users
[ https://issues.apache.org/jira/browse/AMBARI-25019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-25019: Component/s: ambari-server > Update Ambari audit logger to handle proxied users > -- > > Key: AMBARI-25019 > URL: https://issues.apache.org/jira/browse/AMBARI-25019 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Major > > Update Ambari audit logger to handle proxied users. > All logging should be able to specify the authenticated proxy user as well as > the proxied user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24896) [Log Search UI] Turn off features in the client when it is not available on backend
[ https://issues.apache.org/jira/browse/AMBARI-24896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24896: --- Resolution: Fixed Status: Resolved (was: Patch Available) > [Log Search UI] Turn off features in the client when it is not available on > backend > --- > > Key: AMBARI-24896 > URL: https://issues.apache.org/jira/browse/AMBARI-24896 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > > Turn off features when it is not available on backend. > The list of features and their available status is under `/info/features`. > Turn off `Configuration Editor` when `metadata_patterns` is `false`. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24896) [Log Search UI] Turn off features in the client when it is not available on backend
[ https://issues.apache.org/jira/browse/AMBARI-24896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712967#comment-16712967 ] Hudson commented on AMBARI-24896: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #75 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/75/]) [AMBARI-24896] [Log Search UI] Turn off features in the client when it (github: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=81228a70899c8ace045cb1921f644033668313a9]) * (edit) ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.html * (edit) ambari-logsearch-web/src/app/modules/shared/components/dropdown-list/dropdown-list.component.less * (edit) ambari-logsearch-web/src/app/components/action-menu/action-menu.component.spec.ts * (edit) ambari-logsearch-web/src/app/modules/shared/components/dropdown-list/dropdown-list.component.ts * (edit) ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts * (edit) ambari-logsearch-web/src/app/app.module.ts * (add) ambari-logsearch-web/src/app/services/api-feature.guard.ts * (edit) ambari-logsearch-web/src/app/components/menu-button/menu-button.component.html * (edit) ambari-logsearch-web/src/app/modules/shared/components/dropdown-list/dropdown-list.component.html * (edit) ambari-logsearch-web/src/app/modules/app-load/services/app-load.service.ts * (edit) ambari-logsearch-web/src/app/store/reducers/audit-log-repos.reducers.ts * (add) ambari-logsearch-web/src/app/services/meta-data-api-feature.guard.ts * (add) ambari-logsearch-web/src/app/store/reducers/api-features.reducers.ts * (add) ambari-logsearch-web/src/app/store/effects/api-features.effects.ts * (edit) ambari-logsearch-web/src/assets/i18n/en.json * (edit) ambari-logsearch-web/src/app/modules/shipper/shipper-routing.module.ts * (edit) ambari-logsearch-web/src/app/services/storage/reducers.service.ts * (add) ambari-logsearch-web/src/app/store/selectors/api-features.selectors.ts * (edit) ambari-logsearch-web/src/app/classes/models/store.ts * (edit) ambari-logsearch-web/src/app/components/menu-button/menu-button.component.ts * (edit) ambari-logsearch-web/src/app/components/top-menu/top-menu.component.ts * (edit) ambari-logsearch-web/src/app/components/top-menu/top-menu.component.spec.ts * (edit) ambari-logsearch-web/src/app/components/action-menu/action-menu.component.html * (edit) ambari-logsearch-web/src/app/components/filter-history-manager/filter-history-manager.component.html * (edit) ambari-logsearch-web/src/app/classes/list-item.ts * (edit) ambari-logsearch-web/src/app/services/http-client.service.ts * (add) ambari-logsearch-web/src/app/store/actions/api-features.actions.ts > [Log Search UI] Turn off features in the client when it is not available on > backend > --- > > Key: AMBARI-24896 > URL: https://issues.apache.org/jira/browse/AMBARI-24896 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > > Turn off features when it is not available on backend. > The list of features and their available status is under `/info/features`. > Turn off `Configuration Editor` when `metadata_patterns` is `false`. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24896) [Log Search UI] Turn off features in the client when it is not available on backend
[
https://issues.apache.org/jira/browse/AMBARI-24896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712960#comment-16712960
]
ASF GitHub Bot commented on AMBARI-24896:
-
tobias-istvan closed pull request #56: [AMBARI-24896] [Log Search UI] Turn off
features in the client when it is not available on backend
URL: https://github.com/apache/ambari-logsearch/pull/56
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/ambari-logsearch-web/src/app/app.module.ts
b/ambari-logsearch-web/src/app/app.module.ts
index c38924d494..78e3a02e41 100644
--- a/ambari-logsearch-web/src/app/app.module.ts
+++ b/ambari-logsearch-web/src/app/app.module.ts
@@ -116,12 +116,14 @@ import { LogsFilteringUtilsService } from
'@app/services/logs-filtering-utils.se
import { LogsStateService } from '@app/services/storage/logs-state.service';
import { LoginScreenGuardService } from
'@app/services/login-screen-guard.service';
import { UserSettingsService } from '@app/services/user-settings.service';
+import { MetaDataApiFeatureGuard } from
'@app/services/meta-data-api-feature.guard';
import { AuthEffects } from '@app/store/effects/auth.effects';
import { NotificationEffects } from '@app/store/effects/notification.effects';
import { UserSettingsEffects } from '@app/store/effects/user-settings.effects';
import { FilterHistoryManagerComponent } from
'./components/filter-history-manager/filter-history-manager.component';
import { AuditLogReposEffects } from './store/effects/audit-log-repos.effects';
+import { ApiFeaturesEffects } from './store/effects/api-features.effects';
import { HostNamePipe } from '@app/pipes/host-name.pipe';
@@ -205,7 +207,8 @@ import { HostNamePipe } from '@app/pipes/host-name.pipe';
EffectsModule.run(AuthEffects),
EffectsModule.run(AuditLogReposEffects),
EffectsModule.run(UserSettingsEffects),
-EffectsModule.run(NotificationEffects)
+EffectsModule.run(NotificationEffects),
+EffectsModule.run(ApiFeaturesEffects)
],
providers: [
@@ -239,7 +242,8 @@ import { HostNamePipe } from '@app/pipes/host-name.pipe';
LogsFilteringUtilsService,
LogsStateService,
LoginScreenGuardService,
-UserSettingsService
+UserSettingsService,
+MetaDataApiFeatureGuard
],
bootstrap: [AppComponent],
entryComponents: [
diff --git a/ambari-logsearch-web/src/app/classes/list-item.ts
b/ambari-logsearch-web/src/app/classes/list-item.ts
index 3a9b72c92d..5a1a6c0a3f 100644
--- a/ambari-logsearch-web/src/app/classes/list-item.ts
+++ b/ambari-logsearch-web/src/app/classes/list-item.ts
@@ -19,10 +19,12 @@
export interface ListItem {
id?: string | number;
label?: string;
+ secondaryLabel?: string;
value: any;
iconClass?: string;
cssClass?: string;
isChecked?: boolean;
onSelect?: Function;
isDivider?: boolean;
+ disabled?: boolean;
}
diff --git a/ambari-logsearch-web/src/app/classes/models/store.ts
b/ambari-logsearch-web/src/app/classes/models/store.ts
index b1d1bd9164..980944c92a 100644
--- a/ambari-logsearch-web/src/app/classes/models/store.ts
+++ b/ambari-logsearch-web/src/app/classes/models/store.ts
@@ -38,6 +38,7 @@ import * as auth from '@app/store/reducers/auth.reducers';
import * as filterHistory from '@app/store/reducers/filter-history.reducers';
import * as auditLogRepos from '@app/store/reducers/audit-log-repos.reducers';
import * as userSettings from '@app/store/reducers/user-settings.reducers';
+import * as apiFeatures from '@app/store/reducers/api-features.reducers';
const storeActions = {
'ARRAY.ADD': 'ADD',
@@ -77,6 +78,7 @@ export interface AppStore {
auth: auth.State;
filterHistory: filterHistory.FilterHistoryState;
auditLogRepos: auditLogRepos.AuditLogRepo[];
+ apiFeatures: apiFeatures.ApiFeatureSet;
}
export class ModelService {
diff --git
a/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.html
b/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.html
index f8c65de82c..cc8600c44d 100644
---
a/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.html
+++
b/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.html
@@ -16,13 +16,15 @@
-->
+ (buttonClick)="openLogIndexFilter()"
+ [disabled]="!(logLevelFiltersFeatureState$ | async)"
[class.disabled]="!(logLevelFiltersFeatureState$ | async)"
+ [tooltip]="(logLevelFiltersFeatureTooltip$ | async) |
translate">
+ (buttonClick)="startCapture()">
+ (buttonClick)="stopCapture()">
+ (buttonClick)="refresh()">
{
tabs,
dataAvailabilityStates,
auth: auth.reducer,
- userSettings
+ userSettings,
[jira] [Created] (AMBARI-25018) setup-ldap can not be executed non-interactively when using SSL without custom TrustStore
Sandor Molnar created AMBARI-25018:
--
Summary: setup-ldap can not be executed non-interactively when
using SSL without custom TrustStore
Key: AMBARI-25018
URL: https://issues.apache.org/jira/browse/AMBARI-25018
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.8.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.8.0
We should provide a way to our end user to execute {{ambari-server setup-ldap}}
in a non-interactive way (i.e. all answers are provided by command line
options).
This is not the case when we would like to setup a secure LDAP (SSL is set to
true) but we do not want to use a custom trust store. In this case the
following question(s) are being asked:
1. Do you want to provide custom TrustStore for Ambari?
2. Optionally: if custom trust store was set previously the tool displays the
earlier configuration and asks the following: Do you want to remove these
properties?
Sample run:
{code:java}
[root@c7401 ~]# ambari-server setup-ldap --ambari-admin-username=admin
--ambari-admin-password=admin --ldap-url=ad-nano.qe.hortonworks.com:636
--ldap-secondary-url=: --ldap-user-class=user --ldap-user-
attr=sAMAccountName --ldap-group-class=group --ldap-group-attr=cn
--ldap-member-attr=member --ldap-dn=distinguishedName
--ldap-base-dn=CN=Users,DC=hwqe,DC=hortonworks,DC=com --ldap-bind-anonym=false
--ldap-manager-dn=cn=manager,cn=Users,dc=hwqe,dc=hortonworks,dc=com
--ldap-manager-password=TestUser123 --ldap-referral=follow
--ldap-sync-username-collisions-behavior=skip
--ldap-force-lowercase-usernames=false --ldap-pagination-enabled=false
--ldap-ssl=true --ldap-sync-disable-endpoint-identification=true
--ldap-force-setup --ldap-save-settings --ldap-enabled-ambari=true
--ldap-manage-services=true --ldap-enabled-services=*
--ldap-user-group-member-attr=myMemberOf
Using python /usr/bin/python
Fetching LDAP configuration from DB.
Primary LDAP Host (ad-nano.qe.hortonworks.com):
Primary LDAP Port (636):
Secondary LDAP Host :
Secondary LDAP Port :
Use SSL [true/false] (true):
Disable endpoint identification during SSL handshake [true/false] (true):
Do you want to provide custom TrustStore for Ambari [y/n] (y)?n
The TrustStore is already configured:
ssl.trustStore.type = jks
ssl.trustStore.path = /tmp/ambari-server-truststore
ssl.trustStore.password = keystore
Do you want to remove these properties [y/n] (y)? y
User object class (user):
User ID attribute (sAMAccountName):
User group member attribute (myMemberOf):
Group object class (group):
Group name attribute (cn):
Group member attribute (member):
Distinguished name attribute (distinguishedName):
Search Base (CN=Users,DC=hwqe,DC=hortonworks,DC=com):
Referral method [follow/ignore] (follow):
Bind anonymously [true/false] (false):
Bind DN (cn=manager,cn=Users,dc=hwqe,dc=hortonworks,dc=com):
Enter Bind DN Password:
Confirm Bind DN Password:
Handling behavior for username collisions [convert/skip] for LDAP sync (skip):
Force lower-case user names [true/false] (false):
Results from LDAP are paginated when requested [true/false] (false):
Review Settings
Primary LDAP Host (ad-nano.qe.hortonworks.com): ad-nano.qe.hortonworks.com
Primary LDAP Port (636): 636
Use SSL [true/false] (true): true
User object class (user): user
User ID attribute (sAMAccountName): sAMAccountName
User group member attribute (myMemberOf): myMemberOf
Group object class (group): group
Group name attribute (cn): cn
Group member attribute (member): member
Distinguished name attribute (distinguishedName): distinguishedName
Search Base (CN=Users,DC=hwqe,DC=hortonworks,DC=com):
CN=Users,DC=hwqe,DC=hortonworks,DC=com
Referral method [follow/ignore] (follow): follow
Bind anonymously [true/false] (false): false
Handling behavior for username collisions [convert/skip] for LDAP sync (skip):
skip
Force lower-case user names [true/false] (false): false
Results from LDAP are paginated when requested [true/false] (false): false
ambari.ldap.connectivity.bind_dn:
cn=manager,cn=Users,dc=hwqe,dc=hortonworks,dc=com
ambari.ldap.connectivity.bind_password: *
ambari.ldap.advanced.disable_endpoint_identification: true
ambari.ldap.manage_services: true
ambari.ldap.enabled_services: *
Saving LDAP properties...
Saving LDAP properties finished
Ambari Server 'setup-ldap' completed successfully.{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-25016) [Log Search UI] There is console error about TimeZonePicker initialisation
[
https://issues.apache.org/jira/browse/AMBARI-25016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712853#comment-16712853
]
Hudson commented on AMBARI-25016:
-
SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #74 (See
[https://builds.apache.org/job/Ambari-LogSearch-master-Commit/74/])
[AMBARI-25016] [Log Search UI] There is console error about (github:
[https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=72c9b7778450b801d3a48e940016d2b1d56569c4])
* (edit)
ambari-logsearch-web/src/app/components/timezone-picker/timezone-picker.component.html
> [Log Search UI] There is console error about TimeZonePicker initialisation
> --
>
> Key: AMBARI-25016
> URL: https://issues.apache.org/jira/browse/AMBARI-25016
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
> Labels: pull-request-available
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> There is an error in console when the application is initialising:
> {code:java}
> ERROR TypeError: _co.initMap is not a function{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-25015) [Log Search UI] Cluster search param added by default when the app loaded on service logs screen
[ https://issues.apache.org/jira/browse/AMBARI-25015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712854#comment-16712854 ] Hudson commented on AMBARI-25015: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #74 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/74/]) [AMBARI-25015] [Log Search UI] Cluster search param added by default (github: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=1eba447f099f6ab68d8bf8ed1f558a9056c756ca]) * (edit) ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.ts * (edit) ambari-logsearch-web/src/app/components/search-box/search-box.component.spec.ts * (edit) ambari-logsearch-web/src/app/components/search-box/search-box.component.html > [Log Search UI] Cluster search param added by default when the app loaded on > service logs screen > > > Key: AMBARI-25015 > URL: https://issues.apache.org/jira/browse/AMBARI-25015 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25012) Log Search UI: cannot save filters + select all selecting the ovirrides as well
[
https://issues.apache.org/jira/browse/AMBARI-25012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712837#comment-16712837
]
ASF GitHub Bot commented on AMBARI-25012:
-
tobias-istvan closed pull request #57: [AMBARI-25012] Log Search UI: cannot
save filters + select all selecting the ovirrides as well
URL: https://github.com/apache/ambari-logsearch/pull/57
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.html
b/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.html
index f8c65de82c..acd6504140 100644
---
a/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.html
+++
b/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.html
@@ -31,7 +31,7 @@
title="{{'logIndexFilter.title' | translate}}">
+ label="{{'logIndexFilter.selectCluster' | translate}}"
buttonClass="btn-link" (selectItem)="onSelectCluster($event)">
{{'logIndexFilter.caption' | translate}}
@@ -41,7 +41,7 @@
{{'modal.cancel' | translate}}
-
+
{{'modal.save' | translate}}
diff --git
a/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts
b/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts
index cbc35f1dc4..f00eb2d930 100644
---
a/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts
+++
b/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts
@@ -46,8 +46,6 @@ export class ActionMenuComponent implements OnInit,
OnDestroy {
settingsForm: FormGroup = this.settings.settingsFormGroup;
- isModalSubmitDisabled = true;
-
clustersListItems$: Observable = this.clustersService.getAll()
.map((clusterNames: string[]): ListItem[] =>
clusterNames.map(this.utilsService.getListItemFromString))
.map((clusters: ListItem[]) => {
@@ -58,6 +56,7 @@ export class ActionMenuComponent implements OnInit,
OnDestroy {
});
selectedClusterName$: BehaviorSubject = new BehaviorSubject('');
+ isModalSubmitDisabled$: Observable =
this.selectedClusterName$.map(cluster => !cluster);
destroyed$ = new Subject();
@@ -72,10 +71,7 @@ export class ActionMenuComponent implements OnInit,
OnDestroy {
}
ngOnInit() {
-this.selectedClusterName$.takeUntil(this.destroyed$).subscribe(
- (clusterName: string) => this.setModalSubmitDisabled(!clusterName)
-);
-this.clustersListItems$.filter((items: ListItem[]) => items.some((item:
ListItem) => item.isChecked)).first()
+this.clustersListItems$.filter((items: ListItem[]) => items.some((item:
ListItem) => item.isChecked)).take(1)
.map((items: ListItem[]) => items.find((item: ListItem) =>
item.isChecked))
.subscribe((item) => this.selectedClusterName$.next(item.value));
}
@@ -88,10 +84,6 @@ export class ActionMenuComponent implements OnInit,
OnDestroy {
return this.logsContainerService.captureSeconds;
}
- setModalSubmitDisabled(isDisabled: boolean): void {
-this.isModalSubmitDisabled = isDisabled;
- }
-
refresh(): void {
this.logsContainerService.loadLogs();
}
diff --git
a/ambari-logsearch-web/src/app/components/log-index-filter/log-index-filter.component.ts
b/ambari-logsearch-web/src/app/components/log-index-filter/log-index-filter.component.ts
index 5ea0803bbd..02e16798c3 100644
---
a/ambari-logsearch-web/src/app/components/log-index-filter/log-index-filter.component.ts
+++
b/ambari-logsearch-web/src/app/components/log-index-filter/log-index-filter.component.ts
@@ -143,7 +143,7 @@ export class LogIndexFilterComponent implements OnInit,
OnDestroy, OnChanges, Co
processAllComponentsForLevel(levelName: LogLevel, isChecked: boolean): void {
this.activeClusterConfigs.forEach((component:
LogIndexFilterComponentConfig): void => {
component[levelName].defaults = isChecked;
- component[levelName].overrides = isChecked;
+ component[levelName].overrides = component.hasOverrides && isChecked;
});
this.updateValue();
}
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Log Search UI: cannot save filters + select all selecting the ovirrides as
> well
> ---
>
> Key: AMBARI-25012
> URL:
[jira] [Commented] (AMBARI-25012) Log Search UI: cannot save filters + select all selecting the ovirrides as well
[ https://issues.apache.org/jira/browse/AMBARI-25012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712844#comment-16712844 ] Hudson commented on AMBARI-25012: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #73 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/73/]) [AMBARI-25012] Log Search UI: cannot save filters + select all selecting (github: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=b21991615d744a983799af24631d64c4d0640e5c]) * (edit) ambari-logsearch-web/src/app/components/action-menu/action-menu.component.html * (edit) ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts * (edit) ambari-logsearch-web/src/app/components/log-index-filter/log-index-filter.component.ts > Log Search UI: cannot save filters + select all selecting the ovirrides as > well > --- > > Key: AMBARI-25012 > URL: https://issues.apache.org/jira/browse/AMBARI-25012 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Blocker > Labels: pull-request-available > Original Estimate: 2h > Remaining Estimate: 2h > > Clicking out a log level from debug to nothing, save button was still > disabled. > Also clicking select all selected the overrides rows as well (as no hostname > set there or anything, not sure what is expected there, hopefully we would > not save that with filled empty hostname but with one debug log level) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25015) [Log Search UI] Cluster search param added by default when the app loaded on service logs screen
[
https://issues.apache.org/jira/browse/AMBARI-25015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712841#comment-16712841
]
ASF GitHub Bot commented on AMBARI-25015:
-
tobias-istvan closed pull request #59: [AMBARI-25015] [Log Search UI] Cluster
search param added by default when the app loaded on service logs screen
URL: https://github.com/apache/ambari-logsearch/pull/59
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.ts
b/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.ts
index 7fa2b0f596..cc5be260d6 100644
---
a/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.ts
+++
b/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.ts
@@ -119,23 +119,29 @@ export class FiltersPanelComponent implements OnDestroy,
OnInit {
const logsType = this.logsContainerService.logsTypeMap[currentLogsType];
const fieldsModel: any = logsType && logsType.fieldsModel;
let subType: string;
-let fields: Observable;
+let fields$: Observable;
switch (currentLogsType) {
case 'auditLogs':
-fields = fieldsModel.getParameter(subType ? 'overrides' : 'defaults');
+fields$ = fieldsModel.getParameter(subType ? 'overrides' : 'defaults');
if (subType) {
- fields = fields.map(items => items && items[subType]);
+ fields$ = fields$.map(items => items && items[subType]);
}
break;
case 'serviceLogs':
-fields = fieldsModel.getAll();
+fields$ = fieldsModel.getAll();
break;
default:
-fields = Observable.from([]);
+fields$ = Observable.from([]);
break;
}
-this.searchBoxItems$ = fields.defaultIfEmpty([]).map(items => items ?
items.filter(field => field.filterable) : [])
- .map(this.utils.logFieldToListItemMapper);
+this.searchBoxItems$ = fields$.defaultIfEmpty([]).map(items => items ?
items.filter(field => field.filterable) : [])
+ .map(this.utils.logFieldToListItemMapper)
+ .map((fields: ListItem[]): ListItem[] => fields.map(
+(field: ListItem): ListItem => ({
+ ...field,
+ isChecked: false
+})
+ ));
}
isFilterConditionDisplayed(key: string): boolean {
diff --git
a/ambari-logsearch-web/src/app/components/search-box/search-box.component.html
b/ambari-logsearch-web/src/app/components/search-box/search-box.component.html
index 5fd87abea1..25b0b10f4c 100644
---
a/ambari-logsearch-web/src/app/components/search-box/search-box.component.html
+++
b/ambari-logsearch-web/src/app/components/search-box/search-box.component.html
@@ -21,7 +21,11 @@
{{parameter.label | translate}}:
- {{(parameter.name === 'type' ?
(parameter.value | componentLabel | async) : parameter.value)}}
+
+ {{parameter.value |
componentLabel | async}}
+ {{parameter.value |
hostName | async}}
+ {{parameter.value}}
+
diff --git
a/ambari-logsearch-web/src/app/components/search-box/search-box.component.spec.ts
b/ambari-logsearch-web/src/app/components/search-box/search-box.component.spec.ts
index 32348a3c7f..971fe275c0 100644
---
a/ambari-logsearch-web/src/app/components/search-box/search-box.component.spec.ts
+++
b/ambari-logsearch-web/src/app/components/search-box/search-box.component.spec.ts
@@ -26,6 +26,7 @@ import {UtilsService} from '@app/services/utils.service';
import {SearchBoxComponent} from './search-box.component';
import {ComponentsService, components} from
'@app/services/storage/components.service';
import {ComponentLabelPipe} from '@app/pipes/component-label';
+import {HostNamePipe} from "@app/pipes/host-name.pipe";
describe('SearchBoxComponent', () => {
let component: SearchBoxComponent;
@@ -35,6 +36,7 @@ describe('SearchBoxComponent', () => {
TestBed.configureTestingModule({
declarations: [
ComponentLabelPipe,
+HostNamePipe,
SearchBoxComponent
],
imports: [
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Log Search UI] Cluster search param added by default when the app loaded on
> service logs screen
>
>
> Key: AMBARI-25015
> URL:
[jira] [Updated] (AMBARI-25015) [Log Search UI] Cluster search param added by default when the app loaded on service logs screen
[ https://issues.apache.org/jira/browse/AMBARI-25015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-25015: --- Resolution: Fixed Status: Resolved (was: Patch Available) > [Log Search UI] Cluster search param added by default when the app loaded on > service logs screen > > > Key: AMBARI-25015 > URL: https://issues.apache.org/jira/browse/AMBARI-25015 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25016) [Log Search UI] There is console error about TimeZonePicker initialisation
[
https://issues.apache.org/jira/browse/AMBARI-25016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Tobias updated AMBARI-25016:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> [Log Search UI] There is console error about TimeZonePicker initialisation
> --
>
> Key: AMBARI-25016
> URL: https://issues.apache.org/jira/browse/AMBARI-25016
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
> Labels: pull-request-available
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> There is an error in console when the application is initialising:
> {code:java}
> ERROR TypeError: _co.initMap is not a function{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-25016) [Log Search UI] There is console error about TimeZonePicker initialisation
[
https://issues.apache.org/jira/browse/AMBARI-25016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712839#comment-16712839
]
ASF GitHub Bot commented on AMBARI-25016:
-
tobias-istvan closed pull request #58: [AMBARI-25016] [Log Search UI] There is
console error about TimeZonePicker initialisation
URL: https://github.com/apache/ambari-logsearch/pull/58
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ambari-logsearch-web/src/app/components/timezone-picker/timezone-picker.component.html
b/ambari-logsearch-web/src/app/components/timezone-picker/timezone-picker.component.html
index 0d4c759aba..39d7df979d 100644
---
a/ambari-logsearch-web/src/app/components/timezone-picker/timezone-picker.component.html
+++
b/ambari-logsearch-web/src/app/components/timezone-picker/timezone-picker.component.html
@@ -18,7 +18,6 @@
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Log Search UI] There is console error about TimeZonePicker initialisation
> --
>
> Key: AMBARI-25016
> URL: https://issues.apache.org/jira/browse/AMBARI-25016
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
> Labels: pull-request-available
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> There is an error in console when the application is initialising:
> {code:java}
> ERROR TypeError: _co.initMap is not a function{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-25012) Log Search UI: cannot save filters + select all selecting the ovirrides as well
[ https://issues.apache.org/jira/browse/AMBARI-25012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-25012: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Log Search UI: cannot save filters + select all selecting the ovirrides as > well > --- > > Key: AMBARI-25012 > URL: https://issues.apache.org/jira/browse/AMBARI-25012 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Blocker > Labels: pull-request-available > Original Estimate: 2h > Remaining Estimate: 2h > > Clicking out a log level from debug to nothing, save button was still > disabled. > Also clicking select all selected the overrides rows as well (as no hostname > set there or anything, not sure what is expected there, hopefully we would > not save that with filled empty hostname but with one debug log level) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25017) [Log Search UI] Replace Log Search favicon with Ambari's favicon
[ https://issues.apache.org/jira/browse/AMBARI-25017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712708#comment-16712708 ] ASF GitHub Bot commented on AMBARI-25017: - asfgit commented on issue #60: [AMBARI-25017] [Log Search UI] Replace Log Search favicon with Ambari's favicon URL: https://github.com/apache/ambari-logsearch/pull/60#issuecomment-445205871 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/118/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [Log Search UI] Replace Log Search favicon with Ambari's favicon > > > Key: AMBARI-25017 > URL: https://issues.apache.org/jira/browse/AMBARI-25017 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 0.5h > Remaining Estimate: 0.5h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25017) [Log Search UI] Replace Log Search favicon with Ambari's favicon
[ https://issues.apache.org/jira/browse/AMBARI-25017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-25017: --- Status: Patch Available (was: Open) > [Log Search UI] Replace Log Search favicon with Ambari's favicon > > > Key: AMBARI-25017 > URL: https://issues.apache.org/jira/browse/AMBARI-25017 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 0.5h > Remaining Estimate: 0.5h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25017) [Log Search UI] Replace Log Search favicon with Ambari's favicon
[ https://issues.apache.org/jira/browse/AMBARI-25017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25017: Labels: pull-request-available (was: ) > [Log Search UI] Replace Log Search favicon with Ambari's favicon > > > Key: AMBARI-25017 > URL: https://issues.apache.org/jira/browse/AMBARI-25017 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 0.5h > Remaining Estimate: 0.5h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25017) [Log Search UI] Replace Log Search favicon with Ambari's favicon
[ https://issues.apache.org/jira/browse/AMBARI-25017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712700#comment-16712700 ] ASF GitHub Bot commented on AMBARI-25017: - tobias-istvan opened a new pull request #60: [AMBARI-25017] [Log Search UI] Replace Log Search favicon with Ambari's favicon URL: https://github.com/apache/ambari-logsearch/pull/60 # What changes were proposed in this pull request? Simple `index.html` change. ## How was this patch tested? It was tested manually. Please review [Ambari Contributing Guide](https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute) before opening a pull request. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [Log Search UI] Replace Log Search favicon with Ambari's favicon > > > Key: AMBARI-25017 > URL: https://issues.apache.org/jira/browse/AMBARI-25017 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 0.5h > Remaining Estimate: 0.5h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25017) [Log Search UI] Replace Log Search favicon with Ambari's favicon
Istvan Tobias created AMBARI-25017: -- Summary: [Log Search UI] Replace Log Search favicon with Ambari's favicon Key: AMBARI-25017 URL: https://issues.apache.org/jira/browse/AMBARI-25017 Project: Ambari Issue Type: Improvement Components: ambari-logsearch, logsearch Affects Versions: 2.7.3 Reporter: Istvan Tobias Assignee: Istvan Tobias -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25016) [Log Search UI] There is console error about TimeZonePicker initialisation
[
https://issues.apache.org/jira/browse/AMBARI-25016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Tobias updated AMBARI-25016:
---
Status: Patch Available (was: Open)
> [Log Search UI] There is console error about TimeZonePicker initialisation
> --
>
> Key: AMBARI-25016
> URL: https://issues.apache.org/jira/browse/AMBARI-25016
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
> Labels: pull-request-available
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> There is an error in console when the application is initialising:
> {code:java}
> ERROR TypeError: _co.initMap is not a function{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-25015) [Log Search UI] Cluster search param added by default when the app loaded on service logs screen
[ https://issues.apache.org/jira/browse/AMBARI-25015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712686#comment-16712686 ] ASF GitHub Bot commented on AMBARI-25015: - asfgit commented on issue #59: [AMBARI-25015] [Log Search UI] Cluster search param added by default when the app loaded on service logs screen URL: https://github.com/apache/ambari-logsearch/pull/59#issuecomment-445202169 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/117/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [Log Search UI] Cluster search param added by default when the app loaded on > service logs screen > > > Key: AMBARI-25015 > URL: https://issues.apache.org/jira/browse/AMBARI-25015 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25015) [Log Search UI] Cluster search param added by default when the app loaded on service logs screen
[ https://issues.apache.org/jira/browse/AMBARI-25015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-25015: --- Status: Patch Available (was: In Progress) > [Log Search UI] Cluster search param added by default when the app loaded on > service logs screen > > > Key: AMBARI-25015 > URL: https://issues.apache.org/jira/browse/AMBARI-25015 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25015) [Log Search UI] Cluster search param added by default when the app loaded on service logs screen
[ https://issues.apache.org/jira/browse/AMBARI-25015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712679#comment-16712679 ] ASF GitHub Bot commented on AMBARI-25015: - tobias-istvan opened a new pull request #59: [AMBARI-25015] [Log Search UI] Cluster search param added by default when the app loaded on service logs screen URL: https://github.com/apache/ambari-logsearch/pull/59 # What changes were proposed in this pull request? Set `isChecked` prop to `false` when we create the list for the available filter fields in order to prevent the auto selection. ## How was this patch tested? It was tested manually, loading the screens (audit and service logs screens) and via unit tests: ``` Chrome 70.0.3538 (Mac OS X 10.13.6): Executed 295 of 295 SUCCESS (8.843 secs / 8.668 secs) ``` Please review [Ambari Contributing Guide](https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute) before opening a pull request. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [Log Search UI] Cluster search param added by default when the app loaded on > service logs screen > > > Key: AMBARI-25015 > URL: https://issues.apache.org/jira/browse/AMBARI-25015 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25015) [Log Search UI] Cluster search param added by default when the app loaded on service logs screen
[ https://issues.apache.org/jira/browse/AMBARI-25015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25015: Labels: pull-request-available (was: ) > [Log Search UI] Cluster search param added by default when the app loaded on > service logs screen > > > Key: AMBARI-25015 > URL: https://issues.apache.org/jira/browse/AMBARI-25015 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25016) [Log Search UI] There is console error about TimeZonePicker initialisation
[
https://issues.apache.org/jira/browse/AMBARI-25016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712646#comment-16712646
]
ASF GitHub Bot commented on AMBARI-25016:
-
tobias-istvan opened a new pull request #58: [AMBARI-25016] [Log Search UI]
There is console error about TimeZonePicker initialisation
URL: https://github.com/apache/ambari-logsearch/pull/58
# What changes were proposed in this pull request?
Removing the old `afterViewInit` handler, because the map is initialised
within the new component.
## How was this patch tested?
It was tested manually by opening console and checking time zone modal
functionality, also by unit tests:
```
Chrome 70.0.3538 (Mac OS X 10.13.6): Executed 295 of 295 SUCCESS (8.474 secs
/ 8.197 secs)
```
Please review [Ambari Contributing
Guide](https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute)
before opening a pull request.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Log Search UI] There is console error about TimeZonePicker initialisation
> --
>
> Key: AMBARI-25016
> URL: https://issues.apache.org/jira/browse/AMBARI-25016
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
> Labels: pull-request-available
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> There is an error in console when the application is initialising:
> {code:java}
> ERROR TypeError: _co.initMap is not a function{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-25016) [Log Search UI] There is console error about TimeZonePicker initialisation
[
https://issues.apache.org/jira/browse/AMBARI-25016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712652#comment-16712652
]
ASF GitHub Bot commented on AMBARI-25016:
-
asfgit commented on issue #58: [AMBARI-25016] [Log Search UI] There is console
error about TimeZonePicker initialisation
URL: https://github.com/apache/ambari-logsearch/pull/58#issuecomment-445196204
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/116/
Test PASSed.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Log Search UI] There is console error about TimeZonePicker initialisation
> --
>
> Key: AMBARI-25016
> URL: https://issues.apache.org/jira/browse/AMBARI-25016
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
> Labels: pull-request-available
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> There is an error in console when the application is initialising:
> {code:java}
> ERROR TypeError: _co.initMap is not a function{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-25016) [Log Search UI] There is console error about TimeZonePicker initialisation
Istvan Tobias created AMBARI-25016:
--
Summary: [Log Search UI] There is console error about
TimeZonePicker initialisation
Key: AMBARI-25016
URL: https://issues.apache.org/jira/browse/AMBARI-25016
Project: Ambari
Issue Type: Improvement
Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias
There is an error in console when the application is initialising:
{code:java}
ERROR TypeError: _co.initMap is not a function{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-25015) [Log Search UI] Cluster search param added by default when the app loaded on service logs screen
Istvan Tobias created AMBARI-25015: -- Summary: [Log Search UI] Cluster search param added by default when the app loaded on service logs screen Key: AMBARI-25015 URL: https://issues.apache.org/jira/browse/AMBARI-25015 Project: Ambari Issue Type: Improvement Affects Versions: 2.7.3 Reporter: Istvan Tobias Assignee: Istvan Tobias -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25008) Set unique configuration version tag
[
https://issues.apache.org/jira/browse/AMBARI-25008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila resolved AMBARI-25008.
Resolution: Fixed
> Set unique configuration version tag
>
>
> Key: AMBARI-25008
> URL: https://issues.apache.org/jira/browse/AMBARI-25008
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.8.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Add Service does not work for add-delete-add scenario, because configuration
> tag is constant {{ADD_SERVICE}}. It should include some changing part, eg.
> timestamp suffix.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-25005) Ambari hides information about cred_store generation failures. Resulting in confusing errors at later stages
[ https://issues.apache.org/jira/browse/AMBARI-25005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-25005: - Attachment: AMBARI-25005.patch > Ambari hides information about cred_store generation failures. Resulting in > confusing errors at later stages > > > Key: AMBARI-25005 > URL: https://issues.apache.org/jira/browse/AMBARI-25005 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-25005.patch, AMBARI-25005.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Component was failing to install due to: > > > Caught an exception while executing custom service command: 'exceptions.OSError'>: [Errno 2] No such file or directory: > '/var/lib/ambari-agent/cred/conf/dp_profiler_agent/dpprofiler-config.jceks'; > [Errno 2] No such file or directory: > '/var/lib/ambari-agent/cred/conf/dp_profiler_agent/dpprofiler-config.jceks' > > Command failed after 1 tries > > The reason was an empty password provided in blueprint. However it took lots > of time to debug this. Since ambari won't show any information regarding > failures during cred_store generation. > The goal is too fail earlier and show output of failed generation command. > So with the patch it looks like this: > > > Caught an exception while executing custom service command: 'resource_management.core.exceptions.ExecutionFailed'>: Execution of > '/usr/lib/jvm/java-openjdk/bin/java -cp '/var/lib/ambari-agent/cred/lib/*' > org.apache.hadoop.security.alias.CredentialShell create > dpprofiler.spnego.signature.secret -value '[PROTECTED]' -provider > jceks://file/var/lib/ambari-agent/cred/conf/dp_profiler_agent/dpprofiler-config.jceks' > returned 1. SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further > details. > Dec 06, 2018 11:05:45 AM org.apache.hadoop.util.NativeCodeLoader > WARNING: Unable to load native-hadoop library for your platform... using > builtin-java classes where applicable > java.lang.IllegalArgumentException: Empty key > at javax.crypto.spec.SecretKeySpec.(SecretKeySpec.java:96) > at > org.apache.hadoop.security.alias.AbstractJavaKeyStoreProvider.innerSetCredential(AbstractJavaKeyStoreProvider.java:304) > at > org.apache.hadoop.security.alias.AbstractJavaKeyStoreProvider.createCredentialEntry(AbstractJavaKeyStoreProvider.java:269) > at > org.apache.hadoop.security.alias.CredentialShell$CreateCommand.execute(CredentialShell.java:365) > at > org.apache.hadoop.security.alias.CredentialShell.run(CredentialShell.java:68) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at > org.apache.hadoop.security.alias.CredentialShell.main(CredentialShell.java:442); > Execution of '/usr/lib/jvm/java-openjdk/bin/java -cp > '/var/lib/ambari-agent/cred/lib/*' > org.apache.hadoop.security.alias.CredentialShell create > dpprofiler.spnego.signature.secret -value '[PROTECTED]' -provider > jceks://file/var/lib/ambari-agent/cred/conf/dp_profiler_agent/dpprofiler-config.jceks' > returned 1. SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further > details. > Dec 06, 2018 11:05:45 AM org.apache.hadoop.util.NativeCodeLoader > WARNING: Unable to load native-hadoop library for your platform... using > builtin-java classes where applicable > java.lang.IllegalArgumentException: Empty key > at javax.crypto.spec.SecretKeySpec.(SecretKeySpec.java:96) > at > org.apache.hadoop.security.alias.AbstractJavaKeyStoreProvider.innerSetCredential(AbstractJavaKeyStoreProvider.java:304) > at > org.apache.hadoop.security.alias.AbstractJavaKeyStoreProvider.createCredentialEntry(AbstractJavaKeyStoreProvider.java:269) > at > org.apache.hadoop.security.alias.CredentialShell$CreateCommand.execute(CredentialShell.java:365) > at > org.apache.hadoop.security.alias.CredentialShell.run(CredentialShell.java:68) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at > org.apache.hadoop.security.alias.CredentialShell.main(CredentialShell.java:442) > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-25013) Ambari should optionally generate auth-to-local rules for the Kerberos identities of all components of installed services
[
https://issues.apache.org/jira/browse/AMBARI-25013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar reassigned AMBARI-25013:
--
Assignee: Sandor Molnar (was: Robert Levas)
> Ambari should optionally generate auth-to-local rules for the Kerberos
> identities of all components of installed services
> -
>
> Key: AMBARI-25013
> URL: https://issues.apache.org/jira/browse/AMBARI-25013
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.8.0
>Reporter: Rohith Sharma K S
>Assignee: Sandor Molnar
>Priority: Major
> Labels: kerberos
> Fix For: 2.8.0
>
>
> Ambari should optionally generate auth-to-local rules for the Kerberos
> identities of all components of installed services.
> Currently Ambari will generate auth-to-local rules for the installed
> components of installed services. This is generally the accepted behavior.
> However, there may be cases where identities from remote clusters (using the
> same Kerberos realm) need to be translated to local names.
> A use case may be that some slave component for a service is installed on a
> remote cluster, but that component is not installed on the local cluster.
> However a master component of that service is installed on the local cluster
> and the slave component from the remote cluster needs to communicate with it.
> The solution is to add a new property to {{kerberos-env}}, maybe named
> something like {{include_all_components_in_auth_to_local_rules}}, where the
> default value is {{false}}. If set to {{true}}, when building the
> auth-to-local rules, Ambari should add the rules for all components of
> installed services, not just the installed components (which is what it does
> today).
> The relevant code to change is in
> {{org.apache.ambari.server.controller.KerberosHelperImpl#setAuthToLocalRules}}.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
