Project

General

Custom queries

Profile

Actions

Bug #26754

closed

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

Added by Shira Maximov about 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
API
Target version:
-
Difficulty:
Triaged:
No
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

#1

Updated by Shira Maximov about 6 years ago

  • Category deleted (19)
#2

Updated by The Foreman Bot about 6 years 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 almost 6 years ago

  • Fixed in Releases 1.24.0 added
#4

Updated by Tomer Brisker almost 6 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
#5

Updated by Tomer Brisker almost 6 years ago

  • Assignee set to Shira Maximov
#6

Updated by Shira Maximov almost 6 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF