Project

General

Profile

Actions

Bug #15644

closed

import_facts assumes orchestration is available

Added by Daniel Lobato Garcia almost 8 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Orchestration
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Currently (core:develop, discovery:develop) provisioning a discovered host isn't possible. The `import_facts` method assumes there are two methods defined, enable_orchestration! and skip_orchestration! which do not exist for Host::Discovered.

This causes Foreman to throw the following error "undefined method `enable_orchestration!' for #<Host::Discovered:0x005623782265b8>". This is also true when importing facts for a host with :unattended => false

Host::Discovered doesn't need the Orchestration module for anything, however `import_facts` assumes it's there. This should involve two fixes:

1: in discovery, so that it can skip those calls (mocking them or something).
2: in core, so that import_facts doesn't have to rely on anything but Host::Base APIs. It should "know less", and let Host::Managed do these things (enable/skip orchestration) perhaps, as that's where it matters.

The code that causes this error will go in 1.12.1 https://github.com/theforeman/foreman/pull/3574/files#diff-07cbb99bfdb4bed86ad02486bb5adde2R174 so we should hurry up and release a version that fixes the problem. http://projects.theforeman.org/issues/15306


Related issues 2 (0 open2 closed)

Related to Foreman - Bug #15306: Orchestration does not roll back queued actions if DB error occursClosedShimon Shtein06/06/2016Actions
Related to Foreman - Bug #17118: Error pushing facts to foremanDuplicate10/27/2016Actions
Actions

Also available in: Atom PDF