[jira] [Updated] (AMBARI-22803) Update Hadoop RPC Encryption Properties During Kerberization
[
https://issues.apache.org/jira/browse/AMBARI-22803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated AMBARI-22803:
---
Description:
When *HDP 3.0.0* is installed, clients should have the ability to choose
encrypted communication over RPC when talking to core hadoop components. Today,
the properties that control this are:
- {{core-site.xml : hadoop.rpc.protection = authentication}}
- {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
The new value of {{privacy}} enables clients to choose an encrypted means of
communication. By keeping {{authentication}} first, it will be taken as the
default mechanism so that wire encryption is not automatically enabled by
accident.
The following properties should be changed to add {{privacy}}:
- {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
- {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
The following are cases when this needs to be performed:
- During Kerberization, the above two properties should be automatically
reconfigured.
- During a stack upgrade to any version of *HDP 3.0.0* is covered by
AMBARI-22981
Blueprint deployment is not a scenario being covered here.
was:
When *HDP 3.0.0* is installed, clients should have the ability to choose
encrypted communication over RPC when talking to core hadoop components. Today,
the properties that control this are:
- {{core-site.xml : hadoop.rpc.protection = authentication}}
- {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
The new value of {{privacy}} enables clients to choose an encrypted means of
communication. By keeping {{authentication}} first, it will be taken as the
default mechanism so that wire encryption is not automatically enabled by
accident.
The following properties should be changed to add {{privacy}}:
- {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
- {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
The following are cases when this needs to be performed:
- During Kerberization, the above two properties should be automatically
reconfigured.
- During a stack upgrade to any version of *HDP 3.0.0*, they should be
automatically merged
Blueprint deployment is not a scenario being covered here.
> Update Hadoop RPC Encryption Properties During Kerberization
>
>
> Key: AMBARI-22803
> URL: https://issues.apache.org/jira/browse/AMBARI-22803
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Jonathan Hurley
>Assignee: Sandor Molnar
>Priority: Critical
> Fix For: 2.7.0
>
> Attachments: AMBARI-22803.patch
>
>
> When *HDP 3.0.0* is installed, clients should have the ability to choose
> encrypted communication over RPC when talking to core hadoop components.
> Today, the properties that control this are:
> - {{core-site.xml : hadoop.rpc.protection = authentication}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
> The new value of {{privacy}} enables clients to choose an encrypted means of
> communication. By keeping {{authentication}} first, it will be taken as the
> default mechanism so that wire encryption is not automatically enabled by
> accident.
> The following properties should be changed to add {{privacy}}:
> - {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
> The following are cases when this needs to be performed:
> - During Kerberization, the above two properties should be automatically
> reconfigured.
> - During a stack upgrade to any version of *HDP 3.0.0* is covered by
> AMBARI-22981
> Blueprint deployment is not a scenario being covered here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22803) Update Hadoop RPC Encryption Properties During Kerberization
[
https://issues.apache.org/jira/browse/AMBARI-22803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated AMBARI-22803:
---
Summary: Update Hadoop RPC Encryption Properties During Kerberization
(was: Update Hadoop RPC Encryption Properties During Kerberization and Upgrade)
> Update Hadoop RPC Encryption Properties During Kerberization
>
>
> Key: AMBARI-22803
> URL: https://issues.apache.org/jira/browse/AMBARI-22803
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Jonathan Hurley
>Assignee: Sandor Molnar
>Priority: Critical
> Fix For: 2.7.0
>
> Attachments: AMBARI-22803.patch
>
>
> When *HDP 3.0.0* is installed, clients should have the ability to choose
> encrypted communication over RPC when talking to core hadoop components.
> Today, the properties that control this are:
> - {{core-site.xml : hadoop.rpc.protection = authentication}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
> The new value of {{privacy}} enables clients to choose an encrypted means of
> communication. By keeping {{authentication}} first, it will be taken as the
> default mechanism so that wire encryption is not automatically enabled by
> accident.
> The following properties should be changed to add {{privacy}}:
> - {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
> The following are cases when this needs to be performed:
> - During Kerberization, the above two properties should be automatically
> reconfigured.
> - During a stack upgrade to any version of *HDP 3.0.0*, they should be
> automatically merged
> Blueprint deployment is not a scenario being covered here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22981) Update Hadoop RPC Encryption Properties During Upgrade
Sandor Molnar created AMBARI-22981:
--
Summary: Update Hadoop RPC Encryption Properties During Upgrade
Key: AMBARI-22981
URL: https://issues.apache.org/jira/browse/AMBARI-22981
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.7.0
When *HDP 3.0.0* is installed, clients should have the ability to choose
encrypted communication over RPC when talking to core hadoop components. Today,
the properties that control this are:
- {{core-site.xml : hadoop.rpc.protection = authentication}}
- {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
The new value of {{privacy}} enables clients to choose an encrypted means of
communication. By keeping {{authentication}} first, it will be taken as the
default mechanism so that wire encryption is not automatically enabled by
accident.
The following properties should be changed to add {{privacy}}:
- {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
- {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
The following are cases when this needs to be performed:
- During Kerberization, the above two properties should be automatically
reconfigured.
- During a stack upgrade to any version of *HDP 3.0.0*, they should be
automatically merged
Blueprint deployment is not a scenario being covered here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22980) Update Resource Management Library with helper libraries for handling the new layout
[ https://issues.apache.org/jira/browse/AMBARI-22980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22980: Labels: pull-request-available (was: ) > Update Resource Management Library with helper libraries for handling the new > layout > > > Key: AMBARI-22980 > URL: https://issues.apache.org/jira/browse/AMBARI-22980 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22980) Update Resource Management Library with helper libraries for handling the new layout
Madhuvanthi Radhakrishnan created AMBARI-22980: -- Summary: Update Resource Management Library with helper libraries for handling the new layout Key: AMBARI-22980 URL: https://issues.apache.org/jira/browse/AMBARI-22980 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Madhuvanthi Radhakrishnan Assignee: Dmytro Sen Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22925) Mpack/service group admin screen
[ https://issues.apache.org/jira/browse/AMBARI-22925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22925: Labels: pull-request-available (was: ) > Mpack/service group admin screen > > > Key: AMBARI-22925 > URL: https://issues.apache.org/jira/browse/AMBARI-22925 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jason Golieb >Assignee: Jason Golieb >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > Create Management Pack admin screen accessible from main menu. This will show > information about currently installed mpacks and is the entry point for > upgrading mpacks and performing other mpack related administrative actions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22977) NullPointerException in KerberosHelperImpl.addIdentities
[
https://issues.apache.org/jira/browse/AMBARI-22977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363059#comment-16363059
]
Hudson commented on AMBARI-22977:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8723 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8723/])
AMBARI-22977. NullPointerException in KerberosHelperImpl.addIdentities
(m.magyar3:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=4243e3367df2c9826bc94b8584ec0f12d6f6c4be])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
> NullPointerException in KerberosHelperImpl.addIdentities
>
>
> Key: AMBARI-22977
> URL: https://issues.apache.org/jira/browse/AMBARI-22977
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> If a group name or group access is missing from a kerberos descriptor ambari
> will throw an NPE during enable kerberos
> {code:java}
> 13 Feb 2018 11:27:37,466 WARN [Server Action Executor Worker 39]
> ServerActionExecutor:471 - Task #39 failed to complete execution due to
> thrown exception: java.lang.NullPointerException:null
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.addIdentities(KerberosHelperImpl.java:1601)
> at
> org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponents(AbstractPrepareKerberosServerAction.java:177)
> at
> org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponentHosts(AbstractPrepareKerberosServerAction.java:87)
> at
> org.apache.ambari.server.serveraction.kerberos.PrepareKerberosIdentitiesServerAction.execute(PrepareKerberosIdentitiesServerAction.java:128)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:748){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-20840) Upgrade phantomjs to 2.1.1
[ https://issues.apache.org/jira/browse/AMBARI-20840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363034#comment-16363034 ] Ed Vielmetti commented on AMBARI-20840: --- I would very much like to see this happen. > Upgrade phantomjs to 2.1.1 > -- > > Key: AMBARI-20840 > URL: https://issues.apache.org/jira/browse/AMBARI-20840 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin >Reporter: Jun He >Priority: Major > > PhantomJS is used in ambari-admin ambari-web. The current version is 1.9.8 > which runs only on x86. Support for other archs (ppc/arm) are introduced in > 2.1.1. > Upgrade phantomjs in upstream will enable Ambari on those non-x86 platforms. > And that will help to improve Ambari on compatibility, acceptance, gain more > focus and effort/contributions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22918) Decommission RegionServer fails when kerberos is enabled
[
https://issues.apache.org/jira/browse/AMBARI-22918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362976#comment-16362976
]
Hudson commented on AMBARI-22918:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8722 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8722/])
AMBARI-22918 Decommission RegionServer fails when kerberos is enabled (swagle:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=fd46cc507d93a7f069df523997c16f7336b45302])
* (edit)
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_decommission.py
> Decommission RegionServer fails when kerberos is enabled
>
>
> Key: AMBARI-22918
> URL: https://issues.apache.org/jira/browse/AMBARI-22918
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Toshihiro Suzuki
>Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> When kerberos is enabled, Decommission RegionServer fails with the following
> errors:
> stderr:
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 114, in
> HbaseMaster().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 55, in decommission
> hbase_decommission(env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_decommission.py",
> line 84, in hbase_decommission
> logoutput=True
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 166, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/hbase.service.keytab
> hbase/mast...@example.com; /usr/hdp/current/hbase-master/bin/hbase --config
> /usr/hdp/current/hbase-master/conf
> -Djava.security.auth.login.config=/usr/hdp/current/hbase-master/conf/hbase_master_jaas.conf
> org.jruby.Main /usr/hdp/current/hbase-master/bin/draining_servers.rb add
> worker1' returned 1. Error: Could not find or load main class
> org.jruby.Main{code}
> stdout:
> {code:java}
> 2018-02-06 07:25:03,453 - Stack Feature Version Info: Cluster Stack=2.6,
> Cluster Current Version=2.6.2.0-205, Command Stack=None, Command
> Version=2.6.2.0-205 -> 2.6.2.0-205
> 2018-02-06 07:25:03,476 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2018-02-06 07:25:03,484 - checked_call['hostid'] {}
> 2018-02-06 07:25:03,490 - checked_call returned (0, '1aacc56c')
> 2018-02-06 07:25:03,502 -
> File['/usr/hdp/current/hbase-master/bin/draining_servers.rb'] {'content':
> StaticFile('draining_servers.rb'), 'mode': 0755}
> 2018-02-06 07:25:03,504 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab hbase/mast...@example.com;
> /usr/hdp/current/hbase-master/bin/hbase --config
> /usr/hdp/current/hbase-master/conf
> -Djava.security.auth.login.config=/usr/hdp/current/hbase-master/conf/hbase_master_jaas.conf
> org.jruby.Main /usr/hdp/current/hbase-master/bin/draining_servers.rb add
> worker1'] {'logoutput': True, 'user': 'hbase'}
> Error: Could not find or load main class org.jruby.Main
> Command failed after 1 tries{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22891) Logging improvement during the Upgrade when there is invalid Alert definition
[
https://issues.apache.org/jira/browse/AMBARI-22891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362971#comment-16362971
]
Hudson commented on AMBARI-22891:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8722 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8722/])
AMBARI-22891 : Logging improvement during the Upgrade when there is (swagle:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=6d1dc6c4e5baa5b8044806ef0c29f6d15050d70e])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionFactory.java
> Logging improvement during the Upgrade when there is invalid Alert definition
> -
>
> Key: AMBARI-22891
> URL: https://issues.apache.org/jira/browse/AMBARI-22891
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: amarnath reddy pappu
>Assignee: amarnath reddy pappu
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Attachments: AMBARI-22891.txt
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> If there is invalid definition/json in alert definition then Upgrade would
> fail with below exception. there is no way to determine which alert is
> causing the issue here.
> its not clear how this alert definition gets corrupted but we have seen this
> with 3 to 4 customers already - printing the alert definition name would he
> helpful in support point of view to determine the root cause.. other wise it
> is very difficult to find it out - had a give a dev patch to customers to
> find it out.
> {noformat}
> 29 Jan 2018 19:58:50,173 ERROR [main] AlertDefinitionFactory:199 - Unable to
> deserialize the alert definition source during coercion
> com.google.gson.JsonSyntaxException: java.lang.IllegalStateException:
> Expected STRING but was BEGIN_OBJECT
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:176)
> at com.google.gson.Gson.fromJson(Gson.java:795)
> at com.google.gson.Gson.fromJson(Gson.java:859)
> at com.google.gson.Gson$2.deserialize(Gson.java:131)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:373)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:313)
> at com.google.gson.TreeTypeAdapter.read(TreeTypeAdapter.java:58)
> at com.google.gson.Gson.fromJson(Gson.java:795)
> at com.google.gson.Gson.fromJson(Gson.java:761)
> at com.google.gson.Gson.fromJson(Gson.java:710)
> at com.google.gson.Gson.fromJson(Gson.java:682)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory.coerce(AlertDefinitionFactory.java:196)
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1150)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
> Caused by: java.lang.IllegalStateException: Expected STRING but was
> BEGIN_OBJECT
> at
> com.google.gson.internal.bind.JsonTreeReader.nextString(JsonTreeReader.java:154)
> at
> com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:349)
> at
> com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:337)
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:93)
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:172)
> ... 16 more
> 29 Jan 2018 19:58:50,176 ERROR [main] SchemaUpgradeHelper:239 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1163)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
> 29 Jan
[jira] [Commented] (AMBARI-22918) Decommission RegionServer fails when kerberos is enabled
[
https://issues.apache.org/jira/browse/AMBARI-22918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362959#comment-16362959
]
Hudson commented on AMBARI-22918:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #605 (See
[https://builds.apache.org/job/Ambari-branch-2.6/605/])
AMBARI-22918 Decommission RegionServer fails when kerberos is enabled (swagle:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=f40a400da39cff9bd2c32ea6c5f33a256467e1e8])
* (edit)
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_decommission.py
> Decommission RegionServer fails when kerberos is enabled
>
>
> Key: AMBARI-22918
> URL: https://issues.apache.org/jira/browse/AMBARI-22918
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Toshihiro Suzuki
>Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> When kerberos is enabled, Decommission RegionServer fails with the following
> errors:
> stderr:
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 114, in
> HbaseMaster().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 55, in decommission
> hbase_decommission(env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_decommission.py",
> line 84, in hbase_decommission
> logoutput=True
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 166, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/hbase.service.keytab
> hbase/mast...@example.com; /usr/hdp/current/hbase-master/bin/hbase --config
> /usr/hdp/current/hbase-master/conf
> -Djava.security.auth.login.config=/usr/hdp/current/hbase-master/conf/hbase_master_jaas.conf
> org.jruby.Main /usr/hdp/current/hbase-master/bin/draining_servers.rb add
> worker1' returned 1. Error: Could not find or load main class
> org.jruby.Main{code}
> stdout:
> {code:java}
> 2018-02-06 07:25:03,453 - Stack Feature Version Info: Cluster Stack=2.6,
> Cluster Current Version=2.6.2.0-205, Command Stack=None, Command
> Version=2.6.2.0-205 -> 2.6.2.0-205
> 2018-02-06 07:25:03,476 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2018-02-06 07:25:03,484 - checked_call['hostid'] {}
> 2018-02-06 07:25:03,490 - checked_call returned (0, '1aacc56c')
> 2018-02-06 07:25:03,502 -
> File['/usr/hdp/current/hbase-master/bin/draining_servers.rb'] {'content':
> StaticFile('draining_servers.rb'), 'mode': 0755}
> 2018-02-06 07:25:03,504 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab hbase/mast...@example.com;
> /usr/hdp/current/hbase-master/bin/hbase --config
> /usr/hdp/current/hbase-master/conf
> -Djava.security.auth.login.config=/usr/hdp/current/hbase-master/conf/hbase_master_jaas.conf
> org.jruby.Main /usr/hdp/current/hbase-master/bin/draining_servers.rb add
> worker1'] {'logoutput': True, 'user': 'hbase'}
> Error: Could not find or load main class org.jruby.Main
> Command failed after 1 tries{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-22726) Test failing with no changes - BlueprintImplTest.testValidateConfigurations__hostGroupConfigForNameNodeHAPositive
[ https://issues.apache.org/jira/browse/AMBARI-22726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wing Lam resolved AMBARI-22726. --- Resolution: Fixed The patch for this issue has been accepted in the following pull request. https://github.com/apache/ambari/pull/133 > Test failing with no changes - > BlueprintImplTest.testValidateConfigurations__hostGroupConfigForNameNodeHAPositive > -- > > Key: AMBARI-22726 > URL: https://issues.apache.org/jira/browse/AMBARI-22726 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk > Environment: Ubuntu, 16.04 LTS >Reporter: Wing Lam >Priority: Minor > Labels: pull-request-available > Fix For: trunk > > Time Spent: 1h > Remaining Estimate: 0h > > When I run just the test > testValidateConfigurations__hostGroupConfigForNameNodeHAPositive in an IDE, > the test fails. > It appears that the problem is that the configuration for the > BlueprintValidatorImpl is not set up in > testValidateConfigurations__hostGroupConfigForNameNodeHAPositive. Instead, > some other tests setup some configuration for the > testValidateConfigurations__hostGroupConfigForNameNodeHAPositive test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22977) NullPointerException in KerberosHelperImpl.addIdentities
[
https://issues.apache.org/jira/browse/AMBARI-22977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar resolved AMBARI-22977.
Resolution: Fixed
> NullPointerException in KerberosHelperImpl.addIdentities
>
>
> Key: AMBARI-22977
> URL: https://issues.apache.org/jira/browse/AMBARI-22977
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> If a group name or group access is missing from a kerberos descriptor ambari
> will throw an NPE during enable kerberos
> {code:java}
> 13 Feb 2018 11:27:37,466 WARN [Server Action Executor Worker 39]
> ServerActionExecutor:471 - Task #39 failed to complete execution due to
> thrown exception: java.lang.NullPointerException:null
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.addIdentities(KerberosHelperImpl.java:1601)
> at
> org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponents(AbstractPrepareKerberosServerAction.java:177)
> at
> org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponentHosts(AbstractPrepareKerberosServerAction.java:87)
> at
> org.apache.ambari.server.serveraction.kerberos.PrepareKerberosIdentitiesServerAction.execute(PrepareKerberosIdentitiesServerAction.java:128)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:748){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22076) Use A Scoped Repo When Installing stack-tools
[
https://issues.apache.org/jira/browse/AMBARI-22076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362901#comment-16362901
]
Hudson commented on AMBARI-22076:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8721 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8721/])
AMBARI-22076. Unable to create new user after fresh install of Ambari (hiveww:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=6686d11b114f32e999df25deda5a890b1f0bd1c5])
* (edit)
ambari-admin/src/main/resources/ui/admin-web/app/views/userManagement/modals/userCreate.html
> Use A Scoped Repo When Installing stack-tools
> -
>
> Key: AMBARI-22076
> URL: https://issues.apache.org/jira/browse/AMBARI-22076
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.6.0
>
> Attachments: AMBARI-22076.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Ambari does not write out repositories with a "priority" attribute since this
> is a plugin and is not guaranteed to be installed. Also, when installing
> packages with versions "in the middle" of two other installed stacks,
> priority would be incorrect as the most recent stack-tools should always be
> used.
> The following is seen when trying to distribute a stack for a patch upgrade:
> {code}
> 2017-09-26 16:28:58,652 - Package Manager failed to install packages. Error:
> Execution of '/usr/bin/yum -d 0 -e 0 -y install hive_2_6_3_1_1' returned 1.
> Error: Package: hadoop_2_6_3_1_1-2.7.3.2.6.3.1-1.x86_64 (HDP-2.6-repo-2)
>Requires: hdp-select >= 2.6.3.1-1
>Installed: hdp-select-2.6.3.0-122.noarch (@HDP-2.6.3.0-122)
>hdp-select = 2.6.3.0-122
> {code}
> The cause of this seems to be that the repository for HDP-2.6-repo-2 does not
> take priority over the existing installed repository for {{hdp-select}}.
> That's actually good - it shouldn't take priority over it arbitrarily.
> However, this means that the {{hdp-select}} which is installed did not get
> taken from {{HDP-2.6-repo-2}}. So, when installing {{hdp-select}}, we should
> scope the install to the repo we are trying to calculate the version for.
> This works because the stack-select tools do not have their package names
> versioned ({{hdp-select}} as opposed to {{hdp-select_x_y_z}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22979) Update software registry API to support new mpack schema
Jayush Luniya created AMBARI-22979: -- Summary: Update software registry API to support new mpack schema Key: AMBARI-22979 URL: https://issues.apache.org/jira/browse/AMBARI-22979 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Jayush Luniya Assignee: Jayush Luniya Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22977) NullPointerException in KerberosHelperImpl.addIdentities
[
https://issues.apache.org/jira/browse/AMBARI-22977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22977:
Labels: pull-request-available (was: )
> NullPointerException in KerberosHelperImpl.addIdentities
>
>
> Key: AMBARI-22977
> URL: https://issues.apache.org/jira/browse/AMBARI-22977
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> If a group name or group access is missing from a kerberos descriptor ambari
> will throw an NPE during enable kerberos
> {code:java}
> 13 Feb 2018 11:27:37,466 WARN [Server Action Executor Worker 39]
> ServerActionExecutor:471 - Task #39 failed to complete execution due to
> thrown exception: java.lang.NullPointerException:null
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.addIdentities(KerberosHelperImpl.java:1601)
> at
> org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponents(AbstractPrepareKerberosServerAction.java:177)
> at
> org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponentHosts(AbstractPrepareKerberosServerAction.java:87)
> at
> org.apache.ambari.server.serveraction.kerberos.PrepareKerberosIdentitiesServerAction.execute(PrepareKerberosIdentitiesServerAction.java:128)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:748){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22978) Mandatory configs warning in Ambari while editing the config of HDFS
Endre Major created AMBARI-22978: Summary: Mandatory configs warning in Ambari while editing the config of HDFS Key: AMBARI-22978 URL: https://issues.apache.org/jira/browse/AMBARI-22978 Project: Ambari Issue Type: Bug Reporter: Endre Major Assignee: Endre Major On the GUI HDFS advanced settings indicates to problems, that it should not. This is caused by a bad ssl-client.xml at /var/lib/ambari-server/resources/common-services/HDFS/3.0.0.3.0/configuration/ssl-client.xml ssl.client.keystore.password true PASSWORD Password to open the keystore file. password There are 2 value-attributes section. Merging them solves this problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22968) Remove class duplications from Log Search / Log Feeder classpath
[
https://issues.apache.org/jira/browse/AMBARI-22968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362605#comment-16362605
]
Hudson commented on AMBARI-22968:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8719 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8719/])
AMBARI-22968. Remove class duplications from Log Search / Log Feeder (oleewere:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=628cd06ebe421397622953cc79809232df0a0363])
* (edit) ambari-logsearch/ambari-logsearch-logfeeder/pom.xml
* (edit) ambari-logsearch/ambari-logsearch-server/pom.xml
> Remove class duplications from Log Search / Log Feeder classpath
>
>
> Key: AMBARI-22968
> URL: https://issues.apache.org/jira/browse/AMBARI-22968
> 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
>
> Original Estimate: 24h
> Time Spent: 0.5h
> Remaining Estimate: 23.5h
>
> Things like that can happen at runtime:
> (Multiple javax.el implementation on Log Search runtime/compile classpath)
> {code:java}
> Feb 12, 2018 8:03:55 PM org.glassfish.jersey.internal.Errors logErrors
> WARNING: The following warnings have been detected: WARNING: Unknown HK2
> failure detected:
> MultiException stack 1 of 1
> javax.validation.ValidationException: HV000183: Unable to initialize
> 'javax.el.ExpressionFactory'. Check that you have the EL dependencies on the
> classpath, or use ParameterMessageInterpolator instead
> at
> org.hibernate.validator.messageinterpolation.ResourceBundleMessageInterpolator.buildExpressionFactory(ResourceBundleMessageInterpolator.java:102)
> at
> org.hibernate.validator.messageinterpolation.ResourceBundleMessageInterpolator.(ResourceBundleMessageInterpolator.java:45)
> at
> org.hibernate.validator.internal.engine.ConfigurationImpl.getDefaultMessageInterpolator(ConfigurationImpl.java:423)
> at
> org.hibernate.validator.internal.engine.ConfigurationImpl.getDefaultMessageInterpolatorConfiguredWithClassLoader(ConfigurationImpl.java:575)
> at
> org.hibernate.validator.internal.engine.ConfigurationImpl.getMessageInterpolator(ConfigurationImpl.java:364)
> at
> org.hibernate.validator.internal.engine.ValidatorFactoryImpl.(ValidatorFactoryImpl.java:144)
> at
> org.hibernate.validator.HibernateValidator.buildValidatorFactory(HibernateValidator.java:38)
> at
> org.hibernate.validator.internal.engine.ConfigurationImpl.buildValidatorFactory(ConfigurationImpl.java:331)
> at
> org.glassfish.jersey.server.validation.internal.ValidationBinder$DefaultValidatorFactoryProvider.provide(ValidationBinder.java:164)
> at
> org.glassfish.jersey.server.validation.internal.ValidationBinder$DefaultValidatorFactoryProvider.provide(ValidationBinder.java:157)
> at org.jvnet.hk2.internal.FactoryCreator.create(FactoryCreator.java:153)
> at
> org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:487)
> at
> org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:83)
> at
> org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:71)
> at
> org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture$1.call(Cache.java:97)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture.run(Cache.java:154)
> at org.glassfish.hk2.utilities.cache.Cache.compute(Cache.java:199)
> at
> org.jvnet.hk2.internal.SingletonContext.findOrCreate(SingletonContext.java:122)
> at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2022)
> at
> org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:114)
> at
> org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:695)
> at
> org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:78)
> at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:212)
> at
> org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:235)
> at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:358)
> at
> org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:487)
> at
> org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:83)
> at
> org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:71)
> at
> org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture$1.call(Cache.java:97)
> at
[jira] [Commented] (AMBARI-22977) NullPointerException in KerberosHelperImpl.addIdentities
[
https://issues.apache.org/jira/browse/AMBARI-22977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362547#comment-16362547
]
Robert Levas commented on AMBARI-22977:
---
[~amagyar], [~echekanskiy]...
Not specifying user or group ownership of a keytab file in the Kerberos
descriptor is allowed... however it is not recommended. So nulls should be
handled.
If no username or group is specified, the agent-side logic will not attempt to
set them or set access to them. See
{{ambari-common/src/main/python/ambari_commons/kerberos/kerberos_common.py:107}}.
> NullPointerException in KerberosHelperImpl.addIdentities
>
>
> Key: AMBARI-22977
> URL: https://issues.apache.org/jira/browse/AMBARI-22977
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Fix For: 2.7.0
>
>
> If a group name or group access is missing from a kerberos descriptor ambari
> will throw an NPE during enable kerberos
> {code:java}
> 13 Feb 2018 11:27:37,466 WARN [Server Action Executor Worker 39]
> ServerActionExecutor:471 - Task #39 failed to complete execution due to
> thrown exception: java.lang.NullPointerException:null
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.addIdentities(KerberosHelperImpl.java:1601)
> at
> org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponents(AbstractPrepareKerberosServerAction.java:177)
> at
> org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponentHosts(AbstractPrepareKerberosServerAction.java:87)
> at
> org.apache.ambari.server.serveraction.kerberos.PrepareKerberosIdentitiesServerAction.execute(PrepareKerberosIdentitiesServerAction.java:128)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:748){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22977) NullPointerException in KerberosHelperImpl.addIdentities
Attila Magyar created AMBARI-22977:
--
Summary: NullPointerException in KerberosHelperImpl.addIdentities
Key: AMBARI-22977
URL: https://issues.apache.org/jira/browse/AMBARI-22977
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Attila Magyar
Assignee: Attila Magyar
Fix For: 2.7.0
If a group name or group access is missing from a kerberos descriptor ambari
will throw an NPE during enable kerberos
{code:java}
13 Feb 2018 11:27:37,466 WARN [Server Action Executor Worker 39]
ServerActionExecutor:471 - Task #39 failed to complete execution due to thrown
exception: java.lang.NullPointerException:null
java.lang.NullPointerException
at
org.apache.ambari.server.controller.KerberosHelperImpl.addIdentities(KerberosHelperImpl.java:1601)
at
org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponents(AbstractPrepareKerberosServerAction.java:177)
at
org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponentHosts(AbstractPrepareKerberosServerAction.java:87)
at
org.apache.ambari.server.serveraction.kerberos.PrepareKerberosIdentitiesServerAction.execute(PrepareKerberosIdentitiesServerAction.java:128)
at
org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
at
org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
at java.lang.Thread.run(Thread.java:748){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22967) Update Solr version defaults in docker envs (infra-manager and logsearch)
[ https://issues.apache.org/jira/browse/AMBARI-22967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362501#comment-16362501 ] Hudson commented on AMBARI-22967: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8718 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8718/]) AMBARI-22967. Update Solr version defaults in docker envs (infra-manager (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=d49fb1b96e9701c989d2eff13d0a0b3fcc092662]) * (edit) ambari-infra/ambari-infra-manager/docker/infra-manager-docker-compose.sh * (edit) ambari-logsearch/docker/logsearch-docker.sh * (edit) ambari-logsearch/docker/sso.yml * (edit) ambari-infra/ambari-infra-manager/docker/docker-compose.yml * (edit) ambari-logsearch/docker/Dockerfile > Update Solr version defaults in docker envs (infra-manager and logsearch) > - > > Key: AMBARI-22967 > URL: https://issues.apache.org/jira/browse/AMBARI-22967 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22959) Upgrade Log Search Solr client version to 7.2.1
[ https://issues.apache.org/jira/browse/AMBARI-22959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-22959. --- Resolution: Fixed > Upgrade Log Search Solr client version to 7.2.1 > --- > > Key: AMBARI-22959 > URL: https://issues.apache.org/jira/browse/AMBARI-22959 > 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 > > Original Estimate: 24h > Time Spent: 0.5h > Remaining Estimate: 23.5h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22967) Update Solr version defaults in docker envs (infra-manager and logsearch)
[ https://issues.apache.org/jira/browse/AMBARI-22967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-22967. --- Resolution: Fixed > Update Solr version defaults in docker envs (infra-manager and logsearch) > - > > Key: AMBARI-22967 > URL: https://issues.apache.org/jira/browse/AMBARI-22967 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22968) Remove class duplications from Log Search / Log Feeder classpath
[
https://issues.apache.org/jira/browse/AMBARI-22968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-22968.
---
Resolution: Fixed
> Remove class duplications from Log Search / Log Feeder classpath
>
>
> Key: AMBARI-22968
> URL: https://issues.apache.org/jira/browse/AMBARI-22968
> 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
>
> Original Estimate: 24h
> Time Spent: 0.5h
> Remaining Estimate: 23.5h
>
> Things like that can happen at runtime:
> (Multiple javax.el implementation on Log Search runtime/compile classpath)
> {code:java}
> Feb 12, 2018 8:03:55 PM org.glassfish.jersey.internal.Errors logErrors
> WARNING: The following warnings have been detected: WARNING: Unknown HK2
> failure detected:
> MultiException stack 1 of 1
> javax.validation.ValidationException: HV000183: Unable to initialize
> 'javax.el.ExpressionFactory'. Check that you have the EL dependencies on the
> classpath, or use ParameterMessageInterpolator instead
> at
> org.hibernate.validator.messageinterpolation.ResourceBundleMessageInterpolator.buildExpressionFactory(ResourceBundleMessageInterpolator.java:102)
> at
> org.hibernate.validator.messageinterpolation.ResourceBundleMessageInterpolator.(ResourceBundleMessageInterpolator.java:45)
> at
> org.hibernate.validator.internal.engine.ConfigurationImpl.getDefaultMessageInterpolator(ConfigurationImpl.java:423)
> at
> org.hibernate.validator.internal.engine.ConfigurationImpl.getDefaultMessageInterpolatorConfiguredWithClassLoader(ConfigurationImpl.java:575)
> at
> org.hibernate.validator.internal.engine.ConfigurationImpl.getMessageInterpolator(ConfigurationImpl.java:364)
> at
> org.hibernate.validator.internal.engine.ValidatorFactoryImpl.(ValidatorFactoryImpl.java:144)
> at
> org.hibernate.validator.HibernateValidator.buildValidatorFactory(HibernateValidator.java:38)
> at
> org.hibernate.validator.internal.engine.ConfigurationImpl.buildValidatorFactory(ConfigurationImpl.java:331)
> at
> org.glassfish.jersey.server.validation.internal.ValidationBinder$DefaultValidatorFactoryProvider.provide(ValidationBinder.java:164)
> at
> org.glassfish.jersey.server.validation.internal.ValidationBinder$DefaultValidatorFactoryProvider.provide(ValidationBinder.java:157)
> at org.jvnet.hk2.internal.FactoryCreator.create(FactoryCreator.java:153)
> at
> org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:487)
> at
> org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:83)
> at
> org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:71)
> at
> org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture$1.call(Cache.java:97)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture.run(Cache.java:154)
> at org.glassfish.hk2.utilities.cache.Cache.compute(Cache.java:199)
> at
> org.jvnet.hk2.internal.SingletonContext.findOrCreate(SingletonContext.java:122)
> at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2022)
> at
> org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:114)
> at
> org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:695)
> at
> org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:78)
> at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:212)
> at
> org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:235)
> at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:358)
> at
> org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:487)
> at
> org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:83)
> at
> org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:71)
> at
> org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture$1.call(Cache.java:97)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture.run(Cache.java:154)
> at org.glassfish.hk2.utilities.cache.Cache.compute(Cache.java:199)
> at
> org.jvnet.hk2.internal.SingletonContext.findOrCreate(SingletonContext.java:122)
> at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2022)
> at
>
[jira] [Commented] (AMBARI-22975) Add namespace-specific layout for service summary page
[ https://issues.apache.org/jira/browse/AMBARI-22975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362409#comment-16362409 ] Hudson commented on AMBARI-22975: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8717 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8717/]) AMBARI-22975 Add namespace-specific layout for service summary page. (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=dff583c4f30e2b2d40490b631b2b1c0daaeda7a1]) * (edit) ambari-web/app/mappers/service_metrics_mapper.js * (edit) ambari-web/app/views/main/service/info/summary.js * (edit) ambari-web/app/templates/main/service/services/hive.hbs * (edit) ambari-web/app/app.js * (edit) ambari-web/app/templates/main/service/services/hbase.hbs * (edit) ambari-web/test/views/main/service/service_test.js * (edit) ambari-web/app/models/host_component.js * (edit) ambari-web/app/templates/main/service/services/hdfs.hbs * (edit) ambari-web/app/templates/main/service/services/storm.hbs * (edit) ambari-web/app/views/main/service/info/components_list_view.js * (edit) ambari-web/app/views/main/service/service.js * (edit) ambari-web/test/views/main/service/services/hdfs_test.js * (edit) ambari-web/app/templates/main/service/info/summary/master_components.hbs * (edit) ambari-web/app/templates/main/service/services/ranger.hbs * (edit) ambari-web/app/templates/main/service/info/summary.hbs * (edit) ambari-web/test/views/main/service/info/summary_test.js * (edit) ambari-web/app/views/main/service/services/hdfs.js * (edit) ambari-web/app/templates/main/service/info/summary/base.hbs * (edit) ambari-web/app/templates/main/service/services/yarn.hbs > Add namespace-specific layout for service summary page > -- > > Key: AMBARI-22975 > URL: https://issues.apache.org/jira/browse/AMBARI-22975 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > - HDFS components should be grouped by namespace > - Service summary page should have separate tab for each namespace -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22975) Add namespace-specific layout for service summary page
[ https://issues.apache.org/jira/browse/AMBARI-22975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk resolved AMBARI-22975. --- Resolution: Fixed Merged to trunk > Add namespace-specific layout for service summary page > -- > > Key: AMBARI-22975 > URL: https://issues.apache.org/jira/browse/AMBARI-22975 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > - HDFS components should be grouped by namespace > - Service summary page should have separate tab for each namespace -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-21738) OS specific package manager logic need to be moved out from Package provider to ambari_commons
[ https://issues.apache.org/jira/browse/AMBARI-21738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-21738: Labels: pull-request-available (was: ) > OS specific package manager logic need to be moved out from Package provider > to ambari_commons > -- > > Key: AMBARI-21738 > URL: https://issues.apache.org/jira/browse/AMBARI-21738 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 2.6.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > > Package manager logic implemented on > resource_management.core.providers.package.* package need to be moved to > ambari_common package > This should create a unified package to work with package managers and remove > all custom code from scripts -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22976) Unable to create new user after fresh install of Ambari
[ https://issues.apache.org/jira/browse/AMBARI-22976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22976: - Status: Patch Available (was: Open) > Unable to create new user after fresh install of Ambari > --- > > Key: AMBARI-22976 > URL: https://issues.apache.org/jira/browse/AMBARI-22976 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > > Unable to add a user, upon clicking Save the page just does not respond - no > API call, nothing in server logs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22076) Use A Scoped Repo When Installing stack-tools
[
https://issues.apache.org/jira/browse/AMBARI-22076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22076:
Labels: pull-request-available (was: )
> Use A Scoped Repo When Installing stack-tools
> -
>
> Key: AMBARI-22076
> URL: https://issues.apache.org/jira/browse/AMBARI-22076
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.6.0
>
> Attachments: AMBARI-22076.patch
>
>
> Ambari does not write out repositories with a "priority" attribute since this
> is a plugin and is not guaranteed to be installed. Also, when installing
> packages with versions "in the middle" of two other installed stacks,
> priority would be incorrect as the most recent stack-tools should always be
> used.
> The following is seen when trying to distribute a stack for a patch upgrade:
> {code}
> 2017-09-26 16:28:58,652 - Package Manager failed to install packages. Error:
> Execution of '/usr/bin/yum -d 0 -e 0 -y install hive_2_6_3_1_1' returned 1.
> Error: Package: hadoop_2_6_3_1_1-2.7.3.2.6.3.1-1.x86_64 (HDP-2.6-repo-2)
>Requires: hdp-select >= 2.6.3.1-1
>Installed: hdp-select-2.6.3.0-122.noarch (@HDP-2.6.3.0-122)
>hdp-select = 2.6.3.0-122
> {code}
> The cause of this seems to be that the repository for HDP-2.6-repo-2 does not
> take priority over the existing installed repository for {{hdp-select}}.
> That's actually good - it shouldn't take priority over it arbitrarily.
> However, this means that the {{hdp-select}} which is installed did not get
> taken from {{HDP-2.6-repo-2}}. So, when installing {{hdp-select}}, we should
> scope the install to the repo we are trying to calculate the version for.
> This works because the stack-select tools do not have their package names
> versioned ({{hdp-select}} as opposed to {{hdp-select_x_y_z}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22968) Remove class duplications from Log Search / Log Feeder classpath
[
https://issues.apache.org/jira/browse/AMBARI-22968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22968:
Labels: pull-request-available (was: )
> Remove class duplications from Log Search / Log Feeder classpath
>
>
> Key: AMBARI-22968
> URL: https://issues.apache.org/jira/browse/AMBARI-22968
> 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
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Things like that can happen at runtime:
> (Multiple javax.el implementation on Log Search runtime/compile classpath)
> {code:java}
> Feb 12, 2018 8:03:55 PM org.glassfish.jersey.internal.Errors logErrors
> WARNING: The following warnings have been detected: WARNING: Unknown HK2
> failure detected:
> MultiException stack 1 of 1
> javax.validation.ValidationException: HV000183: Unable to initialize
> 'javax.el.ExpressionFactory'. Check that you have the EL dependencies on the
> classpath, or use ParameterMessageInterpolator instead
> at
> org.hibernate.validator.messageinterpolation.ResourceBundleMessageInterpolator.buildExpressionFactory(ResourceBundleMessageInterpolator.java:102)
> at
> org.hibernate.validator.messageinterpolation.ResourceBundleMessageInterpolator.(ResourceBundleMessageInterpolator.java:45)
> at
> org.hibernate.validator.internal.engine.ConfigurationImpl.getDefaultMessageInterpolator(ConfigurationImpl.java:423)
> at
> org.hibernate.validator.internal.engine.ConfigurationImpl.getDefaultMessageInterpolatorConfiguredWithClassLoader(ConfigurationImpl.java:575)
> at
> org.hibernate.validator.internal.engine.ConfigurationImpl.getMessageInterpolator(ConfigurationImpl.java:364)
> at
> org.hibernate.validator.internal.engine.ValidatorFactoryImpl.(ValidatorFactoryImpl.java:144)
> at
> org.hibernate.validator.HibernateValidator.buildValidatorFactory(HibernateValidator.java:38)
> at
> org.hibernate.validator.internal.engine.ConfigurationImpl.buildValidatorFactory(ConfigurationImpl.java:331)
> at
> org.glassfish.jersey.server.validation.internal.ValidationBinder$DefaultValidatorFactoryProvider.provide(ValidationBinder.java:164)
> at
> org.glassfish.jersey.server.validation.internal.ValidationBinder$DefaultValidatorFactoryProvider.provide(ValidationBinder.java:157)
> at org.jvnet.hk2.internal.FactoryCreator.create(FactoryCreator.java:153)
> at
> org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:487)
> at
> org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:83)
> at
> org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:71)
> at
> org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture$1.call(Cache.java:97)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture.run(Cache.java:154)
> at org.glassfish.hk2.utilities.cache.Cache.compute(Cache.java:199)
> at
> org.jvnet.hk2.internal.SingletonContext.findOrCreate(SingletonContext.java:122)
> at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2022)
> at
> org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:114)
> at
> org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:695)
> at
> org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:78)
> at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:212)
> at
> org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:235)
> at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:358)
> at
> org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:487)
> at
> org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:83)
> at
> org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:71)
> at
> org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture$1.call(Cache.java:97)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture.run(Cache.java:154)
> at org.glassfish.hk2.utilities.cache.Cache.compute(Cache.java:199)
> at
> org.jvnet.hk2.internal.SingletonContext.findOrCreate(SingletonContext.java:122)
> at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2022)
> at
>
[jira] [Assigned] (AMBARI-22976) Unable to create new user after fresh install of Ambari
[ https://issues.apache.org/jira/browse/AMBARI-22976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-22976: Assignee: Antonenko Alexander > Unable to create new user after fresh install of Ambari > --- > > Key: AMBARI-22976 > URL: https://issues.apache.org/jira/browse/AMBARI-22976 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > > Unable to add a user, upon clicking Save the page just does not respond - no > API call, nothing in server logs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22976) Unable to create new user after fresh install of Ambari
Antonenko Alexander created AMBARI-22976: Summary: Unable to create new user after fresh install of Ambari Key: AMBARI-22976 URL: https://issues.apache.org/jira/browse/AMBARI-22976 Project: Ambari Issue Type: Task Components: ambari-admin Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 Unable to add a user, upon clicking Save the page just does not respond - no API call, nothing in server logs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22927) Hive View 1.5 Upload Table - not able to change datatype from the dropdown for a wide file
[ https://issues.apache.org/jira/browse/AMBARI-22927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22927: Labels: pull-request-available (was: ) > Hive View 1.5 Upload Table - not able to change datatype from the dropdown > for a wide file > -- > > Key: AMBARI-22927 > URL: https://issues.apache.org/jira/browse/AMBARI-22927 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Labels: pull-request-available > Fix For: 2.5.2 > > > Steps: > # Go to Hive view 1.5, > # Select type CSV > # Upload the attached file > # Try to change the datatype of last column > # The UI comes back to the leftmost column, showing the first few columns -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22961) Blacklist by default /boot/efi path as mount point reported by Ambari Agent
[
https://issues.apache.org/jira/browse/AMBARI-22961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22961:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Blacklist by default /boot/efi path as mount point reported by Ambari Agent
> ---
>
> Key: AMBARI-22961
> URL: https://issues.apache.org/jira/browse/AMBARI-22961
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> On EFI Based systems, efi partition mounting under /boot/efi path. It causing
> Agent to report this mount point as available partition location. On new
> cluster deploy, this partition could be proposed by stack_adviser as datanode
> storage location, which is wrong.
> Workaround for versions without this patch: add \{{/boot/efi}} to
> \{{ignore_mount_points}} property, \{{agent}} section in ambari-agent.ini
> configuration file.
> Problem source:
> -
> https://community.hortonworks.com/questions/118551/namenode-can-not-be-started-1.html
>
> - ASF mailing list
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22973) 'Assign Slaves & Clients' page is empty when 3 or more services selected while adding multiple services
[
https://issues.apache.org/jira/browse/AMBARI-22973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362197#comment-16362197
]
Hudson commented on AMBARI-22973:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8716 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8716/])
AMBARI-22973 'Assign Slaves & Clients' page is empty when 3 or more
(1963907+atkach:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=db4b701799d039e362572c72ffc1a4d124421b0d])
* (edit) ambari-web/app/controllers/wizard/step6_controller.js
> 'Assign Slaves & Clients' page is empty when 3 or more services selected
> while adding multiple services
> ---
>
> Key: AMBARI-22973
> URL: https://issues.apache.org/jira/browse/AMBARI-22973
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> STR:
> # In the cluster, click add service
> # Select the remaining services to be added (Pig, Knox, Logsearch,
> RangerKMS, Zeppelin) and click Next
> # Accept Defaults and Select Next on Assign Masters page
> In the Assign Slaves and Clients page, there is an empty page.
> Adding services individually does not hit this issue.
> There are some error logs in the console:
> {code:java}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at app.js:38709
> at Array.forEach ()
> at app.js:38707
> at Class.forEach (vendor.js:18038)
> at app.js:38706
> at Array.forEach ()
> at Class.enableCheckboxesForDependentComponents (app.js:38705)
> at Class.renderSlaves (app.js:38671)
> at Class.render (app.js:38646)
> at Class.loadStep (app.js:38569)
> {code}
> Calls to server made during while navigating to Assign Slaves and Clients page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22961) Blacklist by default /boot/efi path as mount point reported by Ambari Agent
[
https://issues.apache.org/jira/browse/AMBARI-22961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22961:
-
Status: Patch Available (was: In Progress)
> Blacklist by default /boot/efi path as mount point reported by Ambari Agent
> ---
>
> Key: AMBARI-22961
> URL: https://issues.apache.org/jira/browse/AMBARI-22961
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> On EFI Based systems, efi partition mounting under /boot/efi path. It causing
> Agent to report this mount point as available partition location. On new
> cluster deploy, this partition could be proposed by stack_adviser as datanode
> storage location, which is wrong.
> Workaround for versions without this patch: add \{{/boot/efi}} to
> \{{ignore_mount_points}} property, \{{agent}} section in ambari-agent.ini
> configuration file.
> Problem source:
> -
> https://community.hortonworks.com/questions/118551/namenode-can-not-be-started-1.html
>
> - ASF mailing list
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22975) Add namespace-specific layout for service summary page
[ https://issues.apache.org/jira/browse/AMBARI-22975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22975: Labels: pull-request-available (was: ) > Add namespace-specific layout for service summary page > -- > > Key: AMBARI-22975 > URL: https://issues.apache.org/jira/browse/AMBARI-22975 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > > - HDFS components should be grouped by namespace > - Service summary page should have separate tab for each namespace -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22975) Add namespace-specific layout for service summary page
Andrii Babiichuk created AMBARI-22975: - Summary: Add namespace-specific layout for service summary page Key: AMBARI-22975 URL: https://issues.apache.org/jira/browse/AMBARI-22975 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 2.7.0 - HDFS components should be grouped by namespace - Service summary page should have separate tab for each namespace -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22973) 'Assign Slaves & Clients' page is empty when 3 or more services selected while adding multiple services
[
https://issues.apache.org/jira/browse/AMBARI-22973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362165#comment-16362165
]
Andrii Tkach commented on AMBARI-22973:
---
committed to trunk
> 'Assign Slaves & Clients' page is empty when 3 or more services selected
> while adding multiple services
> ---
>
> Key: AMBARI-22973
> URL: https://issues.apache.org/jira/browse/AMBARI-22973
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> STR:
> # In the cluster, click add service
> # Select the remaining services to be added (Pig, Knox, Logsearch,
> RangerKMS, Zeppelin) and click Next
> # Accept Defaults and Select Next on Assign Masters page
> In the Assign Slaves and Clients page, there is an empty page.
> Adding services individually does not hit this issue.
> There are some error logs in the console:
> {code:java}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at app.js:38709
> at Array.forEach ()
> at app.js:38707
> at Class.forEach (vendor.js:18038)
> at app.js:38706
> at Array.forEach ()
> at Class.enableCheckboxesForDependentComponents (app.js:38705)
> at Class.renderSlaves (app.js:38671)
> at Class.render (app.js:38646)
> at Class.loadStep (app.js:38569)
> {code}
> Calls to server made during while navigating to Assign Slaves and Clients page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-22973) 'Assign Slaves & Clients' page is empty when 3 or more services selected while adding multiple services
[
https://issues.apache.org/jira/browse/AMBARI-22973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach resolved AMBARI-22973.
---
Resolution: Fixed
> 'Assign Slaves & Clients' page is empty when 3 or more services selected
> while adding multiple services
> ---
>
> Key: AMBARI-22973
> URL: https://issues.apache.org/jira/browse/AMBARI-22973
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> STR:
> # In the cluster, click add service
> # Select the remaining services to be added (Pig, Knox, Logsearch,
> RangerKMS, Zeppelin) and click Next
> # Accept Defaults and Select Next on Assign Masters page
> In the Assign Slaves and Clients page, there is an empty page.
> Adding services individually does not hit this issue.
> There are some error logs in the console:
> {code:java}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at app.js:38709
> at Array.forEach ()
> at app.js:38707
> at Class.forEach (vendor.js:18038)
> at app.js:38706
> at Array.forEach ()
> at Class.enableCheckboxesForDependentComponents (app.js:38705)
> at Class.renderSlaves (app.js:38671)
> at Class.render (app.js:38646)
> at Class.loadStep (app.js:38569)
> {code}
> Calls to server made during while navigating to Assign Slaves and Clients page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22940) Service-auto start page update of UI
[ https://issues.apache.org/jira/browse/AMBARI-22940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362148#comment-16362148 ] Hudson commented on AMBARI-22940: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8715 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8715/]) AMBARI-22940 Service-auto start page update of UI (1963907+atkach: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=15ec6f5e084f81a21b3a3545dbdf4ed33492bc0f]) * (delete) ambari-web/app/templates/main/admin/service_auto_start/service_auto_start_indicator.hbs * (delete) ambari-web/app/views/main/admin/service_auto_start/service_auto_start_indicator.js * (delete) ambari-web/test/views/main/admin/service_auto_start/component_auto_start_test.js * (edit) ambari-web/app/views.js * (edit) ambari-web/app/styles/bootstrap_overrides.less * (edit) ambari-web/app/assets/test/tests.js * (edit) ambari-web/app/views/main/admin/service_auto_start.js * (add) ambari-web/app/styles/circle-toggle-switch.less * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/controllers/main/admin/service_auto_start.js * (edit) ambari-web/app/routes/main.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/templates/main/admin/service_auto_start.hbs * (edit) ambari-web/test/controllers/main/admin/service_auto_start_test.js * (delete) ambari-web/app/views/main/admin/service_auto_start/component_auto_start.js * (edit) ambari-web/test/views/main/admin/service_auto_start_test.js * (delete) ambari-web/app/templates/main/admin/service_auto_start/component_auto_start.hbs > Service-auto start page update of UI > > > Key: AMBARI-22940 > URL: https://issues.apache.org/jira/browse/AMBARI-22940 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: auto-start-settings.png > > Time Spent: 50m > Remaining Estimate: 0h > > See screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22974) Ambari API should expose the nameserivceId for NAMENODE host component
[ https://issues.apache.org/jira/browse/AMBARI-22974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Endre Major reassigned AMBARI-22974: Assignee: Endre Major > Ambari API should expose the nameserivceId for NAMENODE host component > -- > > Key: AMBARI-22974 > URL: https://issues.apache.org/jira/browse/AMBARI-22974 > Project: Ambari > Issue Type: Technical task > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Endre Major >Assignee: Endre Major >Priority: Major > Fix For: 2.7.0 > > > The clusterId can be obtained with this call: http://104.196.73.142:50070/jmx > Look for MBean name Hadoop:service=NameNode,name=NameNodeInfo > And property: ClusterId > This needs to be exposed through Ambari API for the UI to utilize. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22974) Ambari API should expose the nameserivceId for NAMENODE host component
[ https://issues.apache.org/jira/browse/AMBARI-22974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Endre Major updated AMBARI-22974: - Issue Type: Technical task (was: Task) Parent: AMBARI-22916 > Ambari API should expose the nameserivceId for NAMENODE host component > -- > > Key: AMBARI-22974 > URL: https://issues.apache.org/jira/browse/AMBARI-22974 > Project: Ambari > Issue Type: Technical task > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Endre Major >Priority: Major > Fix For: 2.7.0 > > > The clusterId can be obtained with this call: http://104.196.73.142:50070/jmx > Look for MBean name Hadoop:service=NameNode,name=NameNodeInfo > And property: ClusterId > This needs to be exposed through Ambari API for the UI to utilize. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22974) Ambari API should expose the nameserivceId for NAMENODE host component
Endre Major created AMBARI-22974: Summary: Ambari API should expose the nameserivceId for NAMENODE host component Key: AMBARI-22974 URL: https://issues.apache.org/jira/browse/AMBARI-22974 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.7.0 Reporter: Endre Major Fix For: 2.7.0 The clusterId can be obtained with this call: http://104.196.73.142:50070/jmx Look for MBean name Hadoop:service=NameNode,name=NameNodeInfo And property: ClusterId This needs to be exposed through Ambari API for the UI to utilize. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22340) Remove Slider from Ambari stack definition of HDP 3.0
[ https://issues.apache.org/jira/browse/AMBARI-22340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-22340: Resolution: Fixed Status: Resolved (was: Patch Available) > Remove Slider from Ambari stack definition of HDP 3.0 > - > > Key: AMBARI-22340 > URL: https://issues.apache.org/jira/browse/AMBARI-22340 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22340.patch > > > Slider is no longer a service on it's own in HDP 3.0, it is a part of YARN. > So it should be removed from the stack definition. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22964) Add NameNode Federation wizard
[ https://issues.apache.org/jira/browse/AMBARI-22964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362096#comment-16362096 ] Hudson commented on AMBARI-22964: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8714 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8714/]) AMBARI-22964. Add NameNode Federation wizard (akovalenko) (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=3af5a0712e957b3a639666380719f51fa4d4b815]) * (add) ambari-web/app/controllers/main/admin/federation/step1_controller.js * (edit) ambari-web/app/views/main/service/item.js * (add) ambari-web/app/templates/main/admin/federation/step4.hbs * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/views.js * (add) ambari-web/app/views/main/admin/federation/step1_view.js * (add) ambari-web/app/controllers/main/admin/federation/step3_controller.js * (add) ambari-web/app/templates/main/admin/federation/wizard.hbs * (edit) ambari-web/app/models/host_component.js * (edit) ambari-web/app/routes/main.js * (edit) ambari-web/app/utils/db.js * (add) ambari-web/app/views/main/admin/federation/step3_view.js * (add) ambari-web/app/views/main/admin/federation/step4_view.js * (edit) ambari-web/test/models/service_test.js * (add) ambari-web/app/views/main/admin/federation/wizard_view.js * (edit) ambari-web/app/controllers/main/admin/highAvailability_controller.js * (add) ambari-web/app/routes/namenode_federation_routes.js * (add) ambari-web/app/views/main/admin/federation/step2_view.js * (edit) ambari-web/app/controllers/main/service/item.js * (add) ambari-web/app/controllers/main/admin/federation/step2_controller.js * (edit) ambari-web/app/models/service.js * (add) ambari-web/app/templates/main/admin/federation/step3.hbs * (add) ambari-web/app/templates/main/admin/federation/step1.hbs * (edit) ambari-web/app/controllers.js * (add) ambari-web/app/controllers/main/admin/federation/step4_controller.js * (add) ambari-web/app/controllers/main/admin/federation/wizard_controller.js > Add NameNode Federation wizard > -- > > Key: AMBARI-22964 > URL: https://issues.apache.org/jira/browse/AMBARI-22964 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Basic implementation of NN Federation wizard. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22940) Service-auto start page update of UI
[ https://issues.apache.org/jira/browse/AMBARI-22940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362051#comment-16362051 ] Andrii Tkach commented on AMBARI-22940: --- committed to trunk > Service-auto start page update of UI > > > Key: AMBARI-22940 > URL: https://issues.apache.org/jira/browse/AMBARI-22940 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: auto-start-settings.png > > Time Spent: 50m > Remaining Estimate: 0h > > See screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22940) Service-auto start page update of UI
[ https://issues.apache.org/jira/browse/AMBARI-22940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach resolved AMBARI-22940. --- Resolution: Fixed > Service-auto start page update of UI > > > Key: AMBARI-22940 > URL: https://issues.apache.org/jira/browse/AMBARI-22940 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: auto-start-settings.png > > Time Spent: 50m > Remaining Estimate: 0h > > See screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22966) ambari-agent fails to start
[
https://issues.apache.org/jira/browse/AMBARI-22966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22966:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> ambari-agent fails to start
> ---
>
> Key: AMBARI-22966
> URL: https://issues.apache.org/jira/browse/AMBARI-22966
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
>Affects Versions: 2.6.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> ambari-agent start gives the following exception:
> {code}
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/main.py", line 92, in
> import ProcessHelper
> File "/usr/lib/ambari-agent/lib/ambari_agent/ProcessHelper.py", line 25, in
>
> from ambari_commons.shell import getTempFiles
> File "/usr/lib/ambari-agent/lib/ambari_commons/shell.py", line 30, in
>
> from resource_management.core import sudo
> File "/usr/lib/ambari-agent/lib/resource_management/__init__.py", line 23,
> in
> from resource_management.libraries import *
> File "/usr/lib/ambari-agent/lib/resource_management/libraries/__init__.py",
> line 23, in
> from resource_management.libraries.functions import *
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/__init__.py",
> line 48, in
> from resource_management.libraries.functions.log_process_information import *
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/log_process_information.py",
> line 22, in
> from ambari_commons.shell import shellRunner
> ImportError: cannot import name shellRunner
> {code}
> Most likely because of a circular dependency that was added by AMBARI-22888.
> Removing the sudo import from shell makes the problem go away.
> sudo -> resource_management.libraries.* ->
> resource_management.libraries.functions.* ->
> esource_management.libraries.functions.log_process_information.* ->
> ambari_commons.shell.shellRunner -> resource_management.core.sudo
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22906) Not able to register new HDP version after upgrading to Ambari2.6.1
[ https://issues.apache.org/jira/browse/AMBARI-22906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362048#comment-16362048 ] Hudson commented on AMBARI-22906: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8713 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8713/]) AMBARI-22906. Not able to register new HDP version after upgrading to (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=9720c68060aaf3189ef4f3ea358f1eec6bfce1d2]) * (edit) ambari-server/src/main/python/ambari_server/serverUpgrade.py * (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py > Not able to register new HDP version after upgrading to Ambari2.6.1 > --- > > Key: AMBARI-22906 > URL: https://issues.apache.org/jira/browse/AMBARI-22906 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: amarnath reddy pappu >Assignee: Andrew Onischuk >Priority: Blocker > Labels: pull-request-available > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22906.patch, AMBARI-22906.patch, > AMBARI-22906.patch, AMBARI-22906.patch, AMBARI-22906.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > > Steps to reproduce the issue > 1. Install Ambari2.5.x and install HDP on that. > 2. Now Upgrade ambari to 2.6.1 version. > 3. Now try to register HDP version with VDF file - Save button is not enabled > (also UI does not load repo URLs and) > 4. In JS it fails with below error > Cannot read property 'gpl.license.accepted' of undefined > What is expected: UI should properly show the message that gpl license needs > to be enabled. also Upgrade should take care of adding this property if it is > needed. > Workaround for this is : add "gpl.license.accepted=true" to ambari.proeprties > and then restart should fix the problem -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22973) 'Assign Slaves & Clients' page is empty when 3 or more services selected while adding multiple services
[
https://issues.apache.org/jira/browse/AMBARI-22973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22973:
Labels: pull-request-available (was: )
> 'Assign Slaves & Clients' page is empty when 3 or more services selected
> while adding multiple services
> ---
>
> Key: AMBARI-22973
> URL: https://issues.apache.org/jira/browse/AMBARI-22973
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> STR:
> # In the cluster, click add service
> # Select the remaining services to be added (Pig, Knox, Logsearch,
> RangerKMS, Zeppelin) and click Next
> # Accept Defaults and Select Next on Assign Masters page
> In the Assign Slaves and Clients page, there is an empty page.
> Adding services individually does not hit this issue.
> There are some error logs in the console:
> {code:java}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at app.js:38709
> at Array.forEach ()
> at app.js:38707
> at Class.forEach (vendor.js:18038)
> at app.js:38706
> at Array.forEach ()
> at Class.enableCheckboxesForDependentComponents (app.js:38705)
> at Class.renderSlaves (app.js:38671)
> at Class.render (app.js:38646)
> at Class.loadStep (app.js:38569)
> {code}
> Calls to server made during while navigating to Assign Slaves and Clients page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22966) ambari-agent fails to start
[
https://issues.apache.org/jira/browse/AMBARI-22966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22966:
-
Status: Patch Available (was: In Progress)
> ambari-agent fails to start
> ---
>
> Key: AMBARI-22966
> URL: https://issues.apache.org/jira/browse/AMBARI-22966
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
>Affects Versions: 2.6.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> ambari-agent start gives the following exception:
> {code}
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/main.py", line 92, in
> import ProcessHelper
> File "/usr/lib/ambari-agent/lib/ambari_agent/ProcessHelper.py", line 25, in
>
> from ambari_commons.shell import getTempFiles
> File "/usr/lib/ambari-agent/lib/ambari_commons/shell.py", line 30, in
>
> from resource_management.core import sudo
> File "/usr/lib/ambari-agent/lib/resource_management/__init__.py", line 23,
> in
> from resource_management.libraries import *
> File "/usr/lib/ambari-agent/lib/resource_management/libraries/__init__.py",
> line 23, in
> from resource_management.libraries.functions import *
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/__init__.py",
> line 48, in
> from resource_management.libraries.functions.log_process_information import *
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/log_process_information.py",
> line 22, in
> from ambari_commons.shell import shellRunner
> ImportError: cannot import name shellRunner
> {code}
> Most likely because of a circular dependency that was added by AMBARI-22888.
> Removing the sudo import from shell makes the problem go away.
> sudo -> resource_management.libraries.* ->
> resource_management.libraries.functions.* ->
> esource_management.libraries.functions.log_process_information.* ->
> ambari_commons.shell.shellRunner -> resource_management.core.sudo
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22973) 'Assign Slaves & Clients' page is empty when 3 or more services selected while adding multiple services
Andrii Tkach created AMBARI-22973:
-
Summary: 'Assign Slaves & Clients' page is empty when 3 or more
services selected while adding multiple services
Key: AMBARI-22973
URL: https://issues.apache.org/jira/browse/AMBARI-22973
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Fix For: 2.7.0
STR:
# In the above cluster, click add service
# Select the remaining services to be added (Pig, Knox, Logsearch, RangerKMS,
Zeppelin) and click Next
# Accept Defaults and Select Next on Assign Masters page
In the Assign Slaves and Clients page, there is an empty page.
Adding services individually does not hit this issue.
There are some error logs in the console:
{code}
Uncaught TypeError: Cannot read property 'get' of undefined
at app.js:38709
at Array.forEach ()
at app.js:38707
at Class.forEach (vendor.js:18038)
at app.js:38706
at Array.forEach ()
at Class.enableCheckboxesForDependentComponents (app.js:38705)
at Class.renderSlaves (app.js:38671)
at Class.render (app.js:38646)
at Class.loadStep (app.js:38569)
{code}
Calls to server made during while navigating to Assign Slaves and Clients page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22973) 'Assign Slaves & Clients' page is empty when 3 or more services selected while adding multiple services
[
https://issues.apache.org/jira/browse/AMBARI-22973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-22973:
--
Description:
STR:
# In the cluster, click add service
# Select the remaining services to be added (Pig, Knox, Logsearch, RangerKMS,
Zeppelin) and click Next
# Accept Defaults and Select Next on Assign Masters page
In the Assign Slaves and Clients page, there is an empty page.
Adding services individually does not hit this issue.
There are some error logs in the console:
{code:java}
Uncaught TypeError: Cannot read property 'get' of undefined
at app.js:38709
at Array.forEach ()
at app.js:38707
at Class.forEach (vendor.js:18038)
at app.js:38706
at Array.forEach ()
at Class.enableCheckboxesForDependentComponents (app.js:38705)
at Class.renderSlaves (app.js:38671)
at Class.render (app.js:38646)
at Class.loadStep (app.js:38569)
{code}
Calls to server made during while navigating to Assign Slaves and Clients page
was:
STR:
# In the above cluster, click add service
# Select the remaining services to be added (Pig, Knox, Logsearch, RangerKMS,
Zeppelin) and click Next
# Accept Defaults and Select Next on Assign Masters page
In the Assign Slaves and Clients page, there is an empty page.
Adding services individually does not hit this issue.
There are some error logs in the console:
{code}
Uncaught TypeError: Cannot read property 'get' of undefined
at app.js:38709
at Array.forEach ()
at app.js:38707
at Class.forEach (vendor.js:18038)
at app.js:38706
at Array.forEach ()
at Class.enableCheckboxesForDependentComponents (app.js:38705)
at Class.renderSlaves (app.js:38671)
at Class.render (app.js:38646)
at Class.loadStep (app.js:38569)
{code}
Calls to server made during while navigating to Assign Slaves and Clients page
> 'Assign Slaves & Clients' page is empty when 3 or more services selected
> while adding multiple services
> ---
>
> Key: AMBARI-22973
> URL: https://issues.apache.org/jira/browse/AMBARI-22973
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.7.0
>
>
> STR:
> # In the cluster, click add service
> # Select the remaining services to be added (Pig, Knox, Logsearch,
> RangerKMS, Zeppelin) and click Next
> # Accept Defaults and Select Next on Assign Masters page
> In the Assign Slaves and Clients page, there is an empty page.
> Adding services individually does not hit this issue.
> There are some error logs in the console:
> {code:java}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at app.js:38709
> at Array.forEach ()
> at app.js:38707
> at Class.forEach (vendor.js:18038)
> at app.js:38706
> at Array.forEach ()
> at Class.enableCheckboxesForDependentComponents (app.js:38705)
> at Class.renderSlaves (app.js:38671)
> at Class.render (app.js:38646)
> at Class.loadStep (app.js:38569)
> {code}
> Calls to server made during while navigating to Assign Slaves and Clients page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22906) Not able to register new HDP version after upgrading to Ambari2.6.1
[ https://issues.apache.org/jira/browse/AMBARI-22906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362033#comment-16362033 ] Hudson commented on AMBARI-22906: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #604 (See [https://builds.apache.org/job/Ambari-branch-2.6/604/]) AMBARI-22906. Not able to register new HDP version after upgrading to (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=4ed6a458ccae533c810529e2c6b6165a6bac427d]) * (edit) ambari-server/src/main/python/ambari_server/serverUpgrade.py * (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py > Not able to register new HDP version after upgrading to Ambari2.6.1 > --- > > Key: AMBARI-22906 > URL: https://issues.apache.org/jira/browse/AMBARI-22906 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: amarnath reddy pappu >Assignee: Andrew Onischuk >Priority: Blocker > Labels: pull-request-available > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22906.patch, AMBARI-22906.patch, > AMBARI-22906.patch, AMBARI-22906.patch, AMBARI-22906.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > > Steps to reproduce the issue > 1. Install Ambari2.5.x and install HDP on that. > 2. Now Upgrade ambari to 2.6.1 version. > 3. Now try to register HDP version with VDF file - Save button is not enabled > (also UI does not load repo URLs and) > 4. In JS it fails with below error > Cannot read property 'gpl.license.accepted' of undefined > What is expected: UI should properly show the message that gpl license needs > to be enabled. also Upgrade should take care of adding this property if it is > needed. > Workaround for this is : add "gpl.license.accepted=true" to ambari.proeprties > and then restart should fix the problem -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22964) Add NameNode Federation wizard
[ https://issues.apache.org/jira/browse/AMBARI-22964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-22964: - Status: Patch Available (was: Open) committed to trunk > Add NameNode Federation wizard > -- > > Key: AMBARI-22964 > URL: https://issues.apache.org/jira/browse/AMBARI-22964 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Basic implementation of NN Federation wizard. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22964) Add NameNode Federation wizard
[ https://issues.apache.org/jira/browse/AMBARI-22964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-22964: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add NameNode Federation wizard > -- > > Key: AMBARI-22964 > URL: https://issues.apache.org/jira/browse/AMBARI-22964 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Basic implementation of NN Federation wizard. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22906) Not able to register new HDP version after upgrading to Ambari2.6.1
[ https://issues.apache.org/jira/browse/AMBARI-22906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk reassigned AMBARI-22906: Assignee: Andrew Onischuk > Not able to register new HDP version after upgrading to Ambari2.6.1 > --- > > Key: AMBARI-22906 > URL: https://issues.apache.org/jira/browse/AMBARI-22906 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: amarnath reddy pappu >Assignee: Andrew Onischuk >Priority: Blocker > Labels: pull-request-available > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22906.patch, AMBARI-22906.patch, > AMBARI-22906.patch, AMBARI-22906.patch, AMBARI-22906.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > > Steps to reproduce the issue > 1. Install Ambari2.5.x and install HDP on that. > 2. Now Upgrade ambari to 2.6.1 version. > 3. Now try to register HDP version with VDF file - Save button is not enabled > (also UI does not load repo URLs and) > 4. In JS it fails with below error > Cannot read property 'gpl.license.accepted' of undefined > What is expected: UI should properly show the message that gpl license needs > to be enabled. also Upgrade should take care of adding this property if it is > needed. > Workaround for this is : add "gpl.license.accepted=true" to ambari.proeprties > and then restart should fix the problem -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22906) Not able to register new HDP version after upgrading to Ambari2.6.1
[ https://issues.apache.org/jira/browse/AMBARI-22906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22906: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > Not able to register new HDP version after upgrading to Ambari2.6.1 > --- > > Key: AMBARI-22906 > URL: https://issues.apache.org/jira/browse/AMBARI-22906 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: amarnath reddy pappu >Assignee: Andrew Onischuk >Priority: Blocker > Labels: pull-request-available > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22906.patch, AMBARI-22906.patch, > AMBARI-22906.patch, AMBARI-22906.patch, AMBARI-22906.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > > Steps to reproduce the issue > 1. Install Ambari2.5.x and install HDP on that. > 2. Now Upgrade ambari to 2.6.1 version. > 3. Now try to register HDP version with VDF file - Save button is not enabled > (also UI does not load repo URLs and) > 4. In JS it fails with below error > Cannot read property 'gpl.license.accepted' of undefined > What is expected: UI should properly show the message that gpl license needs > to be enabled. also Upgrade should take care of adding this property if it is > needed. > Workaround for this is : add "gpl.license.accepted=true" to ambari.proeprties > and then restart should fix the problem -- This message was sent by Atlassian JIRA (v7.6.3#76005)
