Description of problem: We need more than an hour to do a new content-view publication and promotion to the first environment Version-Release number of selected component (if applicable): 6.2.9 How reproducible: Always Steps to Reproduce: # publish cv [root@sat6 ~]# time hammer content-view publish --id 3 [...................................................................................................................................................] [100%] real 26m46.722s user 0m7.689s sys 0m4.333s # update ccv [root@sat6 ~]# hammer content-view remove-version --id=9 --content-view-version-id=653 The component version has been removed [root@sat6 ~]# hammer content-view add-version --id=9 --content-view-version-id=661 The component version has been added # publish ccv [root@sat6 ~]# time hammer content-view publish --id 9 [...................................................................................................................................................] [100%] real 24m36.175s user 0m6.524s sys 0m3.574s # promote ccv [root@sat6 ~]# time hammer content-view version promote --id 662 --organization myorg --to-lifecycle-environment Lab [...................................................................................................................................................] [100%] real 17m49.099s user 0m5.197s sys 0m2.517s
Can you provide more details on the content that is in the content view being published and promoted? E.g. listing of repos (if available), # packages, erratum...etc
(In reply to Brad Buckingham from comment #2) > Can you provide more details on the content that is in the content view > being published and promoted? E.g. listing of repos (if available), # > packages, erratum...etc Please find the info attached, plain text file is hammer output and also some screenshots from the web UI. Let me know if anything is missing.
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
There have been a number of improvements in 6.4 that significantly improved content view publishing and promoting speeds.
Per Jakes Comments, I am marking this as closed/current releae. 6.4 had significant performance improvements. If you are using 6.4+ and are still seeing issues please feel free to open a new BZ.