Project

General

Profile

Actions

Bug #35068

closed

Expired token should return 401 instead of 412

Added by Leos Stejskal over 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Unattended installations
Target version:
-
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1859112

1. Create a host
2. Trigger the build
3. Let the token expire
4. Boot the node
5. Check the error message

The status code should be 401, not 412

Actions #1

Updated by Leos Stejskal over 2 years ago

  • Subject changed from Error 500 returned when token expired while provisioning a Host to Error 500 returned when token expired while provisioning a Host
  • Description updated (diff)
  • Assignee set to Leos Stejskal
  • Triaged changed from No to Yes
Actions #2

Updated by Leos Stejskal over 1 year ago

  • Subject changed from Error 500 returned when token expired while provisioning a Host to Expired token should return 401 instead of 412
  • Description updated (diff)
Actions #3

Updated by The Foreman Bot over 1 year ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/9668 added
Actions #4

Updated by The Foreman Bot over 1 year ago

  • Fixed in Releases 3.7.0 added
Actions #5

Updated by Leos Stejskal over 1 year ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF