Project

General

Profile

Actions

Bug #25790

open

Host Parameters not being saved in v1.20.1

Added by Sina Anvari over 5 years ago. Updated over 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Web Interface
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

We have recently upgraded Foreman from v1.17.1 to v.1.20.1 and since then we have a problem with saving parameters for hosts.
  • Host -> Edit -> Parameter does NOT keep the changes.
  • Classes -> Select Class -> Smart Class Parameter -> Specify Matchers keeps the changes.

Files

production.log production.log 5.4 KB Sina Anvari, 01/07/2019 09:35 AM
Actions #1

Updated by Sina Anvari over 5 years ago

  • Priority changed from High to Normal

Some updates:
Not all hosts have this problems.
As far as we can tell, only hosts that have been installed via Foreman itself and not being managed by foreman anymore have issue saving parameters.
Clicking on submit returns to edit page again instead of host overview.

Workaround so far:
  • Host -> Edit -> Manage Host -> Submit
  • Host -> Edit -> Unmanage Host -> Submit

We have also compared hosts configs before and after submitting the workaround above.
Here are the diffs:

- ptable_id: 86,
- ptable_name: "LVM - Debian 1 HDD vg_sys (sep. var)",
+ ptable_id: null,
- medium_id: 9,
- medium_name: "Debian mirror",
+ medium_id: null,
+ medium_name: null,

Actions #2

Updated by Tomer Brisker over 5 years ago

the production.log attached seems to indicate save fails due to mismatch between medium and operating system, can you verify that the correct installation media is associated with the host's OS under "hosts->operating systems" please?

Actions #3

Updated by Sina Anvari over 5 years ago

Tomer, thanks for the reply and sorry if I was not clear enough in my last comment.
The systems are NOT being managed by Foreman anymore, thus the "Operating System" tab is not visible.
They have been installed using Foreman in v1.17.1 and instantly set to unmanaged after full OS installation.
Now after upgrading to v1.20.1, the problem above started to happen on all hosts, which has been previously installed via Foreman.

Actions

Also available in: Atom PDF