when i try to change the assigned puppet classes to a specific broken host
they would not appear in the yaml file.
if i setup another new host (new host name) everything is working as
expected.
but on reinstall the puppet classes assigned are not applied.
the puppet system is working as the puppet lib's and my custom facts are
synced to the client.
but adding classes to the broken host are not applied to the yaml.
here some screenshots of the problem.
http://ftp.disconnected-by-peer.at/pub/privat/foreman/
yes debian9 but we alredy have about 10 vm's with debain 9 at work without
problem.
so i have no idee where to search for the problem.
my guess is it has something todo with my change of the network "domain"
while in "Build" mode (i think there are now some relicts in the db)
thx for the help in av
geos_one
has someone an idea where to search for the problem ?
···
2017-07-27 17:48 GMT+02:00 Mario Fetka :
when i try to change the assigned puppet classes to a specific broken host
they would not appear in the yaml file.
if i setup another new host (new host name) everything is working as
expected.
but on reinstall the puppet classes assigned are not applied.
the puppet system is working as the puppet lib’s and my custom facts are
synced to the client.
but adding classes to the broken host are not applied to the yaml.
here some screenshots of the problem.
http://ftp.disconnected-by-peer.at/pub/privat/foreman/
yes debian9 but we alredy have about 10 vm’s with debain 9 at work without
problem.
so i have no idee where to search for the problem.
my guess is it has something todo with my change of the network "domain"
while in “Build” mode (i think there are now some relicts in the db)
thx for the help in av
geos_one
–
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 https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
I think I encountered the same problem on the 1.14 branch (pls always
point out your foreman version).
What solved the issue was upgrading to 1.15 and doing import env's. I
noticed it saw all my classes changed.
···
On 27.07.2017 17:48, Mario Fetka wrote:
> when i try to change the assigned puppet classes to a specific broken host
> they would not appear in the yaml file.
> if i setup another new host (new host name) everything is working as
> expected.
> but on reinstall the puppet classes assigned are not applied.
> the puppet system is working as the puppet lib's and my custom facts are
> synced to the client.
> but adding classes to the broken host are not applied to the yaml.
>
> here some screenshots of the problem.
> http://ftp.disconnected-by-peer.at/pub/privat/foreman/
>
>
> yes debian9 but we alredy have about 10 vm's with debain 9 at work without
> problem.
>
> so i have no idee where to search for the problem.
>
> my guess is it has something todo with my change of the network "domain"
> while in "Build" mode (i think there are now some relicts in the db)
>
> thx for the help in av
> geos_one
>
–
Daniel Helgenberger (helge000)
daniel@helgenberger.net
i am already at 1.15.2 (jessie hosts)
an i have imperted the envs more then once
···
2017-07-28 11:01 GMT+02:00 Daniel Helgenberger :
I think I encountered the same problem on the 1.14 branch (pls always
point out your foreman version).
What solved the issue was upgrading to 1.15 and doing import env’s. I
noticed it saw all my classes changed.
On 27.07.2017 17:48, Mario Fetka wrote:
when i try to change the assigned puppet classes to a specific broken
host
they would not appear in the yaml file.
if i setup another new host (new host name) everything is working as
expected.
but on reinstall the puppet classes assigned are not applied.
the puppet system is working as the puppet lib’s and my custom facts are
synced to the client.
but adding classes to the broken host are not applied to the yaml.
here some screenshots of the problem.
http://ftp.disconnected-by-peer.at/pub/privat/foreman/
yes debian9 but we alredy have about 10 vm’s with debain 9 at work
without
problem.
so i have no idee where to search for the problem.
my guess is it has something todo with my change of the network "domain"
while in “Build” mode (i think there are now some relicts in the db)
thx for the help in av
geos_one
–
Daniel Helgenberger (helge000)
daniel@helgenberger.net
–
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 https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
so i have found a sollution. when installing with the same IP while the
install another host appears in the list that has the same ip with a
dynamic name. this host needs to be deleted after the install and then also
assigning new classes to the hosts work.
so i think i created another host with changing the domain while in build
mode (slow inet connection still in pxe download).
year cracy problem
···
2017-07-28 11:04 GMT+02:00 Mario Fetka :
i am already at 1.15.2 (jessie hosts)
an i have imperted the envs more then once
2017-07-28 11:01 GMT+02:00 Daniel Helgenberger daniel@helgenberger.net:
I think I encountered the same problem on the 1.14 branch (pls always
point out your foreman version).
What solved the issue was upgrading to 1.15 and doing import env’s. I
noticed it saw all my classes changed.
On 27.07.2017 17:48, Mario Fetka wrote:
when i try to change the assigned puppet classes to a specific broken
host
they would not appear in the yaml file.
if i setup another new host (new host name) everything is working as
expected.
but on reinstall the puppet classes assigned are not applied.
the puppet system is working as the puppet lib’s and my custom facts are
synced to the client.
but adding classes to the broken host are not applied to the yaml.
here some screenshots of the problem.
http://ftp.disconnected-by-peer.at/pub/privat/foreman/
yes debian9 but we alredy have about 10 vm’s with debain 9 at work
without
problem.
so i have no idee where to search for the problem.
my guess is it has something todo with my change of the network "domain"
while in “Build” mode (i think there are now some relicts in the db)
thx for the help in av
geos_one
–
Daniel Helgenberger (helge000)
daniel@helgenberger.net
–
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 https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
