Bug #8415
closedCannot edit Foreman host after upgrading to next minor release
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.
Updated by Eric Helms over 9 years ago
- translation missing: en.field_release set to 14
- Triaged changed from No to Yes
Updated by Eric Helms over 9 years ago
- translation missing: en.field_release changed from 14 to 23
Updated by Eric Helms about 9 years ago
- Target version deleted (
68) - translation missing: en.field_release deleted (
23)
Updated by Eric Helms over 8 years ago
- translation missing: en.field_release set to 114
Updated by John Mitsch over 4 years ago
- Status changed from New to Closed
Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.
Updated by Justin Sherrill over 4 years ago
- Target version deleted (
Katello Backlog)
Updated by Justin Sherrill over 4 years ago
- Status changed from Closed to Rejected