You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/06/05 20:52:00 UTC
[jira] [Commented] (AMBARI-24026) Service deletion requests get
queued up in Background Ops during Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-24026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502486#comment-16502486 ]
Hudson commented on AMBARI-24026:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9407 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9407/])
[AMBARI-24026] - Service deletion requests get queued up in Background (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=856a2fc73922d18f530526d61c518ecc29784075])
* (edit) ambari-server/src/main/java/org/apache/ambari/annotations/ExperimentalFeature.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/DeleteUnsupportedServicesAndComponents.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/utilities/KerberosIdentityCleanerTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/RemovableIdentities.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/KerberosIdentityCleaner.java
> 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: Vivek Sharma
> Assignee: Jonathan Hurley
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: Screen Shot 2018-06-03 at 12.18.23 PM.png, Screen Shot 2018-06-03 at 12.18.49 PM.png, Screen Shot 2018-06-03 at 12.23.29 PM.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)