Bug #8450
closedmissing remote_user when trying to create new organization
Description
I'm trying to install a recompiled Satellite 6 on Scientific Linux 7.0 (essentially RHEL 7.0 recompiled from source)
Steps to reproduce:
1) Fresh install of Satellite 6 via katello-installer
2) Log in with admin account
3) Click Organizations -> Manage Organizations -> New Organization
4) Fill out Name, Label, Description. Click Submit
This returns an error page with the following output:
Task 3991a254-a044-40c9-9dda-b6d897102771: RuntimeError: missing :remote_user If you feel this is an error with Satellite 6 itself, please open a new issue with Foreman ticketing system, You would probably need to attach the Full trace and relevant log entries. ForemanTasks::TaskError Task 3991a254-a044-40c9-9dda-b6d897102771: RuntimeError: missing :remote_user app/controllers/concerns/foreman/controller/taxonomies_controller.rb:53:in `create' app/models/concerns/foreman/thread_session.rb:33:in `clear_thread' lib/middleware/catch_json_parse_errors.rb:9:in `call'
Let me know if there are any other relevant logs to attach.
Updated by Dominic Cleal over 9 years ago
- Project changed from Foreman to Katello
- Triaged set to No
Updated by Eric Helms over 9 years ago
- Status changed from New to Need more information
- Triaged changed from No to Yes
Howdy,
We don't support Satellite 6 upstream, if you would like to re-compile Katello 2.0 for Scientific Linux we may be able to help walkthrough the issues you encounter.
Updated by tony zheng almost 9 years ago
i got the same error message while creating the new org. i am on RHEL 6.6 and i download and installed foreman and katello manually myself by following your instructions on your page. please help.
Updated by Eric Helms over 8 years ago
- translation missing: en.field_release set to 114
Updated by John Mitsch over 4 years ago
- Status changed from Need more information to Rejected
- Target version deleted (
Katello Backlog)
Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.