Project

General

Profile

Bug #26754

Wrong error message when changing the location of a compute resource to location that doesn't exists

Added by Shira Maximov over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
API
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:

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

Associated revisions

Revision 6997608c (diff)
Added by Shira Maximov about 1 year ago

Fixes #26754 - Change error when updating nested resource fails

History

#1 Updated by Shira Maximov over 1 year 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

#2 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/6742 added

#3 Updated by The Foreman Bot about 1 year ago

  • Fixed in Releases 1.24.0 added

#4 Updated by Tomer Brisker about 1 year ago

  • Category set to API
  • 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

#5 Updated by Tomer Brisker about 1 year ago

  • Assignee set to Shira Maximov

#6 Updated by Shira Maximov about 1 year ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF