Project

General

Profile

Bug #8415

Cannot edit Foreman host after upgrading to next minor release

Added by Stephen Benjamin over 4 years ago. Updated 11 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Hosts
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

After upgrading a host from 6.5 to 6.6, Facter reports the new operating system to Foreman which gets automatically created without installation media.

When you edit the host, Foreman will not save the host, unless you revert the OS to 6.5 (or set some OS with installation media).

I'm not sure if this should be considered a Foreman or Katello bug -- but I would think new OS's of a certailn major should automatically get the Katello distributions of the same major -- e.g. there's no reason I couldn't provision a machine with 6.5 ks tree and it gets updated to 6.6 or 6.7 in the KS post.

Especially if we now asking users to sync the point-release kickstart repos: this is a manual process, while the RPMs repo could get bumped to the next minor as part of a sync plan, for example.

History

#1 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) set to 14
  • Triaged changed from No to Yes

#2 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) changed from 14 to 23

#3 Updated by Eric Helms over 4 years ago

  • Target version set to 67

#4 Updated by Eric Helms over 4 years ago

  • Target version changed from 67 to 68

#5 Updated by Eric Helms about 4 years ago

  • Target version deleted (68)
  • Legacy Backlogs Release (now unused) deleted (23)

#6 Updated by Eric Helms over 3 years ago

  • Legacy Backlogs Release (now unused) set to 114

Also available in: Atom PDF