[jira] [Commented] (AMBARI-7586) "Request name not specified" BG hangs after Upgrade from 1.6.0 to 1.7.0 on secured cluster

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154826#comment-14154826 ] 

Hudson commented on AMBARI-7586:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #439 (See [https://builds.apache.org/job/Ambari-trunk-Commit/439/])
AMBARI-7586. "Request name not specified" BG hangs after Upgrade from 1.6.0 to 1.7.0 on secured cluster.(vbrodetskyi) (vbrodetskyi: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f3c4e436eae156320c41660322604ee24988f426)
* ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog170.java
* ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/package/scripts/params.py


> "Request name not specified" BG hangs after Upgrade from 1.6.0 to 1.7.0 on secured cluster
> ------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-7586
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7586
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent, ambari-server
>    Affects Versions: 1.7.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Blocker
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7586.patch
>
>
> 1) Deploy cluster with all components and default values. (1.6.0)
> 2) Make security enabled 
> STR:
> 1) Make Upgrade
> 2) Look at UI BG-operation list
> Expected result:
> All BG were passed. Have not BG in progress.
> Actual result:
> "Request name not specified" BG hangs for 2+ hours after Upgrade from 1.6.0 to 1.7.0 on secured cluster



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)