Bug #11047: Interfaces are imported even though ignore_puppet_facts_for_provisioning is set to true - Foreman

Custom queries

3.10.0 release DONE
3.10.0 release TODO
3.11.0 release DONE
3.11.0 release TODO
3.8.1 release DONE
3.8.1 release TODO
3.9.2 release DONE
3.9.2 release TODO
All bugs by votes
All issues closed in the last 3 weeks
Easy and Trivial Issues
Easy Issues (only)
Foreman - new open issues in last 10 days
Good first issues - Foreman core
high prio open bugs
Host registration [open]
Mine
My issues closed in the last 3 weeks
old bugs
Open with target version set (aka blockers)
registration
taken-none
Team Atlas untriaged bugs
templates
Trivial Issues
Untriaged and opened in the past two weeks

Actions

Copy link

Bug #11047

closed

Interfaces are imported even though ignore_puppet_facts_for_provisioning is set to true

Added by Marek Hulán almost 9 years ago. Updated about 7 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Facts

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

1.8.2

Red Hat JIRA:

Description

User reports that after enabling ignore_puppet_facts_for_provisioning to true and upgrade from 1.7.2 to 1.8.2, interfaces are still being imported. See #9104 for more details. According to code, importing should be disabled

https://github.com/theforeman/foreman/blob/1.8.2/app/services/fact_parser.rb#L95
https://github.com/theforeman/foreman/blob/1.8.2/app/models/host/base.rb#L150

Related issues 2 (0 open — 2 closed)

	Related to Foreman - Feature #9104: Disable auto network interfaces	Closed	Marek Hulán	01/25/2015			Actions
	Related to Discovery - Bug #12391: Discovery breaks ignore_puppet_facts_for_provisioning global setting	Closed	Lukas Zapletal	11/04/2015			Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Marek Hulán almost 9 years ago

Related to Feature #9104: Disable auto network interfaces added

Actions

Copy link

Updated by Marek Hulán almost 9 years ago

Status changed from New to Need more information

I'm unable to reproduce the behaviour, ignore_puppet_facts_for_provisioning settings is effective and works correctly on my setup. Mark, could you please upgrade to 1.8 again, remove interfaces, enable debug mode, rerun puppet agent and paste a production.log or ideally run foreman-debug? Also adding few debugging lines to the code would help to find the cause.

Actions

Copy link

Updated by The Foreman Bot almost 9 years ago

Status changed from Need more information to Ready For Testing
Pull request https://github.com/theforeman/foreman/pull/2616 added
Pull request deleted ()

Actions

Copy link

Updated by Marek Hulán almost 9 years ago

Status changed from Ready For Testing to Need more information
Pull request added
Pull request deleted (~~https://github.com/theforeman/foreman/pull/2616~~)

Reverting back, typo in commit message

Actions

Copy link

Updated by Jörn Ott over 8 years ago

Marek Hulán wrote:

I'm unable to reproduce the behaviour, ignore_puppet_facts_for_provisioning settings is effective and works correctly on my setup. Mark, could you please upgrade to 1.8 again, remove interfaces, enable debug mode, rerun puppet agent and paste a production.log or ideally run foreman-debug? Also adding few debugging lines to the code would help to find the cause.

I have a physical server with 4 physical NICs and I use openvswitch to bond them together. One virtual port is int0 (bound to the internal VLAN) and the other is ext0 (bound to the external VLAN). As a result, foreman shows a lot of NICs (also ovs-system showing up 4 times with different MAC addresses). It does not list ext0 however and enp2s0f0 is shown as eth0 instead.

When I try to edit the host in foreman, it complains about invalid interfaces. When I try to delete the interfaces I don't want to show up, they are re-added and saving the host fails again.

Actions

Copy link