[jira] [Updated] (AMBARI-23256) Ambari-agent setting permission of .hash files in /var/lib/ambari-agent/cache to 666
[
https://issues.apache.org/jira/browse/AMBARI-23256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-23256:
--
Description:
Ambari-agent is setting permission of some files in /var/lib/ambari-agent/cache
folder to 666
{code:java}
[root@asnaik3 ambari-agent]# find cache -printf '%m %p\n' |grep 666
666 cache/custom_actions/.hash
666 cache/common-services/AMBARI_INFRA/0.1.0/package/.hash
666 cache/common-services/AMBARI_METRICS/0.1.0/package/.hash
666 cache/common-services/HDFS/2.1.0.2.0/package/.hash
666 cache/common-services/HIVE/0.12.0.2.0/package/.hash
666 cache/common-services/LOGSEARCH/0.5.0/package/.hash
666 cache/common-services/OOZIE/4.0.0.2.0/package/.hash
666 cache/common-services/PIG/0.12.0.2.0/package/.hash
666 cache/common-services/SLIDER/0.60.0.2.2/package/.hash
666 cache/common-services/SPARK/1.2.1/package/.hash
666 cache/common-services/SPARK2/2.0.0/package/.hash
666 cache/common-services/TEZ/0.4.0.2.1/package/.hash
666 cache/common-services/YARN/2.1.0.2.0/package/.hash
666 cache/common-services/ZOOKEEPER/3.4.5/package/.hash
666 cache/stacks/HDP/2.0.6/hooks/.hash
666 cache/host_scripts/.hash
{code}
root cause :
https://github.com/apache/ambari/blob/trunk/ambari-agent/src/main/python/ambari_agent/FileCache.py
{code:java}
hash_file = os.path.join(directory, self.HASH_SUM_FILE)
try:
with open(hash_file, "w") as fh:
fh.write(new_hash)
os.chmod(hash_file, 0o666)
{code}
Need to change the permission to os.chmod(hash_file, 0o644)
was:
Ambari-agent is setting permission of some files in /var/lib/ambari-agent/cache
folder to 666
{code:java}
[root@asnaik3 ambari-agent]# find cache -printf '%m %p\n' |grep 666
666 cache/custom_actions/.hash
666 cache/common-services/AMBARI_INFRA/0.1.0/package/.hash
666 cache/common-services/AMBARI_METRICS/0.1.0/package/.hash
666 cache/common-services/HDFS/2.1.0.2.0/package/.hash
666 cache/common-services/HIVE/0.12.0.2.0/package/.hash
666 cache/common-services/LOGSEARCH/0.5.0/package/.hash
666 cache/common-services/OOZIE/4.0.0.2.0/package/.hash
666 cache/common-services/PIG/0.12.0.2.0/package/.hash
666 cache/common-services/SLIDER/0.60.0.2.2/package/.hash
666 cache/common-services/SPARK/1.2.1/package/.hash
666 cache/common-services/SPARK2/2.0.0/package/.hash
666 cache/common-services/TEZ/0.4.0.2.1/package/.hash
666 cache/common-services/YARN/2.1.0.2.0/package/.hash
666 cache/common-services/ZOOKEEPER/3.4.5/package/.hash
666 cache/stacks/HDP/2.0.6/hooks/.hash
666 cache/host_scripts/.hash
{code}
root cause :
https://github.com/apache/ambari/blob/trunk/ambari-agent/src/main/python/ambari_agent/FileCache.py
{code:java}
hash_file = os.path.join(directory, self.HASH_SUM_FILE)
try:
with open(hash_file, "w") as fh:
fh.write(new_hash)
os.chmod(hash_file, 0o666)
{code}
Need to change the permission to os.chmod(hash_file, 0o755)
> Ambari-agent setting permission of .hash files in /var/lib/ambari-agent/cache
> to 666
>
>
> Key: AMBARI-23256
> URL: https://issues.apache.org/jira/browse/AMBARI-23256
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.6.1
> Environment: ambari-agent-2.6.1
> also applicable in lower versions
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: ambari-agent, pull-request-available, python
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Ambari-agent is setting permission of some files in
> /var/lib/ambari-agent/cache folder to 666
> {code:java}
> [root@asnaik3 ambari-agent]# find cache -printf '%m %p\n' |grep 666
> 666 cache/custom_actions/.hash
> 666 cache/common-services/AMBARI_INFRA/0.1.0/package/.hash
> 666 cache/common-services/AMBARI_METRICS/0.1.0/package/.hash
> 666 cache/common-services/HDFS/2.1.0.2.0/package/.hash
> 666 cache/common-services/HIVE/0.12.0.2.0/package/.hash
> 666 cache/common-services/LOGSEARCH/0.5.0/package/.hash
> 666 cache/common-services/OOZIE/4.0.0.2.0/package/.hash
> 666 cache/common-services/PIG/0.12.0.2.0/package/.hash
> 666 cache/common-services/SLIDER/0.60.0.2.2/package/.hash
> 666 cache/common-services/SPARK/1.2.1/package/.hash
> 666 cache/common-services/SPARK2/2.0.0/package/.hash
> 666 cache/common-services/TEZ/0.4.0.2.1/package/.hash
> 666 cache/common-services/YARN/2.1.0.2.0/package/.hash
> 666 cache/common-services/ZOOKEEPER/3.4.5/package/.hash
> 666 cache/stacks/HDP/2.0.6/hooks/.hash
> 666 cache/host_scripts/.hash
> {code}
> root cause :
> https://github.com/apache/ambari/blob/trunk/ambari-agent/src/main/python/ambari_agent/FileCache.py
> {code:java}
> hash_file = os.path.join(directory, self.HASH_SUM_FILE)
> try:
> with open(hash_file, "w") as fh:
>
[jira] [Commented] (AMBARI-23305) Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'"
[ https://issues.apache.org/jira/browse/AMBARI-23305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407038#comment-16407038 ] Hudson commented on AMBARI-23305: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8885 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8885/]) AMBARI-23305. Grafana install fails with "KeyError: 'getpwnam(): name (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=ef2b0ae16fb3975888962d0e2615678d7bdc7fd5]) * (edit) ambari-agent/src/main/python/ambari_agent/FileCache.py * (edit) ambari-agent/src/test/python/ambari_agent/TestFileCache.py > Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'" > > > Key: AMBARI-23305 > URL: https://issues.apache.org/jira/browse/AMBARI-23305 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23305.patch, AMBARI-23305.patch, > AMBARI-23305.patch, AMBARI-23305.patch, AMBARI-23305.patch, AMBARI-23305.patch > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23303) Use NameNode Upgrade Timeout Override In All Upgrade Packs
[ https://issues.apache.org/jira/browse/AMBARI-23303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407037#comment-16407037 ] Hudson commented on AMBARI-23303: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8885 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8885/]) AMBARI-23303 - Use NameNode Upgrade Timeout Override In All Upgrade (jonathanhurley: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=b71c9ae963a6aeb54cfd8ea672f9e9894d1a7a09]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/host-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml > Use NameNode Upgrade Timeout Override In All Upgrade Packs > -- > > Key: AMBARI-23303 > URL: https://issues.apache.org/jira/browse/AMBARI-23303 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The upgrade timeout parameter for NameNode restarts is only defined in > rolling upgrade packs. It should be used in all upgrade packs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23305) Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'"
[ https://issues.apache.org/jira/browse/AMBARI-23305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23305: - Attachment: AMBARI-23305.patch > Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'" > > > Key: AMBARI-23305 > URL: https://issues.apache.org/jira/browse/AMBARI-23305 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23305.patch, AMBARI-23305.patch, > AMBARI-23305.patch, AMBARI-23305.patch, AMBARI-23305.patch, AMBARI-23305.patch > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23305) Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'"
[ https://issues.apache.org/jira/browse/AMBARI-23305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23305: - Attachment: AMBARI-23305.patch > Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'" > > > Key: AMBARI-23305 > URL: https://issues.apache.org/jira/browse/AMBARI-23305 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23305.patch, AMBARI-23305.patch, > AMBARI-23305.patch, AMBARI-23305.patch, AMBARI-23305.patch, AMBARI-23305.patch > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23305) Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'"
[ https://issues.apache.org/jira/browse/AMBARI-23305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23305: - Attachment: AMBARI-23305.patch > Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'" > > > Key: AMBARI-23305 > URL: https://issues.apache.org/jira/browse/AMBARI-23305 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23305.patch, AMBARI-23305.patch, > AMBARI-23305.patch, AMBARI-23305.patch > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23305) Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'"
[ https://issues.apache.org/jira/browse/AMBARI-23305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23305: - Attachment: AMBARI-23305.patch > Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'" > > > Key: AMBARI-23305 > URL: https://issues.apache.org/jira/browse/AMBARI-23305 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23305.patch, AMBARI-23305.patch, > AMBARI-23305.patch, AMBARI-23305.patch > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23305) Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'"
[ https://issues.apache.org/jira/browse/AMBARI-23305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23305: - Attachment: AMBARI-23305.patch > Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'" > > > Key: AMBARI-23305 > URL: https://issues.apache.org/jira/browse/AMBARI-23305 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23305.patch, AMBARI-23305.patch > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23097) Log Search: knox proxy support
[ https://issues.apache.org/jira/browse/AMBARI-23097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23097: Labels: pull-request-available (was: ) > Log Search: knox proxy support > -- > > Key: AMBARI-23097 > URL: https://issues.apache.org/jira/browse/AMBARI-23097 > 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.7.0 > > > Add knox proxy support and update knox docker env with that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23303) Use NameNode Upgrade Timeout Override In All Upgrade Packs
[ https://issues.apache.org/jira/browse/AMBARI-23303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley resolved AMBARI-23303. -- Resolution: Fixed > Use NameNode Upgrade Timeout Override In All Upgrade Packs > -- > > Key: AMBARI-23303 > URL: https://issues.apache.org/jira/browse/AMBARI-23303 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The upgrade timeout parameter for NameNode restarts is only defined in > rolling upgrade packs. It should be used in all upgrade packs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-21008) Integrate AlertTargetService and subresources with swagger
[ https://issues.apache.org/jira/browse/AMBARI-21008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Boros resolved AMBARI-21008. -- Resolution: Resolved > Integrate AlertTargetService and subresources with swagger > -- > > Key: AMBARI-21008 > URL: https://issues.apache.org/jira/browse/AMBARI-21008 > Project: Ambari > Issue Type: Task >Reporter: Balázs Bence Sári >Assignee: Gabor Boros >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 2h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23230) Upgrade Solr configuration while upgrading Ambari 2.6.1 -> 2.7.0
[ https://issues.apache.org/jira/browse/AMBARI-23230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23230: Labels: pull-request-available (was: ) > Upgrade Solr configuration while upgrading Ambari 2.6.1 -> 2.7.0 > > > Key: AMBARI-23230 > URL: https://issues.apache.org/jira/browse/AMBARI-23230 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23292) livy.superusers is not getting configured correctly when Spark2 and Zeppelin are added as a service later on
[
https://issues.apache.org/jira/browse/AMBARI-23292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406659#comment-16406659
]
Hudson commented on AMBARI-23292:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8884 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8884/])
[AMBARI-23292] livy.superusers is not getting configured correctly when
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=b3f77793cd5b45fc4f01c937ca19bf4387018de7])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
> livy.superusers is not getting configured correctly when Spark2 and Zeppelin
> are added as a service later on
>
>
> Key: AMBARI-23292
> URL: https://issues.apache.org/jira/browse/AMBARI-23292
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This bug was found during bugbash. I had a cluster where Spark2 and Zeppelin
> was not present. I added both these services via Add service wizard in
> Ambari.
> The string '$
> {zeppelin-env/zeppelin_user}
> $
> {principal_suffix}
> ' is not getting replaced by correct zeppelin principal value and hence the
> %livy2 paragraphs are failing
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23289) Add SSO integration support information to service information via Ambari's REST API
[
https://issues.apache.org/jira/browse/AMBARI-23289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23289:
Labels: pull-request-available (was: )
> Add SSO integration support information to service information via Ambari's
> REST API
>
>
> Key: AMBARI-23289
> URL: https://issues.apache.org/jira/browse/AMBARI-23289
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> Add SSO integration support information to service information via Ambari's
> REST API. This information should be usable by Ambari's search predicate
> feature.
> New _read-only_ properties for (stack) services should be:
> * *{{sso_integration_supported}}* - Indicates whether the service supports
> SSO integration or not
> ** Information is expected to be determined by service's meta info (see
> BUG-98626)
> New _read-only_ properties for installed services should be:
> * *{{sso_integration_supported}}* - Indicates whether the service supports
> SSO integration or not
> ** Information is expected to be determined by the service's meta info (see
> BUG-98626)
> * *{{sso_integration_enabled}}* - Indicates whether the service is configured
> for SSO integration or not
> ** Information is expected to be determined by a value indicated in the
> service's meta info (see BUG-98626)
> * *{{sso_integration_desired}}* - Indicates whether the service is chosen for
> SSO integration or not
> ** Information is expected to be in {{cluster-env/sso_enabled_services}} (see
> BUG-98451)
> Examples:
> {noformat:title=Get stack service details}
> GET /api/v1/stacks/:STACK_NAME/versions/:VERSION/services/:SERVICE_NAME",
> {
> "href" : ":URL",
> "StackServices" : {
> ...
> "sso_integration_supported": "false",
> ...
> },
> ...
> {noformat}
> {noformat:title=Get installed service information}
> GET /api/v1/clusters/:CLUSTER_NAME/services/:SERVICE_NAME
> {
> "href" : ":URL",
> "ServiceInfo" : {
> "cluster_name" : ":CLUSTER_NAME",
> ...
> "sso_integration_supported": "true",
> "sso_integration_enabled": "false",
> "sso_integration_desired": "false",
> ...
> },
> ...
> {noformat}
> {noformat:title=List installed services that support SSO integration}
> GET
> /api/v1/clusters/:CLUSTER_NAME/services?ServiceInfo/sso_integration_supported=true
> {
> "href" : ":URL",
> "items" : [
> ...
>]
> }
> {noformat}
> {noformat:title=List stack services that support SSO integration}
> GET
> /api/v1/stacks/:STACK_NAME/versions/:VERSION/services?StackServices/credential_store_enabled=false
> {
> "href" : ":URL",
> "items" : [
> ...
>]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23306) Ambari Upgrade: Start All Services fails after AU at MapReduce2 Client Install with error "Configuration parameter 'container-executor' was not found in configurations
[
https://issues.apache.org/jira/browse/AMBARI-23306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23306:
Labels: pull-request-available upgrade (was: upgrade)
> Ambari Upgrade: Start All Services fails after AU at MapReduce2 Client
> Install with error "Configuration parameter 'container-executor' was not
> found in configurations dictionary!"
> -
>
> Key: AMBARI-23306
> URL: https://issues.apache.org/jira/browse/AMBARI-23306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
> Labels: pull-request-available, upgrade
> Fix For: 2.7.0
>
>
> After Ambari Upgrade from 2.6.0.0 to 2.7.0.0 , start all services operation
> fails at MapReduce2 Client Install with below error.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py",
> line 91, in
> MapReduce2Client().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 377, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py",
> line 41, in install
> self.configure(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 122, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py",
> line 50, in configure
> yarn(config_dir=config_dir)
> File "/usr/lib/ambari-agent/lib/ambari_commons/os_family_impl.py", line 89,
> in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py",
> line 166, in yarn
> content=InlineTemplate(params.container_executor_cfg_template)
> File "/usr/lib/ambari-agent/lib/resource_management/core/source.py", line
> 150, in __init__
> super(InlineTemplate, self).__init__(name, extra_imports, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/source.py", line
> 137, in __init__
> self.template = self.template_env.get_template(self.name)
> File "/usr/lib/ambari-agent/lib/ambari_jinja2/environment.py", line 716, in
> get_template
> return self._load_template(name, self.make_globals(globals))
> File "/usr/lib/ambari-agent/lib/ambari_jinja2/environment.py", line 686, in
> _load_template
> template = self.cache.get(name)
> File "/usr/lib/ambari-agent/lib/ambari_jinja2/utils.py", line 405, in get
> return self[key]
> File "/usr/lib/ambari-agent/lib/ambari_jinja2/utils.py", line 448, in
> __getitem__
> rv = self._mapping[key]
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'container-executor' was not found in configurations dictionary!
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23306) Ambari Upgrade: Start All Services fails after AU at MapReduce2 Client Install with error "Configuration parameter 'container-executor' was not found in configurations
Sandor Molnar created AMBARI-23306:
--
Summary: Ambari Upgrade: Start All Services fails after AU at
MapReduce2 Client Install with error "Configuration parameter
'container-executor' was not found in configurations dictionary!"
Key: AMBARI-23306
URL: https://issues.apache.org/jira/browse/AMBARI-23306
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.7.0
After Ambari Upgrade from 2.6.0.0 to 2.7.0.0 , start all services operation
fails at MapReduce2 Client Install with below error.
{code:java}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py",
line 91, in
MapReduce2Client().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 377, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py",
line 41, in install
self.configure(env)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 122, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py",
line 50, in configure
yarn(config_dir=config_dir)
File "/usr/lib/ambari-agent/lib/ambari_commons/os_family_impl.py", line 89,
in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py",
line 166, in yarn
content=InlineTemplate(params.container_executor_cfg_template)
File "/usr/lib/ambari-agent/lib/resource_management/core/source.py", line
150, in __init__
super(InlineTemplate, self).__init__(name, extra_imports, **kwargs)
File "/usr/lib/ambari-agent/lib/resource_management/core/source.py", line
137, in __init__
self.template = self.template_env.get_template(self.name)
File "/usr/lib/ambari-agent/lib/ambari_jinja2/environment.py", line 716, in
get_template
return self._load_template(name, self.make_globals(globals))
File "/usr/lib/ambari-agent/lib/ambari_jinja2/environment.py", line 686, in
_load_template
template = self.cache.get(name)
File "/usr/lib/ambari-agent/lib/ambari_jinja2/utils.py", line 405, in get
return self[key]
File "/usr/lib/ambari-agent/lib/ambari_jinja2/utils.py", line 448, in
__getitem__
rv = self._mapping[key]
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found in
configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter
'container-executor' was not found in configurations dictionary!
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23292) livy.superusers is not getting configured correctly when Spark2 and Zeppelin are added as a service later on
[
https://issues.apache.org/jira/browse/AMBARI-23292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-23292:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> livy.superusers is not getting configured correctly when Spark2 and Zeppelin
> are added as a service later on
>
>
> Key: AMBARI-23292
> URL: https://issues.apache.org/jira/browse/AMBARI-23292
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This bug was found during bugbash. I had a cluster where Spark2 and Zeppelin
> was not present. I added both these services via Add service wizard in
> Ambari.
> The string '$
> {zeppelin-env/zeppelin_user}
> $
> {principal_suffix}
> ' is not getting replaced by correct zeppelin principal value and hence the
> %livy2 paragraphs are failing
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23305) Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'"
[ https://issues.apache.org/jira/browse/AMBARI-23305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406533#comment-16406533 ] Hudson commented on AMBARI-23305: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8883 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8883/]) AMBARI-23305. Grafana install fails with "KeyError: 'getpwnam(): name (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=d7b93999d7891f830193e2f85230af4f8645d14e]) * (edit) ambari-agent/src/main/python/ambari_agent/FileCache.py * (edit) ambari-agent/src/test/python/ambari_agent/TestFileCache.py > Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'" > > > Key: AMBARI-23305 > URL: https://issues.apache.org/jira/browse/AMBARI-23305 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23305.patch > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23305) Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'"
[ https://issues.apache.org/jira/browse/AMBARI-23305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23305: Labels: pull-request-available (was: ) > Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'" > > > Key: AMBARI-23305 > URL: https://issues.apache.org/jira/browse/AMBARI-23305 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23305.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23305) Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'"
[ https://issues.apache.org/jira/browse/AMBARI-23305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23305: - Attachment: AMBARI-23305.patch > Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'" > > > Key: AMBARI-23305 > URL: https://issues.apache.org/jira/browse/AMBARI-23305 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23305.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23305) Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'"
Andrew Onischuk created AMBARI-23305: Summary: Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'" Key: AMBARI-23305 URL: https://issues.apache.org/jira/browse/AMBARI-23305 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.0 Attachments: AMBARI-23305.patch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23305) Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'"
[ https://issues.apache.org/jira/browse/AMBARI-23305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23305: - Status: Patch Available (was: Open) > Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'" > > > Key: AMBARI-23305 > URL: https://issues.apache.org/jira/browse/AMBARI-23305 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23305.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23122) Yarn Queue Manager is not case sensitive
[ https://issues.apache.org/jira/browse/AMBARI-23122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-23122: -- Status: Patch Available (was: In Progress) > Yarn Queue Manager is not case sensitive > > > Key: AMBARI-23122 > URL: https://issues.apache.org/jira/browse/AMBARI-23122 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Prabhu Joseph >Assignee: Akhil S Naik >Priority: Major > Labels: pull-request-available > Attachments: Screen Shot 2018-03-01 at 10.47.13 PM.png, Screen Shot > 2018-03-01 at 10.47.53 PM.png, capacity-scheduler.xml > > Time Spent: 40m > Remaining Estimate: 0h > > YARN Queue Manager does not allow two queues with "abc" and "ABC" whereas > YARN Capacity Scheduler allows the same. > Attached screenshots of YARN Queue Manager and RM UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23304) Add namespace-specific layout for HDFS metrics
[ https://issues.apache.org/jira/browse/AMBARI-23304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23304: Labels: pull-request-available (was: ) > Add namespace-specific layout for HDFS metrics > -- > > Key: AMBARI-23304 > URL: https://issues.apache.org/jira/browse/AMBARI-23304 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > > The layout of HDFS metrics section should look like as follows: non-namespace > specific metrics on top and then a selector for namespace specific metrics > below. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23301) Add Service wizards succesfully completes with warning
[ https://issues.apache.org/jira/browse/AMBARI-23301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23301: - Status: Patch Available (was: Open) > Add Service wizards succesfully completes with warning > -- > > Key: AMBARI-23301 > URL: https://issues.apache.org/jira/browse/AMBARI-23301 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-03-18 at 4.05.31 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23304) Add namespace-specific layout for HDFS metrics
Aleksandr Kovalenko created AMBARI-23304: Summary: Add namespace-specific layout for HDFS metrics Key: AMBARI-23304 URL: https://issues.apache.org/jira/browse/AMBARI-23304 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 The layout of HDFS metrics section should look like as follows: non-namespace specific metrics on top and then a selector for namespace specific metrics below. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23303) Use NameNode Upgrade Timeout Override In All Upgrade Packs
[ https://issues.apache.org/jira/browse/AMBARI-23303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23303: Labels: pull-request-available (was: ) > Use NameNode Upgrade Timeout Override In All Upgrade Packs > -- > > Key: AMBARI-23303 > URL: https://issues.apache.org/jira/browse/AMBARI-23303 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > > The upgrade timeout parameter for NameNode restarts is only defined in > rolling upgrade packs. It should be used in all upgrade packs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23303) Use NameNode Upgrade Timeout Override In All Upgrade Packs
Jonathan Hurley created AMBARI-23303: Summary: Use NameNode Upgrade Timeout Override In All Upgrade Packs Key: AMBARI-23303 URL: https://issues.apache.org/jira/browse/AMBARI-23303 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Fix For: 2.7.0 The upgrade timeout parameter for NameNode restarts is only defined in rolling upgrade packs. It should be used in all upgrade packs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23213) Enable or disable SSO using Ambari CLI with options
[
https://issues.apache.org/jira/browse/AMBARI-23213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated AMBARI-23213:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Enable or disable SSO using Ambari CLI with options
> ---
>
> Key: AMBARI-23213
> URL: https://issues.apache.org/jira/browse/AMBARI-23213
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: SSO, pull-request-available, security
> Fix For: 2.7.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> To enable or disable SSO using the Ambari CLI, the user needs to answer each
> prompt. This is not convenient for automated tools. So the following command
> line options should be available for use. If any mandatory option is not
> specified via the command line, the user should be prompted for a value.
> Global SSO options:
> * {{--sso-enabled}}
> if {{sso-enabled}} is "true":
> * {{--sso-provider-url}}
> * {{--sso-public-cert-file}}
> * {{--sso-jwt-cookie-name}}
> ** optional, if not supplied, the documented default value will be used
> * {{--sso-jwt-audience-list}}
> ** optional, if not supplied, the documented default value will be used
> {noformat:title=Examples}
> ambari-server setup-sso --help
> ambari-server setup-sso --sso-enabled=true
> --sso-provider-url=https://knox.ambari.apache.org:8443
> --sso-public-cert-file=/tmp/sso.pem
> ambari-server setup-sso --sso-enabled=true
> --sso-provider-url=https://knox.ambari.apache.org:8443
> --sso-public-cert-file=/tmp/sso.pem --sso-jwt-cookie-name=ambari-jtw
> ambari-server setup-sso --sso-enabled=true
> --sso-provider-url=https://knox.ambari.apache.org:8443
> --sso-public-cert-file=/tmp/sso.pem --sso-jwt-cookie-name=ambari-jtw
> --sso-jwt-audience-list=ambari
> ambari-server setup-sso --sso-enabled=true
> --sso-provider-url=https://knox.ambari.apache.org:8443
> --sso-public-cert-file=/tmp/sso.pem
> ambari-server setup-sso --sso-enabled=false
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23302) Ambari Upgrade from 2.6.0.0 - 2.7.0.0 - Dashboard is unable to load and spinner keeps spinning
[ https://issues.apache.org/jira/browse/AMBARI-23302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23302: Labels: pull-request-available (was: ) > Ambari Upgrade from 2.6.0.0 - 2.7.0.0 - Dashboard is unable to load and > spinner keeps spinning > -- > > Key: AMBARI-23302 > URL: https://issues.apache.org/jira/browse/AMBARI-23302 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > > After Ambari Upgrade from 2.6.0.0 to 2.7.0.0 , the Ambari UI Dashboard is > unable to load. Spinner keeps spinning, > Seems like Wizard-Data API calls are returning null and not being handled > properly on the UI. Ideally, the dashboard should be shown with widgets with > No data (if AMS is down) > Additional Information: > Adding few more observed issues. These might be related to the originally > raised issue. > # Quick Links are not shown for services. Spinner keeps spinning. > # Component information is not shown for some services. e.g. Oozie. > # For HDFS, YARN -> DataNodes, NodeManagers keep showing Loading and never > loads. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23302) Ambari Upgrade from 2.6.0.0 - 2.7.0.0 - Dashboard is unable to load and spinner keeps spinning
[ https://issues.apache.org/jira/browse/AMBARI-23302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-23302: -- Description: After Ambari Upgrade from 2.6.0.0 to 2.7.0.0 , the Ambari UI Dashboard is unable to load. Spinner keeps spinning, Seems like Wizard-Data API calls are returning null and not being handled properly on the UI. Ideally, the dashboard should be shown with widgets with No data (if AMS is down) Additional Information: Adding few more observed issues. These might be related to the originally raised issue. # Quick Links are not shown for services. Spinner keeps spinning. # Component information is not shown for some services. e.g. Oozie. # For HDFS, YARN -> DataNodes, NodeManagers keep showing Loading and never loads. was: After Ambari Upgrade from 2.6.0.0 to 2.7.0.0 , the Ambari UI Dashboard is unable to load. Spinner keeps spinning, Seems like Wizard-Data API calls are returning null and not being handled properly on the UI. Ideally, the dashboard should be shown with widgets with No data (if AMS is down) Additional Information: Adding few more observed issues. These might be related to the originally raised issue. 1) Quick Links are not shown for services. Spinner keeps spinning. 2) Component information is not shown for some services. e.g. Oozie. 3) For HDFS, YARN -> DataNodes, NodeManagers keep showing Loading and never loads. > Ambari Upgrade from 2.6.0.0 - 2.7.0.0 - Dashboard is unable to load and > spinner keeps spinning > -- > > Key: AMBARI-23302 > URL: https://issues.apache.org/jira/browse/AMBARI-23302 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Fix For: 2.7.0 > > > After Ambari Upgrade from 2.6.0.0 to 2.7.0.0 , the Ambari UI Dashboard is > unable to load. Spinner keeps spinning, > Seems like Wizard-Data API calls are returning null and not being handled > properly on the UI. Ideally, the dashboard should be shown with widgets with > No data (if AMS is down) > Additional Information: > Adding few more observed issues. These might be related to the originally > raised issue. > # Quick Links are not shown for services. Spinner keeps spinning. > # Component information is not shown for some services. e.g. Oozie. > # For HDFS, YARN -> DataNodes, NodeManagers keep showing Loading and never > loads. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23302) Ambari Upgrade from 2.6.0.0 - 2.7.0.0 - Dashboard is unable to load and spinner keeps spinning
Andrii Babiichuk created AMBARI-23302: - Summary: Ambari Upgrade from 2.6.0.0 - 2.7.0.0 - Dashboard is unable to load and spinner keeps spinning Key: AMBARI-23302 URL: https://issues.apache.org/jira/browse/AMBARI-23302 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 2.7.0 After Ambari Upgrade from 2.6.0.0 to 2.7.0.0 , the Ambari UI Dashboard is unable to load. Spinner keeps spinning, Seems like Wizard-Data API calls are returning null and not being handled properly on the UI. Ideally, the dashboard should be shown with widgets with No data (if AMS is down) Additional Information: Adding few more observed issues. These might be related to the originally raised issue. 1) Quick Links are not shown for services. Spinner keeps spinning. 2) Component information is not shown for some services. e.g. Oozie. 3) For HDFS, YARN -> DataNodes, NodeManagers keep showing Loading and never loads. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23301) Add Service wizards succesfully completes with warning
[ https://issues.apache.org/jira/browse/AMBARI-23301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23301: Labels: pull-request-available (was: ) > Add Service wizards succesfully completes with warning > -- > > Key: AMBARI-23301 > URL: https://issues.apache.org/jira/browse/AMBARI-23301 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-03-18 at 4.05.31 PM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23165) Install Wizard/Customise Services - Clear Filters is not working
[ https://issues.apache.org/jira/browse/AMBARI-23165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23165: - Attachment: Screen Shot 2018-03-18 at 4.05.31 PM.png > Install Wizard/Customise Services - Clear Filters is not working > > > Key: AMBARI-23165 > URL: https://issues.apache.org/jira/browse/AMBARI-23165 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23301) Add Service wizards succesfully completes with warning
[ https://issues.apache.org/jira/browse/AMBARI-23301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23301: - Attachment: Screen Shot 2018-03-18 at 4.05.31 PM.png > Add Service wizards succesfully completes with warning > -- > > Key: AMBARI-23301 > URL: https://issues.apache.org/jira/browse/AMBARI-23301 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-03-18 at 4.05.31 PM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23165) Install Wizard/Customise Services - Clear Filters is not working
[ https://issues.apache.org/jira/browse/AMBARI-23165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23165: - Attachment: (was: Screen Shot 2018-03-18 at 4.05.31 PM.png) > Install Wizard/Customise Services - Clear Filters is not working > > > Key: AMBARI-23165 > URL: https://issues.apache.org/jira/browse/AMBARI-23165 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23301) Add Service wizards succesfully completes with warning
[ https://issues.apache.org/jira/browse/AMBARI-23301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23301: Assignee: Antonenko Alexander > Add Service wizards succesfully completes with warning > -- > > Key: AMBARI-23301 > URL: https://issues.apache.org/jira/browse/AMBARI-23301 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23301) Add Service wizards succesfully completes with warning
Antonenko Alexander created AMBARI-23301: Summary: Add Service wizards succesfully completes with warning Key: AMBARI-23301 URL: https://issues.apache.org/jira/browse/AMBARI-23301 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-21008) Integrate AlertTargetService and subresources with swagger
[ https://issues.apache.org/jira/browse/AMBARI-21008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406333#comment-16406333 ] Hudson commented on AMBARI-21008: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8882 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8882/]) AMBARI-21008. Integrate AlertTargetService and subresources with swagger (6454655+adoroszlai: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=ee0784a9b3393eb0c76f0ce0bd7ed4ea775864df]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertTarget.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertGroupResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/AlertTargetService.java * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/AlertTargetSwagger.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java > Integrate AlertTargetService and subresources with swagger > -- > > Key: AMBARI-21008 > URL: https://issues.apache.org/jira/browse/AMBARI-21008 > Project: Ambari > Issue Type: Task >Reporter: Balázs Bence Sári >Assignee: Gabor Boros >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 2h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23300) Install Wizard/Customise Services clear filters button is not visible while input is focused
[ https://issues.apache.org/jira/browse/AMBARI-23300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23300: - Status: Patch Available (was: Open) > Install Wizard/Customise Services clear filters button is not visible while > input is focused > > > Key: AMBARI-23300 > URL: https://issues.apache.org/jira/browse/AMBARI-23300 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23300) Install Wizard/Customise Services clear filters button is not visible while input is focused
[ https://issues.apache.org/jira/browse/AMBARI-23300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23300: Labels: pull-request-available (was: ) > Install Wizard/Customise Services clear filters button is not visible while > input is focused > > > Key: AMBARI-23300 > URL: https://issues.apache.org/jira/browse/AMBARI-23300 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23300) Install Wizard/Customise Services clear filters button is not visible while input is focused
Antonenko Alexander created AMBARI-23300: Summary: Install Wizard/Customise Services clear filters button is not visible while input is focused Key: AMBARI-23300 URL: https://issues.apache.org/jira/browse/AMBARI-23300 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23300) Install Wizard/Customise Services clear filters button is not visible while input is focused
[ https://issues.apache.org/jira/browse/AMBARI-23300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23300: Assignee: Antonenko Alexander > Install Wizard/Customise Services clear filters button is not visible while > input is focused > > > Key: AMBARI-23300 > URL: https://issues.apache.org/jira/browse/AMBARI-23300 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23299) Intermittent failure in TestAgentStompResponses
Doroszlai, Attila created AMBARI-23299:
--
Summary: Intermittent failure in TestAgentStompResponses
Key: AMBARI-23299
URL: https://issues.apache.org/jira/browse/AMBARI-23299
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.7.0
Reporter: Doroszlai, Attila
Fix For: 2.7.0
Intermittent unit test failure, probably due to use of threads:
{noformat}
FAIL: test_alert_definitions_update_and_delete
(TestAgentStompResponses.TestAgentStompResponses)
...
-u'uuid':
u'69ff4c8f-8e98-4cfd-b90f-6914e2f147ff'}],
?
-
+u'uuid':
u'69ff4c8f-8e98-4cfd-b90f-6914e2f147ff'},
+ {u'clusterId': 2,
+u'componentName': u'HBASE_MASTER',
+u'definitionId': 1,
+u'description': u'This alert is triggered if
the HBase master processes cannot be confirmed to be up and listening on the
network for the configured critical threshold, given in seconds.',
+u'enabled': True,
+u'ignore_host': False,
+u'interval': 1,
+u'label': u'HBase Master Process',
+u'name': u'hbase_master_process',
+u'scope': u'ANY',
+u'serviceName': u'HBASE',
+u'source': {u'default_port': 6,
+u'reporting': {u'critical':
{u'text': u'Connection failed: {0} to {1}:{2}',
+
u'value': 5.0},
+ u'ok': {u'text':
u'TCP OK - {0:.3f}s response on port {1}'},
+ u'warning':
{u'text': u'TCP OK - {0:.3f}s response on port {1}',
+
u'value': 1.5}},
+u'type': u'PORT',
+u'uri':
u'{{hbase-site/hbase.master.port}}'},
+u'uuid':
u'ff73ead7-13b4-43ea-a747-d230f17bf230'}],
u'clusterName': u'cl1',
...
{noformat}
https://builds.apache.org/job/Ambari-trunk-Commit/8872/
https://builds.apache.org/job/Ambari-trunk-Commit/8863/
https://builds.apache.org/job/Ambari-trunk-Commit/8862/
https://builds.apache.org/job/Ambari-trunk-Commit/8858/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23298) Pass full stack version in recommendation request for 2.7
[ https://issues.apache.org/jira/browse/AMBARI-23298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23298: Labels: pull-request-available (was: ) > Pass full stack version in recommendation request for 2.7 > - > > Key: AMBARI-23298 > URL: https://issues.apache.org/jira/browse/AMBARI-23298 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23298) Pass full stack version in recommendation request for 2.7
[ https://issues.apache.org/jira/browse/AMBARI-23298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23298: Assignee: Antonenko Alexander > Pass full stack version in recommendation request for 2.7 > - > > Key: AMBARI-23298 > URL: https://issues.apache.org/jira/browse/AMBARI-23298 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23297) Pass full stack version in recommendation request for 2.7
[ https://issues.apache.org/jira/browse/AMBARI-23297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-23297. -- Resolution: Fixed Assignee: Antonenko Alexander AMBARI-23298 > Pass full stack version in recommendation request for 2.7 > - > > Key: AMBARI-23297 > URL: https://issues.apache.org/jira/browse/AMBARI-23297 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23298) Pass full stack version in recommendation request for 2.7
Antonenko Alexander created AMBARI-23298: Summary: Pass full stack version in recommendation request for 2.7 Key: AMBARI-23298 URL: https://issues.apache.org/jira/browse/AMBARI-23298 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23297) Pass full stack version in recommendation request for 2.7
Antonenko Alexander created AMBARI-23297: Summary: Pass full stack version in recommendation request for 2.7 Key: AMBARI-23297 URL: https://issues.apache.org/jira/browse/AMBARI-23297 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23283) Install Wizard > Select Version page: the user cannot proceed with Redhat Satellite option
[ https://issues.apache.org/jira/browse/AMBARI-23283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23283: Labels: pull-request-available (was: ) > Install Wizard > Select Version page: the user cannot proceed with Redhat > Satellite option > -- > > Key: AMBARI-23283 > URL: https://issues.apache.org/jira/browse/AMBARI-23283 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.2, 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Labels: pull-request-available > Fix For: 2.6.2, 2.7.0 > > > STR: > * Launch Install Wizard > * On Select Version page, select "Use Local Repository" and then "Use RedHat > Satellite/Spacewalk" > * The Next button is disabled. The Next button must be enabled in this > scenario. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23296) Python UT failure
[ https://issues.apache.org/jira/browse/AMBARI-23296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23296: - Status: Patch Available (was: Open) > Python UT failure > - > > Key: AMBARI-23296 > URL: https://issues.apache.org/jira/browse/AMBARI-23296 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23296.patch > > > ERROR: test_get_service_base_dir (TestFileCache.TestFileCache) > -- > ERROR 2018-03-20 06:58:54,744 - Python unit tests failed > Traceback (most recent call last): > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-common/src/test/python/mock/mock.py", > line 1199, in patched > return func(*args, **keywargs) > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/test/python/ambari_agent/TestFileCache.py", > line 72, in test_get_service_base_dir > res = fileCache.get_service_base_dir(command, "server_url_pref") > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/main/python/ambari_agent/FileCache.py", > line 77, in get_service_base_dir > if 'service_package_folder' in command['commandParams']: > KeyError: 'commandParams' > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23296) Python UT failure
[ https://issues.apache.org/jira/browse/AMBARI-23296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23296: Labels: pull-request-available (was: ) > Python UT failure > - > > Key: AMBARI-23296 > URL: https://issues.apache.org/jira/browse/AMBARI-23296 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23296.patch > > > ERROR: test_get_service_base_dir (TestFileCache.TestFileCache) > -- > ERROR 2018-03-20 06:58:54,744 - Python unit tests failed > Traceback (most recent call last): > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-common/src/test/python/mock/mock.py", > line 1199, in patched > return func(*args, **keywargs) > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/test/python/ambari_agent/TestFileCache.py", > line 72, in test_get_service_base_dir > res = fileCache.get_service_base_dir(command, "server_url_pref") > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/main/python/ambari_agent/FileCache.py", > line 77, in get_service_base_dir > if 'service_package_folder' in command['commandParams']: > KeyError: 'commandParams' > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23296) Python UT failure
Andrew Onischuk created AMBARI-23296: Summary: Python UT failure Key: AMBARI-23296 URL: https://issues.apache.org/jira/browse/AMBARI-23296 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.0 Attachments: AMBARI-23296.patch ERROR: test_get_service_base_dir (TestFileCache.TestFileCache) -- ERROR 2018-03-20 06:58:54,744 - Python unit tests failed Traceback (most recent call last): File "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-common/src/test/python/mock/mock.py", line 1199, in patched return func(*args, **keywargs) File "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/test/python/ambari_agent/TestFileCache.py", line 72, in test_get_service_base_dir res = fileCache.get_service_base_dir(command, "server_url_pref") File "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/main/python/ambari_agent/FileCache.py", line 77, in get_service_base_dir if 'service_package_folder' in command['commandParams']: KeyError: 'commandParams' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23295) Python UT failure
Andrew Onischuk created AMBARI-23295: Summary: Python UT failure Key: AMBARI-23295 URL: https://issues.apache.org/jira/browse/AMBARI-23295 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.0 ERROR: test_get_service_base_dir (TestFileCache.TestFileCache) -- ERROR 2018-03-20 06:58:54,744 - Python unit tests failed Traceback (most recent call last): File "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-common/src/test/python/mock/mock.py", line 1199, in patched return func(*args, **keywargs) File "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/test/python/ambari_agent/TestFileCache.py", line 72, in test_get_service_base_dir res = fileCache.get_service_base_dir(command, "server_url_pref") File "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/main/python/ambari_agent/FileCache.py", line 77, in get_service_base_dir if 'service_package_folder' in command['commandParams']: KeyError: 'commandParams' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23296) Python UT failure
[ https://issues.apache.org/jira/browse/AMBARI-23296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23296: - Attachment: AMBARI-23296.patch > Python UT failure > - > > Key: AMBARI-23296 > URL: https://issues.apache.org/jira/browse/AMBARI-23296 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23296.patch > > > ERROR: test_get_service_base_dir (TestFileCache.TestFileCache) > -- > ERROR 2018-03-20 06:58:54,744 - Python unit tests failed > Traceback (most recent call last): > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-common/src/test/python/mock/mock.py", > line 1199, in patched > return func(*args, **keywargs) > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/test/python/ambari_agent/TestFileCache.py", > line 72, in test_get_service_base_dir > res = fileCache.get_service_base_dir(command, "server_url_pref") > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/main/python/ambari_agent/FileCache.py", > line 77, in get_service_base_dir > if 'service_package_folder' in command['commandParams']: > KeyError: 'commandParams' > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22625) Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different
[ https://issues.apache.org/jira/browse/AMBARI-22625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-22625: -- Resolution: Fixed Status: Resolved (was: Patch Available) resolved as part of : AMBARI-23271 > Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different > --- > > Key: AMBARI-22625 > URL: https://issues.apache.org/jira/browse/AMBARI-22625 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Minor > Labels: pull-request-available > Fix For: 3.0.0 > > Attachments: AMBARI-22625-trunk.patch, ambari-2.png, namenode.png > > Time Spent: 40m > Remaining Estimate: 0h > > 'NON DFS Used' value in Services -> HDFS -> Summary if different from the > Value shown in NameNode UI (see Picture). > in NAMENODE UI --> > !https://issues.apache.org/jira/secure/attachment/12901501/namenode.png! > In Services -> HDFS -> Summary > !https://issues.apache.org/jira/secure/attachment/12901499/ambari-2.png! > In NameNode UI the Non DFS Used is taken from 'NonDfsUsedSpace' variable from > REST API call : > http://host1:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeInfo > Where host1 is the Name Node Server FQDN > but in Ambari we are calculating the same value from (Total Allocated - DFS > USed - DFS Remaining) . > due to which this issue is happening. > as a Fix we need to use the 'capacityNonDfsUsed' which comes from Server in > NameNode metrics > 'FSNamesystem > CapacityNonDFSUsed' > attached the patch in the JIRA. > Please fix this bug -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22625) Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different
[ https://issues.apache.org/jira/browse/AMBARI-22625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik reassigned AMBARI-22625: - Assignee: Akhil S Naik > Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different > --- > > Key: AMBARI-22625 > URL: https://issues.apache.org/jira/browse/AMBARI-22625 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Minor > Labels: pull-request-available > Fix For: 3.0.0 > > Attachments: AMBARI-22625-trunk.patch, ambari-2.png, namenode.png > > Time Spent: 20m > Remaining Estimate: 0h > > 'NON DFS Used' value in Services -> HDFS -> Summary if different from the > Value shown in NameNode UI (see Picture). > in NAMENODE UI --> > !https://issues.apache.org/jira/secure/attachment/12901501/namenode.png! > In Services -> HDFS -> Summary > !https://issues.apache.org/jira/secure/attachment/12901499/ambari-2.png! > In NameNode UI the Non DFS Used is taken from 'NonDfsUsedSpace' variable from > REST API call : > http://host1:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeInfo > Where host1 is the Name Node Server FQDN > but in Ambari we are calculating the same value from (Total Allocated - DFS > USed - DFS Remaining) . > due to which this issue is happening. > as a Fix we need to use the 'capacityNonDfsUsed' which comes from Server in > NameNode metrics > 'FSNamesystem > CapacityNonDFSUsed' > attached the patch in the JIRA. > Please fix this bug -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23294) Ambari Files view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone
[ https://issues.apache.org/jira/browse/AMBARI-23294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-23294: --- Status: Patch Available (was: Open) > Ambari Files view throws 500 ERROR while trying to upload/download to/from > HDFS encrypted zone > -- > > Key: AMBARI-23294 > URL: https://issues.apache.org/jira/browse/AMBARI-23294 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.6.2 > > Time Spent: 20m > Remaining Estimate: 0h > > The problem is that the error does not show up properly on UI. > So it becomes difficult to understand. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23258) Ambari-agent logs are messy/hard to read
[ https://issues.apache.org/jira/browse/AMBARI-23258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23258: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Ambari-agent logs are messy/hard to read > > > Key: AMBARI-23258 > URL: https://issues.apache.org/jira/browse/AMBARI-23258 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23258.patch, AMBARI-23258.patch > > Time Spent: 2h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23257) Address stack changes to create apps and user directories on nameservices
[ https://issues.apache.org/jira/browse/AMBARI-23257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23257: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Address stack changes to create apps and user directories on nameservices > - > > Key: AMBARI-23257 > URL: https://issues.apache.org/jira/browse/AMBARI-23257 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23257.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23294) Ambari Files view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone
[ https://issues.apache.org/jira/browse/AMBARI-23294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23294: Labels: pull-request-available (was: ) > Ambari Files view throws 500 ERROR while trying to upload/download to/from > HDFS encrypted zone > -- > > Key: AMBARI-23294 > URL: https://issues.apache.org/jira/browse/AMBARI-23294 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.6.2 > > > The problem is that the error does not show up properly on UI. > So it becomes difficult to understand. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23294) Ambari Files view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone
[ https://issues.apache.org/jira/browse/AMBARI-23294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-23294: --- Summary: Ambari Files view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone (was: Ambari view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone) > Ambari Files view throws 500 ERROR while trying to upload/download to/from > HDFS encrypted zone > -- > > Key: AMBARI-23294 > URL: https://issues.apache.org/jira/browse/AMBARI-23294 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Fix For: trunk, 2.6.2 > > > The problem is that the error does not show up properly on UI. > So it becomes difficult to understand. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23294) Ambari view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone
Nitiraj Singh Rathore created AMBARI-23294: -- Summary: Ambari view throws 500 ERROR while trying to upload/download to/from HDFS encrypted zone Key: AMBARI-23294 URL: https://issues.apache.org/jira/browse/AMBARI-23294 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.1 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: trunk, 2.6.2 The problem is that the error does not show up properly on UI. So it becomes difficult to understand. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22711) Ambari Versions Page is having JS error When using redhat satellite server for repos
[ https://issues.apache.org/jira/browse/AMBARI-22711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22711: Labels: pull-request-available (was: ) > Ambari Versions Page is having JS error When using redhat satellite server > for repos > -- > > Key: AMBARI-22711 > URL: https://issues.apache.org/jira/browse/AMBARI-22711 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 > Environment: upgraded ambari Server from 2.4.2 to 2.5.2 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Attachments: AMBARI-22711.patch, Ambari_versions_page.png > > > Ambari Versions page not updating when using Redhat satellite server for repos > Versions page was showing up like below > !https://issues.apache.org/jira/secure/attachment/12904190/Ambari_versions_page.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-22711) Ambari Versions Page is having JS error When using redhat satellite server for repos
[ https://issues.apache.org/jira/browse/AMBARI-22711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307815#comment-16307815 ] Akhil S Naik edited comment on AMBARI-22711 at 3/20/18 7:10 AM: This issue is due to a Exception in JS code . This issue is similar to one Fix of AMBARI-21233 And the Fix is similar to commit : https://github.com/apache/ambari/commit/f80c6ee45b5c6708aa9db98b9afe7ebbeba2afe7#diff-54dfff5dc7cb7e0a058e60f9a27bd47d Where we need to remove the direct check of property and use the Ember Metal Em.get instead. attached the patch, Please review. was (Author: akhilsnaik): This issue is due to a Exception in JS code . This issue is similar to one Fix of AMBARI-21233[https://issues.apache.org/jira/browse/AMBARI-21233] And the Fix is similar to commit : https://github.com/apache/ambari/commit/f80c6ee45b5c6708aa9db98b9afe7ebbeba2afe7#diff-54dfff5dc7cb7e0a058e60f9a27bd47d Where we need to remove the direct check of property and use the Ember Metal Em.get instead. attached the patch, Please review. > Ambari Versions Page is having JS error When using redhat satellite server > for repos > -- > > Key: AMBARI-22711 > URL: https://issues.apache.org/jira/browse/AMBARI-22711 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 > Environment: upgraded ambari Server from 2.4.2 to 2.5.2 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22711.patch, Ambari_versions_page.png > > > Ambari Versions page not updating when using Redhat satellite server for repos > Versions page was showing up like below > !https://issues.apache.org/jira/secure/attachment/12904190/Ambari_versions_page.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22711) Ambari Versions Page is having JS error When using redhat satellite server for repos
[ https://issues.apache.org/jira/browse/AMBARI-22711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik reassigned AMBARI-22711: - Assignee: Akhil S Naik > Ambari Versions Page is having JS error When using redhat satellite server > for repos > -- > > Key: AMBARI-22711 > URL: https://issues.apache.org/jira/browse/AMBARI-22711 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 > Environment: upgraded ambari Server from 2.4.2 to 2.5.2 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22711.patch, Ambari_versions_page.png > > > Ambari Versions page not updating when using Redhat satellite server for repos > Versions page was showing up like below > !https://issues.apache.org/jira/secure/attachment/12904190/Ambari_versions_page.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
