Project

General

Profile

Feature #9104

Disable auto network interfaces

Added by Mark Chaney over 7 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Facts
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

I use foreman for provisioning and I have very complex network configurations. I want/need to use Foreman to keep track of what I want the network interface configurations to be, not what the server currently has configured. I do not want Foreman to automatically add network interfaces and I dont like the fact that they are automatically re-added after i delete them from Foreman. I had to spend well over a dozen hours trying to figure out my network configurations for all my servers that i hadnt worked on in 7 months and I had all of them configured in Foreman and they were all wiped practically when I upgraded from 1.5. to 1.7 because of this auto network import feature. Can we have the option not to automatically import them?

Simply put, I use Foreman for provisioning and keeping track of what the settings should be for my servers. Not what they currently are. =)


Related issues

Related to Foreman - Tracker #2409: NetworkingNew

Related to Foreman - Bug #3864: Change ignore_puppet_facts_for_provisioning default to trueRejected2013-12-12
Related to Foreman - Bug #11047: Interfaces are imported even though ignore_puppet_facts_for_provisioning is set to trueResolved2015-07-08
Related to Discovery - Bug #12391: Discovery breaks ignore_puppet_facts_for_provisioning global settingClosed2015-11-04

Associated revisions

Revision aa48b69c (diff)
Added by Marek Hulán over 7 years ago

Fixes #9104 - allow disabling of interface updates

History

#1 Updated by Marek Hulán over 7 years ago

  • Category set to Facts

Would you prefer one option to disable all host attributes updates (e.g. OS) or just network interfaces?

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

#3 Updated by Mark Chaney over 7 years ago

Marek Hulán wrote:

Would you prefer one option to disable all host attributes updates (e.g. OS) or just network interfaces?

I only need network attributes, but others might like the need to disable all of them. Maybe since the data is already stored as facts, there could be a button on a page that says Populate with Facts or something like that should someone want to pull them for a particular host or set of settings? Just an idea.

#4 Updated by Dominic Cleal over 7 years ago

  • Related to Bug #3864: Change ignore_puppet_facts_for_provisioning default to true added

#5 Updated by Jorick Astrego over 7 years ago

For when you already have a network setup, we would like the option to keep this and update the facts in foreman and the option to overwrite the currently used config and reload the network service to apply the new settings.

And maybe add a network managed/unmanaged flag to each nic/host/hostgroup

We use ovirt to manage the nic's of our virtualization hosts, but for the rest we want to use foreman. While some of the systems have a specific network setting that we apply through other means. Maybe we will use foreman to setup/manage these too but we would like to have the choice.

#6 Updated by Martin Jackson over 7 years ago

It seems that only the network facts are the scary ones to auto-update, because of the weirdness of the facts that contain them (e.g. ipaddress) and the amount of "intent" you have to divine to determine which one is the right one. There are lots of edge cases, too, where you could have a NIC replacement on a server that could throw everything off.

#7 Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2138 added
  • Pull request deleted ()

#8 Updated by Marek Hulán over 7 years ago

  • Assignee set to Marek Hulán
  • Legacy Backlogs Release (now unused) set to 28

Linked PR adds support to completely disable interfaces configuration based on facts (based on ignore_puppet_facts_for_provisioning setting). If there's need to change this behaviour per host/hostgroup/... please create a separate RFE.

#9 Updated by Marek Hulán over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#10 Updated by Mark Chaney about 7 years ago

Upgraded from 1.7.2 to 1.82. with this setting already set to true and new interfaces were still added and existing ones were reset.

#11 Updated by Marek Hulán about 7 years ago

  • Related to Bug #11047: Interfaces are imported even though ignore_puppet_facts_for_provisioning is set to true added

#12 Updated by Dominic Cleal almost 7 years ago

  • Related to Bug #12391: Discovery breaks ignore_puppet_facts_for_provisioning global setting added

Also available in: Atom PDF