Bug #3915
Hammer does not handle 404s well
Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman commands (obsolete)
Target version:
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:
Description
Hammer should return more informative messages than
Could not create the subnet: 404 Resource Not Found
or
RestClient::ResourceNotFound (404 Resource Not Found)
when --verbose is set.
https://github.com/theforeman/foreman/pull/1098 needs to be merged for this to happen though.
Related issues
Associated revisions
History
#1
Updated by Daniel Lobato Garcia over 8 years ago
- Related to Bug #3515: Associated resources not found by ID causes 500 Internal Server Error added
#2
Updated by Daniel Lobato Garcia over 8 years ago
- Related to deleted (Bug #3515: Associated resources not found by ID causes 500 Internal Server Error)
#3
Updated by Daniel Lobato Garcia over 8 years ago
- Blocked by Bug #3515: Associated resources not found by ID causes 500 Internal Server Error added
#4
Updated by Tomáš Strachota over 8 years ago
- Has duplicate Bug #3514: Improve 404 response when a resource isn't found added
#5
Updated by Tomáš Strachota over 8 years ago
- Category changed from Hammer core to Foreman commands (obsolete)
- Status changed from New to Assigned
- Assignee set to Tomáš Strachota
Switched the category to Foreman commands as the handling will be foreman specific.
#6
Updated by Tomáš Strachota over 8 years ago
- Status changed from Assigned to Ready For Testing
#7
Updated by Dominic Cleal over 8 years ago
- Target version set to 1.9.2
#8
Updated by Anonymous over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman:hammer-cli-foreman|commit:e34ae228a4c29d01952bf3372ca8598543213b38.
fixes #3915 - better handling of 404 exceptions