[jira] [Commented] (AMBARI-24610) [Log Search UI] Show user friendly component name in query input
[ https://issues.apache.org/jira/browse/AMBARI-24610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609888#comment-16609888 ] Hudson commented on AMBARI-24610: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9934 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9934/]) [AMBARI-24610] [Log Search UI] Show user friendly component name in (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=c17762bdd91fddc0cca87d3aa24e4121c7b5e675]) * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/search-box/search-box.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/search-box/search-box.component.html > [Log Search UI] Show user friendly component name in query input > > > Key: AMBARI-24610 > URL: https://issues.apache.org/jira/browse/AMBARI-24610 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Original Estimate: 3h > Time Spent: 1h 10m > Remaining Estimate: 1h 50m > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24610) [Log Search UI] Show user friendly component name in query input
[ https://issues.apache.org/jira/browse/AMBARI-24610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609886#comment-16609886 ] Hudson commented on AMBARI-24610: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #236 (See [https://builds.apache.org/job/Ambari-branch-2.7/236/]) [AMBARI-24610] [Log Search UI] Show user friendly component name in (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=48c616ae1d9de05124167a2f413ec8e8e520f6bc]) * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/search-box/search-box.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/search-box/search-box.component.html > [Log Search UI] Show user friendly component name in query input > > > Key: AMBARI-24610 > URL: https://issues.apache.org/jira/browse/AMBARI-24610 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Original Estimate: 3h > Time Spent: 1h 10m > Remaining Estimate: 1h 50m > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24617) Ambari 2.7 for HDP 3.0 has missing parameter while adding Hive service with LDAP Authentication
[ https://issues.apache.org/jira/browse/AMBARI-24617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko resolved AMBARI-24617. - Resolution: Incomplete > Ambari 2.7 for HDP 3.0 has missing parameter while adding Hive service with > LDAP Authentication > --- > > Key: AMBARI-24617 > URL: https://issues.apache.org/jira/browse/AMBARI-24617 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Major > Fix For: 2.7.2 > > > Hi, > When we want to add Hive service with LDAP authentication from Ambari, it is > asking for a parameter value but that parameter namely > hive.server2.authentication.ldap.url is missing in Ambari UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24617) Ambari 2.7 for HDP 3.0 has missing parameter while adding Hive service with LDAP Authentication
[ https://issues.apache.org/jira/browse/AMBARI-24617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-24617: Fix Version/s: 2.7.2 > Ambari 2.7 for HDP 3.0 has missing parameter while adding Hive service with > LDAP Authentication > --- > > Key: AMBARI-24617 > URL: https://issues.apache.org/jira/browse/AMBARI-24617 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Major > Fix For: 2.7.2 > > > Hi, > When we want to add Hive service with LDAP authentication from Ambari, it is > asking for a parameter value but that parameter namely > hive.server2.authentication.ldap.url is missing in Ambari UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24617) Ambari 2.7 for HDP 3.0 has missing parameter while adding Hive service with LDAP Authentication
[ https://issues.apache.org/jira/browse/AMBARI-24617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-24617: Affects Version/s: 2.7.0 > Ambari 2.7 for HDP 3.0 has missing parameter while adding Hive service with > LDAP Authentication > --- > > Key: AMBARI-24617 > URL: https://issues.apache.org/jira/browse/AMBARI-24617 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Major > Fix For: 2.7.2 > > > Hi, > When we want to add Hive service with LDAP authentication from Ambari, it is > asking for a parameter value but that parameter namely > hive.server2.authentication.ldap.url is missing in Ambari UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24617) Ambari 2.7 for HDP 3.0 has missing parameter while adding Hive service with LDAP Authentication
Dmitry Lysnichenko created AMBARI-24617: --- Summary: Ambari 2.7 for HDP 3.0 has missing parameter while adding Hive service with LDAP Authentication Key: AMBARI-24617 URL: https://issues.apache.org/jira/browse/AMBARI-24617 Project: Ambari Issue Type: Bug Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Hi, When we want to add Hive service with LDAP authentication from Ambari, it is asking for a parameter value but that parameter namely hive.server2.authentication.ldap.url is missing in Ambari UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24617) Ambari 2.7 for HDP 3.0 has missing parameter while adding Hive service with LDAP Authentication
[ https://issues.apache.org/jira/browse/AMBARI-24617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-24617: Component/s: ambari-server > Ambari 2.7 for HDP 3.0 has missing parameter while adding Hive service with > LDAP Authentication > --- > > Key: AMBARI-24617 > URL: https://issues.apache.org/jira/browse/AMBARI-24617 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Major > > Hi, > When we want to add Hive service with LDAP authentication from Ambari, it is > asking for a parameter value but that parameter namely > hive.server2.authentication.ldap.url is missing in Ambari UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24616) Disable Kerberos from Ambari UI didn't clean up keytab directories
Robert Levas created AMBARI-24616:
-
Summary: Disable Kerberos from Ambari UI didn't clean up keytab
directories
Key: AMBARI-24616
URL: https://issues.apache.org/jira/browse/AMBARI-24616
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.1
Reporter: Kishor Ramakrishnan
Assignee: Robert Levas
Fix For: 2.7.2
Disable Kerberos from Ambari UI didn't clean up keytab directories,
stderr:
{code:java}
2018-09-08 05:27:19,276 - Failed to remove identity for
amsmon/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:19,298 - Failed to remove identity for
amsmon/ctr-e138-1518143905142-467151-01-06.hwx.s...@example.com from the
Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:19,325 - Failed to remove identity for
amsmon/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:19,348 - Failed to remove identity for
amsmon/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:19,465 - Failed to remove identity for
dn/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the Ambari
database - Object: null is not a known Entity type.
2018-09-08 05:27:19,491 - Failed to remove identity for
dn/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the Ambari
database - Object: null is not a known Entity type.
2018-09-08 05:27:19,515 - Failed to remove identity for
dn/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the Ambari
database - Object: null is not a known Entity type.
2018-09-08 05:27:19,539 - Failed to remove identity for
dn/ctr-e138-1518143905142-467151-01-04.hwx.s...@example.com from the Ambari
database - Object: null is not a known Entity type.
2018-09-08 05:27:19,671 - Failed to remove identity for
hbase/ctr-e138-1518143905142-467151-01-06.hwx.s...@example.com from the
Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:19,696 - Failed to remove identity for
hbase/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:19,723 - Failed to remove identity for
hbase/ctr-e138-1518143905142-467151-01-04.hwx.s...@example.com from the
Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:19,744 - Failed to remove identity for
hbase/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:19,959 - Failed to remove identity for
nm/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the Ambari
database - Object: null is not a known Entity type.
2018-09-08 05:27:19,987 - Failed to remove identity for
nm/ctr-e138-1518143905142-467151-01-06.hwx.s...@example.com from the Ambari
database - Object: null is not a known Entity type.
2018-09-08 05:27:20,049 - Failed to remove identity for
nn/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the Ambari
database - Object: null is not a known Entity type.
2018-09-08 05:27:20,376 - Failed to remove identity for
HTTP/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:20,399 - Failed to remove identity for
HTTP/ctr-e138-1518143905142-467151-01-04.hwx.s...@example.com from the
Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:20,420 - Failed to remove identity for
HTTP/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:20,441 - Failed to remove identity for
HTTP/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:20,590 - Failed to remove identity for
yarn-ats-hbase/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com
from the Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:20,617 - Failed to remove identity for
yarn-ats-hbase/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com
from the Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:20,647 - Failed to remove identity for
yarn-ats-hbase/ctr-e138-1518143905142-467151-01-04.hwx.s...@example.com
from the Ambari database - Object: null is not a known Entity type.
2018-09-08 05:27:20,677 - Failed to remove identity for
yarn-ats-hbase/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com
from the Ambari database
[jira] [Commented] (AMBARI-24614) deploy-gce-perf-cluster.py script does not work
[ https://issues.apache.org/jira/browse/AMBARI-24614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609431#comment-16609431 ] Hudson commented on AMBARI-24614: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9933 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9933/]) AMBARI-24614. deploy-gce-perf-cluster.py script does not work (aonishuk) (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7cc5c9d3c49740fabdece358429dd5b7fad4f007]) * (edit) contrib/utils/perf/deploy-gce-perf-cluster.py > deploy-gce-perf-cluster.py script does not work > --- > > Key: AMBARI-24614 > URL: https://issues.apache.org/jira/browse/AMBARI-24614 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24614.patch, AMBARI-24614.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24609) Ability to install common ambari python libraries to maven repository (local / remote)
[
https://issues.apache.org/jira/browse/AMBARI-24609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609432#comment-16609432
]
Hudson commented on AMBARI-24609:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9933 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9933/])
AMBARI-24609. Ability to install common ambari python libraries to maven
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=68d0b6430c5c2fbb72e7e4b52f1b60bccb07e773])
* (add) install-ambari-python.sh
* (edit) setup.py
> Ability to install common ambari python libraries to maven repository (local
> / remote)
> --
>
> Key: AMBARI-24609
> URL: https://issues.apache.org/jira/browse/AMBARI-24609
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> New cli script to create a maven tar.gz artifact:
> - `--clean` option to just delete dist directories
> - by default it uses `mvn install` on the generated tar.gz, that install the
> artifact into local maven repository
> - `--deploy` option to use `mvn deploy` for uploading generated tar.gz
> artifact to remote maven repository
> - `--version` option to provide the artifact and generated python dist
> version
> - update setup.py script to read the version from pom.xml during dist
> building, otherwise it uses PKG-INFO to get the right version, therefore if
> you are overriding the version during the build, it will always use the right
> version with pip or setup.py
> How it works:
> with setup.py an installable distribution created, with pip the packages are
> installed locally, then the install-ambari-python script creates a tar.gz
> from the installd packages and upload it to a maven repo (tar.gz content is
> the site-packages, the python version before that is not included)
> after the artifacts are installed to maven repos, these could be provided in
> external projects (to use to extend PYTHONPATH variable, in order to run
> tests against any stack code, like in MPacks);
> Maven example:
> {code:xml}
>
> org.apache.ambari
> ambari-python
> 2.0.0.0-SNAPSHOT
> test
>
> {code}
> Gradle example:
> {code:groovy}
> testCompile "org.apache.ambari:ambari-python:2.0.0.0-snaps...@tar.gz"
> {code}
> So in an external project, the ambari python files can be extracted during
> build time, and add them to the PYTHONPATH
> Usage examples:
> Install to maven local repo
> {code:bash}
> ./install-ambari-python.sh
> {code}
> Deploy to maven remote repo
> {code:bash}
> ./install-ambari-python.sh --deploy -i -r
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24609) Ability to install common ambari python libraries to maven repository (local / remote)
[
https://issues.apache.org/jira/browse/AMBARI-24609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-24609.
---
Resolution: Fixed
> Ability to install common ambari python libraries to maven repository (local
> / remote)
> --
>
> Key: AMBARI-24609
> URL: https://issues.apache.org/jira/browse/AMBARI-24609
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> New cli script to create a maven tar.gz artifact:
> - `--clean` option to just delete dist directories
> - by default it uses `mvn install` on the generated tar.gz, that install the
> artifact into local maven repository
> - `--deploy` option to use `mvn deploy` for uploading generated tar.gz
> artifact to remote maven repository
> - `--version` option to provide the artifact and generated python dist
> version
> - update setup.py script to read the version from pom.xml during dist
> building, otherwise it uses PKG-INFO to get the right version, therefore if
> you are overriding the version during the build, it will always use the right
> version with pip or setup.py
> How it works:
> with setup.py an installable distribution created, with pip the packages are
> installed locally, then the install-ambari-python script creates a tar.gz
> from the installd packages and upload it to a maven repo (tar.gz content is
> the site-packages, the python version before that is not included)
> after the artifacts are installed to maven repos, these could be provided in
> external projects (to use to extend PYTHONPATH variable, in order to run
> tests against any stack code, like in MPacks);
> Maven example:
> {code:xml}
>
> org.apache.ambari
> ambari-python
> 2.0.0.0-SNAPSHOT
> test
>
> {code}
> Gradle example:
> {code:groovy}
> testCompile "org.apache.ambari:ambari-python:2.0.0.0-snaps...@tar.gz"
> {code}
> So in an external project, the ambari python files can be extracted during
> build time, and add them to the PYTHONPATH
> Usage examples:
> Install to maven local repo
> {code:bash}
> ./install-ambari-python.sh
> {code}
> Deploy to maven remote repo
> {code:bash}
> ./install-ambari-python.sh --deploy -i -r
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24614) deploy-gce-perf-cluster.py script does not work
[ https://issues.apache.org/jira/browse/AMBARI-24614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609384#comment-16609384 ] Hudson commented on AMBARI-24614: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #235 (See [https://builds.apache.org/job/Ambari-branch-2.7/235/]) AMBARI-24614. deploy-gce-perf-cluster.py script does not work (aonishuk) (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=a75ae27740a42b7ec08215024a35def87bccedb0]) * (edit) contrib/utils/perf/deploy-gce-perf-cluster.py > deploy-gce-perf-cluster.py script does not work > --- > > Key: AMBARI-24614 > URL: https://issues.apache.org/jira/browse/AMBARI-24614 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24614.patch, AMBARI-24614.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24612) Host Level Maintenance mode is not working through Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-24612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609375#comment-16609375
]
Hudson commented on AMBARI-24612:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9932 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9932/])
AMBARI-24612 Host Level Maintenance mode is not working through Ambari
(1963907+atkach:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=70b0579d1a66adc9299e3cd9aa44c920406a0da9])
* (edit) ambari-web/app/views/main/host/details.js
> Host Level Maintenance mode is not working through Ambari UI
>
>
> Key: AMBARI-24612
> URL: https://issues.apache.org/jira/browse/AMBARI-24612
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: Screen Shot 2018-09-10 at 1.38.14 PM (1).png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Steps to reproduce:-
> 1. Login
> 2.Open host page.
> 3. select on host.
> 4. click on "Host-Action" Tab and select "Turn On Maintenance mode "
> The message is showing
> {code}
> Are you sure you want to Turn Off Maintenance Mode for
> ctr-e138-1518143905142-471677-01-06.hwx.site?
> {code}
> I am trying to Turn On Maintenance Mode.
> after that
> !Screen Shot 2018-09-10 at 2.31.42 PM.png|thumbnail!
> {code}
> Maintenance Mode has been turned off. It may take a few minutes for the
> alerts to be enabled.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24615) Ambari - Manage Kafka Client Configs
[ https://issues.apache.org/jira/browse/AMBARI-24615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-24615: - Description: Request for Ambari to manage Kafka Client Configs. Currently only brokers are listed so you cannot split Kafka client configs to another config group and deploy them to allow Kafka clients to use less memory. There is no way to deploy the Kafka client config updates in Ambari. For example, if you have 8G heap allocated to Kafka brokers, clients fail to start on edge nodes as they cannot satisfy the broker's -Xms8G setting in kafka-env.sh, and splitting to a different config group for clients/brokers doesn't work as there is currently no way in Ambari to deploy the Kafka client config updates as only brokers are listed on summary page and there is no deploy client configurations type option, changes made to config only result in Restart Required for the few broker nodes. was: Ambari doesn't manage Kafka Client Configs(only brokers are listed) so you cannot split Kafka client configs to allow Kafka clients to use less memory and then deploy the client config updates. If you have 8G heap allocated to Kafka brokers, clients fail to start on edge nodes as they cannot satisfy the broker's -Xms8G setting, and there is no way to split the configs as you cannot deploy the client config updates as only brokers are listed on summary page and there is no deploy client configurations type option, changes made only result in Restart Required for the few broker nodes. > Ambari - Manage Kafka Client Configs > > > Key: AMBARI-24615 > URL: https://issues.apache.org/jira/browse/AMBARI-24615 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-client, ambari-server, ambari-web >Affects Versions: 2.6.2 > Environment: HDP 2.6 >Reporter: Hari Sekhon >Priority: Major > > Request for Ambari to manage Kafka Client Configs. > Currently only brokers are listed so you cannot split Kafka client configs to > another config group and deploy them to allow Kafka clients to use less > memory. There is no way to deploy the Kafka client config updates in Ambari. > For example, if you have 8G heap allocated to Kafka brokers, clients fail to > start on edge nodes as they cannot satisfy the broker's -Xms8G setting in > kafka-env.sh, and splitting to a different config group for clients/brokers > doesn't work as there is currently no way in Ambari to deploy the Kafka > client config updates as only brokers are listed on summary page and there is > no deploy client configurations type option, changes made to config only > result in Restart Required for the few broker nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24615) Ambari - Manage Kafka Client Configs
Hari Sekhon created AMBARI-24615: Summary: Ambari - Manage Kafka Client Configs Key: AMBARI-24615 URL: https://issues.apache.org/jira/browse/AMBARI-24615 Project: Ambari Issue Type: Task Components: ambari-agent, ambari-client, ambari-server, ambari-web Affects Versions: 2.6.2 Environment: HDP 2.6 Reporter: Hari Sekhon Ambari doesn't manage Kafka Client Configs(only brokers are listed) so you cannot split Kafka client configs to allow Kafka clients to use less memory and then deploy the client config updates. If you have 8G heap allocated to Kafka brokers, clients fail to start on edge nodes as they cannot satisfy the broker's -Xms8G setting, and there is no way to split the configs as you cannot deploy the client config updates as only brokers are listed on summary page and there is no deploy client configurations type option, changes made only result in Restart Required for the few broker nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24612) Host Level Maintenance mode is not working through Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-24612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609310#comment-16609310
]
Hudson commented on AMBARI-24612:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #234 (See
[https://builds.apache.org/job/Ambari-branch-2.7/234/])
AMBARI-24612 Host Level Maintenance mode is not working through Ambari
(1963907+atkach:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=fde00bb409fcdd908e13b33d5852fd45f871daa5])
* (edit) ambari-web/app/views/main/host/details.js
> Host Level Maintenance mode is not working through Ambari UI
>
>
> Key: AMBARI-24612
> URL: https://issues.apache.org/jira/browse/AMBARI-24612
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: Screen Shot 2018-09-10 at 1.38.14 PM (1).png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Steps to reproduce:-
> 1. Login
> 2.Open host page.
> 3. select on host.
> 4. click on "Host-Action" Tab and select "Turn On Maintenance mode "
> The message is showing
> {code}
> Are you sure you want to Turn Off Maintenance Mode for
> ctr-e138-1518143905142-471677-01-06.hwx.site?
> {code}
> I am trying to Turn On Maintenance Mode.
> after that
> !Screen Shot 2018-09-10 at 2.31.42 PM.png|thumbnail!
> {code}
> Maintenance Mode has been turned off. It may take a few minutes for the
> alerts to be enabled.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24612) Host Level Maintenance mode is not working through Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-24612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609243#comment-16609243
]
Andrii Tkach commented on AMBARI-24612:
---
committed to trunk and branch-2.7
> Host Level Maintenance mode is not working through Ambari UI
>
>
> Key: AMBARI-24612
> URL: https://issues.apache.org/jira/browse/AMBARI-24612
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: Screen Shot 2018-09-10 at 1.38.14 PM (1).png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Steps to reproduce:-
> 1. Login
> 2.Open host page.
> 3. select on host.
> 4. click on "Host-Action" Tab and select "Turn On Maintenance mode "
> The message is showing
> {code}
> Are you sure you want to Turn Off Maintenance Mode for
> ctr-e138-1518143905142-471677-01-06.hwx.site?
> {code}
> I am trying to Turn On Maintenance Mode.
> after that
> !Screen Shot 2018-09-10 at 2.31.42 PM.png|thumbnail!
> {code}
> Maintenance Mode has been turned off. It may take a few minutes for the
> alerts to be enabled.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24612) Host Level Maintenance mode is not working through Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-24612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach resolved AMBARI-24612.
---
Resolution: Fixed
> Host Level Maintenance mode is not working through Ambari UI
>
>
> Key: AMBARI-24612
> URL: https://issues.apache.org/jira/browse/AMBARI-24612
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: Screen Shot 2018-09-10 at 1.38.14 PM (1).png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Steps to reproduce:-
> 1. Login
> 2.Open host page.
> 3. select on host.
> 4. click on "Host-Action" Tab and select "Turn On Maintenance mode "
> The message is showing
> {code}
> Are you sure you want to Turn Off Maintenance Mode for
> ctr-e138-1518143905142-471677-01-06.hwx.site?
> {code}
> I am trying to Turn On Maintenance Mode.
> after that
> !Screen Shot 2018-09-10 at 2.31.42 PM.png|thumbnail!
> {code}
> Maintenance Mode has been turned off. It may take a few minutes for the
> alerts to be enabled.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24605) ambari-server exception if any user with cluster operator role is trying to edit the widget.
[ https://issues.apache.org/jira/browse/AMBARI-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609147#comment-16609147 ] Hudson commented on AMBARI-24605: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9930 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9930/]) AMBARI-24605. Using the new RBAC framework to allow cluster (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=d9ab7ba8cc9f8b3ee4a7d888945d474c187ddb38]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/WidgetResourceProviderTest.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/WidgetResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/RoleAuthorization.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog272.java > ambari-server exception if any user with cluster operator role is trying to > edit the widget. > > > Key: AMBARI-24605 > URL: https://issues.apache.org/jira/browse/AMBARI-24605 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: RoleChart.png, > errorWhileEditingWidgetsAsClusterOperator.png > > Time Spent: 1h > Remaining Estimate: 0h > > *STR* > 1. login using widgetuser(username),widgetpass(password) the role is cluster > operator > 2. go to hdfs-> metrics tab > 3. EDIT shared the "Under Replicated Blocks" widgets. > 4. the error can be reproduced > *Actual Result:* > !errorWhileEditingWidgetsAsClusterOperator.png! > *Expected Result:* > According to our Role Chart a user with Cluster Operator role should be able > to create/edit widgets > !RoleChart.png! > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24605) ambari-server exception if any user with cluster operator role is trying to edit the widget.
[ https://issues.apache.org/jira/browse/AMBARI-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609145#comment-16609145 ] Hudson commented on AMBARI-24605: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #233 (See [https://builds.apache.org/job/Ambari-branch-2.7/233/]) AMBARI-24605. Using the new RBAC framework to allow cluster (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=d96bfd326d186955dee564e03e27488ab1da8df2]) * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/RoleAuthorization.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog272.java * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/WidgetResourceProvider.java * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/WidgetResourceProviderTest.java > ambari-server exception if any user with cluster operator role is trying to > edit the widget. > > > Key: AMBARI-24605 > URL: https://issues.apache.org/jira/browse/AMBARI-24605 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: RoleChart.png, > errorWhileEditingWidgetsAsClusterOperator.png > > Time Spent: 1h > Remaining Estimate: 0h > > *STR* > 1. login using widgetuser(username),widgetpass(password) the role is cluster > operator > 2. go to hdfs-> metrics tab > 3. EDIT shared the "Under Replicated Blocks" widgets. > 4. the error can be reproduced > *Actual Result:* > !errorWhileEditingWidgetsAsClusterOperator.png! > *Expected Result:* > According to our Role Chart a user with Cluster Operator role should be able > to create/edit widgets > !RoleChart.png! > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24614) deploy-gce-perf-cluster.py script does not work
[ https://issues.apache.org/jira/browse/AMBARI-24614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24614: Labels: pull-request-available (was: ) > deploy-gce-perf-cluster.py script does not work > --- > > Key: AMBARI-24614 > URL: https://issues.apache.org/jira/browse/AMBARI-24614 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24614.patch, AMBARI-24614.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24614) deploy-gce-perf-cluster.py script does not work
[ https://issues.apache.org/jira/browse/AMBARI-24614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24614: - Attachment: AMBARI-24614.patch > deploy-gce-perf-cluster.py script does not work > --- > > Key: AMBARI-24614 > URL: https://issues.apache.org/jira/browse/AMBARI-24614 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.2 > > Attachments: AMBARI-24614.patch, AMBARI-24614.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24614) deploy-gce-perf-cluster.py script does not work
[ https://issues.apache.org/jira/browse/AMBARI-24614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24614: - Attachment: AMBARI-24614.patch > deploy-gce-perf-cluster.py script does not work > --- > > Key: AMBARI-24614 > URL: https://issues.apache.org/jira/browse/AMBARI-24614 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.2 > > Attachments: AMBARI-24614.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24614) deploy-gce-perf-cluster.py script does not work
[ https://issues.apache.org/jira/browse/AMBARI-24614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24614: - Status: Patch Available (was: Open) > deploy-gce-perf-cluster.py script does not work > --- > > Key: AMBARI-24614 > URL: https://issues.apache.org/jira/browse/AMBARI-24614 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.2 > > Attachments: AMBARI-24614.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24614) deploy-gce-perf-cluster.py script does not work
Andrew Onischuk created AMBARI-24614: Summary: deploy-gce-perf-cluster.py script does not work Key: AMBARI-24614 URL: https://issues.apache.org/jira/browse/AMBARI-24614 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.2 Attachments: AMBARI-24614.patch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24604) Stack advisor error popup with "500 status code" thrown during customize service page of install wizard
[ https://issues.apache.org/jira/browse/AMBARI-24604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609052#comment-16609052 ] Hudson commented on AMBARI-24604: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9929 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9929/]) [AMBARI-24604] Stack advisor error popup with "500 status code" thrown (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=ab3a2449432a23cb9c050d0876717e9f581dd767]) * (edit) ambari-server/src/main/resources/stacks/stack_advisor.py > Stack advisor error popup with "500 status code" thrown during customize > service page of install wizard > --- > > Key: AMBARI-24604 > URL: https://issues.apache.org/jira/browse/AMBARI-24604 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > ams-hbase hbase.rootdir property being set to "file://" leads to 500 server > error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24604) Stack advisor error popup with "500 status code" thrown during customize service page of install wizard
[ https://issues.apache.org/jira/browse/AMBARI-24604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609036#comment-16609036 ] Hudson commented on AMBARI-24604: - FAILURE: Integrated in Jenkins build Ambari-branch-2.7 #232 (See [https://builds.apache.org/job/Ambari-branch-2.7/232/]) [AMBARI-24604] Stack advisor error popup with "500 status code" thrown (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=2a084df031d640c3427932eadf3c30b66cb60339]) * (edit) ambari-server/src/main/resources/stacks/stack_advisor.py > Stack advisor error popup with "500 status code" thrown during customize > service page of install wizard > --- > > Key: AMBARI-24604 > URL: https://issues.apache.org/jira/browse/AMBARI-24604 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > ams-hbase hbase.rootdir property being set to "file://" leads to 500 server > error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24613) [Log Search UI] Date picker preset ranges are not displayed properly
[ https://issues.apache.org/jira/browse/AMBARI-24613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24613: --- Status: Patch Available (was: In Progress) > [Log Search UI] Date picker preset ranges are not displayed properly > > > Key: AMBARI-24613 > URL: https://issues.apache.org/jira/browse/AMBARI-24613 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Original Estimate: 1h > Time Spent: 20m > Remaining Estimate: 40m > > [Logsearch UI] Date picker preset ranges are not displayed properly -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24613) [Log Search UI] Date picker preset ranges are not displayed properly
[ https://issues.apache.org/jira/browse/AMBARI-24613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24613: Labels: pull-request-available (was: ) > [Log Search UI] Date picker preset ranges are not displayed properly > > > Key: AMBARI-24613 > URL: https://issues.apache.org/jira/browse/AMBARI-24613 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Original Estimate: 1h > Remaining Estimate: 1h > > [Logsearch UI] Date picker preset ranges are not displayed properly -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24612) Host Level Maintenance mode is not working through Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-24612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24612:
Labels: pull-request-available (was: )
> Host Level Maintenance mode is not working through Ambari UI
>
>
> Key: AMBARI-24612
> URL: https://issues.apache.org/jira/browse/AMBARI-24612
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: Screen Shot 2018-09-10 at 1.38.14 PM (1).png
>
>
> Steps to reproduce:-
> 1. Login
> 2.Open host page.
> 3. select on host.
> 4. click on "Host-Action" Tab and select "Turn On Maintenance mode "
> The message is showing
> {code}
> Are you sure you want to Turn Off Maintenance Mode for
> ctr-e138-1518143905142-471677-01-06.hwx.site?
> {code}
> I am trying to Turn On Maintenance Mode.
> after that
> !Screen Shot 2018-09-10 at 2.31.42 PM.png|thumbnail!
> {code}
> Maintenance Mode has been turned off. It may take a few minutes for the
> alerts to be enabled.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24613) [Log Search UI] Date picker preset ranges are not displayed properly
Istvan Tobias created AMBARI-24613: -- Summary: [Log Search UI] Date picker preset ranges are not displayed properly Key: AMBARI-24613 URL: https://issues.apache.org/jira/browse/AMBARI-24613 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias [Logsearch UI] Date picker preset ranges are not displayed properly -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24612) Host Level Maintenance mode is not working through Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-24612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-24612:
--
Description:
Steps to reproduce:-
1. Login
2.Open host page.
3. select on host.
4. click on "Host-Action" Tab and select "Turn On Maintenance mode "
The message is showing
{code}
Are you sure you want to Turn Off Maintenance Mode for
ctr-e138-1518143905142-471677-01-06.hwx.site?
{code}
I am trying to Turn On Maintenance Mode.
after that
!Screen Shot 2018-09-10 at 2.31.42 PM.png|thumbnail!
{code}
Maintenance Mode has been turned off. It may take a few minutes for the alerts
to be enabled.
{code}
was:
Steps to reproduce:-
1. Login
2.Open host page.
3. select on host.
4. click on "Host-Action" Tab and select "Turn On Maintenance mode "
!Screen Shot 2018-09-10 at 1.38.14 PM.png|thumbnail!
The message is showing
{code}
Are you sure you want to Turn Off Maintenance Mode for
ctr-e138-1518143905142-471677-01-06.hwx.site?
{code}
I am trying to Turn On Maintenance Mode.
after that
!Screen Shot 2018-09-10 at 2.31.42 PM.png|thumbnail!
{code}
Maintenance Mode has been turned off. It may take a few minutes for the alerts
to be enabled.
{code}
> Host Level Maintenance mode is not working through Ambari UI
>
>
> Key: AMBARI-24612
> URL: https://issues.apache.org/jira/browse/AMBARI-24612
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.7.1
>
> Attachments: Screen Shot 2018-09-10 at 1.38.14 PM (1).png
>
>
> Steps to reproduce:-
> 1. Login
> 2.Open host page.
> 3. select on host.
> 4. click on "Host-Action" Tab and select "Turn On Maintenance mode "
> The message is showing
> {code}
> Are you sure you want to Turn Off Maintenance Mode for
> ctr-e138-1518143905142-471677-01-06.hwx.site?
> {code}
> I am trying to Turn On Maintenance Mode.
> after that
> !Screen Shot 2018-09-10 at 2.31.42 PM.png|thumbnail!
> {code}
> Maintenance Mode has been turned off. It may take a few minutes for the
> alerts to be enabled.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24612) Host Level Maintenance mode is not working through Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-24612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-24612:
--
Attachment: Screen Shot 2018-09-10 at 1.38.14 PM (1).png
> Host Level Maintenance mode is not working through Ambari UI
>
>
> Key: AMBARI-24612
> URL: https://issues.apache.org/jira/browse/AMBARI-24612
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.7.1
>
> Attachments: Screen Shot 2018-09-10 at 1.38.14 PM (1).png
>
>
> Steps to reproduce:-
> 1. Login
> 2.Open host page.
> 3. select on host.
> 4. click on "Host-Action" Tab and select "Turn On Maintenance mode "
> !Screen Shot 2018-09-10 at 1.38.14 PM.png|thumbnail!
> The message is showing
> {code}
> Are you sure you want to Turn Off Maintenance Mode for
> ctr-e138-1518143905142-471677-01-06.hwx.site?
> {code}
> I am trying to Turn On Maintenance Mode.
> after that
> !Screen Shot 2018-09-10 at 2.31.42 PM.png|thumbnail!
> {code}
> Maintenance Mode has been turned off. It may take a few minutes for the
> alerts to be enabled.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24612) Host Level Maintenance mode is not working through Ambari UI
Andrii Tkach created AMBARI-24612:
-
Summary: Host Level Maintenance mode is not working through Ambari
UI
Key: AMBARI-24612
URL: https://issues.apache.org/jira/browse/AMBARI-24612
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.1
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Fix For: 2.7.1
Steps to reproduce:-
1. Login
2.Open host page.
3. select on host.
4. click on "Host-Action" Tab and select "Turn On Maintenance mode "
!Screen Shot 2018-09-10 at 1.38.14 PM.png|thumbnail!
The message is showing
{code}
Are you sure you want to Turn Off Maintenance Mode for
ctr-e138-1518143905142-471677-01-06.hwx.site?
{code}
I am trying to Turn On Maintenance Mode.
after that
!Screen Shot 2018-09-10 at 2.31.42 PM.png|thumbnail!
{code}
Maintenance Mode has been turned off. It may take a few minutes for the alerts
to be enabled.
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24610) [Log Search UI] Show user friendly component name in query input
[ https://issues.apache.org/jira/browse/AMBARI-24610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24610: --- Status: Patch Available (was: In Progress) > [Log Search UI] Show user friendly component name in query input > > > Key: AMBARI-24610 > URL: https://issues.apache.org/jira/browse/AMBARI-24610 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Original Estimate: 3h > Time Spent: 20m > Remaining Estimate: 2h 40m > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24610) [Log Search UI] Show user friendly component name in query input
[ https://issues.apache.org/jira/browse/AMBARI-24610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24610: Labels: pull-request-available (was: ) > [Log Search UI] Show user friendly component name in query input > > > Key: AMBARI-24610 > URL: https://issues.apache.org/jira/browse/AMBARI-24610 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Original Estimate: 3h > Remaining Estimate: 3h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24597) Popup shown when Ambari started on a different port other than 8080
[
https://issues.apache.org/jira/browse/AMBARI-24597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16608987#comment-16608987
]
Hudson commented on AMBARI-24597:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9928 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9928/])
AMBARI-24597. Popup shown when Ambari started on a different port other
(aleksandrkovalenko:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=4b60f5ce03a44f320a252dbb8ab88c078d54a345])
* (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/app.js
> Popup shown when Ambari started on a different port other than 8080
> ---
>
> Key: AMBARI-24597
> URL: https://issues.apache.org/jira/browse/AMBARI-24597
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Change the Ambari server port by setting the following
> {code:title=ambari.properties}
> client.api.port=8000
> {code}
> Ab error popup is observed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24611) Disabling an Alert Does Not Clear It in the Web UI
Myroslav Papirkovskyi created AMBARI-24611: -- Summary: Disabling an Alert Does Not Clear It in the Web UI Key: AMBARI-24611 URL: https://issues.apache.org/jira/browse/AMBARI-24611 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 2.7.2 When you disable an alert, the web client shows that the instance of the alert was removed immediately, however, the red badges indicating a critical alert do not disappear. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24610) [Log Search UI] Show user friendly component name in query input
Istvan Tobias created AMBARI-24610: -- Summary: [Log Search UI] Show user friendly component name in query input Key: AMBARI-24610 URL: https://issues.apache.org/jira/browse/AMBARI-24610 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24605) ambari-server exception if any user with cluster operator role is trying to edit the widget.
[ https://issues.apache.org/jira/browse/AMBARI-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24605: Labels: pull-request-available (was: ) > ambari-server exception if any user with cluster operator role is trying to > edit the widget. > > > Key: AMBARI-24605 > URL: https://issues.apache.org/jira/browse/AMBARI-24605 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: RoleChart.png, > errorWhileEditingWidgetsAsClusterOperator.png > > > *STR* > 1. login using widgetuser(username),widgetpass(password) the role is cluster > operator > 2. go to hdfs-> metrics tab > 3. EDIT shared the "Under Replicated Blocks" widgets. > 4. the error can be reproduced > *Actual Result:* > !errorWhileEditingWidgetsAsClusterOperator.png! > *Expected Result:* > According to our Role Chart a user with Cluster Operator role should be able > to create/edit widgets > !RoleChart.png! > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
