[jira] [Comment Edited] (AMBARI-13109) Verify that max logs parameter wouldn't cause premature region flush
[ https://issues.apache.org/jira/browse/AMBARI-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16120333#comment-16120333 ] Ted Yu edited comment on AMBARI-13109 at 9/22/17 2:42 AM: -- The max logs parameter plays an important role in preventing fragmentation in memstore. was (Author: yuzhih...@gmail.com): The max logs parameter plays an important role in preventing fragmentation in memstore . > Verify that max logs parameter wouldn't cause premature region flush > > > Key: AMBARI-13109 > URL: https://issues.apache.org/jira/browse/AMBARI-13109 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > For hbase, the following relationship should be maintained: > dfs.blocksize * 0.95 * hbase.regionserver.maxlogs (default 32) > > hbase.regionserver.global.memstore.upperLimit * HBASE_HEAPSIZE > The rationale is to avoid premature region flush due to log roll which is > triggered by insufficiently high max logs. > When user changes the values for max logs, memstore upper limit or max heap > size, we should verify that the above relationship is satisfied. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-13671) Ambari should check for duplicate config values
[ https://issues.apache.org/jira/browse/AMBARI-13671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-13671: Description: Using /#/main/services/HBASE/configs, I was able to save duplicate values for hbase.coprocessor.region.classes : org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint,org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint Ambari should check for duplicate config values. was: Using /#/main/services/HBASE/configs, I was able to save duplicate values for hbase.coprocessor.region.classes : org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint,org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint Ambari should check for duplicate config values. > Ambari should check for duplicate config values > --- > > Key: AMBARI-13671 > URL: https://issues.apache.org/jira/browse/AMBARI-13671 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu > > Using /#/main/services/HBASE/configs, I was able to save duplicate values for > hbase.coprocessor.region.classes : > org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint,org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint > Ambari should check for duplicate config values. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-14160) Ambari Slider View should pick up multiple versions of the same app package
[ https://issues.apache.org/jira/browse/AMBARI-14160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-14160: Description: I was validating some fix for Slider hbase with Gour. A new Slider hbase app package was built and moved to under: /var/lib/ambari-server/resources/apps We tried naming the new app package ending with -ted.zip -999.zip After 'ambari-server restart', the new app package was not picked up by Ambari. Ambari Slider View should be able to accommodate more than one version of app package. was: I was validating some fix for Slider hbase with Gour. A new Slider hbase app package was built and moved to under: /var/lib/ambari-server/resources/apps We tried naming the new app package ending with -ted.zip -999.zip After 'ambari-server restart', the new app package was not picked up by Ambari. Ambari Slider View should be able to accommodate more than one version of app package. > Ambari Slider View should pick up multiple versions of the same app package > --- > > Key: AMBARI-14160 > URL: https://issues.apache.org/jira/browse/AMBARI-14160 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > I was validating some fix for Slider hbase with Gour. > A new Slider hbase app package was built and moved to under: > /var/lib/ambari-server/resources/apps > We tried naming the new app package ending with -ted.zip -999.zip > After 'ambari-server restart', the new app package was not picked up by > Ambari. > Ambari Slider View should be able to accommodate more than one version of app > package. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-14163) zookeeper session timeout for hbase should take zookeeper tickTime into account
[ https://issues.apache.org/jira/browse/AMBARI-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-14163: Description: With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value of 1 min 40 seconds. The change was accepted. However, such timeout is not reachable (it is > 20 times tickTime). Ambari should detect such scenario and warn user. was: With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value of 1 min 40 seconds. The change was accepted. However, such timeout is not reachable (it is > 20 times tickTime). Ambari should detect such scenario and warn user. > zookeeper session timeout for hbase should take zookeeper tickTime into > account > --- > > Key: AMBARI-14163 > URL: https://issues.apache.org/jira/browse/AMBARI-14163 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu > > With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value > of 1 min 40 seconds. > The change was accepted. > However, such timeout is not reachable (it is > 20 times tickTime). > Ambari should detect such scenario and warn user. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-17346) Dependent components should be shutdown before stopping hdfs
[ https://issues.apache.org/jira/browse/AMBARI-17346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-17346: Description: Sometimes admin shuts down hdfs first, then hbase. By the time hbase is shutdown, no data can be persisted (including metadata). This results in large number of inconsistencies when hbase cluster is brought back up. Before hdfs is shutdown, the components dependent on hdfs should be shutdown first. was: Sometimes admin shuts down hdfs first, then hbase. By the time hbase is shutdown, no data can be persisted (including metadata). This results in large number of inconsistencies when hbase cluster is brought back up. Before hdfs is shutdown, the components dependent on hdfs should be shutdown first. > Dependent components should be shutdown before stopping hdfs > > > Key: AMBARI-17346 > URL: https://issues.apache.org/jira/browse/AMBARI-17346 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu > > Sometimes admin shuts down hdfs first, then hbase. > By the time hbase is shutdown, no data can be persisted (including metadata). > This results in large number of inconsistencies when hbase cluster is brought > back up. > Before hdfs is shutdown, the components dependent on hdfs should be shutdown > first. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-18528) Need a way to escape config values that contain $
[
https://issues.apache.org/jira/browse/AMBARI-18528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603928#comment-15603928
]
Ted Yu edited comment on AMBARI-18528 at 9/22/17 2:40 AM:
--
Escaping the dollar sign automatically is the desirable solution .
was (Author: yuzhih...@gmail.com):
Escaping the dollar sign automatically is the desirable solution.
> Need a way to escape config values that contain $
> -
>
> Key: AMBARI-18528
> URL: https://issues.apache.org/jira/browse/AMBARI-18528
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
> Labels: zookeeper
>
> We tried specifying auth_to_local in zookeeper env input box:
> {code}
> export SERVER_JVMFLAGS="$SERVER_JVMFLAGS
> -Dzookeeper.security.auth_to_local=RULE:[2:$1@$0](hb...@c.net)s/.*/hbase/
> -Djava.security.auth.login.config={{zk_server_jaas_file}}"
> {code}
> However, when zookeeper quorum starts, the rule got interrupted with
> zkServer.sh
> We should add the capability of specifying auth_to_local in Ambari UI
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22020) Setup tez ats loglevel to TASK_ATTEMPT to enable the filters.
[ https://issues.apache.org/jira/browse/AMBARI-22020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harish Jaiprakash updated AMBARI-22020: --- Attachment: AMBARI-22020.02.patch Recreating diff using without noprefix. > Setup tez ats loglevel to TASK_ATTEMPT to enable the filters. > - > > Key: AMBARI-22020 > URL: https://issues.apache.org/jira/browse/AMBARI-22020 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Harish Jaiprakash > Attachments: AMBARI-22020.01.patch, AMBARI-22020.02.patch > > > tez.history.logging.log.level should be TASK_ATTEMPT so that task kill filter > will work. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21954) Option to skip Host Check during the host add wizard
[ https://issues.apache.org/jira/browse/AMBARI-21954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175628#comment-16175628 ] Hudson commented on AMBARI-21954: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #270 (See [https://builds.apache.org/job/Ambari-branch-2.6/270/]) Revert "AMBARI-21954. Option to skip Host Check during the host add (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=412c7d2fc1d3db4dc8c594fbc9642a9ed9454749]) * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/templates/wizard/step2.hbs * (edit) ambari-web/app/views/wizard/step2_view.js * (edit) ambari-web/app/controllers/wizard/step3_controller.js * (edit) ambari-web/app/controllers/wizard/step2_controller.js * (edit) ambari-web/app/config.js > Option to skip Host Check during the host add wizard > > > Key: AMBARI-21954 > URL: https://issues.apache.org/jira/browse/AMBARI-21954 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.6.0 > > Attachments: AMBARI-21954_branch-2.6.patch, Skip Host Check > checkbox.png, Skip Host Check warning.png > > > some times we see customers were not able to add the new hosts to cluster. > message says it is checking for potential problems but it never gets > completed. because of that customers were not able to add the hosts. but > after that they were able to add the hosts with API call. This allows a the > administrator to skip Host Check after a due warning -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22030) OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object has no attribute 'upper' during EU
[
https://issues.apache.org/jira/browse/AMBARI-22030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175603#comment-16175603
]
Hudson commented on AMBARI-22030:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8119 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8119/])
AMBARI-22030. OOZIE/OOZIE_SERVER restart failed saying AttributeError: (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5d5f9749e82bf815a1c8f82f090b769421d39949])
* (delete)
ambari-common/src/main/python/resource_management/libraries/functions/copy_tarball.py.rej
> OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object
> has no attribute 'upper' during EU
> -
>
> Key: AMBARI-22030
> URL: https://issues.apache.org/jira/browse/AMBARI-22030
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22030.patch
>
>
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 150, in
> OozieServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 327, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 879, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 123, in pre_upgrade_restart
> OozieUpgrade.prepare_libext_directory(upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py",
> line 94, in prepare_libext_directory
> source_ext_zip_paths = oozie.get_oozie_ext_zip_source_paths(upgrade_type,
> params)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
> line 230, in get_oozie_ext_zip_source_paths
> source_ext_js_path = "/usr/share/" + params.source_stack_name.upper() +
> "-oozie/" + params.ext_js_file
> AttributeError: 'NoneType' object has no attribute 'upper'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21686) Implement a test driver that provides a set of metric series with different kinds of metric behavior.
[ https://issues.apache.org/jira/browse/AMBARI-21686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21686: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-3.0-ams. > Implement a test driver that provides a set of metric series with different > kinds of metric behavior. > - > > Key: AMBARI-21686 > URL: https://issues.apache.org/jira/browse/AMBARI-21686 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 3.0.0 > > Attachments: AMBARI-21686.patch, Dual band Series.png, Monotonic > Series.png, Normal Series with outliers.png, Steady Series with a turbulent > period.png, Step Series.png, Uniform Series with outliers.png > > > * Uniform distributed series with some outliers. > * Normally distributed series with some outliers. > * Gradually increasing / decreasing series. (Monotonic Series) > * Step Function Series > * Series with a low value period and high value period (Not periodic) > * Steady series with a small period of turbulence and then back to steady. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21954) Option to skip Host Check during the host add wizard
[ https://issues.apache.org/jira/browse/AMBARI-21954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly resolved AMBARI-21954. --- Resolution: Duplicate This issue is being tracked at AMBARI-21985 and will be fixed in 3.0.0 As of now ambari-web already has an experimental flag to turn this feature on in 2.6.0 which can be used for such issues. > Option to skip Host Check during the host add wizard > > > Key: AMBARI-21954 > URL: https://issues.apache.org/jira/browse/AMBARI-21954 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.6.0 > > Attachments: AMBARI-21954_branch-2.6.patch, Skip Host Check > checkbox.png, Skip Host Check warning.png > > > some times we see customers were not able to add the new hosts to cluster. > message says it is checking for potential problems but it never gets > completed. because of that customers were not able to add the hosts. but > after that they were able to add the hosts with API call. This allows a the > administrator to skip Host Check after a due warning -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-21954) Option to skip Host Check during the host add wizard
[ https://issues.apache.org/jira/browse/AMBARI-21954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly reopened AMBARI-21954: --- > Option to skip Host Check during the host add wizard > > > Key: AMBARI-21954 > URL: https://issues.apache.org/jira/browse/AMBARI-21954 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.6.0 > > Attachments: AMBARI-21954_branch-2.6.patch, Skip Host Check > checkbox.png, Skip Host Check warning.png > > > some times we see customers were not able to add the new hosts to cluster. > message says it is checking for potential problems but it never gets > completed. because of that customers were not able to add the hosts. but > after that they were able to add the hosts with API call. This allows a the > administrator to skip Host Check after a due warning -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22025) Service auto start broken due to incomplete execution command
[
https://issues.apache.org/jira/browse/AMBARI-22025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175547#comment-16175547
]
Hudson commented on AMBARI-22025:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #269 (See
[https://builds.apache.org/job/Ambari-branch-2.6/269/])
AMBARI-22025. Service auto start broken due to incomplete execution
(adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=65ae3215696da666f33e08794cd812f680a40f20])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatMonitor.java
> Service auto start broken due to incomplete execution command
> -
>
> Key: AMBARI-22025
> URL: https://issues.apache.org/jira/browse/AMBARI-22025
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22025.patch
>
>
> STR:
> # Install Ambari 2.6
> # Create cluster (ZooKeeper-only is enough)
> # Enable Service Auto Start for services
> # Restart node ({{shutdown -r now}})
> Result: service auto start permanently fails with the following error.
> {noformat}
> INFO 2017-09-21 11:22:40,296 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs
> recovery, desired = STARTED, and current = INSTALLED.
> INFO 2017-09-21 11:22:40,297 Controller.py:410 - Adding recovery command
> START for component ZOOKEEPER_SERVER
> INFO 2017-09-21 11:22:40,300 Controller.py:249 - Adding 1 commands. Heartbeat
> id = 12
> INFO 2017-09-21 11:22:40,300 ActionQueue.py:113 - Adding
> AUTO_EXECUTION_COMMAND for role ZOOKEEPER_SERVER for service ZOOKEEPER of
> cluster TEST to the queue.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:238 - Executing command with id =
> 1-0, taskId = 1505992937 for role = ZOOKEEPER_SERVER of cluster TEST.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:279 - Command execution metadata
> - taskId = 1505992937, retry enabled = False, max retry duration (sec) = 0,
> log_output = True
> ERROR 2017-09-21 11:22:40,306 CustomServiceOrchestrator.py:437 - Caught an
> exception while executing custom service command: 'exceptions.KeyError'>: 'service_package_folder'; 'service_package_folder'
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/CustomServiceOrchestrator.py",
> line 345, in runCommand
> base_dir = self.file_cache.get_service_base_dir(command,
> server_url_prefix)
> File "/usr/lib/python2.6/site-packages/ambari_agent/FileCache.py", line 76,
> in get_service_base_dir
> service_subpath = command['commandParams']['service_package_folder']
> KeyError: 'service_package_folder'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22030) OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object has no attribute 'upper' during EU
[
https://issues.apache.org/jira/browse/AMBARI-22030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175498#comment-16175498
]
Hudson commented on AMBARI-22030:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #268 (See
[https://builds.apache.org/job/Ambari-branch-2.6/268/])
AMBARI-22030. OOZIE/OOZIE_SERVER restart failed saying AttributeError: (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fb9ef3c39f0db8a32688c669f95a6b5329b5e844])
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/upgrade_summary.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py
> OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object
> has no attribute 'upper' during EU
> -
>
> Key: AMBARI-22030
> URL: https://issues.apache.org/jira/browse/AMBARI-22030
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22030.patch
>
>
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 150, in
> OozieServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 327, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 879, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 123, in pre_upgrade_restart
> OozieUpgrade.prepare_libext_directory(upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py",
> line 94, in prepare_libext_directory
> source_ext_zip_paths = oozie.get_oozie_ext_zip_source_paths(upgrade_type,
> params)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
> line 230, in get_oozie_ext_zip_source_paths
> source_ext_js_path = "/usr/share/" + params.source_stack_name.upper() +
> "-oozie/" + params.ext_js_file
> AttributeError: 'NoneType' object has no attribute 'upper'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22036) Update services API to explicitly take stack id as a parameter
Madhuvanthi Radhakrishnan created AMBARI-22036: -- Summary: Update services API to explicitly take stack id as a parameter Key: AMBARI-22036 URL: https://issues.apache.org/jira/browse/AMBARI-22036 Project: Ambari Issue Type: Bug Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 3.0.0 Add support to services api to explicitly take "stack-id" from which to install a service. At present, we have a one-one relationship between cluster and stack and we can only deploy services from a single stack. We need to make changes to the services API to explicit say "Create ZOOKEEPER service from HDP-3.0 mpack and create NIFI from HDF-3.1 mpack". We use stack id but effectively are deploying from different mpacks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22025) Service auto start broken due to incomplete execution command
[
https://issues.apache.org/jira/browse/AMBARI-22025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175478#comment-16175478
]
Hudson commented on AMBARI-22025:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8118 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8118/])
AMBARI-22025. Service auto start broken due to incomplete execution
(adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7c687bbc226b19f85a6f6f292537760e5d6d8048])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatMonitor.java
> Service auto start broken due to incomplete execution command
> -
>
> Key: AMBARI-22025
> URL: https://issues.apache.org/jira/browse/AMBARI-22025
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22025.patch
>
>
> STR:
> # Install Ambari 2.6
> # Create cluster (ZooKeeper-only is enough)
> # Enable Service Auto Start for services
> # Restart node ({{shutdown -r now}})
> Result: service auto start permanently fails with the following error.
> {noformat}
> INFO 2017-09-21 11:22:40,296 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs
> recovery, desired = STARTED, and current = INSTALLED.
> INFO 2017-09-21 11:22:40,297 Controller.py:410 - Adding recovery command
> START for component ZOOKEEPER_SERVER
> INFO 2017-09-21 11:22:40,300 Controller.py:249 - Adding 1 commands. Heartbeat
> id = 12
> INFO 2017-09-21 11:22:40,300 ActionQueue.py:113 - Adding
> AUTO_EXECUTION_COMMAND for role ZOOKEEPER_SERVER for service ZOOKEEPER of
> cluster TEST to the queue.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:238 - Executing command with id =
> 1-0, taskId = 1505992937 for role = ZOOKEEPER_SERVER of cluster TEST.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:279 - Command execution metadata
> - taskId = 1505992937, retry enabled = False, max retry duration (sec) = 0,
> log_output = True
> ERROR 2017-09-21 11:22:40,306 CustomServiceOrchestrator.py:437 - Caught an
> exception while executing custom service command: 'exceptions.KeyError'>: 'service_package_folder'; 'service_package_folder'
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/CustomServiceOrchestrator.py",
> line 345, in runCommand
> base_dir = self.file_cache.get_service_base_dir(command,
> server_url_prefix)
> File "/usr/lib/python2.6/site-packages/ambari_agent/FileCache.py", line 76,
> in get_service_base_dir
> service_subpath = command['commandParams']['service_package_folder']
> KeyError: 'service_package_folder'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22025) Service auto start broken due to incomplete execution command
[
https://issues.apache.org/jira/browse/AMBARI-22025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila resolved AMBARI-22025.
Resolution: Fixed
Committed to
[trunk|http://git-wip-us.apache.org/repos/asf/ambari/commit/7c687bbc22].
> Service auto start broken due to incomplete execution command
> -
>
> Key: AMBARI-22025
> URL: https://issues.apache.org/jira/browse/AMBARI-22025
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22025.patch
>
>
> STR:
> # Install Ambari 2.6
> # Create cluster (ZooKeeper-only is enough)
> # Enable Service Auto Start for services
> # Restart node ({{shutdown -r now}})
> Result: service auto start permanently fails with the following error.
> {noformat}
> INFO 2017-09-21 11:22:40,296 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs
> recovery, desired = STARTED, and current = INSTALLED.
> INFO 2017-09-21 11:22:40,297 Controller.py:410 - Adding recovery command
> START for component ZOOKEEPER_SERVER
> INFO 2017-09-21 11:22:40,300 Controller.py:249 - Adding 1 commands. Heartbeat
> id = 12
> INFO 2017-09-21 11:22:40,300 ActionQueue.py:113 - Adding
> AUTO_EXECUTION_COMMAND for role ZOOKEEPER_SERVER for service ZOOKEEPER of
> cluster TEST to the queue.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:238 - Executing command with id =
> 1-0, taskId = 1505992937 for role = ZOOKEEPER_SERVER of cluster TEST.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:279 - Command execution metadata
> - taskId = 1505992937, retry enabled = False, max retry duration (sec) = 0,
> log_output = True
> ERROR 2017-09-21 11:22:40,306 CustomServiceOrchestrator.py:437 - Caught an
> exception while executing custom service command: 'exceptions.KeyError'>: 'service_package_folder'; 'service_package_folder'
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/CustomServiceOrchestrator.py",
> line 345, in runCommand
> base_dir = self.file_cache.get_service_base_dir(command,
> server_url_prefix)
> File "/usr/lib/python2.6/site-packages/ambari_agent/FileCache.py", line 76,
> in get_service_base_dir
> service_subpath = command['commandParams']['service_package_folder']
> KeyError: 'service_package_folder'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22025) Service auto start broken due to incomplete execution command
[
https://issues.apache.org/jira/browse/AMBARI-22025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175468#comment-16175468
]
Doroszlai, Attila commented on AMBARI-22025:
Committed to
[branch-2.6|http://git-wip-us.apache.org/repos/asf/ambari/commit/65ae321569].
> Service auto start broken due to incomplete execution command
> -
>
> Key: AMBARI-22025
> URL: https://issues.apache.org/jira/browse/AMBARI-22025
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22025.patch
>
>
> STR:
> # Install Ambari 2.6
> # Create cluster (ZooKeeper-only is enough)
> # Enable Service Auto Start for services
> # Restart node ({{shutdown -r now}})
> Result: service auto start permanently fails with the following error.
> {noformat}
> INFO 2017-09-21 11:22:40,296 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs
> recovery, desired = STARTED, and current = INSTALLED.
> INFO 2017-09-21 11:22:40,297 Controller.py:410 - Adding recovery command
> START for component ZOOKEEPER_SERVER
> INFO 2017-09-21 11:22:40,300 Controller.py:249 - Adding 1 commands. Heartbeat
> id = 12
> INFO 2017-09-21 11:22:40,300 ActionQueue.py:113 - Adding
> AUTO_EXECUTION_COMMAND for role ZOOKEEPER_SERVER for service ZOOKEEPER of
> cluster TEST to the queue.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:238 - Executing command with id =
> 1-0, taskId = 1505992937 for role = ZOOKEEPER_SERVER of cluster TEST.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:279 - Command execution metadata
> - taskId = 1505992937, retry enabled = False, max retry duration (sec) = 0,
> log_output = True
> ERROR 2017-09-21 11:22:40,306 CustomServiceOrchestrator.py:437 - Caught an
> exception while executing custom service command: 'exceptions.KeyError'>: 'service_package_folder'; 'service_package_folder'
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/CustomServiceOrchestrator.py",
> line 345, in runCommand
> base_dir = self.file_cache.get_service_base_dir(command,
> server_url_prefix)
> File "/usr/lib/python2.6/site-packages/ambari_agent/FileCache.py", line 76,
> in get_service_base_dir
> service_subpath = command['commandParams']['service_package_folder']
> KeyError: 'service_package_folder'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22030) OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object has no attribute 'upper' during EU
[
https://issues.apache.org/jira/browse/AMBARI-22030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175466#comment-16175466
]
Hudson commented on AMBARI-22030:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8117 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8117/])
AMBARI-22030. OOZIE/OOZIE_SERVER restart failed saying AttributeError: (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f9c0c909be405ecfe3607ad4e07d3aa6eb6cf3df])
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/upgrade_summary.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py
> OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object
> has no attribute 'upper' during EU
> -
>
> Key: AMBARI-22030
> URL: https://issues.apache.org/jira/browse/AMBARI-22030
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22030.patch
>
>
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 150, in
> OozieServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 327, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 879, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 123, in pre_upgrade_restart
> OozieUpgrade.prepare_libext_directory(upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py",
> line 94, in prepare_libext_directory
> source_ext_zip_paths = oozie.get_oozie_ext_zip_source_paths(upgrade_type,
> params)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
> line 230, in get_oozie_ext_zip_source_paths
> source_ext_js_path = "/usr/share/" + params.source_stack_name.upper() +
> "-oozie/" + params.ext_js_file
> AttributeError: 'NoneType' object has no attribute 'upper'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22035) Stack and Versions page is stuck while trying to install a new stack
Vivek Rathod created AMBARI-22035: - Summary: Stack and Versions page is stuck while trying to install a new stack Key: AMBARI-22035 URL: https://issues.apache.org/jira/browse/AMBARI-22035 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Vivek Rathod Fix For: 2.6.0 STR: Install Ambari 2.5.2 with HDP 2.5 Upgrade to Ambari 2.6.0 Register a new stack HDP 2.6.* Click Install On button -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22030) OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object has no attribute 'upper' during EU
[
https://issues.apache.org/jira/browse/AMBARI-22030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-22030:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object
> has no attribute 'upper' during EU
> -
>
> Key: AMBARI-22030
> URL: https://issues.apache.org/jira/browse/AMBARI-22030
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22030.patch
>
>
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 150, in
> OozieServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 327, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 879, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 123, in pre_upgrade_restart
> OozieUpgrade.prepare_libext_directory(upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py",
> line 94, in prepare_libext_directory
> source_ext_zip_paths = oozie.get_oozie_ext_zip_source_paths(upgrade_type,
> params)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
> line 230, in get_oozie_ext_zip_source_paths
> source_ext_js_path = "/usr/share/" + params.source_stack_name.upper() +
> "-oozie/" + params.ext_js_file
> AttributeError: 'NoneType' object has no attribute 'upper'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22033) LLAP log level propagated incorrectly
[
https://issues.apache.org/jira/browse/AMBARI-22033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175382#comment-16175382
]
Hadoop QA commented on AMBARI-22033:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888350/AMBARI-22033.1.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12328//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12328//console
This message is automatically generated.
> LLAP log level propagated incorrectly
> -
>
> Key: AMBARI-22033
> URL: https://issues.apache.org/jira/browse/AMBARI-22033
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
> Attachments: AMBARI-22033.1.patch
>
>
> llap daemon log4j2 properties is using {{hive_log_level}} for log level
> replacement instead of {{llap_log_level}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22034) AMS: Add smart configs support for service
[ https://issues.apache.org/jira/browse/AMBARI-22034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22034: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk. > AMS: Add smart configs support for service > -- > > Key: AMBARI-22034 > URL: https://issues.apache.org/jira/browse/AMBARI-22034 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.1.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22034.patch > > > Mode, memory and some other settings are hard to hand edit and can use some > better UI tooling. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22034) AMS: Add smart configs support for service
[ https://issues.apache.org/jira/browse/AMBARI-22034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22034: - Attachment: AMBARI-22034.patch > AMS: Add smart configs support for service > -- > > Key: AMBARI-22034 > URL: https://issues.apache.org/jira/browse/AMBARI-22034 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.1.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22034.patch > > > Mode, memory and some other settings are hard to hand edit and can use some > better UI tooling. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22034) AMS: Add smart configs support for service
[ https://issues.apache.org/jira/browse/AMBARI-22034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22034: - Status: Patch Available (was: Open) > AMS: Add smart configs support for service > -- > > Key: AMBARI-22034 > URL: https://issues.apache.org/jira/browse/AMBARI-22034 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.1.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22034.patch > > > Mode, memory and some other settings are hard to hand edit and can use some > better UI tooling. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22034) AMS: Add smart configs support for service
[ https://issues.apache.org/jira/browse/AMBARI-22034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22034: - Summary: AMS: Add smart configs support for service (was: AMS: Add smart configs support for mode and memory) > AMS: Add smart configs support for service > -- > > Key: AMBARI-22034 > URL: https://issues.apache.org/jira/browse/AMBARI-22034 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.1.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 3.0.0 > > > Mode, memory and some other settings are hard to hand edit and can use some > better UI tooling. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22034) AMS: Add smart configs support for mode and memory
Siddharth Wagle created AMBARI-22034: Summary: AMS: Add smart configs support for mode and memory Key: AMBARI-22034 URL: https://issues.apache.org/jira/browse/AMBARI-22034 Project: Ambari Issue Type: Improvement Components: ambari-metrics Affects Versions: 2.1.0 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Priority: Critical Fix For: 3.0.0 Mode, memory and some other settings are hard to hand edit and can use some better UI tooling. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22033) LLAP log level propagated incorrectly
[
https://issues.apache.org/jira/browse/AMBARI-22033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasanth Jayachandran updated AMBARI-22033:
---
Status: Patch Available (was: Open)
> LLAP log level propagated incorrectly
> -
>
> Key: AMBARI-22033
> URL: https://issues.apache.org/jira/browse/AMBARI-22033
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
> Attachments: AMBARI-22033.1.patch
>
>
> llap daemon log4j2 properties is using {{hive_log_level}} for log level
> replacement instead of {{llap_log_level}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22027) Add UID/GID related issue with external users not listed in /etc/passwd
[ https://issues.apache.org/jira/browse/AMBARI-22027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175271#comment-16175271 ] Hudson commented on AMBARI-22027: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #267 (See [https://builds.apache.org/job/Ambari-branch-2.6/267/]) AMBARI-22027. Add UID/GID related issue with external users not listed (echekanskiy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a047748655370a4936d593acf26723d5de2680c6]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py * (edit) ambari-server/src/test/python/stacks/2.0.6/hooks/before-ANY/test_before_any.py > Add UID/GID related issue with external users not listed in /etc/passwd > --- > > Key: AMBARI-22027 > URL: https://issues.apache.org/jira/browse/AMBARI-22027 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.6.0 > > Attachments: AMBARI-22027.1.patch, AMBARI-22027-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22033) LLAP log level propagated incorrectly
[
https://issues.apache.org/jira/browse/AMBARI-22033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175260#comment-16175260
]
Prasanth Jayachandran commented on AMBARI-22033:
[~swapanshridhar] can you please take a look?
> LLAP log level propagated incorrectly
> -
>
> Key: AMBARI-22033
> URL: https://issues.apache.org/jira/browse/AMBARI-22033
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
> Attachments: AMBARI-22033.1.patch
>
>
> llap daemon log4j2 properties is using {{hive_log_level}} for log level
> replacement instead of {{llap_log_level}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22033) LLAP log level propagated incorrectly
Prasanth Jayachandran created AMBARI-22033:
--
Summary: LLAP log level propagated incorrectly
Key: AMBARI-22033
URL: https://issues.apache.org/jira/browse/AMBARI-22033
Project: Ambari
Issue Type: Bug
Affects Versions: 2.6.0
Reporter: Prasanth Jayachandran
Assignee: Prasanth Jayachandran
llap daemon log4j2 properties is using {{hive_log_level}} for log level
replacement instead of {{llap_log_level}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22025) Service auto start broken due to incomplete execution command
[
https://issues.apache.org/jira/browse/AMBARI-22025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22025:
---
Attachment: AMBARI-22025.patch
> Service auto start broken due to incomplete execution command
> -
>
> Key: AMBARI-22025
> URL: https://issues.apache.org/jira/browse/AMBARI-22025
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22025.patch
>
>
> STR:
> # Install Ambari 2.6
> # Create cluster (ZooKeeper-only is enough)
> # Enable Service Auto Start for services
> # Restart node ({{shutdown -r now}})
> Result: service auto start permanently fails with the following error.
> {noformat}
> INFO 2017-09-21 11:22:40,296 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs
> recovery, desired = STARTED, and current = INSTALLED.
> INFO 2017-09-21 11:22:40,297 Controller.py:410 - Adding recovery command
> START for component ZOOKEEPER_SERVER
> INFO 2017-09-21 11:22:40,300 Controller.py:249 - Adding 1 commands. Heartbeat
> id = 12
> INFO 2017-09-21 11:22:40,300 ActionQueue.py:113 - Adding
> AUTO_EXECUTION_COMMAND for role ZOOKEEPER_SERVER for service ZOOKEEPER of
> cluster TEST to the queue.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:238 - Executing command with id =
> 1-0, taskId = 1505992937 for role = ZOOKEEPER_SERVER of cluster TEST.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:279 - Command execution metadata
> - taskId = 1505992937, retry enabled = False, max retry duration (sec) = 0,
> log_output = True
> ERROR 2017-09-21 11:22:40,306 CustomServiceOrchestrator.py:437 - Caught an
> exception while executing custom service command: 'exceptions.KeyError'>: 'service_package_folder'; 'service_package_folder'
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/CustomServiceOrchestrator.py",
> line 345, in runCommand
> base_dir = self.file_cache.get_service_base_dir(command,
> server_url_prefix)
> File "/usr/lib/python2.6/site-packages/ambari_agent/FileCache.py", line 76,
> in get_service_base_dir
> service_subpath = command['commandParams']['service_package_folder']
> KeyError: 'service_package_folder'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22033) LLAP log level propagated incorrectly
[
https://issues.apache.org/jira/browse/AMBARI-22033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasanth Jayachandran updated AMBARI-22033:
---
Attachment: AMBARI-22033.1.patch
> LLAP log level propagated incorrectly
> -
>
> Key: AMBARI-22033
> URL: https://issues.apache.org/jira/browse/AMBARI-22033
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
> Attachments: AMBARI-22033.1.patch
>
>
> llap daemon log4j2 properties is using {{hive_log_level}} for log level
> replacement instead of {{llap_log_level}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22025) Service auto start broken due to incomplete execution command
[
https://issues.apache.org/jira/browse/AMBARI-22025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22025:
---
Attachment: (was: AMBARI-22025.patch)
> Service auto start broken due to incomplete execution command
> -
>
> Key: AMBARI-22025
> URL: https://issues.apache.org/jira/browse/AMBARI-22025
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.6.0
>
>
> STR:
> # Install Ambari 2.6
> # Create cluster (ZooKeeper-only is enough)
> # Enable Service Auto Start for services
> # Restart node ({{shutdown -r now}})
> Result: service auto start permanently fails with the following error.
> {noformat}
> INFO 2017-09-21 11:22:40,296 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs
> recovery, desired = STARTED, and current = INSTALLED.
> INFO 2017-09-21 11:22:40,297 Controller.py:410 - Adding recovery command
> START for component ZOOKEEPER_SERVER
> INFO 2017-09-21 11:22:40,300 Controller.py:249 - Adding 1 commands. Heartbeat
> id = 12
> INFO 2017-09-21 11:22:40,300 ActionQueue.py:113 - Adding
> AUTO_EXECUTION_COMMAND for role ZOOKEEPER_SERVER for service ZOOKEEPER of
> cluster TEST to the queue.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:238 - Executing command with id =
> 1-0, taskId = 1505992937 for role = ZOOKEEPER_SERVER of cluster TEST.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:279 - Command execution metadata
> - taskId = 1505992937, retry enabled = False, max retry duration (sec) = 0,
> log_output = True
> ERROR 2017-09-21 11:22:40,306 CustomServiceOrchestrator.py:437 - Caught an
> exception while executing custom service command: 'exceptions.KeyError'>: 'service_package_folder'; 'service_package_folder'
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/CustomServiceOrchestrator.py",
> line 345, in runCommand
> base_dir = self.file_cache.get_service_base_dir(command,
> server_url_prefix)
> File "/usr/lib/python2.6/site-packages/ambari_agent/FileCache.py", line 76,
> in get_service_base_dir
> service_subpath = command['commandParams']['service_package_folder']
> KeyError: 'service_package_folder'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22032) Make it possible to change steps in installer wizard
[
https://issues.apache.org/jira/browse/AMBARI-22032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175240#comment-16175240
]
Hadoop QA commented on AMBARI-22032:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888346/AMBARI-22032.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12325//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12325//console
This message is automatically generated.
> Make it possible to change steps in installer wizard
>
>
> Key: AMBARI-22032
> URL: https://issues.apache.org/jira/browse/AMBARI-22032
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Jason Golieb
>Assignee: Jason Golieb
> Fix For: 3.0.0
>
> Attachments: AMBARI-22032.patch
>
>
> The wizard infrastructure uses hard coded steps with hard coded names/routes
> like "step1", "step2", etc. This makes it difficult to change the step order,
> insert steps, or delete steps. For the installer wizard, we need to make
> significant changes to support Modular Deployment. We need to make some
> changes to enable greater flexibility in the structure of the wizard, while
> hopefully not breaking other wizards that don't need to be touched.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22027) Add UID/GID related issue with external users not listed in /etc/passwd
[ https://issues.apache.org/jira/browse/AMBARI-22027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-22027: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Add UID/GID related issue with external users not listed in /etc/passwd > --- > > Key: AMBARI-22027 > URL: https://issues.apache.org/jira/browse/AMBARI-22027 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.6.0 > > Attachments: AMBARI-22027.1.patch, AMBARI-22027-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22027) Add UID/GID related issue with external users not listed in /etc/passwd
[ https://issues.apache.org/jira/browse/AMBARI-22027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175235#comment-16175235 ] Hudson commented on AMBARI-22027: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8115 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8115/]) AMBARI-22027. Add UID/GID related issue with external users not listed (echekanskiy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f1b53000c65a97ac7784d51c9a648e7e135acaab]) * (edit) ambari-server/src/test/python/stacks/2.0.6/hooks/before-ANY/test_before_any.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py > Add UID/GID related issue with external users not listed in /etc/passwd > --- > > Key: AMBARI-22027 > URL: https://issues.apache.org/jira/browse/AMBARI-22027 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.6.0 > > Attachments: AMBARI-22027.1.patch, AMBARI-22027-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22027) Add UID/GID related issue with external users not listed in /etc/passwd
[ https://issues.apache.org/jira/browse/AMBARI-22027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175236#comment-16175236 ] Eugene Chekanskiy commented on AMBARI-22027: 2a06021..f1b5300 trunk -> trunk 30a046a..a047748 branch-2.6 -> branch-2.6 > Add UID/GID related issue with external users not listed in /etc/passwd > --- > > Key: AMBARI-22027 > URL: https://issues.apache.org/jira/browse/AMBARI-22027 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.6.0 > > Attachments: AMBARI-22027.1.patch, AMBARI-22027-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22032) Make it possible to change steps in installer wizard
[ https://issues.apache.org/jira/browse/AMBARI-22032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Golieb updated AMBARI-22032: -- Description: The wizard infrastructure uses hard coded steps with hard coded names/routes like "step1", "step2", etc. This makes it difficult to change the step order, insert steps, or delete steps. For the installer wizard, we need to make significant changes to support Modular Deployment. We need to make some changes to enable greater flexibility in the structure of the wizard, while hopefully not breaking other wizards that don't need to be touched. (was: The wizard infrastructure uses on hard coded steps with hard coded names/routes like "step1", "step2", etc. This makes it difficult to change the step order, insert steps, or delete steps. For the installer wizard, we need to make significant changes to support Modular Deployment. We need to make some changes to enable greater flexibility in the structure of the wizard, while hopefully not breaking other wizards that don't need to be touched.) > Make it possible to change steps in installer wizard > > > Key: AMBARI-22032 > URL: https://issues.apache.org/jira/browse/AMBARI-22032 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jason Golieb >Assignee: Jason Golieb > Fix For: 3.0.0 > > Attachments: AMBARI-22032.patch > > > The wizard infrastructure uses hard coded steps with hard coded names/routes > like "step1", "step2", etc. This makes it difficult to change the step order, > insert steps, or delete steps. For the installer wizard, we need to make > significant changes to support Modular Deployment. We need to make some > changes to enable greater flexibility in the structure of the wizard, while > hopefully not breaking other wizards that don't need to be touched. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22027) Add UID/GID related issue with external users not listed in /etc/passwd
[ https://issues.apache.org/jira/browse/AMBARI-22027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-22027: --- Attachment: AMBARI-22027.1.patch > Add UID/GID related issue with external users not listed in /etc/passwd > --- > > Key: AMBARI-22027 > URL: https://issues.apache.org/jira/browse/AMBARI-22027 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.6.0 > > Attachments: AMBARI-22027.1.patch, AMBARI-22027-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22032) Make it possible to change steps in installer wizard
[ https://issues.apache.org/jira/browse/AMBARI-22032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Golieb updated AMBARI-22032: -- Attachment: AMBARI-22032.patch > Make it possible to change steps in installer wizard > > > Key: AMBARI-22032 > URL: https://issues.apache.org/jira/browse/AMBARI-22032 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jason Golieb >Assignee: Jason Golieb > Fix For: 3.0.0 > > Attachments: AMBARI-22032.patch > > > The wizard infrastructure uses on hard coded steps with hard coded > names/routes like "step1", "step2", etc. This makes it difficult to change > the step order, insert steps, or delete steps. For the installer wizard, we > need to make significant changes to support Modular Deployment. We need to > make some changes to enable greater flexibility in the structure of the > wizard, while hopefully not breaking other wizards that don't need to be > touched. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22032) Make it possible to change steps in installer wizard
[ https://issues.apache.org/jira/browse/AMBARI-22032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Golieb updated AMBARI-22032: -- Status: Patch Available (was: Open) > Make it possible to change steps in installer wizard > > > Key: AMBARI-22032 > URL: https://issues.apache.org/jira/browse/AMBARI-22032 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jason Golieb >Assignee: Jason Golieb > Fix For: 3.0.0 > > Attachments: AMBARI-22032.patch > > > The wizard infrastructure uses on hard coded steps with hard coded > names/routes like "step1", "step2", etc. This makes it difficult to change > the step order, insert steps, or delete steps. For the installer wizard, we > need to make significant changes to support Modular Deployment. We need to > make some changes to enable greater flexibility in the structure of the > wizard, while hopefully not breaking other wizards that don't need to be > touched. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22032) Make it possible to change steps in installer wizard
Jason Golieb created AMBARI-22032: - Summary: Make it possible to change steps in installer wizard Key: AMBARI-22032 URL: https://issues.apache.org/jira/browse/AMBARI-22032 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Jason Golieb Assignee: Jason Golieb Fix For: 3.0.0 The wizard infrastructure uses on hard coded steps with hard coded names/routes like "step1", "step2", etc. This makes it difficult to change the step order, insert steps, or delete steps. For the installer wizard, we need to make significant changes to support Modular Deployment. We need to make some changes to enable greater flexibility in the structure of the wizard, while hopefully not breaking other wizards that don't need to be touched. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22019) Enable logsearch-web unit tests and make them skippable
[ https://issues.apache.org/jira/browse/AMBARI-22019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-22019: -- Status: Open (was: Patch Available) > Enable logsearch-web unit tests and make them skippable > --- > > Key: AMBARI-22019 > URL: https://issues.apache.org/jira/browse/AMBARI-22019 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > Attachments: AMBARI-22019.patch > > > enable UT for logseach-web > can be skipped by adding -DskipTests to the mvn command -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22019) Enable logsearch-web unit tests and make them skippable
[ https://issues.apache.org/jira/browse/AMBARI-22019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-22019: -- Status: Patch Available (was: Open) > Enable logsearch-web unit tests and make them skippable > --- > > Key: AMBARI-22019 > URL: https://issues.apache.org/jira/browse/AMBARI-22019 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > Attachments: AMBARI-22019.patch > > > enable UT for logseach-web > can be skipped by adding -DskipTests to the mvn command -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21919) Kerberos identity references should use the "reference" attribute
[ https://issues.apache.org/jira/browse/AMBARI-21919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175141#comment-16175141 ] Hudson commented on AMBARI-21919: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #266 (See [https://builds.apache.org/job/Ambari-branch-2.6/266/]) AMBARI-21919. Kerberos identity references should use the "reference" (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=30a046adb2e3e62a8f18abe4d00af91441a4cd64]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog260Test.java * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.10.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/SOLR/kerberos.json * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/YARN/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/kerberos.json * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/AbstractKerberosDescriptorContainer.java * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/KAFKA/kerberos.json * (edit) ambari-server/src/main/resources/kerberos_descriptor_schema.json * (edit) ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/kerberos.json * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/kerberos.json * (edit) ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.3.ECS/services/ECS/kerberos.json * (edit) contrib/management-packs/odpi-ambari-mpack/src/main/resources/stacks/ODPi/2.0/services/HIVE/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/TEZ/kerberos.json * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/SOLR/kerberos.json * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.2.3/kerberos.json * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER_KMS/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/GRUMPY/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/KNOX/kerberos.json * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.0/services/HDFS/kerberos.json * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/RANGER_KMS/kerberos.json * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.0/services/PIG/kerberos.json * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHBASE/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/OOZIE/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/ZEPPELIN/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/DRUID/kerberos.json * (edit) ambari-server/src/test/resources/stacks/HDP/2.0.8/services/HDFS/kerberos.json * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/kerberos.json * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/HIVE/kerberos.json * (edit) ambari-server/src/main/resources/common-services/TITAN/1.0.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/SPARK/kerberos.json * (edit) contrib/management-packs/microsoft-r_mpack/src/main/resources/common-services/MICROSOFT_R_SERVER/8.0.5/kerberos.json * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEYARN/kerberos.json * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/SPARK/kerberos.json * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.0/services/HBASE/kerberos.json * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/kerberos.json * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/KERBEROS/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.3.ECS/services/HBASE/kerberos.json * (edit) ambari-funtest/src/test/resources/stacks/HDP/2.0.8/services/HDFS/kerberos.json * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/RANGER_KMS/kerberos.json * (edit)
[jira] [Updated] (AMBARI-21919) Kerberos identity references should use the "reference" attribute
[
https://issues.apache.org/jira/browse/AMBARI-21919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-21919:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 2a0602104f719d8dec7cc34f9a10fe885d55a551
Author: Robert Levas
Date: Thu Sep 21 12:01:15 2017 -0400
{noformat}
Committed to branch-2.6
{noformat}
commit 30a046adb2e3e62a8f18abe4d00af91441a4cd64
Author: Robert Levas
Date: Thu Sep 21 12:46:30 2017 -0400
{noformat}
> Kerberos identity references should use the "reference" attribute
> -
>
> Key: AMBARI-21919
> URL: https://issues.apache.org/jira/browse/AMBARI-21919
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos_descriptor
> Fix For: 2.6.0
>
> Attachments: AMBARI-21919_branch-2.6_01.patch,
> AMBARI-21919_branch-2.6_02.patch, AMBARI-21919_trunk_01.patch,
> AMBARI-21919_trunk_02.patch
>
>
> Kerberos identity references should use the "reference" attribute rather than
> rely on the "name" attribute to indicate the identity descriptor references
> some other identity descriptor.
> Either method should work on the backend, however the UI appears to not fully
> handle the "named" reference properly.
> The solution is to change
> {code}
> {
> "name": "/HDFS/NAMENODE/namenode_nn",
> "principal": {
> "configuration":
> "ranger-hdfs-audit/xasecure.audit.jaas.Client.option.principal"
> },
> "keytab": {
> "configuration":
> "ranger-hdfs-audit/xasecure.audit.jaas.Client.option.keyTab"
> }
> }
> {code}
> by changing the "name" attribute to "reference" and adding a new "name"
> reference with a unique name relative to the scope of the identity
> descriptor. For example:
> {code}
> {
> "name":"ranger_hdfs_audit"
> "reference": "/HDFS/NAMENODE/namenode_nn",
> "principal": {
> "configuration":
> "ranger-hdfs-audit/xasecure.audit.jaas.Client.option.principal"
> },
> "keytab": {
> "configuration":
> "ranger-hdfs-audit/xasecure.audit.jaas.Client.option.keyTab"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22024) Stack and versions view style issues
[ https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175071#comment-16175071 ] Hudson commented on AMBARI-22024: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #265 (See [https://builds.apache.org/job/Ambari-branch-2.6/265/]) AMBARI-22024. Stack and versions view style issues (alexantonenko) (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=47461e1e76d02585d6f823bf5b242f3f844d706f]) * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_box_view_test.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_column.hbs * (edit) ambari-web/app/styles/stack_versions.less > Stack and versions view style issues > > > Key: AMBARI-22024 > URL: https://issues.apache.org/jira/browse/AMBARI-22024 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22024.patch, AMBARI-22024_trunk.patch > > > # Corners on versions headers should match. We need to make non-triangle area > higher. > # All versions headers should have a background. For example, installing > proccess. > # This menu must be left centred like every other. > # Buttons background on click should be blue as previous. > # Since this shows up as “Hidden” in the version list this call to action > should be “Hide”, this menu must be left centred. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22031) Invalid error message on UI after performing downgrade - Before finalizing the upgrade
Supreeth Sharma created AMBARI-22031: Summary: Invalid error message on UI after performing downgrade - Before finalizing the upgrade Key: AMBARI-22031 URL: https://issues.apache.org/jira/browse/AMBARI-22031 Project: Ambari Issue Type: Bug Components: ambari-upgrade Affects Versions: 2.6.0 Environment: ambari-server --version 2.6.0.0-128 Reporter: Supreeth Sharma Priority: Critical Fix For: 2.6.0 Invalid error message is shown on the UI when user performs downgrade from mid point. Live cluster : http://172.22.83.55:8080/ Steps to reproduce : 1) Install ambari 2.6.0.0 with HDP-2.6.3.0 (Error could be seen on all the HDP versions) 2) Start the patch upgrade for Hive or storm. (I guess this issue will occur for all the services which asks user to perform manual steps and provides the option to do downgrade.) 3) In the second step when user is asked to perform manual steps, option is available to do downgrade. Click on downgrade.(Attaching the screenshot) 4) Downgrade completes successfully. But error message 'Upgrade Action Required' is still shown on the UI. (Attaching the screenshot) Workaround : Cluster looks good and error message is removed after performing ambari-server restart -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22028) Downgrade button TypeError
[
https://issues.apache.org/jira/browse/AMBARI-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175013#comment-16175013
]
Hudson commented on AMBARI-22028:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #264 (See
[https://builds.apache.org/job/Ambari-branch-2.6/264/])
AMBARI-22028 Downgrade button TypeError. (atkach) (atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=34aa2fc1d04788bfb42619367a4feac8c1a7b25d])
* (edit) ambari-web/test/controllers/global/cluster_controller_test.js
* (edit) ambari-web/app/controllers/global/cluster_controller.js
> Downgrade button TypeError
> --
>
> Key: AMBARI-22028
> URL: https://issues.apache.org/jira/browse/AMBARI-22028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22028.patch, AMBARI-22028_trunk.patch
>
>
> {code}Uncaught TypeError: Cannot read property 'repository_name' of null
> at Class.confirmDowngrade (app.js:14968)
> at handler (vendor.js:21208)
> at HTMLButtonElement. (vendor.js:13000)
> at HTMLDivElement.dispatch (vendor.js:107)
> at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22030) OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object has no attribute 'upper' during EU
[
https://issues.apache.org/jira/browse/AMBARI-22030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175009#comment-16175009
]
Hadoop QA commented on AMBARI-22030:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888326/AMBARI-22030.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/12324//console
This message is automatically generated.
> OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object
> has no attribute 'upper' during EU
> -
>
> Key: AMBARI-22030
> URL: https://issues.apache.org/jira/browse/AMBARI-22030
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22030.patch
>
>
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 150, in
> OozieServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 327, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 879, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 123, in pre_upgrade_restart
> OozieUpgrade.prepare_libext_directory(upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py",
> line 94, in prepare_libext_directory
> source_ext_zip_paths = oozie.get_oozie_ext_zip_source_paths(upgrade_type,
> params)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
> line 230, in get_oozie_ext_zip_source_paths
> source_ext_js_path = "/usr/share/" + params.source_stack_name.upper() +
> "-oozie/" + params.ext_js_file
> AttributeError: 'NoneType' object has no attribute 'upper'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21919) Kerberos identity references should use the "reference" attribute
[ https://issues.apache.org/jira/browse/AMBARI-21919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175005#comment-16175005 ] Hudson commented on AMBARI-21919: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8114 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8114/]) AMBARI-21919. Kerberos identity references should use the "reference" (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2a0602104f719d8dec7cc34f9a10fe885d55a551]) * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHDFS/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEYARN/kerberos.json * (edit) ambari-server/src/main/resources/kerberos_descriptor_schema.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/GRUMPY/kerberos.json * (edit) ambari-server/src/main/resources/common-services/TEZ/0.9.0.3.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/kerberos.json * (edit) ambari-server/src/main/resources/common-services/HIVE/2.1.0.3.0/kerberos.json * (edit) ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SUPERSET/kerberos.json * (edit) ambari-server/src/main/resources/common-services/HAWQ/2.0.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHBASE/kerberos.json * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/kerberos.json * (edit) ambari-server/src/main/resources/common-services/SPARK/1.2.1/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.3.ECS/services/HBASE/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/FALCON/kerberos.json * (edit) ambari-server/src/main/resources/common-services/STORM/1.0.1.3.0/kerberos.json * (edit) ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/kerberos.json * (edit) ambari-server/src/main/resources/common-services/STORM/1.1.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.3.ECS/services/ECS/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/YARN/kerberos.json * (edit) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/kerberos.json * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/KNOX/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/kerberos.json * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosDescriptor.java * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/stacks/HDF/2.0/services/KAFKA/kerberos.json * (edit) ambari-server/src/main/resources/common-services/SPARK/2.2.0/kerberos.json * (edit) ambari-server/src/main/resources/common-services/HBASE/2.0.0.3.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/TEZ/kerberos.json * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/AbstractKerberosDescriptorContainer.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/DRUID/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.3.ECS/services/YARN/kerberos.json * (edit) ambari-server/src/main/resources/common-services/STORM/1.0.1/kerberos.json * (edit) ambari-funtest/src/test/resources/stacks/HDP/2.0.8/services/HDFS/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER_KMS/kerberos.json * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.10.0/kerberos.json * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/kerberos.json * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HBASE/kerberos.json * (edit) ambari-server/src/test/resources/stacks/HDP/2.0.8/services/HDFS/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK/kerberos.json * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/ZEPPELIN/kerberos.json * (edit) ambari-server/src/test/resources/kerberos/test_kerberos_descriptor_ranger_kms.json * (edit) contrib/management-packs/microsoft-r_mpack/src/main/resources/common-services/MICROSOFT_R_SERVER/8.0.5/kerberos.json * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/kerberos.json * (edit) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/kerberos.json * (edit)
[jira] [Updated] (AMBARI-22030) OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object has no attribute 'upper' during EU
[
https://issues.apache.org/jira/browse/AMBARI-22030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-22030:
---
Status: Patch Available (was: Open)
> OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object
> has no attribute 'upper' during EU
> -
>
> Key: AMBARI-22030
> URL: https://issues.apache.org/jira/browse/AMBARI-22030
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22030.patch
>
>
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 150, in
> OozieServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 327, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 879, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 123, in pre_upgrade_restart
> OozieUpgrade.prepare_libext_directory(upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py",
> line 94, in prepare_libext_directory
> source_ext_zip_paths = oozie.get_oozie_ext_zip_source_paths(upgrade_type,
> params)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
> line 230, in get_oozie_ext_zip_source_paths
> source_ext_js_path = "/usr/share/" + params.source_stack_name.upper() +
> "-oozie/" + params.ext_js_file
> AttributeError: 'NoneType' object has no attribute 'upper'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22030) OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object has no attribute 'upper' during EU
[
https://issues.apache.org/jira/browse/AMBARI-22030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-22030:
---
Attachment: AMBARI-22030.patch
> OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object
> has no attribute 'upper' during EU
> -
>
> Key: AMBARI-22030
> URL: https://issues.apache.org/jira/browse/AMBARI-22030
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22030.patch
>
>
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 150, in
> OozieServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 327, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 879, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 123, in pre_upgrade_restart
> OozieUpgrade.prepare_libext_directory(upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py",
> line 94, in prepare_libext_directory
> source_ext_zip_paths = oozie.get_oozie_ext_zip_source_paths(upgrade_type,
> params)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
> line 230, in get_oozie_ext_zip_source_paths
> source_ext_js_path = "/usr/share/" + params.source_stack_name.upper() +
> "-oozie/" + params.ext_js_file
> AttributeError: 'NoneType' object has no attribute 'upper'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22024) Stack and versions view style issues
[ https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22024: - Resolution: Fixed Status: Resolved (was: Patch Available) > Stack and versions view style issues > > > Key: AMBARI-22024 > URL: https://issues.apache.org/jira/browse/AMBARI-22024 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22024.patch, AMBARI-22024_trunk.patch > > > # Corners on versions headers should match. We need to make non-triangle area > higher. > # All versions headers should have a background. For example, installing > proccess. > # This menu must be left centred like every other. > # Buttons background on click should be blue as previous. > # Since this shows up as “Hidden” in the version list this call to action > should be “Hide”, this menu must be left centred. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22024) Stack and versions view style issues
[ https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174978#comment-16174978 ] Antonenko Alexander commented on AMBARI-22024: -- Committed to trunk and branch-2.6 > Stack and versions view style issues > > > Key: AMBARI-22024 > URL: https://issues.apache.org/jira/browse/AMBARI-22024 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22024.patch, AMBARI-22024_trunk.patch > > > # Corners on versions headers should match. We need to make non-triangle area > higher. > # All versions headers should have a background. For example, installing > proccess. > # This menu must be left centred like every other. > # Buttons background on click should be blue as previous. > # Since this shows up as “Hidden” in the version list this call to action > should be “Hide”, this menu must be left centred. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22030) OOZIE/OOZIE_SERVER restart failed saying AttributeError: 'NoneType' object has no attribute 'upper' during EU
Nate Cole created AMBARI-22030:
--
Summary: OOZIE/OOZIE_SERVER restart failed saying AttributeError:
'NoneType' object has no attribute 'upper' during EU
Key: AMBARI-22030
URL: https://issues.apache.org/jira/browse/AMBARI-22030
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Priority: Critical
Fix For: 2.6.0
{noformat}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
line 150, in
OozieServer().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 327, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 879, in restart
self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
File
"/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
line 123, in pre_upgrade_restart
OozieUpgrade.prepare_libext_directory(upgrade_type=upgrade_type)
File
"/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py",
line 94, in prepare_libext_directory
source_ext_zip_paths = oozie.get_oozie_ext_zip_source_paths(upgrade_type,
params)
File
"/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
line 230, in get_oozie_ext_zip_source_paths
source_ext_js_path = "/usr/share/" + params.source_stack_name.upper() +
"-oozie/" + params.ext_js_file
AttributeError: 'NoneType' object has no attribute 'upper'
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22027) Add UID/GID related issue with external users not listed in /etc/passwd
[
https://issues.apache.org/jira/browse/AMBARI-22027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174970#comment-16174970
]
Hadoop QA commented on AMBARI-22027:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888321/AMBARI-22027-trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12323//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12323//console
This message is automatically generated.
> Add UID/GID related issue with external users not listed in /etc/passwd
> ---
>
> Key: AMBARI-22027
> URL: https://issues.apache.org/jira/browse/AMBARI-22027
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 2.6.0
>
> Attachments: AMBARI-22027-trunk.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22024) Stack and versions view style issues
[ https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174968#comment-16174968 ] Hudson commented on AMBARI-22024: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8113 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8113/]) AMBARI-22024. Stack and versions view style issues (alexantonenko) (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2e170e4801794ddbbcd331585782a5f5b7e897a1]) * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_box_view_test.js * (edit) ambari-web/app/styles/stack_versions.less > Stack and versions view style issues > > > Key: AMBARI-22024 > URL: https://issues.apache.org/jira/browse/AMBARI-22024 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22024.patch, AMBARI-22024_trunk.patch > > > # Corners on versions headers should match. We need to make non-triangle area > higher. > # All versions headers should have a background. For example, installing > proccess. > # This menu must be left centred like every other. > # Buttons background on click should be blue as previous. > # Since this shows up as “Hidden” in the version list this call to action > should be “Hide”, this menu must be left centred. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22024) Stack and versions view style issues
[ https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174964#comment-16174964 ] Andrii Tkach commented on AMBARI-22024: --- +1 for the patch > Stack and versions view style issues > > > Key: AMBARI-22024 > URL: https://issues.apache.org/jira/browse/AMBARI-22024 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22024.patch, AMBARI-22024_trunk.patch > > > # Corners on versions headers should match. We need to make non-triangle area > higher. > # All versions headers should have a background. For example, installing > proccess. > # This menu must be left centred like every other. > # Buttons background on click should be blue as previous. > # Since this shows up as “Hidden” in the version list this call to action > should be “Hide”, this menu must be left centred. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22024) Stack and versions view style issues
[ https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174961#comment-16174961 ] Antonenko Alexander commented on AMBARI-22024: -- Build fails on ambari-main. Manually tested. > Stack and versions view style issues > > > Key: AMBARI-22024 > URL: https://issues.apache.org/jira/browse/AMBARI-22024 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22024.patch, AMBARI-22024_trunk.patch > > > # Corners on versions headers should match. We need to make non-triangle area > higher. > # All versions headers should have a background. For example, installing > proccess. > # This menu must be left centred like every other. > # Buttons background on click should be blue as previous. > # Since this shows up as “Hidden” in the version list this call to action > should be “Hide”, this menu must be left centred. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22027) Add UID/GID related issue with external users not listed in /etc/passwd
[ https://issues.apache.org/jira/browse/AMBARI-22027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-22027: --- Status: Patch Available (was: Open) > Add UID/GID related issue with external users not listed in /etc/passwd > --- > > Key: AMBARI-22027 > URL: https://issues.apache.org/jira/browse/AMBARI-22027 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.6.0 > > Attachments: AMBARI-22027-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22024) Stack and versions view style issues
[
https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174946#comment-16174946
]
Hadoop QA commented on AMBARI-22024:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888308/AMBARI-22024_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12322//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12322//console
This message is automatically generated.
> Stack and versions view style issues
>
>
> Key: AMBARI-22024
> URL: https://issues.apache.org/jira/browse/AMBARI-22024
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22024.patch, AMBARI-22024_trunk.patch
>
>
> # Corners on versions headers should match. We need to make non-triangle area
> higher.
> # All versions headers should have a background. For example, installing
> proccess.
> # This menu must be left centred like every other.
> # Buttons background on click should be blue as previous.
> # Since this shows up as “Hidden” in the version list this call to action
> should be “Hide”, this menu must be left centred.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22028) Downgrade button TypeError
[
https://issues.apache.org/jira/browse/AMBARI-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-22028:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Downgrade button TypeError
> --
>
> Key: AMBARI-22028
> URL: https://issues.apache.org/jira/browse/AMBARI-22028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22028.patch, AMBARI-22028_trunk.patch
>
>
> {code}Uncaught TypeError: Cannot read property 'repository_name' of null
> at Class.confirmDowngrade (app.js:14968)
> at handler (vendor.js:21208)
> at HTMLButtonElement. (vendor.js:13000)
> at HTMLDivElement.dispatch (vendor.js:107)
> at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22028) Downgrade button TypeError
[
https://issues.apache.org/jira/browse/AMBARI-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174944#comment-16174944
]
Andrii Tkach commented on AMBARI-22028:
---
committed to trunk and branch-2.6
> Downgrade button TypeError
> --
>
> Key: AMBARI-22028
> URL: https://issues.apache.org/jira/browse/AMBARI-22028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22028.patch, AMBARI-22028_trunk.patch
>
>
> {code}Uncaught TypeError: Cannot read property 'repository_name' of null
> at Class.confirmDowngrade (app.js:14968)
> at handler (vendor.js:21208)
> at HTMLButtonElement. (vendor.js:13000)
> at HTMLDivElement.dispatch (vendor.js:107)
> at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22028) Downgrade button TypeError
[
https://issues.apache.org/jira/browse/AMBARI-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174943#comment-16174943
]
Hadoop QA commented on AMBARI-22028:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888315/AMBARI-22028_trunk.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/12321//console
This message is automatically generated.
> Downgrade button TypeError
> --
>
> Key: AMBARI-22028
> URL: https://issues.apache.org/jira/browse/AMBARI-22028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22028.patch, AMBARI-22028_trunk.patch
>
>
> {code}Uncaught TypeError: Cannot read property 'repository_name' of null
> at Class.confirmDowngrade (app.js:14968)
> at handler (vendor.js:21208)
> at HTMLButtonElement. (vendor.js:13000)
> at HTMLDivElement.dispatch (vendor.js:107)
> at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22028) Downgrade button TypeError
[
https://issues.apache.org/jira/browse/AMBARI-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174942#comment-16174942
]
Hudson commented on AMBARI-22028:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8112 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8112/])
AMBARI-22028 Downgrade button TypeError. (atkach) (atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=37b847069f1d2a07ed9deb5e580ba23e90b77ade])
* (edit) ambari-web/test/controllers/global/cluster_controller_test.js
* (edit) ambari-web/app/controllers/global/cluster_controller.js
> Downgrade button TypeError
> --
>
> Key: AMBARI-22028
> URL: https://issues.apache.org/jira/browse/AMBARI-22028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22028.patch, AMBARI-22028_trunk.patch
>
>
> {code}Uncaught TypeError: Cannot read property 'repository_name' of null
> at Class.confirmDowngrade (app.js:14968)
> at handler (vendor.js:21208)
> at HTMLButtonElement. (vendor.js:13000)
> at HTMLDivElement.dispatch (vendor.js:107)
> at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22028) Downgrade button TypeError
[
https://issues.apache.org/jira/browse/AMBARI-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174932#comment-16174932
]
Aleksandr Kovalenko commented on AMBARI-22028:
--
+1 for the patch
> Downgrade button TypeError
> --
>
> Key: AMBARI-22028
> URL: https://issues.apache.org/jira/browse/AMBARI-22028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22028.patch, AMBARI-22028_trunk.patch
>
>
> {code}Uncaught TypeError: Cannot read property 'repository_name' of null
> at Class.confirmDowngrade (app.js:14968)
> at handler (vendor.js:21208)
> at HTMLButtonElement. (vendor.js:13000)
> at HTMLDivElement.dispatch (vendor.js:107)
> at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22027) Add UID/GID related issue with external users not listed in /etc/passwd
[ https://issues.apache.org/jira/browse/AMBARI-22027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-22027: --- Attachment: AMBARI-22027-trunk.patch > Add UID/GID related issue with external users not listed in /etc/passwd > --- > > Key: AMBARI-22027 > URL: https://issues.apache.org/jira/browse/AMBARI-22027 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.6.0 > > Attachments: AMBARI-22027-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22028) Downgrade button TypeError
[
https://issues.apache.org/jira/browse/AMBARI-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174922#comment-16174922
]
Hadoop QA commented on AMBARI-22028:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888315/AMBARI-22028_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12320//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12320//console
This message is automatically generated.
> Downgrade button TypeError
> --
>
> Key: AMBARI-22028
> URL: https://issues.apache.org/jira/browse/AMBARI-22028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22028.patch, AMBARI-22028_trunk.patch
>
>
> {code}Uncaught TypeError: Cannot read property 'repository_name' of null
> at Class.confirmDowngrade (app.js:14968)
> at handler (vendor.js:21208)
> at HTMLButtonElement. (vendor.js:13000)
> at HTMLDivElement.dispatch (vendor.js:107)
> at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22024) Stack and versions view style issues
[
https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174903#comment-16174903
]
Hadoop QA commented on AMBARI-22024:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888308/AMBARI-22024_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12319//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12319//console
This message is automatically generated.
> Stack and versions view style issues
>
>
> Key: AMBARI-22024
> URL: https://issues.apache.org/jira/browse/AMBARI-22024
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22024.patch, AMBARI-22024_trunk.patch
>
>
> # Corners on versions headers should match. We need to make non-triangle area
> higher.
> # All versions headers should have a background. For example, installing
> proccess.
> # This menu must be left centred like every other.
> # Buttons background on click should be blue as previous.
> # Since this shows up as “Hidden” in the version list this call to action
> should be “Hide”, this menu must be left centred.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22028) Downgrade button TypeError
[
https://issues.apache.org/jira/browse/AMBARI-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174899#comment-16174899
]
Hadoop QA commented on AMBARI-22028:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888315/AMBARI-22028_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12318//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12318//console
This message is automatically generated.
> Downgrade button TypeError
> --
>
> Key: AMBARI-22028
> URL: https://issues.apache.org/jira/browse/AMBARI-22028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22028.patch, AMBARI-22028_trunk.patch
>
>
> {code}Uncaught TypeError: Cannot read property 'repository_name' of null
> at Class.confirmDowngrade (app.js:14968)
> at handler (vendor.js:21208)
> at HTMLButtonElement. (vendor.js:13000)
> at HTMLDivElement.dispatch (vendor.js:107)
> at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22025) Service auto start broken due to incomplete execution command
[
https://issues.apache.org/jira/browse/AMBARI-22025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22025:
---
Attachment: AMBARI-22025.patch
> Service auto start broken due to incomplete execution command
> -
>
> Key: AMBARI-22025
> URL: https://issues.apache.org/jira/browse/AMBARI-22025
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22025.patch
>
>
> STR:
> # Install Ambari 2.6
> # Create cluster (ZooKeeper-only is enough)
> # Enable Service Auto Start for services
> # Restart node ({{shutdown -r now}})
> Result: service auto start permanently fails with the following error.
> {noformat}
> INFO 2017-09-21 11:22:40,296 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs
> recovery, desired = STARTED, and current = INSTALLED.
> INFO 2017-09-21 11:22:40,297 Controller.py:410 - Adding recovery command
> START for component ZOOKEEPER_SERVER
> INFO 2017-09-21 11:22:40,300 Controller.py:249 - Adding 1 commands. Heartbeat
> id = 12
> INFO 2017-09-21 11:22:40,300 ActionQueue.py:113 - Adding
> AUTO_EXECUTION_COMMAND for role ZOOKEEPER_SERVER for service ZOOKEEPER of
> cluster TEST to the queue.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:238 - Executing command with id =
> 1-0, taskId = 1505992937 for role = ZOOKEEPER_SERVER of cluster TEST.
> INFO 2017-09-21 11:22:40,306 ActionQueue.py:279 - Command execution metadata
> - taskId = 1505992937, retry enabled = False, max retry duration (sec) = 0,
> log_output = True
> ERROR 2017-09-21 11:22:40,306 CustomServiceOrchestrator.py:437 - Caught an
> exception while executing custom service command: 'exceptions.KeyError'>: 'service_package_folder'; 'service_package_folder'
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/CustomServiceOrchestrator.py",
> line 345, in runCommand
> base_dir = self.file_cache.get_service_base_dir(command,
> server_url_prefix)
> File "/usr/lib/python2.6/site-packages/ambari_agent/FileCache.py", line 76,
> in get_service_base_dir
> service_subpath = command['commandParams']['service_package_folder']
> KeyError: 'service_package_folder'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22028) Downgrade button TypeError
[
https://issues.apache.org/jira/browse/AMBARI-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-22028:
--
Status: Patch Available (was: Open)
> Downgrade button TypeError
> --
>
> Key: AMBARI-22028
> URL: https://issues.apache.org/jira/browse/AMBARI-22028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22028.patch, AMBARI-22028_trunk.patch
>
>
> {code}Uncaught TypeError: Cannot read property 'repository_name' of null
> at Class.confirmDowngrade (app.js:14968)
> at handler (vendor.js:21208)
> at HTMLButtonElement. (vendor.js:13000)
> at HTMLDivElement.dispatch (vendor.js:107)
> at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22028) Downgrade button TypeError
[
https://issues.apache.org/jira/browse/AMBARI-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-22028:
--
Attachment: AMBARI-22028_trunk.patch
> Downgrade button TypeError
> --
>
> Key: AMBARI-22028
> URL: https://issues.apache.org/jira/browse/AMBARI-22028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22028.patch, AMBARI-22028_trunk.patch
>
>
> {code}Uncaught TypeError: Cannot read property 'repository_name' of null
> at Class.confirmDowngrade (app.js:14968)
> at handler (vendor.js:21208)
> at HTMLButtonElement. (vendor.js:13000)
> at HTMLDivElement.dispatch (vendor.js:107)
> at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-22028) Downgrade button TypeError
[
https://issues.apache.org/jira/browse/AMBARI-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174888#comment-16174888
]
Andrii Tkach edited comment on AMBARI-22028 at 9/21/17 3:02 PM:
branch-2.6:
30500 passing (26s)
157 pending
trunk:
21350 passing (29s)
128 pending
was (Author: atkach):
branch-2.6:
30500 passing (26s)
157 pending
> Downgrade button TypeError
> --
>
> Key: AMBARI-22028
> URL: https://issues.apache.org/jira/browse/AMBARI-22028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22028.patch
>
>
> {code}Uncaught TypeError: Cannot read property 'repository_name' of null
> at Class.confirmDowngrade (app.js:14968)
> at handler (vendor.js:21208)
> at HTMLButtonElement. (vendor.js:13000)
> at HTMLDivElement.dispatch (vendor.js:107)
> at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22028) Downgrade button TypeError
[
https://issues.apache.org/jira/browse/AMBARI-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174888#comment-16174888
]
Andrii Tkach commented on AMBARI-22028:
---
branch-2.6:
30500 passing (26s)
157 pending
> Downgrade button TypeError
> --
>
> Key: AMBARI-22028
> URL: https://issues.apache.org/jira/browse/AMBARI-22028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22028.patch
>
>
> {code}Uncaught TypeError: Cannot read property 'repository_name' of null
> at Class.confirmDowngrade (app.js:14968)
> at handler (vendor.js:21208)
> at HTMLButtonElement. (vendor.js:13000)
> at HTMLDivElement.dispatch (vendor.js:107)
> at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22028) Downgrade button TypeError
[
https://issues.apache.org/jira/browse/AMBARI-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-22028:
--
Attachment: AMBARI-22028.patch
> Downgrade button TypeError
> --
>
> Key: AMBARI-22028
> URL: https://issues.apache.org/jira/browse/AMBARI-22028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22028.patch
>
>
> {code}Uncaught TypeError: Cannot read property 'repository_name' of null
> at Class.confirmDowngrade (app.js:14968)
> at handler (vendor.js:21208)
> at HTMLButtonElement. (vendor.js:13000)
> at HTMLDivElement.dispatch (vendor.js:107)
> at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22029) "Download All Client Configs" for a cluster and downloading clients from a host with Oozie client fails
Myroslav Papirkovskyi created AMBARI-22029:
--
Summary: "Download All Client Configs" for a cluster and
downloading clients from a host with Oozie client fails
Key: AMBARI-22029
URL: https://issues.apache.org/jira/browse/AMBARI-22029
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.0
Reporter: Myroslav Papirkovskyi
Assignee: Myroslav Papirkovskyi
Priority: Blocker
Fix For: 2.6.0
* Navigate to Dashboard page and use Download All Client Configs to download
all client configs for the cluster. It fails
* Go to host with Oozie client and from Host Actions - Download Client Configs
- All Clients on Host. This action also fails
* Download just Oozie client from the host. That one fails too
{code}
{
status: 500,
message: "org.apache.ambari.server.controller.spi.SystemException: Execution of
"ambari-python-wrap
/var/lib/ambari-server/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_client.py
generate_configs
/var/lib/ambari-server/data/tmp/OOZIE_CLIENT8027664465495831823-configuration.json
/var/lib/ambari-server/resources/common-services/OOZIE/4.0.0.2.0/package
/var/lib/ambari-server/data/tmp/structured-out.json INFO
/var/lib/ambari-server/data/tmp" returned 1. java.lang.Throwable: 2017-09-19
21:23:43,446 - Stack Feature Version Info: Cluster Stack=2.6, Command
Stack=None, Command Version=None -> 2.6
2017-09-19 21:23:43,447 - Using hadoop conf dir:
/usr/hdp/current/hadoop-client/conf
Traceback (most recent call last):
File
"/var/lib/ambari-server/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_client.py",
line 71, in
OozieClient().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 327, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 964, in generate_configs
import params
File
"/var/lib/ambari-server/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params.py",
line 28, in
from params_linux import *
File
"/var/lib/ambari-server/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py",
line 387, in
all_lzo_packages = get_lzo_packages(stack_version_unformatted)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_lzo_packages.py",
line 45, in get_lzo_packages
lzo_packages +=
[script_instance.format_package_name("hadooplzo_${stack_version}"),
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 476, in format_package_name
repo_version = self.get_stack_version_before_packages_installed()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 430, in get_stack_version_before_packages_installed
stack_select_package_name = stack_select.get_package_name()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
line 100, in get_package_name
raise Fail("Both the role and the service name must be included in the
command in order to determine which packages to use with the stack-select tool")
resource_management.core.exceptions.Fail: Both the role and the service name
must be included in the command in order to determine which packages to use
with the stack-select tool
"
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22028) Downgrade button TypeError
Andrii Tkach created AMBARI-22028:
-
Summary: Downgrade button TypeError
Key: AMBARI-22028
URL: https://issues.apache.org/jira/browse/AMBARI-22028
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.6.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Priority: Critical
Fix For: 2.6.0
{code}Uncaught TypeError: Cannot read property 'repository_name' of null
at Class.confirmDowngrade (app.js:14968)
at handler (vendor.js:21208)
at HTMLButtonElement. (vendor.js:13000)
at HTMLDivElement.dispatch (vendor.js:107)
at HTMLDivElement.i (vendor.js:107){code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22027) Add UID/GID related issue with external users not listed in /etc/passwd
Eugene Chekanskiy created AMBARI-22027: -- Summary: Add UID/GID related issue with external users not listed in /etc/passwd Key: AMBARI-22027 URL: https://issues.apache.org/jira/browse/AMBARI-22027 Project: Ambari Issue Type: Bug Affects Versions: 2.5.2 Reporter: Eugene Chekanskiy Assignee: Eugene Chekanskiy Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22026) Restart of all components on host operation failed with 500 status code
Myroslav Papirkovskyi created AMBARI-22026:
--
Summary: Restart of all components on host operation failed with
500 status code
Key: AMBARI-22026
URL: https://issues.apache.org/jira/browse/AMBARI-22026
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.0
Reporter: Myroslav Papirkovskyi
Assignee: Myroslav Papirkovskyi
Priority: Blocker
Fix For: 2.6.0
Restart all components on host operation failed with 500 status code
STR:
1)Enable wire encryption
2)Try to restart all components on host
In ambari-server logs met this error:
{code}
Sep 2017 12:02:56,281 ERROR [ambari-client-thread-35963]
BaseManagementHandler:71 - Caught a runtime exception while attempting to
create a resource: null
java.lang.NullPointerException
at
java.util.concurrent.ConcurrentSkipListMap.doGet(ConcurrentSkipListMap.java:778)
at
java.util.concurrent.ConcurrentSkipListMap.get(ConcurrentSkipListMap.java:1546)
at
org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:861)
at
org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.isTopologyRefreshRequired(AmbariCustomCommandExecutionHelper.java:1529)
at
org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.addExecutionCommandsToStage(AmbariCustomCommandExecutionHelper.java:1188)
at
org.apache.ambari.server.controller.AmbariManagementControllerImpl.createAction(AmbariManagementControllerImpl.java:4243)
at
org.apache.ambari.server.controller.internal.RequestResourceProvider$1.invoke(RequestResourceProvider.java:264)
at
org.apache.ambari.server.controller.internal.RequestResourceProvider$1.invoke(RequestResourceProvider.java:193)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:455)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:278)
at
org.apache.ambari.server.controller.internal.RequestResourceProvider.createResources(RequestResourceProvider.java:193)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
at
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
at
org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
at
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
at
org.apache.ambari.server.api.services.RequestService.createRequests(RequestService.java:145)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at
[jira] [Created] (AMBARI-22025) Service auto start broken due to incomplete execution command
Doroszlai, Attila created AMBARI-22025:
--
Summary: Service auto start broken due to incomplete execution
command
Key: AMBARI-22025
URL: https://issues.apache.org/jira/browse/AMBARI-22025
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.0
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Priority: Blocker
Fix For: 2.6.0
STR:
# Install Ambari 2.6
# Create cluster (ZooKeeper-only is enough)
# Enable Service Auto Start for services
# Restart node ({{shutdown -r now}})
Result: service auto start permanently fails with the following error.
{noformat}
INFO 2017-09-21 11:22:40,296 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs
recovery, desired = STARTED, and current = INSTALLED.
INFO 2017-09-21 11:22:40,297 Controller.py:410 - Adding recovery command START
for component ZOOKEEPER_SERVER
INFO 2017-09-21 11:22:40,300 Controller.py:249 - Adding 1 commands. Heartbeat
id = 12
INFO 2017-09-21 11:22:40,300 ActionQueue.py:113 - Adding AUTO_EXECUTION_COMMAND
for role ZOOKEEPER_SERVER for service ZOOKEEPER of cluster TEST to the queue.
INFO 2017-09-21 11:22:40,306 ActionQueue.py:238 - Executing command with id =
1-0, taskId = 1505992937 for role = ZOOKEEPER_SERVER of cluster TEST.
INFO 2017-09-21 11:22:40,306 ActionQueue.py:279 - Command execution metadata -
taskId = 1505992937, retry enabled = False, max retry duration (sec) = 0,
log_output = True
ERROR 2017-09-21 11:22:40,306 CustomServiceOrchestrator.py:437 - Caught an
exception while executing custom service command: :
'service_package_folder'; 'service_package_folder'
Traceback (most recent call last):
File
"/usr/lib/python2.6/site-packages/ambari_agent/CustomServiceOrchestrator.py",
line 345, in runCommand
base_dir = self.file_cache.get_service_base_dir(command, server_url_prefix)
File "/usr/lib/python2.6/site-packages/ambari_agent/FileCache.py", line 76,
in get_service_base_dir
service_subpath = command['commandParams']['service_package_folder']
KeyError: 'service_package_folder'
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22024) Stack and versions view style issues
[
https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174861#comment-16174861
]
Hadoop QA commented on AMBARI-22024:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888308/AMBARI-22024_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12317//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12317//console
This message is automatically generated.
> Stack and versions view style issues
>
>
> Key: AMBARI-22024
> URL: https://issues.apache.org/jira/browse/AMBARI-22024
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22024.patch, AMBARI-22024_trunk.patch
>
>
> # Corners on versions headers should match. We need to make non-triangle area
> higher.
> # All versions headers should have a background. For example, installing
> proccess.
> # This menu must be left centred like every other.
> # Buttons background on click should be blue as previous.
> # Since this shows up as “Hidden” in the version list this call to action
> should be “Hide”, this menu must be left centred.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21619) More ResourceManager HA host group placeholders in blueprints
[
https://issues.apache.org/jira/browse/AMBARI-21619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21619:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> More ResourceManager HA host group placeholders in blueprints
> -
>
> Key: AMBARI-21619
> URL: https://issues.apache.org/jira/browse/AMBARI-21619
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-21619.patch
>
>
> Some ResourceManager HA addresses are not replaced during blueprint
> processing (cluster creation, export). This may cause failure of starting
> ResourceManager, or force user to enter specific host names in the blueprint
> as a workaround.
> {noformat:title=/usr/hdp/current/hadoop-client/conf/yarn-site.xml}
>
> yarn.resourcemanager.address.rm1
> %HOSTGROUP::master0%:8050
>
>
> yarn.resourcemanager.address.rm2
> %HOSTGROUP::master1%:8050
>
>
> yarn.resourcemanager.admin.address.rm1
> %HOSTGROUP::master0%:8141
>
>
> yarn.resourcemanager.admin.address.rm2
> %HOSTGROUP::master1%:8141
>
>
> yarn.resourcemanager.resource-tracker.address.rm1
> %HOSTGROUP::master0%:8025
>
>
> yarn.resourcemanager.resource-tracker.address.rm2
> %HOSTGROUP::master1%:8025
>
>
> yarn.resourcemanager.scheduler.address.rm1
> %HOSTGROUP::master0%:8030
>
>
> yarn.resourcemanager.scheduler.address.rm2
> %HOSTGROUP::master1%:8030
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22024) Stack and versions view style issues
[ https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22024: - Status: Patch Available (was: Open) > Stack and versions view style issues > > > Key: AMBARI-22024 > URL: https://issues.apache.org/jira/browse/AMBARI-22024 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22024.patch, AMBARI-22024_trunk.patch > > > # Corners on versions headers should match. We need to make non-triangle area > higher. > # All versions headers should have a background. For example, installing > proccess. > # This menu must be left centred like every other. > # Buttons background on click should be blue as previous. > # Since this shows up as “Hidden” in the version list this call to action > should be “Hide”, this menu must be left centred. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21619) More ResourceManager HA host group placeholders in blueprints
[
https://issues.apache.org/jira/browse/AMBARI-21619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21619:
---
Fix Version/s: (was: 2.5.3)
2.6.0
> More ResourceManager HA host group placeholders in blueprints
> -
>
> Key: AMBARI-21619
> URL: https://issues.apache.org/jira/browse/AMBARI-21619
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-21619.patch
>
>
> Some ResourceManager HA addresses are not replaced during blueprint
> processing (cluster creation, export). This may cause failure of starting
> ResourceManager, or force user to enter specific host names in the blueprint
> as a workaround.
> {noformat:title=/usr/hdp/current/hadoop-client/conf/yarn-site.xml}
>
> yarn.resourcemanager.address.rm1
> %HOSTGROUP::master0%:8050
>
>
> yarn.resourcemanager.address.rm2
> %HOSTGROUP::master1%:8050
>
>
> yarn.resourcemanager.admin.address.rm1
> %HOSTGROUP::master0%:8141
>
>
> yarn.resourcemanager.admin.address.rm2
> %HOSTGROUP::master1%:8141
>
>
> yarn.resourcemanager.resource-tracker.address.rm1
> %HOSTGROUP::master0%:8025
>
>
> yarn.resourcemanager.resource-tracker.address.rm2
> %HOSTGROUP::master1%:8025
>
>
> yarn.resourcemanager.scheduler.address.rm1
> %HOSTGROUP::master0%:8030
>
>
> yarn.resourcemanager.scheduler.address.rm2
> %HOSTGROUP::master1%:8030
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22024) Stack and versions view style issues
[ https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22024: - Attachment: AMBARI-22024_trunk.patch > Stack and versions view style issues > > > Key: AMBARI-22024 > URL: https://issues.apache.org/jira/browse/AMBARI-22024 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22024.patch, AMBARI-22024_trunk.patch > > > # Corners on versions headers should match. We need to make non-triangle area > higher. > # All versions headers should have a background. For example, installing > proccess. > # This menu must be left centred like every other. > # Buttons background on click should be blue as previous. > # Since this shows up as “Hidden” in the version list this call to action > should be “Hide”, this menu must be left centred. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22011) Could not copy tez tarball to HDFS during prepare upgrade (EU)
[
https://issues.apache.org/jira/browse/AMBARI-22011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174851#comment-16174851
]
Hudson commented on AMBARI-22011:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8111 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8111/])
AMBARI-22011. Could not copy tez tarball to HDFS during prepare upgrade (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=001c77f5773e3ca778ee6ff78ba8c616f0e3007c])
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/copy_tarball.py
* (add)
ambari-common/src/main/python/resource_management/libraries/functions/copy_tarball.py.rej
> Could not copy tez tarball to HDFS during prepare upgrade (EU)
> --
>
> Key: AMBARI-22011
> URL: https://issues.apache.org/jira/browse/AMBARI-22011
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22011.patch
>
>
> {code}
> 2017-09-19 11:42:05,103 - Task. Type: EXECUTE, Script: scripts/pre_upgrade.py
> - Function: prepare
> 2017-09-19 11:42:05,738 - Skipping stack-select on RU_EXECUTE_TASKS because
> it does not exist in the stack-select package structure.
> 2017-09-19 11:42:05,739 - Skipping stack-select on RU_EXECUTE_TASKS because
> it does not exist in the stack-select package structure.
> 2017-09-19 11:42:05,739 - An upgrade/downgrade for HDP-2.5.3.0-37 is in
> progress, determining which hadoop conf dir to use.
> 2017-09-19 11:42:05,740 - Skipping stack-select on RU_EXECUTE_TASKS because
> it does not exist in the stack-select package structure.
> 2017-09-19 11:42:05,740 - Hadoop conf dir: /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-09-19 11:42:05,740 - Using hadoop conf dir:
> /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-09-19 11:42:05,742 - Before starting Stack Upgrade, check if tez tarball
> has been copied to HDFS.
> 2017-09-19 11:42:05,742 - Stack version 2.6.0.0 is sufficient to check if
> need to copy tez.tar.gz to HDFS.
> 2017-09-19 11:42:05,742 - Called copy_to_hdfs tarball: tez
> 2017-09-19 11:42:05,743 - Stack Feature Version Info: Cluster Stack=2.6,
> Command Stack=None, Command Version=2.5.3.0-37, Upgrade Direction=upgrade ->
> 2.5.3.0-37
> 2017-09-19 11:42:05,743 - Skipping stack-select on RU_EXECUTE_TASKS because
> it does not exist in the stack-select package structure.
> 2017-09-19 11:42:05,743 - Unable to determine the current version of the
> component for this command; unable to copy the tarball
> 2017-09-19 11:42:05,743 - Cannot copy tez tarball to HDFS because stack
> version could be be determined.
> 2017-09-19 11:42:05,743 - Cannot copy tez tarball to HDFS because stack
> version could be be determined.
> 2017-09-19 11:42:05,744 - Could not copy tarball tez due to a missing or
> incorrect parameter.
> 2017-09-19 11:42:05,744 - Could not copy tarball tez due to a missing or
> incorrect parameter.
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/pre_upgrade.py",
> line 58, in
> TezPreUpgrade().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 327, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/pre_upgrade.py",
> line 55, in prepare
> raise Fail("Could not copy tez tarball to HDFS.")
> resource_management.core.exceptions.Fail: Could not copy tez tarball to HDFS.
> Command failed after 1 tries
> {code}
> stderr:-
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 156, in
> ExecuteUpgradeTasks().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 327, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 153, in actionexecute
> shell.checked_call(task.command, logoutput=True, quiet=True)
> 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
[jira] [Updated] (AMBARI-22024) Stack and versions view style issues
[ https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22024: - Description: # Corners on versions headers should match. We need to make non-triangle area higher. # All versions headers should have a background. For example, installing proccess. # This menu must be left centred like every other. # Buttons background on click should be blue as previous. # Since this shows up as “Hidden” in the version list this call to action should be “Hide”, this menu must be left centred. was: # Corners on versions headers should match. We need to make non-triangle area higher. # All versions headers should have a background. For example, installing proccess. # This menu must be left centred like every other: # Buttons background on click should be blue as previous: # Since this shows up as “Hidden” in the version list this call to action should be “Hide”, this menu must be left centred. > Stack and versions view style issues > > > Key: AMBARI-22024 > URL: https://issues.apache.org/jira/browse/AMBARI-22024 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22024.patch > > > # Corners on versions headers should match. We need to make non-triangle area > higher. > # All versions headers should have a background. For example, installing > proccess. > # This menu must be left centred like every other. > # Buttons background on click should be blue as previous. > # Since this shows up as “Hidden” in the version list this call to action > should be “Hide”, this menu must be left centred. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22022) NullPointerException in ActionScheduler when using DEPENDENCY_ORDERED execution
[ https://issues.apache.org/jira/browse/AMBARI-22022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174849#comment-16174849 ] Hudson commented on AMBARI-22022: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8110 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8110/]) AMBARI-22022. NullPointerException in ActionScheduler when using (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3e5f60ab9d30761df08923c4e56dd518fc71d271]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java > NullPointerException in ActionScheduler when using DEPENDENCY_ORDERED > execution > --- > > Key: AMBARI-22022 > URL: https://issues.apache.org/jira/browse/AMBARI-22022 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 3.0.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 3.0.0 > > Attachments: AMBARI-22022.patch > > > NullPointerException may occur in ActionScheduler when using > DEPENDENCY_ORDERED execution. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22024) Stack and versions view style issues
[ https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-22024: Assignee: Antonenko Alexander > Stack and versions view style issues > > > Key: AMBARI-22024 > URL: https://issues.apache.org/jira/browse/AMBARI-22024 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22024.patch > > > # Corners on versions headers should match. We need to make non-triangle area > higher. > # All versions headers should have a background. For example, installing > proccess. > # This menu must be left centred like every other: > # Buttons background on click should be blue as previous: > # Since this shows up as “Hidden” in the version list this call to action > should be “Hide”, this menu must be left centred. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22024) Stack and versions view style issues
[ https://issues.apache.org/jira/browse/AMBARI-22024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22024: - Attachment: AMBARI-22024.patch > Stack and versions view style issues > > > Key: AMBARI-22024 > URL: https://issues.apache.org/jira/browse/AMBARI-22024 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22024.patch > > > # Corners on versions headers should match. We need to make non-triangle area > higher. > # All versions headers should have a background. For example, installing > proccess. > # This menu must be left centred like every other: > # Buttons background on click should be blue as previous: > # Since this shows up as “Hidden” in the version list this call to action > should be “Hide”, this menu must be left centred. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22024) Stack and versions view style issues
Antonenko Alexander created AMBARI-22024: Summary: Stack and versions view style issues Key: AMBARI-22024 URL: https://issues.apache.org/jira/browse/AMBARI-22024 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Priority: Critical Fix For: 2.6.0 # Corners on versions headers should match. We need to make non-triangle area higher. # All versions headers should have a background. For example, installing proccess. # This menu must be left centred like every other: # Buttons background on click should be blue as previous: # Since this shows up as “Hidden” in the version list this call to action should be “Hide”, this menu must be left centred. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174833#comment-16174833 ] Hudson commented on AMBARI-22023: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #263 (See [https://builds.apache.org/job/Ambari-branch-2.6/263/]) AMBARI-22023 Upgrade dialog style issues. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1cb4ee144779f013c5454033c77c6f1870b00130]) * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_group.hbs * (edit) ambari-web/app/routes/stack_upgrade_routes.js * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_wizard_view_test.js * (edit) ambari-web/app/views/common/helpers/status_icon_view.js * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_wizard_view.js * (edit) ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 2.png, AMBARI-22023.patch > > > Upgrade dialog should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22019) Enable logsearch-web unit tests and make them skippable
[
https://issues.apache.org/jira/browse/AMBARI-22019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174820#comment-16174820
]
Hadoop QA commented on AMBARI-22019:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888254/AMBARI-22019.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12316//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12316//console
This message is automatically generated.
> Enable logsearch-web unit tests and make them skippable
> ---
>
> Key: AMBARI-22019
> URL: https://issues.apache.org/jira/browse/AMBARI-22019
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0
>
> Attachments: AMBARI-22019.patch
>
>
> enable UT for logseach-web
> can be skipped by adding -DskipTests to the mvn command
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22020) Setup tez ats loglevel to TASK_ATTEMPT to enable the filters.
[
https://issues.apache.org/jira/browse/AMBARI-22020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174817#comment-16174817
]
Hadoop QA commented on AMBARI-22020:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888255/AMBARI-22020.01.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/12315//console
This message is automatically generated.
> Setup tez ats loglevel to TASK_ATTEMPT to enable the filters.
> -
>
> Key: AMBARI-22020
> URL: https://issues.apache.org/jira/browse/AMBARI-22020
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Harish Jaiprakash
> Attachments: AMBARI-22020.01.patch
>
>
> tez.history.logging.log.level should be TASK_ATTEMPT so that task kill filter
> will work.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21406) Refresh configurations without restarting components
[
https://issues.apache.org/jira/browse/AMBARI-21406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174813#comment-16174813
]
Hadoop QA commented on AMBARI-21406:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888265/AMBARI-21406-v5.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12314//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12314//console
This message is automatically generated.
> Refresh configurations without restarting components
>
>
> Key: AMBARI-21406
> URL: https://issues.apache.org/jira/browse/AMBARI-21406
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent, ambari-server
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
> Fix For: 3.0.0
>
> Attachments: AMBARI-21406-v1.patch, AMBARI-21406-v2.patch,
> AMBARI-21406-v3.patch, AMBARI-21406-v4.patch, AMBARI-21406-v5.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21919) Kerberos identity references should use the "reference" attribute
[
https://issues.apache.org/jira/browse/AMBARI-21919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174811#comment-16174811
]
Hadoop QA commented on AMBARI-21919:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888267/AMBARI-21919_branch-2.6_02.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/12313//console
This message is automatically generated.
> Kerberos identity references should use the "reference" attribute
> -
>
> Key: AMBARI-21919
> URL: https://issues.apache.org/jira/browse/AMBARI-21919
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos_descriptor
> Fix For: 2.6.0
>
> Attachments: AMBARI-21919_branch-2.6_01.patch,
> AMBARI-21919_branch-2.6_02.patch, AMBARI-21919_trunk_01.patch,
> AMBARI-21919_trunk_02.patch
>
>
> Kerberos identity references should use the "reference" attribute rather than
> rely on the "name" attribute to indicate the identity descriptor references
> some other identity descriptor.
> Either method should work on the backend, however the UI appears to not fully
> handle the "named" reference properly.
> The solution is to change
> {code}
> {
> "name": "/HDFS/NAMENODE/namenode_nn",
> "principal": {
> "configuration":
> "ranger-hdfs-audit/xasecure.audit.jaas.Client.option.principal"
> },
> "keytab": {
> "configuration":
> "ranger-hdfs-audit/xasecure.audit.jaas.Client.option.keyTab"
> }
> }
> {code}
> by changing the "name" attribute to "reference" and adding a new "name"
> reference with a unique name relative to the scope of the identity
> descriptor. For example:
> {code}
> {
> "name":"ranger_hdfs_audit"
> "reference": "/HDFS/NAMENODE/namenode_nn",
> "principal": {
> "configuration":
> "ranger-hdfs-audit/xasecure.audit.jaas.Client.option.principal"
> },
> "keytab": {
> "configuration":
> "ranger-hdfs-audit/xasecure.audit.jaas.Client.option.keyTab"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22021) Livy not working with the default configuration
[
https://issues.apache.org/jira/browse/AMBARI-22021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174808#comment-16174808
]
Hadoop QA commented on AMBARI-22021:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888280/AMBARI-22021_trunk_v2.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12311//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12311//console
This message is automatically generated.
> Livy not working with the default configuration
> ---
>
> Key: AMBARI-22021
> URL: https://issues.apache.org/jira/browse/AMBARI-22021
> Project: Ambari
> Issue Type: Bug
>Reporter: Prabhjyot Singh
> Attachments: AMBARI-22021_trunk_v1.patch, AMBARI-22021_trunk_v2.patch
>
>
> This started failing with ZEPPELIN-2909, which introduces `"className":
> "org.apache.zeppelin.livy.LivySharedInterpreter". and now Livy fails with
> following exception;
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.zeppelin.livy.BaseLivyInterpreter.open(BaseLivyInterpreter.java:109)
> at
> org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:69)
> at
> org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:493)
> at org.apache.zeppelin.scheduler.Job.run(Job.java:175)
> at
> org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
