Red Hat Bugzilla – Bug 1465389
ssh key creation in User throws 'page doesn't exists' error
Last modified: 2017-08-15 15:47:24 EDT
Created attachment 1292268 [details] Screenshot Attached Description of problem: While creating a ssh key from new user dialog, clicking and submitting 'create ssh key' button throws 'The page you were looking for doesn't exist.' error. Version-Release number of selected component (if applicable): Satellite 6.3.0 snap 4 How reproducible: Always Steps to Reproduce: 1. Go to Admin -> Users -> New User -> ssh keys tab 2. Click on 'create SSH key' button to create new ssh key. Actual results: Redirected to page showing an error 'The page you were looking for doesn't exist.' Expected results: The satellite should allow to create a new ssh key with user. Additional info:
Adding failure logs from production.log: ``` 017-06-27 10:45:06 927a33fa [app] [I] Started GET "/notification_recipients" for 10.65.223.122 at 2017-06-27 10:45:06 -0400 2017-06-27 10:45:06 927a33fa [app] [I] Processing by NotificationRecipientsController#index as JSON 2017-06-27 10:45:06 927a33fa [app] [I] Current user: admin (administrator) 2017-06-27 10:45:06 927a33fa [app] [I] Completed 200 OK in 4ms (Views: 0.1ms | ActiveRecord: 0.4ms) 2017-06-27 10:45:07 02f3beea [app] [I] Started GET "/users//ssh_keys/new" for 10.65.223.122 at 2017-06-27 10:45:07 -0400 2017-06-27 10:45:07 02f3beea [app] [F] | ActionController::RoutingError (No route matches [GET] "/users/ssh_keys/new"): | lib/middleware/tagged_logging.rb:18:in `call' | | 2017-06-27 10:45:08 f250b88e [app] [I] Started GET "/users//ssh_keys/new" for 10.65.223.122 at 2017-06-27 10:45:08 -0400 2017-06-27 10:45:08 f250b88e [app] [F] | ActionController::RoutingError (No route matches [GET] "/users/ssh_keys/new"): | lib/middleware/tagged_logging.rb:18:in `call' | | 2017-06-27 10:45:08 e1cba46f [app] [I] Started GET "/notification_recipients" for 10.65.223.122 at 2017-06-27 10:45:08 -0400 2017-06-27 10:45:08 e1cba46f [app] [I] Processing by NotificationRecipientsController#index as JSON 2017-06-27 10:45:08 e1cba46f [app] [I] Current user: admin (administrator) 2017-06-27 10:45:08 e1cba46f [app] [I] Completed 200 OK in 4ms (Views: 0.1ms | ActiveRecord: 0.6ms) ```
This happens only when the user is not saved yet. We shouldn't probably display create button until the user is already saved. Jitendra, I think this is not a blocker though. Could you please remove the blocker flag? Easy workaround is to create user, then edit him/her and create the ssh key from there.
Created redmine issue http://projects.theforeman.org/issues/20137 from this bug
Agree with comment 4.
Upstream bug assigned to mhulan@redhat.com
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20137 has been resolved.
Created attachment 1311603 [details] screenshot of UI before saving user VERIFIED Version Tested: Satellite-6.3 Snap 10 After saving user, 'create ssh key' redirects to respective page and before saving user, it shows "In order to create the SSH key, the user must be saved first".
Created attachment 1311605 [details] screenshot of UI ssh key create screen shot of page redirect after clicking 'create user key'