Bug 1859112
Summary: | Error 500 returned when token expired while provisioning a Content Host | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Anand Jambhulkar <ajambhul> |
Component: | Provisioning | Assignee: | Leos Stejskal <lstejska> |
Status: | CLOSED ERRATA | QA Contact: | Shweta Singh <shwsingh> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.6.0 | CC: | gtalreja, inecas, lstejska, lzap, mfalz, rlavi, sganar, shwsingh, sshtein |
Target Milestone: | 6.14.0 | Keywords: | EasyFix, Reopened, Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-11-08 14:17:32 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Anand Jambhulkar
2020-07-21 09:38:46 UTC
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. 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. Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35068 has been resolved. Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35068 has been resolved. Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35068 has been resolved. 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. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Satellite 6.14 security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:6818 |