You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2018/06/04 17:29:00 UTC

[jira] [Created] (AMBARI-24026) Service deletion requests get queued up in Background Ops during Upgrade

Jonathan Hurley created AMBARI-24026:
----------------------------------------

             Summary: Service deletion requests get queued up in Background Ops during Upgrade
                 Key: AMBARI-24026
                 URL: https://issues.apache.org/jira/browse/AMBARI-24026
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.7.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
             Fix For: 2.7.0


On a cluster having Flume and Slider with HDP-2.6, started an Express Upgrade to HDP-3.0

The above services were deleted as part of removal task !Screen Shot 2018-06-03 at 12.18.49 PM.png|thumbnail! during EU


However the above operation created a corresponding request, which shows up in Background Operations window that is always in-progress state !Screen Shot 2018-06-03 at 12.18.23 PM.png|thumbnail!

*Expected Result*
We need to mark the request complete, else any failure at a later step would cause the user to see the above entries as in-progress which is confusing and undesirable
See the number 4 showing up here, towards top right in the background !Screen Shot 2018-06-03 at 12.23.29 PM.png|thumbnail!


Note: If the user pauses the Upgrade, that is when the above requests get marked as completed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)