Hide Forgot
+++ This bug was initially created as a clone of Bug #1369234 +++ If I attempt to delete a content view version, either from the CLI or GUI, it takes a long time to start, and typically times out in the CLI, and leads to the delete confirmation screen in the GUI to sit with an hourglass forever. When this happens, the dynflow task shows as planning/pending, and there is a single 'ruby' process running, using 100% of one CPU core. If this is left, it eventually stops doing this, and the task starts and does eventually complete. There was a suggestion that there was a problem with lack of entropy on the system - I installed and run haveged, and while initially it seemed like it could have helped, it seems that patience was what really helped - it just takes a *long* time to delete a content view version. --- Additional comment from Brad Buckingham on 2016-08-22 14:40:37 EDT --- Created from redmine issue http://projects.theforeman.org/issues/15531 --- Additional comment from Brad Buckingham on 2016-08-22 15:19:21 EDT --- Upstream Katello PR: https://github.com/Katello/katello/pull/6263 --- Additional comment from RHEL Product and Program Management on 2016-08-22 16:30:28 EDT --- Since this issue was entered in Red Hat Bugzilla, the pm_ack has been set to + automatically for the next planned release --- Additional comment from Bryan Kearney on 2016-10-03 13:32:13 EDT --- Moving all bugs POST fixed in katello 3.0.x or 3.1 to ON_QA for satellite 6.3. --- Additional comment from Manikandan Somasundaram on 2016-10-17 13:34:18 EDT --- cu update on case : 01683120 Andrew Homich (10/13/2016 11:59 AM) Just an update - I've been watching this more closely and found out that progress doesn't show during the "planning" phase. This phase usually takes the longest time. Once it goes to actual removal, then progress bar is displayed correctly in GUI. --- Additional comment from Roman Plevka on 2016-11-10 08:40:23 EST --- is this supposed to be reproducible even on empty, non-promoted content-views? i was unable to reproduce this on # rpm -qa satellite satellite-6.2.4-1.0.el7sat.noarch # rpm -qa katello katello-3.0.0-14.el7sat.noarch ` # hammer content-view publish --id 3 # hammer content-view version list --content-view-id 3 ---|------------|---------|----------------------- ID | NAME | VERSION | LIFECYCLE ENVIRONMENTS ---|------------|---------|----------------------- 5 | foo_cv 2.0 | 2.0 | Library ---|------------|---------|----------------------- # hammer content-view version delete --id 5 --content-view-id 3 Could not delete the content view: Cannot delete version while it is in environments: Library # hammer content-view remove-from-environment --id 3 --lifecycle-environment-id 1 [..................] [100%] # time hammer content-view version delete --id 5 --content-view-id 3 [..................................................................................................................................................] [100%] real 0m4.265s user 0m1.788s sys 0m0.189s ` Could you provide more specific steps to reproducte the issue if mine are not correct?
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/15531 has been resolved.
For the CVV I removed (consisting of RHEL 7 server promoted to one environment) this took 17.56s which is a huge improvement over 10 minutes. I am marking this as verified against sat 6.3.0 snap 9.
Created attachment 1308848 [details] removal request timing
(In reply to Walden Raines from comment #3) > For the CVV I removed (consisting of RHEL 7 server promoted to one > environment) this took 17.56s which is a huge improvement over 10 minutes. > I am marking this as verified against sat 6.3.0 snap 9. Neglected to mention that this is around the same time this operation takes in 6.2.z.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:0336