Project

General

Profile

Refactor #10413

Reimplement !unattended mode support as mainline feature

Added by Dominic Cleal over 6 years ago. Updated over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Host creation
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

settings.yaml contains :unattended set to true by default, which enables provisioning related features during initialisation. Turning it off is meant to put Foreman into a reporting-only mode, suitable for use as a dashboard, but it's notoriously unreliable and untested.

Many major releases contain regressions because !unattended users are a minority and all developers and tests run with unattended enabled in order to test all features.

I'd suggest that we should remove this global setting and make sure Foreman can operate sensibly and be well-tested with both reporting-only and provisioning usage in a single, default configuration.


The main difference was always the New Host page, which had significant behaviour differences around OS requirements and the tabs shown. When in unattended mode, it is only possible to create a managed host in the New Host form.

Related is that there's an inconsistency in use of the host "managed" flag. Generally when unattended is enabled and hosts are !managed, Foreman acts similarly to !unattended mode. We should probably migrate hosts created under !unattended to being !managed hosts and then have Foreman work well with both managed and !managed hosts.

Related again, consider how Host::Managed should be split up or renamed when it's an unmanaged host.


Related issues

Related to Foreman - Bug #10307: Editing a host with "unattended: false" set in settings.yaml results in error.Closed2015-04-29
Related to Foreman - Bug #10379: Facts import error: no superclass method `setup_clone' for #<Host::Managed...>Closed2015-05-05
Related to Foreman - Bug #4018: API host creation fails with 500 error when unattended == falseNew2014-01-15
Related to Foreman - Bug #16866: Facts import doesn't work with unattended=falseClosed2016-10-11

History

#1 Updated by Dominic Cleal over 6 years ago

  • Related to Bug #10307: Editing a host with "unattended: false" set in settings.yaml results in error. added

#2 Updated by Marek Hulán over 6 years ago

  • Related to Bug #10379: Facts import error: no superclass method `setup_clone' for #<Host::Managed...> added

#3 Updated by Rickard von Essen over 6 years ago

  • Related to Bug #4018: API host creation fails with 500 error when unattended == false added

#4 Updated by Anonymous about 5 years ago

  • Related to Bug #16866: Facts import doesn't work with unattended=false added

Also available in: Atom PDF