Description of problem: ---------------------- When a Content View fails to provision, it throws "500 Internal Server Error" message. However, the customer feels that the error code that should be thrown when the token expires is 4.1 Version-Release number of selected component (if applicable): ------------------------------------------------------------ Red Hat Satellite 6.6 Steps to Reproduce: ------------------ Following are the steps shared by the customer to reproduce the issue - 1. Create a host. 2. Trigger the build. 3. Let token expire. 4. Boot the node. 5. Check error message. It will be 500. Actual results: -------------- The screenshot (error500.png) shows - "500 Internal Server Error" message. Expected results: ---------------- The customer thinks that it should be error message with the error code of 401 (Comment-9 and Case Description). Additional info: --------------- I had informed him that the error code 401 is for "incorrect user authentication" and error code 500 is for "Internal Server Error", and had shared the following link with him (Comment-4) - https://access.redhat.com/documentation/en-us/red_hat_satellite/6.6/html-single/api_guide/index#appe-Response_Codes Also attaching the screenshots provided by the customer to the ticket.
Created redmine issue https://projects.theforeman.org/issues/35068 from this bug
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.
Created redmine issue https://projects.theforeman.org/issues/36243 from this bug
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35068 has been resolved.
https://github.com/theforeman/smart-proxy/pull/869
Moving back to assigned, https://github.com/theforeman/smart-proxy/pull/869 is still in review
Verified. Version Tested: Satellite 6.14.0 Snap 5.0 Verification Steps: 1. Create a host, register it. 2. Update the "token expiration" setting in Administer --> Settings to 5 minutes so that token will expire soon. 3. Start provisioning the host. 4. Boot the host. 5. Check the error message. Result: It no longer shows 500 error after token expires and gives proper error.