Project

General

Profile

Bug #25513

compute resource host import does not correctly set the compute resource

Added by Timo Goebel about 2 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources
Target version:
Difficulty:
easy
Triaged:
No
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

When importing a host from a compute resource into Foreman, the compute resource is not set on the host object. The host needs to be associated manually after the import.

Associated revisions

Revision 8c0afbbf (diff)
Added by Timo Goebel about 2 months ago

fixes #25513 - associate host during import

History

#1 Updated by The Foreman Bot about 2 months ago

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

#2 Updated by Tomer Brisker about 2 months ago

  • Fixed in Releases 1.19.2, 1.20.1, 1.21.0 added

#3 Updated by Timo Goebel about 2 months ago

  • Status changed from Ready For Testing to Closed

#4 Updated by Ewoud Kohl van Wijngaarden about 1 month ago

  • Subject changed from compute resource host import does not correctly set the compute ressource to compute resource host import does not correctly set the compute resource

Also available in: Atom PDF