Bug 1369234
Summary: | Deleting a Content View version takes a long time (to start) | |||
---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Brad Buckingham <bbuckingham> | |
Component: | Content Views | Assignee: | Brad Buckingham <bbuckingham> | |
Status: | CLOSED ERRATA | QA Contact: | Roman Plevka <rplevka> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 6.2.0 | CC: | bbuckingham, bkearney, chrobert, cwelton, mmccune, msomasun, oshtaier, rplevka, zhunting | |
Target Milestone: | Unspecified | Keywords: | Performance, PrioBumpField, Triaged | |
Target Release: | Unused | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | tfm-rubygem-katello-3.0.0.86-1 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1394420 (view as bug list) | Environment: | ||
Last Closed: | 2016-12-12 17:13:21 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1394420 |
Description
Brad Buckingham
2016-08-22 18:40:33 UTC
Created from redmine issue http://projects.theforeman.org/issues/15531 Upstream Katello PR: https://github.com/Katello/katello/pull/6263 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? In certain situations it can completely fail to ever get past the Planning phase and never delete. We need to get this into 6.2.z Roman, to test, I'd recommend doing a 'Remove' via the UI of a content view version that contains a lot of data (e.g. packages, errata...etc). The issue that was observed was that it took a very long time to 'plan' the removal task as that step would actually destroy a lot of the data that had been indexed as part of that version within Katello. VERIFIED
# rpm -qa satellite
satellite-6.2.5-1.0.el7sat.noarch
synced a rhel7 server repo and published it inside a CV.
>13443 Packages
>1304 Errata ( 309 824 171 )
Removal of the CV version took about 5 seconds
run:
5: Actions::Pulp::Repository::Destroy (success) [ 1.60s / 0.27s ]
11: Actions::Pulp::Repository::Destroy (success) [ 3.59s / 0.38s ]
17: Actions::Pulp::Repository::Destroy (success) [ 1.61s / 0.29s ]
finalize:
8: Actions::Katello::Repository::Destroy (success) [ 0.01s / 0.01s ]
14: Actions::Katello::Repository::Destroy (success) [ 0.01s / 0.01s ]
18: Actions::Katello::ContentViewPuppetEnvironment::Destroy (success) [ 0.03s / 0.03s ]
19: Actions::Katello::ContentViewVersion::Destroy (success) [ 0.07s / 0.07s ]
20: Actions::Katello::ContentView::Remove (success) [ 0.01s / 0.01s ]
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/RHBA-2016:2940 |