Greetings,
Has anyone noticed how Foreman handles Solaris Operating Systems with
Puppet 3?
I have a Solaris 10u10 box that's runninng Puppet 3.2 (opencsw
experimental) and another Solaris 10u10 running Puppet 2.7 (opencsw
standard). The facts presented between the two are different.
The 3.2 agent reports:
operatingsystem => Solaris
operatingsystemrelease => 10_u10
osfamily => Solaris
puppetversion => 3.2.2
The 2.7 agent reports:
operatingsystem => Solaris
operatingsystemrelease => 5.10
osfamily => Solaris
puppetversion => 2.7.14
Foreman is showing this guy as a "new" Solaris operating system with major
version 1010. I'm going to guess that Foreman is hoping to parse
operatingsystemrelease fact as $major.$minor and puppet/facter is no longer
conforming to that pattern?
Should I file a bug?.. with Foreman or Puppet/Facter?
···
--
Sean M. Alderman
Senior Engineer, UDit Systems Integration and Engineering
University of Dayton
300 College Park
Dayton, Ohio 45469-1530
(937) 229-5088
salderman1@udayton.edu
> Greetings,
> Has anyone noticed how Foreman handles Solaris Operating Systems with
> Puppet 3?
>
> I have a Solaris 10u10 box that's runninng Puppet 3.2 (opencsw
> experimental) and another Solaris 10u10 running Puppet 2.7 (opencsw
> standard). The facts presented between the two are different.
>
> The 3.2 agent reports:
> operatingsystem => Solaris
> operatingsystemrelease => 10_u10
> osfamily => Solaris
> puppetversion => 3.2.2
> The 2.7 agent reports:
> operatingsystem => Solaris
> operatingsystemrelease => 5.10
> osfamily => Solaris
> puppetversion => 2.7.14
>
> Foreman is showing this guy as a "new" Solaris operating system with major
> version 1010. I'm going to guess that Foreman is hoping to parse
> operatingsystemrelease fact as $major.$minor and puppet/facter is no longer
> conforming to that pattern?
>
> Should I file a bug?.. with Foreman or Puppet/Facter?
>
I've no idea why it changed, probably worth asking on both, we can surely
fix it at foreman side as well.
Ohad
···
On Thu, Aug 1, 2013 at 10:52 PM, Sean Alderman wrote:
–
Sean M. Alderman
Senior Engineer, UDit Systems Integration and Engineering
University of Dayton
300 College Park
Dayton, Ohio 45469-1530
(937) 229-5088
salderman1@udayton.edu
–
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/groups/opt_out.
>
>
>>
>> Greetings,
>> Has anyone noticed how Foreman handles Solaris Operating Systems with
>> Puppet 3?
>>
>> I have a Solaris 10u10 box that's runninng Puppet 3.2 (opencsw
>> experimental) and another Solaris 10u10 running Puppet 2.7 (opencsw
>> standard). The facts presented between the two are different.
>>
>> The 3.2 agent reports:
>> operatingsystem => Solaris
>> operatingsystemrelease => 10_u10
>> osfamily => Solaris
>> puppetversion => 3.2.2
>> The 2.7 agent reports:
>> operatingsystem => Solaris
>> operatingsystemrelease => 5.10
>> osfamily => Solaris
>> puppetversion => 2.7.14
>>
>> Foreman is showing this guy as a "new" Solaris operating system with major
>> version 1010. I'm going to guess that Foreman is hoping to parse
>> operatingsystemrelease fact as $major.$minor and puppet/facter is no longer
>> conforming to that pattern?
>>
>> Should I file a bug?.. with Foreman or Puppet/Facter?
Well drawing on my memories from being a Solaris admin back in the
day, it looks like they made the OS version string in facter more
"precise". Basically every release of "Solaris 10" is SunOS 5.10.
10_u10, means Solaris 10 update 10. I haven't played with Solaris in
ages, and certainly not with Puppet. I'd ask on puppet-users and find
out the reason for this change. If there reasoning is well thought
out, and they are going to keep it this way, I'd file a feature
request on the Foreman side. I'm guessing they had a customer that
needed to differentiate between Solaris 10 releases, which is probably
why they made the change. (Almost tempted to boot up an S10 VM and
test, but I don't have any handy media.)
A couple other options:
- If you want the old behavior you COULD write a custom fact called
"sunosrelease" that emulates the old behavior. (IE: If you want all
S10 hosts regardless of update to return 5.10). It would be a fairly
easy task.
- If you want the new behaviour on the old version of facter, you
could patch facter to emulate the new bahavior.
Cheers,
Brian
···
On Thu, Aug 1, 2013 at 3:58 PM, Ohad Levy wrote:
> On Thu, Aug 1, 2013 at 10:52 PM, Sean Alderman > wrote:
I’ve no idea why it changed, probably worth asking on both, we can surely
fix it at foreman side as well.
Ohad
–
Sean M. Alderman
Senior Engineer, UDit Systems Integration and Engineering
University of Dayton
300 College Park
Dayton, Ohio 45469-1530
(937) 229-5088
salderman1@udayton.edu
–
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/groups/opt_out.
–
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/groups/opt_out.
That was my "baby" and was rolled into facter 1.7.0 (
https://projects.puppetlabs.com/issues/11082#note-15)
You can address it on older versions of facter as a custom fact (I do this)
John
···
On 2 August 2013 05:58, Ohad Levy wrote:
On Thu, Aug 1, 2013 at 10:52 PM, Sean Alderman salderman1@udayton.eduwrote:
Greetings,
Has anyone noticed how Foreman handles Solaris Operating Systems with
Puppet 3?
I have a Solaris 10u10 box that’s runninng Puppet 3.2 (opencsw
experimental) and another Solaris 10u10 running Puppet 2.7 (opencsw
standard). The facts presented between the two are different.
The 3.2 agent reports:
operatingsystem => Solaris
operatingsystemrelease => 10_u10
osfamily => Solaris
puppetversion => 3.2.2
The 2.7 agent reports:
operatingsystem => Solaris
operatingsystemrelease => 5.10
osfamily => Solaris
puppetversion => 2.7.14
I’ve no idea why it changed, probably worth asking on both, we can surely
fix it at foreman side as well.
Ohad
Ok, so where does this leave us? Foreman Bug?
Foreman is creating a new Operating System for each v10 Release if the
node's puppet agent version >= 2.7. I'm not sure if this has an impact on
unattended installs or not, but it would seem to if the user creating a
node picks the "new" Solaris OS.
Downgrading puppet seems to be the best option to keep things operating
cleanly in Foreman…and perhaps any puppet modules that are backward
compatible to 2.7 and use release fact.
I've attached a couple of Foreman Screen clips. The (hw0113) OS is the one
I manually created for unattended installs, its also the one that Foreman
assigns to the 2.7 agents. I get the reasoning for the fact change, since
none of the Solaris boxes I've migrated to Foreman's PuppetMaster are
actually running 01/13, they're all on 08/11. The only nodes I have
running 01/13 are ones done unattended provisioning with.
Perhaps we can just get Foreman to properly match the $major_u$minor and
display it correctly for puppet 3.x clients? Do I need to file a bug for
this or a feature request?
···
--
Sean M. Alderman
Senior Engineer, UDit Systems Integration and Engineering
University of Dayton
300 College Park
Dayton, Ohio 45469-1530
(937) 229-5088
salderman1@udayton.edu
On Thu, Aug 1, 2013 at 7:07 PM, John Warburton jwarburton@gmail.com wrote:
On 2 August 2013 05:58, Ohad Levy ohadlevy@gmail.com wrote:
On Thu, Aug 1, 2013 at 10:52 PM, Sean Alderman salderman1@udayton.eduwrote:
Greetings,
Has anyone noticed how Foreman handles Solaris Operating Systems with
Puppet 3?
I have a Solaris 10u10 box that’s runninng Puppet 3.2 (opencsw
experimental) and another Solaris 10u10 running Puppet 2.7 (opencsw
standard). The facts presented between the two are different.
The 3.2 agent reports:
operatingsystem => Solaris
operatingsystemrelease => 10_u10
osfamily => Solaris
puppetversion => 3.2.2
The 2.7 agent reports:
operatingsystem => Solaris
operatingsystemrelease => 5.10
osfamily => Solaris
puppetversion => 2.7.14
I’ve no idea why it changed, probably worth asking on both, we can surely
fix it at foreman side as well.
Ohad
That was my “baby” and was rolled into facter 1.7.0 (
https://projects.puppetlabs.com/issues/11082#note-15)
You can address it on older versions of facter as a custom fact (I do this)
John
–
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/groups/opt_out.
