Bug #26754
closed
Wrong error message when changing the location of a compute resource to location that doesn't exists
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1692753
Description of problem:
After adding the a compute resource from API, and changing its location via PUT request, just navigating the organisation from UI makes Foreman crash, and also reset the ssl certs
Video link: https://drive.google.com/file/d/1rvd-aX9-D7piO3_szR0VdbASGGrHpZZ4/view?usp=sharing
Check the video for more info
Version-Release number of selected component (if applicable):
master of kubevirt plugin
How reproducible:
Not always, but many times, was able to reproduce 5+ times
Steps to Reproduce:
1.Add a Compute resource from API
2.Change its location via a PUT call
3.Navigate through organisation in UI
Actual results:
Crashes Foreman and resets SSL Certs in Client Browser
Expected results:
Should show the Compute resource correctly without crashing
Additional info:
check the video
Updated by Shira Maximov over 5 years ago
- Category deleted (
19)
Description:
1.updating a compute resource with a location_id that doesn't exist send a wrong error message:
{
"compute_resource": {
"location_ids": [5]
}
}
"Compute resource doesn't exists" instead "Couldn't find Taxonomy with 'id'=[5]"
2. Location_id description is not very clear
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/6742 added
Updated by Tomer Brisker over 5 years ago
- Subject changed from [API] - Wrong error message when changing the location of a compute resource to location that doesn't exists to Wrong error message when changing the location of a compute resource to location that doesn't exists
- Category set to API
Updated by Shira Maximov over 5 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset 6997608ce585dd1b7b6699e43efc8b022d72cc5f.