Hide Forgot
Description of problem: Sat 6.1.8 on RHEL 7.2 Capsule 6.1.4 on RHEL 7.2 (didn't have time to update both on the same day) A colleague tried to publish a new CV (adding a puppet module) and wondered why the module is on the Satellite itself but not on the Capsule. Seems the sync between 6.1.8 and 6.1.4 did not work, production log contained lines like this: 2016-04-07 09:27:21 [F] ActionController::RoutingError (No route matches [GET] "/pulp/nodes/https/repos/…"): /usr/share/gems/gems/passenger-4.0.18/lib/phusion_passenger/rack/thread_handler_extension.rb:77:in `process_request' /usr/share/gems/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:140:in `accept_and_process_next_request' /usr/share/gems/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:108:in `main_loop' /usr/share/gems/gems/passenger-4.0.18/lib/phusion_passenger/request_handler.rb:441:in `block (3 levels) in start_threads' After the update of the Capsule (and a forced sync) everything seems good again. I think it would be nice if the sync job fails with an error message saying the versions are incompatible instead of finishing sucessfully (according to the forman task) but not having all the content synced.
Moving 6.2 bugs out to sat-backlog.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.