[jira] [Created] (AMBARI-22497) Disk usage is not updated
Dmytro Grinenko created AMBARI-22497: Summary: Disk usage is not updated Key: AMBARI-22497 URL: https://issues.apache.org/jira/browse/AMBARI-22497 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: 2.6.1 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Priority: Critical Fix For: 2.6.1 Ambari Agent sends disk usage info once in every minute. Ambari Server apparently ignores this and only uses the initial disk report. STR: Create dummy /usr/local/sbin/df script that does nothing (ensure that this directory precedes in $PATH the directory where the real df resides) Start Ambari Agent and Server Create cluster via blueprint Request Hosts/disk_info via API Delete dummy timeout script Wait 2 minutes Request Hosts/disk_info via API Expected result: disk info is updated in server once the "transient failure" of df is resolved Actual result: disk info continues to be empty -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22496) Admin View - Manage Versions page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22496: Component/s: (was: ambari-web) ambari-admin > Admin View - Manage Versions page should show HDP-GPL repo if necessary > --- > > Key: AMBARI-22496 > URL: https://issues.apache.org/jira/browse/AMBARI-22496 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22496.v0.br-feature.patch > > > Display HDP-GPL repo field under Repositories in Manage Versions of Admin > View only if the user agreed to the GPL license agreement during > ambari-server setup -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22496) Admin View - Manage Versions page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22496: Attachment: AMBARI-22496.v0.br-feature.patch > Admin View - Manage Versions page should show HDP-GPL repo if necessary > --- > > Key: AMBARI-22496 > URL: https://issues.apache.org/jira/browse/AMBARI-22496 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22496.v0.br-feature.patch > > > Display HDP-GPL repo field under Repositories in Manage Versions of Admin > View only if the user agreed to the GPL license agreement during > ambari-server setup -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22496) Admin View - Manage Versions page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22496: Status: Patch Available (was: In Progress) > Admin View - Manage Versions page should show HDP-GPL repo if necessary > --- > > Key: AMBARI-22496 > URL: https://issues.apache.org/jira/browse/AMBARI-22496 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22496.v0.br-feature.patch > > > Display HDP-GPL repo field under Repositories in Manage Versions of Admin > View only if the user agreed to the GPL license agreement during > ambari-server setup -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22496) Admin View - Manage Versions page should show HDP-GPL repo if necessary
Vivek Ratnavel Subramanian created AMBARI-22496: --- Summary: Admin View - Manage Versions page should show HDP-GPL repo if necessary Key: AMBARI-22496 URL: https://issues.apache.org/jira/browse/AMBARI-22496 Project: Ambari Issue Type: Task Components: ambari-web Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.6.1 Display HDP-GPL repo field under Repositories in Manage Versions of Admin View only if the user agreed to the GPL license agreement during ambari-server setup -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22485) Allow Ambari to support non-kerberos SASL mechanisms for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-22485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yolanda M. Davis updated AMBARI-22485: -- Status: Patch Available (was: Open) > Allow Ambari to support non-kerberos SASL mechanisms for Kafka > -- > > Key: AMBARI-22485 > URL: https://issues.apache.org/jira/browse/AMBARI-22485 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.0 >Reporter: Yolanda M. Davis >Assignee: Yolanda M. Davis > Attachments: AMBARI-22485.patch, AMBARI-22485_branch-2.6.patch > > > Currently AMBARI support's SASL and SSL as the security options for Kafka. > Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other > mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP > system into Kafka. > Also another important option is SASL_SSL. > We need to expose necessary configs in Ambari to enable these mechanisms for > users. > Ambari should allow users to not only configure Kafka for non-kerberos based > SASL mechanisms, but also ensure that jaas configuration files are written > when these options are provided (as opposed to only writing those files when > kerberos has been enabled).. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22485) Allow Ambari to support non-kerberos SASL mechanisms for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-22485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261916#comment-16261916 ] Yolanda M. Davis commented on AMBARI-22485: --- Kafka supports *PLAINTEXT, SSL, SASL_PLAINTEXT(PLAINTEXTSASL), SASL_SSL* protocols to communicate with Kafka brokers. Brokers can be configured with all these protocols at the same using_ "listeners" _config property. listeners=PLAINTEXT://host.name:port1,SASL_PLAINTEXT://host.name:port2,SSL://host.name:port3,SASL_SSL://host.name:port4 *PLAINTEXT* This is the default protocol. No special configuration is required. This support is available in Ambari. *SSL* This can be configured in Ambari. Required configs are documented in https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.2/bk_security/content/ch_wire-kafka.html *SASL_PLAINTEXT(PLAINTEXTSASL)* Under SASL protocol, Kafka supports below given SASL mechanisms SASL/GSSAPI (Kerberos) - [This is default mechanism) SASL/PLAIN SASL/SCRAM-SHA-256 SASL/SCRAM-SHA-512 Above mechanisms are configured using kafka_server_jaas.conf and below configs listeners sasl.enabled.mechanisms security.inter.broker.protocol sasl.mechanism.inter.broker.protocol Currently, on the kerberozied cluster, Ambari automates kafka_server_jaas.conf, configs for SASL/GSSAPI (Kerberos) mechanism and also pass below java system property to java runtime command. "-Djava.security.auth.login.config=/usr/hdf/current/kafka-broker/config/kafka_jaas.conf" For other mechanisms, we should support including kafka_server_jaas.conf in non-kerberozied environments. Enable below props to Custom Broker Section: sasl.enabled.mechanisms security.inter.broker.protocol sasl.mechanism.inter.broker.protocol *SASL_SSL* Above SASL mechanisms can be combined with SSL encryption. *THINGS TO DO:* 1. Write docs for configuring SASL/PLAIN, SASL/SCRAM-SHA-256, SASL/SCRAM-SHA-512 mechanisms, jaas conf files and configs 2. Enable below props to Custom Broker Section: sasl.enabled.mechanisms=GSSAPI security.inter.broker.protocol=PLAINTEXT sasl.mechanism.inter.broker.protocol=GSSAPI 3. Allow Ambari to pass kafka_server_jaas.conf on non-kerberozied cluster if listeners contains SASL_PLAINTEXT, SASL_SSL. We also need to pass kafka_client_jaas.conf files to kafka CLI scripts. 4. Resolve if any issues exist while enabling multiple listeners > Allow Ambari to support non-kerberos SASL mechanisms for Kafka > -- > > Key: AMBARI-22485 > URL: https://issues.apache.org/jira/browse/AMBARI-22485 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.0 >Reporter: Yolanda M. Davis >Assignee: Yolanda M. Davis > Attachments: AMBARI-22485.patch, AMBARI-22485_branch-2.6.patch > > > Currently AMBARI support's SASL and SSL as the security options for Kafka. > Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other > mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP > system into Kafka. > Also another important option is SASL_SSL. > We need to expose necessary configs in Ambari to enable these mechanisms for > users. > Ambari should allow users to not only configure Kafka for non-kerberos based > SASL mechanisms, but also ensure that jaas configuration files are written > when these options are provided (as opposed to only writing those files when > kerberos has been enabled).. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22485) Allow Ambari to support non-kerberos SASL mechanisms for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-22485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yolanda M. Davis updated AMBARI-22485: -- Description: Currently AMBARI support's SASL and SSL as the security options for Kafka. Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP system into Kafka. Also another important option is SASL_SSL. We need to expose necessary configs in Ambari to enable these mechanisms for users. Ambari should allow users to not only configure Kafka for non-kerberos based SASL mechanisms, but also ensure that jaas configuration files are written when these options are provided (as opposed to only writing those files when kerberos has been enabled).. was: Currently AMBARI support's SASL and SSL as the security options for Kafka. Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP system into Kafka. Also another important option is SASL_SSL. We need to expose necessary configs in Ambari to enable these mechanisms for users. > Allow Ambari to support non-kerberos SASL mechanisms for Kafka > -- > > Key: AMBARI-22485 > URL: https://issues.apache.org/jira/browse/AMBARI-22485 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.0 >Reporter: Yolanda M. Davis >Assignee: Yolanda M. Davis > Attachments: AMBARI-22485.patch, AMBARI-22485_branch-2.6.patch > > > Currently AMBARI support's SASL and SSL as the security options for Kafka. > Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other > mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP > system into Kafka. > Also another important option is SASL_SSL. > We need to expose necessary configs in Ambari to enable these mechanisms for > users. > Ambari should allow users to not only configure Kafka for non-kerberos based > SASL mechanisms, but also ensure that jaas configuration files are written > when these options are provided (as opposed to only writing those files when > kerberos has been enabled).. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22485) Allow Ambari to support non-kerberos SASL mechanisms for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-22485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yolanda M. Davis updated AMBARI-22485: -- Attachment: AMBARI-22485_branch-2.6.patch AMBARI-22485.patch > Allow Ambari to support non-kerberos SASL mechanisms for Kafka > -- > > Key: AMBARI-22485 > URL: https://issues.apache.org/jira/browse/AMBARI-22485 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.0 >Reporter: Yolanda M. Davis >Assignee: Yolanda M. Davis > Attachments: AMBARI-22485.patch, AMBARI-22485_branch-2.6.patch > > > Currently AMBARI support's SASL and SSL as the security options for Kafka. > Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other > mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP > system into Kafka. > Also another important option is SASL_SSL. > We need to expose necessary configs in Ambari to enable these mechanisms for > users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22485) Allow Ambari to support non-kerberos SASL mechanisms for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-22485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yolanda M. Davis updated AMBARI-22485: -- Attachment: (was: AMBARI-22485-branch-2.6.patch) > Allow Ambari to support non-kerberos SASL mechanisms for Kafka > -- > > Key: AMBARI-22485 > URL: https://issues.apache.org/jira/browse/AMBARI-22485 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.0 >Reporter: Yolanda M. Davis >Assignee: Yolanda M. Davis > Attachments: AMBARI-22485.patch, AMBARI-22485_branch-2.6.patch > > > Currently AMBARI support's SASL and SSL as the security options for Kafka. > Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other > mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP > system into Kafka. > Also another important option is SASL_SSL. > We need to expose necessary configs in Ambari to enable these mechanisms for > users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22495) Installer - Select Version page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22495: Attachment: AMBARI-22495.v1.br-feature.patch > Installer - Select Version page should show HDP-GPL repo if necessary > - > > Key: AMBARI-22495 > URL: https://issues.apache.org/jira/browse/AMBARI-22495 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22495.v0.br-feature.patch, > AMBARI-22495.v1.br-feature.patch > > > Display HDP-GPL repo field under Repositories in Select Version step of > Installer only if user agrees to gpl license agreement -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22486) Conditionally Rebuild MapReduce and Tez Tarballs with LZO if Enabled
[ https://issues.apache.org/jira/browse/AMBARI-22486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-22486: - Attachment: AMBARI-22486.patch > Conditionally Rebuild MapReduce and Tez Tarballs with LZO if Enabled > > > Key: AMBARI-22486 > URL: https://issues.apache.org/jira/browse/AMBARI-22486 > Project: Ambari > Issue Type: Task >Affects Versions: 2.6.1 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22486.patch > > > If LZO is enabled and has been opted-in, then the Tez and MapReduce tarballs > should have LZO added to them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22486) Conditionally Rebuild MapReduce and Tez Tarballs with LZO if Enabled
[ https://issues.apache.org/jira/browse/AMBARI-22486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-22486: - Resolution: Fixed Status: Resolved (was: Patch Available) > Conditionally Rebuild MapReduce and Tez Tarballs with LZO if Enabled > > > Key: AMBARI-22486 > URL: https://issues.apache.org/jira/browse/AMBARI-22486 > Project: Ambari > Issue Type: Task >Affects Versions: 2.6.1 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22486.patch > > > If LZO is enabled and has been opted-in, then the Tez and MapReduce tarballs > should have LZO added to them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22486) Conditionally Rebuild MapReduce and Tez Tarballs with LZO if Enabled
[ https://issues.apache.org/jira/browse/AMBARI-22486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-22486: - Status: Patch Available (was: Open) > Conditionally Rebuild MapReduce and Tez Tarballs with LZO if Enabled > > > Key: AMBARI-22486 > URL: https://issues.apache.org/jira/browse/AMBARI-22486 > Project: Ambari > Issue Type: Task >Affects Versions: 2.6.1 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Fix For: 2.6.1 > > > If LZO is enabled and has been opted-in, then the Tez and MapReduce tarballs > should have LZO added to them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22495) Installer - Select Version page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22495: Status: Patch Available (was: In Progress) > Installer - Select Version page should show HDP-GPL repo if necessary > - > > Key: AMBARI-22495 > URL: https://issues.apache.org/jira/browse/AMBARI-22495 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22495.v0.br-feature.patch > > > Display HDP-GPL repo field under Repositories in Select Version step of > Installer only if user agrees to gpl license agreement -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22495) Installer - Select Version page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22495: Attachment: AMBARI-22495.v0.br-feature.patch > Installer - Select Version page should show HDP-GPL repo if necessary > - > > Key: AMBARI-22495 > URL: https://issues.apache.org/jira/browse/AMBARI-22495 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22495.v0.br-feature.patch > > > Display HDP-GPL repo field under Repositories in Select Version step of > Installer only if user agrees to gpl license agreement -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22495) Installer - Select Version page should show HDP-GPL repo if necessary
Vivek Ratnavel Subramanian created AMBARI-22495: --- Summary: Installer - Select Version page should show HDP-GPL repo if necessary Key: AMBARI-22495 URL: https://issues.apache.org/jira/browse/AMBARI-22495 Project: Ambari Issue Type: Task Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.6.1 Display HDP-GPL repo field under Repositories in Select Version step of Installer only if user agrees to gpl license agreement -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22495) Installer - Select Version page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22495: Component/s: ambari-web > Installer - Select Version page should show HDP-GPL repo if necessary > - > > Key: AMBARI-22495 > URL: https://issues.apache.org/jira/browse/AMBARI-22495 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > > Display HDP-GPL repo field under Repositories in Select Version step of > Installer only if user agrees to gpl license agreement -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22494) Unable to install the cluster
amarnath reddy pappu created AMBARI-22494:
-
Summary: Unable to install the cluster
Key: AMBARI-22494
URL: https://issues.apache.org/jira/browse/AMBARI-22494
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.0
Reporter: amarnath reddy pappu
Customer has installed Ambari 2.6 and trying to install the cluster. in the
hosts page it keeps loading for hostcheck results and never loads/enables Next
button.
It fails out with JS error like below,
{noformat}
##
Uncaught TypeError: _hostPackagesData.installedPackages.forEach is not a
function
at Class. (app.js:40783)
at Array.forEach ()
at Class.parseHostCheckWarnings (app.js:40746)
at Class.getHostInfoSuccessCallback (app.js:41079)
at Class.opt.success (app.js:177567)
at o (vendor.js:106)
at Object.fireWith [as resolveWith] (vendor.js:106)
at w (vendor.js:108)
##
{noformat}
If the API response is like below,
{noformat}
{
"Requests" : {
"id" : 18,
"inputs" :
"{\"jdk_location\":\"https://HOST:8443/resources/\",\"threshold\":\"20\",\"HAS_RESOURCE_FILTERS\":\"true\",\"check_execute_list\":\"last_agent_env_check,installed_packages,existing_repos,transparentHugePage\"}";,
"request_status" : "COMPLETED"
},
"tasks" : [
{
"Tasks" : {
"command_detail" : "check_host ACTIONEXECUTE",
"error_log" : "/var/lib/ambari-agent/data/errors-178.txt",
"host_name" : "host.net",
"id" : 178,
"status" : "COMPLETED",
"stderr" : "2017-11-20 15:53:40,844 - There was an unknown error while
checking installed packages and existing repositories: list index out of
range\nTraceback (most recent call last):\n File
\"/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py\", line 170,
in actionexecute\ninstalled_packages, repos =
self.execute_existing_repos_and_installed_packages_check(config)\n File
\"/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py\", line 233,
in execute_existing_repos_and_installed_packages_check\ninstalledPackages =
self.pkg_provider.all_installed_packages()\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
line 222, in all_installed_packages\nreturn
self._get_installed_packages(None)\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
line 157, in _get_installed_packages\npackages =
self._lookup_packages([AMBARI_SUDO_BINARY, \"yum\", \"list\", \"installed\"],
\"Installed Packages\")\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
line 191, in _lookup_packages\nif items[i + 2].find('@') ==
0:\nIndexError: list index out of range\nNo handlers could be found for logger
\"ambari_agent.HostCheckReportFileHandler\"\nTraceback (most recent call
last):\n File
\"/usr/lib/python2.6/site-packages/ambari_agent/HostCheckReportFileHandler.py\",
line 74, in writeHostChecksCustomActionsFile\n
items.append(itemDetail['name'])\nTypeError: string indices must be integers,
not str",
"stdout" : "2017-11-20 15:53:39,422 - Host checks started.\n2017-11-20
15:53:39,422 - Check execute list:
last_agent_env_check,installed_packages,existing_repos,transparentHugePage\n2017-11-20
15:53:39,422 - Last Agent Env check started.\n2017-11-20 15:53:39,469 - Last
Agent Env check completed successfully.\n2017-11-20 15:53:39,469 - Installed
packages and existing repos checks started.\n2017-11-20 15:53:40,844 - There
was an unknown error while checking installed packages and existing
repositories: list index out of range\nTraceback (most recent call last):\n
File \"/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py\", line
170, in actionexecute\ninstalled_packages, repos =
self.execute_existing_repos_and_installed_packages_check(config)\n File
\"/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py\", line 233,
in execute_existing_repos_and_installed_packages_check\ninstalledPackages =
self.pkg_provider.all_installed_packages()\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
line 222, in all_installed_packages\nreturn
self._get_installed_packages(None)\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
line 157, in _get_installed_packages\npackages =
self._lookup_packages([AMBARI_SUDO_BINARY, \"yum\", \"list\", \"installed\"],
\"Installed Packages\")\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
line 191, in _lookup_packages\nif items[i + 2].find('@') ==
0:\nIndexError: list index out of range\n2017-11-20 15:53:40,845 - Transparent
huge page check started.\n2017-11-20 15:53:40,846 - Transparent huge page check
[jira] [Commented] (AMBARI-22492) A bad WebHDFS request is issued when starting Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-22492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261665#comment-16261665
]
David Tucker commented on AMBARI-22492:
---
This bug is not obvious because of HDFS-12846.
> A bad WebHDFS request is issued when starting Hive Metastore
>
>
> Key: AMBARI-22492
> URL: https://issues.apache.org/jira/browse/AMBARI-22492
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: David Tucker
>
> When deploying a cluster with Hive (1.2.1000, in this case), Ambari issues an
> incorrect WebHDFS request:
> {code}
> 2017-11-20 20:21:21,839 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X GET
> '"'"'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1?op=GETFILESTATUS&user.name=hdfs'"'"'
> 1>/tmp/tmpzipnFe 2>/tmp/tmpbGajx_''] {'logoutput': None, 'quiet': False}
> {code}
> That command should be:
> {code}
> curl -sS -L -w '%{http_code}' -X GET
> 'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1/?op=GETFILESTATUS&user.name=hdfs'
> {code}
> (Note the / after v1.)
> On Apache, this results in a FileNotFoundException (404); however, this
> causes problems with OneFS which returns an IllegalArgumentException (400)
> and prevents the Metastore from starting.
> Here is the full traceback:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 203, in
>HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
>method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 54, in start
>self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 120, in locking_configure
>original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 72, in configure
>hive(name = 'metastore')
> 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/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 343, in hive
>mode = 01777)
> 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/libraries/providers/hdfs_resource.py",
> line 604, in action_create_on_execute
>self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 601, in action_delayed
>self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 328, in action_delayed
>self._assert_valid()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 287, in _assert_valid
>self.target_status = self._get_file_status(target)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 430, in _get_file_status
>list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET',
> ignore_status_codes=['404'], assertable_result=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 177, in run_command
>return self._run_command(*args, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 248, in _run_command
>raise WebHDFSCallException(err_msg, result_dict)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22493) Fix build for test classes in feature branch
[ https://issues.apache.org/jira/browse/AMBARI-22493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-22493: --- Attachment: AMBARI-22493.patch > Fix build for test classes in feature branch > > > Key: AMBARI-22493 > URL: https://issues.apache.org/jira/browse/AMBARI-22493 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22493.patch > > > First step, we need to fix build process for test classes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22493) Fix build for test classes in feature branch
[ https://issues.apache.org/jira/browse/AMBARI-22493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-22493: --- Status: Patch Available (was: Open) > Fix build for test classes in feature branch > > > Key: AMBARI-22493 > URL: https://issues.apache.org/jira/browse/AMBARI-22493 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22493.patch > > > First step, we need to fix build process for test classes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22493) Fix build for test classes in feature branch
Vitaly Brodetskyi created AMBARI-22493: -- Summary: Fix build for test classes in feature branch Key: AMBARI-22493 URL: https://issues.apache.org/jira/browse/AMBARI-22493 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Critical Fix For: 3.0.0 First step, we need to fix build process for test classes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22492) A bad WebHDFS request is issued when starting Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-22492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Tucker updated AMBARI-22492:
--
Description:
When deploying a cluster with Hive (1.2.1000, in this case), Ambari issues an
incorrect WebHDFS request:
{code}
2017-11-20 20:21:21,839 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c 'curl
-sS -L -w '"'"'%{http_code}'"'"' -X GET
'"'"'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1?op=GETFILESTATUS&user.name=hdfs'"'"'
1>/tmp/tmpzipnFe 2>/tmp/tmpbGajx_''] {'logoutput': None, 'quiet': False}
{code}
That command should be:
{code}
curl -sS -L -w '%{http_code}' -X GET
'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1/?op=GETFILESTATUS&user.name=hdfs'
{code}
(Note the / after v1.)
On Apache, this results in a FileNotFoundException (404); however, this causes
problems with OneFS which returns an IllegalArgumentException (400) and
prevents the Metastore from starting.
Here is the full traceback:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
line 203, in
HiveMetastore().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 367, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
line 54, in start
self.configure(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 120, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
line 72, in configure
hive(name = 'metastore')
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/HIVE/0.12.0.2.0/package/scripts/hive.py",
line 343, in hive
mode = 01777)
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/libraries/providers/hdfs_resource.py",
line 604, in action_create_on_execute
self.action_delayed("create")
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 601, in action_delayed
self.get_hdfs_resource_executor().action_delayed(action_name, self)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 328, in action_delayed
self._assert_valid()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 287, in _assert_valid
self.target_status = self._get_file_status(target)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 430, in _get_file_status
list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET',
ignore_status_codes=['404'], assertable_result=False)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 177, in run_command
return self._run_command(*args, **kwargs)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 248, in _run_command
raise WebHDFSCallException(err_msg, result_dict)
{code}
was:
When deploying a cluster with Hive (1.2.1000, in this case), Ambari issues an
incorrect WebHDFS request:
{code}
2017-11-20 20:21:21,839 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c 'curl
-sS -L -w '"'"'%{http_code}'"'"' -X GET
'"'"'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1?op=GETFILESTATUS&user.name=hdfs'"'"'
1>/tmp/tmpzipnFe 2>/tmp/tmpbGajx_''] {'logoutput': None, 'quiet': False}
{code}
That command should be:
{code}
curl -sS -L -w '%{http_code}' -X GET
'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1/?op=GETFILESTATUS&user.name=hdfs'
{code}
(Note the / after v1.)
On Apache, this results in a FileNotFoundException (404); however, this causes
problems with OneFS which returns an IllegalArgumentException (400) and
prevents the Metastore from starting.
> A bad WebHDFS request is issued when starting Hive Metastore
>
>
> Key: AMBARI-22492
> URL: https://issues.apache.org/jira/browse/AMBARI-22492
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: David Tucker
>
> When deploying a cluster with Hive (1.2.1000,
[jira] [Created] (AMBARI-22492) A bad WebHDFS request is issued when starting Hive Metastore
David Tucker created AMBARI-22492:
-
Summary: A bad WebHDFS request is issued when starting Hive
Metastore
Key: AMBARI-22492
URL: https://issues.apache.org/jira/browse/AMBARI-22492
Project: Ambari
Issue Type: Bug
Affects Versions: 2.6.0
Reporter: David Tucker
When deploying a cluster with Hive (1.2.1000, in this case), Ambari issues an
incorrect WebHDFS request:
{code}
2017-11-20 20:21:21,839 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c 'curl
-sS -L -w '"'"'%{http_code}'"'"' -X GET
'"'"'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1?op=GETFILESTATUS&user.name=hdfs'"'"'
1>/tmp/tmpzipnFe 2>/tmp/tmpbGajx_''] {'logoutput': None, 'quiet': False}
{code}
That command should be:
{code}
curl -sS -L -w '%{http_code}' -X GET
'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1/?op=GETFILESTATUS&user.name=hdfs'
{code}
(Note the / after v1.)
On Apache, this results in a FileNotFoundException (404); however, this causes
problems with OneFS which returns an IllegalArgumentException (400) and
prevents the Metastore from starting.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22489) Port AMBARI-22467 to BigInsight
[
https://issues.apache.org/jira/browse/AMBARI-22489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261139#comment-16261139
]
Hadoop QA commented on AMBARI-22489:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898646/AMBARI-22489.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12704//console
This message is automatically generated.
> Port AMBARI-22467 to BigInsight
> ---
>
> Key: AMBARI-22489
> URL: https://issues.apache.org/jira/browse/AMBARI-22489
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.6.1
>
> Attachments: AMBARI-22489.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[
https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261138#comment-16261138
]
Hadoop QA commented on AMBARI-22491:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898677/AMBARI-22491.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12703//console
This message is automatically generated.
> Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
> ---
>
> Key: AMBARI-22491
> URL: https://issues.apache.org/jira/browse/AMBARI-22491
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22491.patch
>
>
> When moving a Metrics Collector, a ZooKeeper Server is installed on the
> target host along with the Metrics Collector. This ZooKeeper Server is added
> and quorum can be upset in large clusters, and the customer was not intending
> to have a ZooKeeper server on the target directory.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[ https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261074#comment-16261074 ] Antonenko Alexander commented on AMBARI-22491: -- Committed to trunk and branch-2.6 > Moving Metrics Collector Forces ZooKeeper Server Install on Target Host > --- > > Key: AMBARI-22491 > URL: https://issues.apache.org/jira/browse/AMBARI-22491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22491.patch > > > When moving a Metrics Collector, a ZooKeeper Server is installed on the > target host along with the Metrics Collector. This ZooKeeper Server is added > and quorum can be upset in large clusters, and the customer was not intending > to have a ZooKeeper server on the target directory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[ https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261067#comment-16261067 ] Aleksandr Kovalenko commented on AMBARI-22491: -- +1 for the patch > Moving Metrics Collector Forces ZooKeeper Server Install on Target Host > --- > > Key: AMBARI-22491 > URL: https://issues.apache.org/jira/browse/AMBARI-22491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22491.patch > > > When moving a Metrics Collector, a ZooKeeper Server is installed on the > target host along with the Metrics Collector. This ZooKeeper Server is added > and quorum can be upset in large clusters, and the customer was not intending > to have a ZooKeeper server on the target directory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[
https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261037#comment-16261037
]
Hadoop QA commented on AMBARI-22491:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898677/AMBARI-22491.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12702//console
This message is automatically generated.
> Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
> ---
>
> Key: AMBARI-22491
> URL: https://issues.apache.org/jira/browse/AMBARI-22491
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22491.patch
>
>
> When moving a Metrics Collector, a ZooKeeper Server is installed on the
> target host along with the Metrics Collector. This ZooKeeper Server is added
> and quorum can be upset in large clusters, and the customer was not intending
> to have a ZooKeeper server on the target directory.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[
https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260972#comment-16260972
]
Hadoop QA commented on AMBARI-22491:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898677/AMBARI-22491.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12701//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12701//console
This message is automatically generated.
> Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
> ---
>
> Key: AMBARI-22491
> URL: https://issues.apache.org/jira/browse/AMBARI-22491
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22491.patch
>
>
> When moving a Metrics Collector, a ZooKeeper Server is installed on the
> target host along with the Metrics Collector. This ZooKeeper Server is added
> and quorum can be upset in large clusters, and the customer was not intending
> to have a ZooKeeper server on the target directory.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[ https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22491: - Attachment: AMBARI-22491.patch > Moving Metrics Collector Forces ZooKeeper Server Install on Target Host > --- > > Key: AMBARI-22491 > URL: https://issues.apache.org/jira/browse/AMBARI-22491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22491.patch > > > When moving a Metrics Collector, a ZooKeeper Server is installed on the > target host along with the Metrics Collector. This ZooKeeper Server is added > and quorum can be upset in large clusters, and the customer was not intending > to have a ZooKeeper server on the target directory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[ https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22491: - Status: Patch Available (was: Open) > Moving Metrics Collector Forces ZooKeeper Server Install on Target Host > --- > > Key: AMBARI-22491 > URL: https://issues.apache.org/jira/browse/AMBARI-22491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22491.patch > > > When moving a Metrics Collector, a ZooKeeper Server is installed on the > target host along with the Metrics Collector. This ZooKeeper Server is added > and quorum can be upset in large clusters, and the customer was not intending > to have a ZooKeeper server on the target directory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
Antonenko Alexander created AMBARI-22491: Summary: Moving Metrics Collector Forces ZooKeeper Server Install on Target Host Key: AMBARI-22491 URL: https://issues.apache.org/jira/browse/AMBARI-22491 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.2 Reporter: Antonenko Alexander Priority: Blocker Fix For: 2.6.1 When moving a Metrics Collector, a ZooKeeper Server is installed on the target host along with the Metrics Collector. This ZooKeeper Server is added and quorum can be upset in large clusters, and the customer was not intending to have a ZooKeeper server on the target directory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[ https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-22491: Assignee: Antonenko Alexander > Moving Metrics Collector Forces ZooKeeper Server Install on Target Host > --- > > Key: AMBARI-22491 > URL: https://issues.apache.org/jira/browse/AMBARI-22491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.6.1 > > > When moving a Metrics Collector, a ZooKeeper Server is installed on the > target host along with the Metrics Collector. This ZooKeeper Server is added > and quorum can be upset in large clusters, and the customer was not intending > to have a ZooKeeper server on the target directory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22488) RU: Restarting HiveServer2 on RU failed
[
https://issues.apache.org/jira/browse/AMBARI-22488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260908#comment-16260908
]
Hudson commented on AMBARI-22488:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #470 (See
[https://builds.apache.org/job/Ambari-branch-2.6/470/])
AMBARI-22488 RU: Restarting HiveServer2 on RU failed (dgrinenko) (hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a49be4af86484a55816cf8bf3aba06d24e176335])
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/copy_tarball.py
> RU: Restarting HiveServer2 on RU failed
> ---
>
> Key: AMBARI-22488
> URL: https://issues.apache.org/jira/browse/AMBARI-22488
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: 2.6.1
>
>
> STR:
> Deploy HDP 2.5.3.0-37 on Ambari
> Register and install HDP 2.6.4.0
> Perform RU.
> Result: Restarting HiveServer2 on RU failed
> {code}
> 2017-11-19 10:43:17,205 - Cannot copy tarball to HDFS because hive2 is not
> supported in stack HDP for this operation.
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 612, in
> HiveServerInteractive().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 946, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 91, in pre_upgrade_restart
> skip=params.sysprep_skip_copy_tarballs_hdfs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/copy_tarball.py",
> line 343, in copy_to_hdfs
> custom_source_file, custom_dest_file)
> ValueError: need more than 3 values to unpack
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22488) RU: Restarting HiveServer2 on RU failed
[
https://issues.apache.org/jira/browse/AMBARI-22488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22488:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed:
eecd8513a3..a49be4af86 branch-2.6 -> branch-2.6
> RU: Restarting HiveServer2 on RU failed
> ---
>
> Key: AMBARI-22488
> URL: https://issues.apache.org/jira/browse/AMBARI-22488
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: 2.6.1
>
>
> STR:
> Deploy HDP 2.5.3.0-37 on Ambari
> Register and install HDP 2.6.4.0
> Perform RU.
> Result: Restarting HiveServer2 on RU failed
> {code}
> 2017-11-19 10:43:17,205 - Cannot copy tarball to HDFS because hive2 is not
> supported in stack HDP for this operation.
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 612, in
> HiveServerInteractive().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 946, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 91, in pre_upgrade_restart
> skip=params.sysprep_skip_copy_tarballs_hdfs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/copy_tarball.py",
> line 343, in copy_to_hdfs
> custom_source_file, custom_dest_file)
> ValueError: need more than 3 values to unpack
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-22483) Add SAM StackFeatures to HDP StackFeatures - DB Storage Support
[
https://issues.apache.org/jira/browse/AMBARI-22483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yolanda M. Davis reassigned AMBARI-22483:
-
Assignee: Yolanda M. Davis
> Add SAM StackFeatures to HDP StackFeatures - DB Storage Support
> ---
>
> Key: AMBARI-22483
> URL: https://issues.apache.org/jira/browse/AMBARI-22483
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Fix For: 2.6.1
>
>
> {
> "name": "sam_db_file_storage",
> "description": "DB based file storage in SAM",
> "min_version": "2.6.3.0"
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22490) Uploading a Zero KB file to HDFS via File View Fails and no message is shown
[ https://issues.apache.org/jira/browse/AMBARI-22490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260636#comment-16260636 ] Akhil S Naik commented on AMBARI-22490: --- In Upload-File.js fileLoaded function , we are unncesarly checking for whether file is empty and not allow to upload to HDFS if the file is empty. This is not required as HDFS allowed empty file to be present i HDFS. Attached patch for the changes. > Uploading a Zero KB file to HDFS via File View Fails and no message is shown > > > Key: AMBARI-22490 > URL: https://issues.apache.org/jira/browse/AMBARI-22490 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: Akhil S Naik >Priority: Minor > Attachments: AMBARI-22490.patch > > > When We Try to upload a File of Zero KB ( empty File) File View Doesnt > upload the file. > But in HDFS i can upload the same file using command. > Ambari doesn't show any errors but yet the file is not uploaded. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22490) Uploading a Zero KB file to HDFS via File View Fails and no message is shown
[ https://issues.apache.org/jira/browse/AMBARI-22490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-22490: -- Attachment: AMBARI-22490.patch > Uploading a Zero KB file to HDFS via File View Fails and no message is shown > > > Key: AMBARI-22490 > URL: https://issues.apache.org/jira/browse/AMBARI-22490 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: Akhil S Naik >Priority: Minor > Attachments: AMBARI-22490.patch > > > When We Try to upload a File of Zero KB ( empty File) File View Doesnt > upload the file. > But in HDFS i can upload the same file using command. > Ambari doesn't show any errors but yet the file is not uploaded. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22490) Uploading a Zero KB file to HDFS via File View Fails and no message is shown
Akhil S Naik created AMBARI-22490: - Summary: Uploading a Zero KB file to HDFS via File View Fails and no message is shown Key: AMBARI-22490 URL: https://issues.apache.org/jira/browse/AMBARI-22490 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.2 Reporter: Akhil S Naik Priority: Minor When We Try to upload a File of Zero KB ( empty File) File View Doesnt upload the file. But in HDFS i can upload the same file using command. Ambari doesn't show any errors but yet the file is not uploaded. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22489) Port AMBARI-22467 to BigInsight
[
https://issues.apache.org/jira/browse/AMBARI-22489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260572#comment-16260572
]
Hadoop QA commented on AMBARI-22489:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898646/AMBARI-22489.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12700//console
This message is automatically generated.
> Port AMBARI-22467 to BigInsight
> ---
>
> Key: AMBARI-22489
> URL: https://issues.apache.org/jira/browse/AMBARI-22489
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.6.1
>
> Attachments: AMBARI-22489.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22489) Port AMBARI-22467 to BigInsight
[ https://issues.apache.org/jira/browse/AMBARI-22489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22489: - Attachment: AMBARI-22489.patch > Port AMBARI-22467 to BigInsight > --- > > Key: AMBARI-22489 > URL: https://issues.apache.org/jira/browse/AMBARI-22489 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22489.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22489) Port AMBARI-22467 to BigInsight
[ https://issues.apache.org/jira/browse/AMBARI-22489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22489: - Status: Patch Available (was: Open) > Port AMBARI-22467 to BigInsight > --- > > Key: AMBARI-22489 > URL: https://issues.apache.org/jira/browse/AMBARI-22489 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22489.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22489) Port AMBARI-22467 to BigInsight
[ https://issues.apache.org/jira/browse/AMBARI-22489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22489: - Summary: Port AMBARI-22467 to BigInsight (was: Port BUG-91794 to BigInsight) > Port AMBARI-22467 to BigInsight > --- > > Key: AMBARI-22489 > URL: https://issues.apache.org/jira/browse/AMBARI-22489 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22489.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22489) Port BUG-91794 to BigInsight
Andrew Onischuk created AMBARI-22489: Summary: Port BUG-91794 to BigInsight Key: AMBARI-22489 URL: https://issues.apache.org/jira/browse/AMBARI-22489 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.6.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22488) RU: Restarting HiveServer2 on RU failed
[
https://issues.apache.org/jira/browse/AMBARI-22488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22488:
-
Description:
STR:
Deploy HDP 2.5.3.0-37 on Ambari
Register and install HDP 2.6.4.0
Perform RU.
Result: Restarting HiveServer2 on RU failed
{code}
2017-11-19 10:43:17,205 - Cannot copy tarball to HDFS because hive2 is not
supported in stack HDP for this operation.
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
line 612, in
HiveServerInteractive().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 367, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 946, in restart
self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
line 91, in pre_upgrade_restart
skip=params.sysprep_skip_copy_tarballs_hdfs)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/copy_tarball.py",
line 343, in copy_to_hdfs
custom_source_file, custom_dest_file)
ValueError: need more than 3 values to unpack
{code}
was:
STR:
Deploy HDP 2.5.3.0-37 on Ambari 2.4.3.0
Enable NN HA
Upgrade Ambari to 2.6.1.0
Register and install HDP 2.6.4.0
Perform RU.
Result: Restarting HiveServer2 on RU failed
> RU: Restarting HiveServer2 on RU failed
> ---
>
> Key: AMBARI-22488
> URL: https://issues.apache.org/jira/browse/AMBARI-22488
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: 2.6.1
>
>
> STR:
> Deploy HDP 2.5.3.0-37 on Ambari
> Register and install HDP 2.6.4.0
> Perform RU.
> Result: Restarting HiveServer2 on RU failed
> {code}
> 2017-11-19 10:43:17,205 - Cannot copy tarball to HDFS because hive2 is not
> supported in stack HDP for this operation.
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 612, in
> HiveServerInteractive().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 946, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 91, in pre_upgrade_restart
> skip=params.sysprep_skip_copy_tarballs_hdfs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/copy_tarball.py",
> line 343, in copy_to_hdfs
> custom_source_file, custom_dest_file)
> ValueError: need more than 3 values to unpack
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22488) RU: Restarting HiveServer2 on RU failed
[ https://issues.apache.org/jira/browse/AMBARI-22488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-22488: - Status: Patch Available (was: In Progress) > RU: Restarting HiveServer2 on RU failed > --- > > Key: AMBARI-22488 > URL: https://issues.apache.org/jira/browse/AMBARI-22488 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.6.1 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Blocker > Fix For: 2.6.1 > > > STR: > Deploy HDP 2.5.3.0-37 on Ambari 2.4.3.0 > Enable NN HA > Upgrade Ambari to 2.6.1.0 > Register and install HDP 2.6.4.0 > Perform RU. > Result: Restarting HiveServer2 on RU failed -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22488) RU: Restarting HiveServer2 on RU failed
Dmytro Grinenko created AMBARI-22488: Summary: RU: Restarting HiveServer2 on RU failed Key: AMBARI-22488 URL: https://issues.apache.org/jira/browse/AMBARI-22488 Project: Ambari Issue Type: Bug Affects Versions: 2.6.1 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Priority: Blocker Fix For: 2.6.1 STR: Deploy HDP 2.5.3.0-37 on Ambari 2.4.3.0 Enable NN HA Upgrade Ambari to 2.6.1.0 Register and install HDP 2.6.4.0 Perform RU. Result: Restarting HiveServer2 on RU failed -- This message was sent by Atlassian JIRA (v6.4.14#64029)
