Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Promoting Content View version results in ActionController::RoutingError (No route matches [POST] "/katello/api/v2/content_view_versions/promote")
Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140321.2
How reproducible:
always
Steps to Reproduce:
1. Sync RHEL 6.5 RPMs and Kickstart
2. Create Content View with these repos selected
3. Publish first version of that content view
4. Publish the CV to Library first
Actual results:
Got empty red box when promoting. And error in the logs.
Expected results:
Content should be promoted nicely
Additional info:
==> /var/log/foreman/production.log <==
ActionController::RoutingError (No route matches [POST] "/katello/api/v2/content_view_versions/promote"):
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.5/lib/phusion_passenger/rack/thread_handler_extension.rb:77:in `process_request'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.5/lib/phusion_passenger/request_handler/thread_handler.rb:140:in `accept_and_process_next_request'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.5/lib/phusion_passenger/request_handler/thread_handler.rb:108:in `main_loop'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.5/lib/phusion_passenger/request_handler.rb:441:in `block (3 levels) in start_threads'
Comment 1RHEL Program Management
2014-03-24 21:54:31 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
I'm 95% sure you are hitting:
http://projects.theforeman.org/issues/4847
along with http://projects.theforeman.org/issues/4782
The issue is that a rest call is made which takes over a minute to return, in the meantime the page should not be interacted with but the ui doesn't stop you from doing so. So some inaccurate data is presented (the view is already in library by default), and the promote button causes a failure. The Good news is that http://projects.theforeman.org/issues/4782 is already fixed upstream so the issue should not be very apparent now that the rest call returns within a second or two.
Verified as below:
1. Synced RHEL 6.5 RPMs and Kickstart
2. Created Content View with these repos selected
3. Published first version of that content view version1 to Library successfully
as seen from the screenshot attached.