Upgrade from 1.7.2 to latest and retain network settings

Support
1

I had to comment out some code at the direction of one of the devs with
1.7.2 so that i could enter my own network values as I wanted use foreman
to provision a server the way I wanted it to be, not the way its current
settings were. It was very frustrating when all my work would be wiped out
during a fact update. Anyway, the commenting out worked and I was told that
1.8.x made it so that we could have the network settings work this way
without having to hack any core code. My concern though is that i think
this new setting is something that I would have to enable, thus could wipe
out my network settings before I cant that setting enabled. Any suggestions
for a safe upgrade path?

2

Hello,

I think you're talking about "ignore_puppet_facts_for_provisioning" setting
which now affects all interfaces (since 1.8.0). could you point us to the
original issue just to be sure? Anyway you can just turn it on before the
upgrade and it should prevent any interface updates. And we always recommend
doing a backup of Foreman DB before updating.

··· On Monday 29 of June 2015 23:07:11 Mark Chaney wrote: > I had to comment out some code at the direction of one of the devs with > 1.7.2 so that i could enter my own network values as I wanted use foreman > to provision a server the way I wanted it to be, not the way its current > settings were. It was very frustrating when all my work would be wiped out > during a fact update. Anyway, the commenting out worked and I was told that > 1.8.x made it so that we could have the network settings work this way > without having to hack any core code. My concern though is that i think > this new setting is something that I would have to enable, thus could wipe > out my network settings before I cant that setting enabled. Any suggestions > for a safe upgrade path?

–
Marek

3

How can I turn off a setting that doesn't exist yet?

··· On Tue, Jun 30, 2015 at 3:42 AM, Marek Hulan wrote:

On Monday 29 of June 2015 23:07:11 Mark Chaney wrote:

I had to comment out some code at the direction of one of the devs with
1.7.2 so that i could enter my own network values as I wanted use foreman
to provision a server the way I wanted it to be, not the way its current
settings were. It was very frustrating when all my work would be wiped
out
during a fact update. Anyway, the commenting out worked and I was told
that
1.8.x made it so that we could have the network settings work this way
without having to hack any core code. My concern though is that i think
this new setting is something that I would have to enable, thus could
wipe
out my network settings before I cant that setting enabled. Any
suggestions
for a safe upgrade path?

Hello,

I think you’re talking about “ignore_puppet_facts_for_provisioning” setting
which now affects all interfaces (since 1.8.0). could you point us to the
original issue just to be sure? Anyway you can just turn it on before the
upgrade and it should prevent any interface updates. And we always
recommend
doing a backup of Foreman DB before updating.

–
Marek

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

4

Hello

It exists for a long time, only its impact was changed in 1.8.0.

Hope this helps

··· -- Marek

On Tuesday 30 of June 2015 06:52:05 Mark Chaney wrote:

How can I turn off a setting that doesn’t exist yet?

On Tue, Jun 30, 2015 at 3:42 AM, Marek Hulan mhulan@redhat.com wrote:

On Monday 29 of June 2015 23:07:11 Mark Chaney wrote:

I had to comment out some code at the direction of one of the devs with
1.7.2 so that i could enter my own network values as I wanted use
foreman
to provision a server the way I wanted it to be, not the way its current
settings were. It was very frustrating when all my work would be wiped

out

during a fact update. Anyway, the commenting out worked and I was told

that

1.8.x made it so that we could have the network settings work this way
without having to hack any core code. My concern though is that i think
this new setting is something that I would have to enable, thus could

wipe

out my network settings before I cant that setting enabled. Any

suggestions

for a safe upgrade path?

Hello,

I think you’re talking about "ignore_puppet_facts_for_provisioning"
setting
which now affects all interfaces (since 1.8.0). could you point us to the
original issue just to be sure? Anyway you can just turn it on before the
upgrade and it should prevent any interface updates. And we always
recommend
doing a backup of Foreman DB before updating.

–
Marek

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Marek

5

I dont think you are following me. By default, foreman lists all interfaces
that the devices has that it gets from facts. I do not want foreman to list
any interfaces it receives from facts. I want to use foreman to provision
the system the way I WANT it to be, not the way it currently is setup. I
cant remember the file name, but I was told to comment out some code in
1.7.2 so that this did not happen. I was told that future versions would
have an option so that I could use it this way. Simply setting
"ignore_puppet_facts_for_provisioning" to "true" solves nothing. I just did
an upgrade to 1.8.2 and all my network settings were wiped and replaced
with what all the hosts currently have. =(

6

For those who follow this conversation, original issue was [1]. I was unable
to reproduce the behavior you describe, but reported the issue as [2]. It
works for me exactly as you want.

[1] Feature #9104: Disable auto network interfaces - Foreman
[2] Bug #11047: Interfaces are imported even though ignore_puppet_facts_for_provisioning is set to true - Foreman

··· On Tuesday 07 of July 2015 17:56:26 Mark Chaney wrote: > I dont think you are following me. By default, foreman lists all interfaces > that the devices has that it gets from facts. I do not want foreman to list > any interfaces it receives from facts. I want to use foreman to provision > the system the way I WANT it to be, not the way it currently is setup. I > cant remember the file name, but I was told to comment out some code in > 1.7.2 so that this did not happen. I was told that future versions would > have an option so that I could use it this way. Simply setting > "ignore_puppet_facts_for_provisioning" to "true" solves nothing. I just did > an upgrade to 1.8.2 and all my network settings were wiped and replaced > with what all the hosts currently have. =(

–
Marek

7

So you are stating that if I set that setting to true, then have a host
with actual interfaces of eth0, eth1, eth2, etc, and in foreman, i delete
eth2, add an ip address for eth1, after upgraded, I should only have eth0
and eth1 with the custom ip showing in foreman? This is not the case.

··· On Wed, Jul 8, 2015 at 6:53 AM, Marek Hulan wrote:

On Tuesday 07 of July 2015 17:56:26 Mark Chaney wrote:

I dont think you are following me. By default, foreman lists all
interfaces
that the devices has that it gets from facts. I do not want foreman to
list
any interfaces it receives from facts. I want to use foreman to provision
the system the way I WANT it to be, not the way it currently is setup. I
cant remember the file name, but I was told to comment out some code in
1.7.2 so that this did not happen. I was told that future versions would
have an option so that I could use it this way. Simply setting
"ignore_puppet_facts_for_provisioning" to “true” solves nothing. I just
did
an upgrade to 1.8.2 and all my network settings were wiped and replaced
with what all the hosts currently have. =(

For those who follow this conversation, original issue was [1]. I was
unable
to reproduce the behavior you describe, but reported the issue as [2]. It
works for me exactly as you want.

[1] Feature #9104: Disable auto network interfaces - Foreman
[2] Bug #11047: Interfaces are imported even though ignore_puppet_facts_for_provisioning is set to true - Foreman

–
Marek

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

8

Hello,

it works for me exactly as you described. Maybe someone else could try to
reproduce. Or as I suggested in the issue, could you please upgrade to 1.8
again, enable debug mode, remove interfaces (eth2 in your example), 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 could
prepare a small patch with it if you want.

··· -- Marek

On Wednesday 08 of July 2015 13:25:55 Mark Chaney wrote:

So you are stating that if I set that setting to true, then have a host
with actual interfaces of eth0, eth1, eth2, etc, and in foreman, i delete
eth2, add an ip address for eth1, after upgraded, I should only have eth0
and eth1 with the custom ip showing in foreman? This is not the case.

On Wed, Jul 8, 2015 at 6:53 AM, Marek Hulan mhulan@redhat.com wrote:

On Tuesday 07 of July 2015 17:56:26 Mark Chaney wrote:

I dont think you are following me. By default, foreman lists all

interfaces

that the devices has that it gets from facts. I do not want foreman to

list

any interfaces it receives from facts. I want to use foreman to
provision
the system the way I WANT it to be, not the way it currently is setup. I
cant remember the file name, but I was told to comment out some code in
1.7.2 so that this did not happen. I was told that future versions would
have an option so that I could use it this way. Simply setting
"ignore_puppet_facts_for_provisioning" to “true” solves nothing. I just

did

an upgrade to 1.8.2 and all my network settings were wiped and replaced
with what all the hosts currently have. =(

For those who follow this conversation, original issue was [1]. I was
unable
to reproduce the behavior you describe, but reported the issue as [2]. It
works for me exactly as you want.

[1] Feature #9104: Disable auto network interfaces - Foreman
[2] Bug #11047: Interfaces are imported even though ignore_puppet_facts_for_provisioning is set to true - Foreman

–
Marek

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Marek