Announce: Puppet-Agent 1.2.4, Puppet 4.2.2, Facter 3.1.0

[Eric Sorenson]

Puppet Agent 1.2.4 is out! This is a new minor release of the all-in-one
agent bundle which incorporates updates to Puppet, Facter, Hiera, and
Mcollective.

* Puppet 4.2.2, a bugfix release which includes an important Windows security
fix: https://docs.puppetlabs.com/puppet/4.2/reference/release_notes.html#puppet-422

* Facter 3.1.0, a backwards-compatible feature release of Facter which adds
support for OpenBSD and Solaris facts, improves the network interface facts,
and fixes a regression that caused Docker containers on systemd hosts to
erroneously report themselves not to be virtual:
https://docs.puppetlabs.com/facter/3.1/release_notes.html#facter-310

* Mcollective 2.8.5, which reverted a problem renaming the mcollective service
on Mac OS X and improves the init script on SUSE.

* Hiera 3.0.3, which is a tag-only release (necessary for tooling, no
functional changes)

You can find out more about the all-in-one puppet-agent package here:
https://docs.puppetlabs.com/puppet/4.2/reference/about_agent.html

The installation and upgrade instructions are linked from the main docs page:
https://docs.puppetlabs.com/puppet/4.2/reference/index.html

Eric Sorenson - eric.s...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles

[Jo Rhett]

What’s the ETA for Puppet 4.3?  Looking forward to numerous changes committed for that release.

-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.

[Dirk Heinrichs]

Am 14.09.2015 um 22:00 schrieb Eric Sorenson:

Puppet Agent 1.2.4 is out! This is a new minor release of the all-in-one
agent bundle which incorporates updates to Puppet, Facter, Hiera, and Mcollective.

I'm using a self-written class to manage the Puppet agent package on agent nodes. It works fine on any Linux and Windows Server 2008R2, but fails reproducably on Windows Server 2012R2 when trying to upgrade the agent package. The following message appears in the report:

"change from 1.2.2 to 1.2.4 failed: Could not update: Failed to install: The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance."

The agent service is running under the local system account on both Windows versions.

Any idea what could be wrong here?

Thanks...

    Dirk

--

Dirk Heinrichs, Senior Systems Engineer, Engineering Solutions
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Tel: +49 2226 1596666 (Ansage) 1149
Email: d...@recommind.com
Skype: dirk.heinrichs.recommind
www.recommind.com

[Francois Lafont]

Hi,

On 17/09/2015 09:11, Dirk Heinrichs wrote:

> I'm using a self-written class to manage the Puppet agent package on agent
> nodes. It works fine on any Linux and Windows Server 2008R2, but fails
> reproducably on Windows Server 2012R2 when trying to upgrade the agent package.

> The following message appears in the report: [...]

I wanted to do exactly the same but I had errors too during an upgrade
(sorry I don't remember the messages). But in fact (and after interesting
discussions on IRC ;)) I was convinced that it's logical. Indeed, finally
I think it's not reasonable to upgrade the AIO puppet-agent package
*during* a puppet run. It's a curious situation where there is an execution
of a software during its upgrade. Finally, it seems to me a not reasonable
situation, and we can't hope a normal behavior during a such situation.

So, I'm not a puppet expert, but I think it's better to upgrade the
puppet-agent with another way that a puppet run.

Regards.

François Lafont

[Francois Lafont]

On 17/09/2015 12:53, Francois Lafont wrote:

> I wanted to do exactly the same but I had errors too during an upgrade
> (sorry I don't remember the messages). But in fact (and after interesting
> discussions on IRC ;)) I was convinced that it's logical. Indeed, finally
> I think it's not reasonable to upgrade the AIO puppet-agent package
> *during* a puppet run. It's a curious situation where there is an execution
> of a software during its upgrade. Finally, it seems to me a not reasonable
> situation, and we can't hope a normal behavior during a such situation.
>
> So, I'm not a puppet expert, but I think it's better to upgrade the
> puppet-agent with another way that a puppet run.

Of course, I'm maybe wrong, I have no certainty on the issue, it's just a
personal conclusion and I will follow with interest the following answers.

Regards.
François Lafont

[Dirk Heinrichs]

Am 17.09.2015 um 12:53 schrieb Francois Lafont:

It's a curious situation where there is an execution of a software during its upgrade.

No, that's quite normal. Think "yum upgrade" upgrading yum itself on Linux.

Finally, it seems to me a not reasonable situation, and we can't hope a normal behavior during a such situation.

I did this for quite some time now, let various 3.x versions upgrade themselves to their successors w/o problems on both Linux and Win 2008. The self-upgrade from agent 1.2.2 to 1.2.4 also works fine on Win 2008. It just seems to be special to Win 2012.

Bye...

[Rob Reynolds]

On Thu, Sep 17, 2015 at 6:01 AM, Dirk Heinrichs <dirk.he...@recommind.com> wrote:

Am 17.09.2015 um 12:53 schrieb Francois Lafont:

It's a curious situation where there is an execution of a software during its upgrade.

No, that's quite normal. Think "yum upgrade" upgrading yum itself on Linux.

It's quite normal on a POSIX system, but the same just does not apply to Windows. Perhaps if you read through MODULES-2040[1] you will better understand why it is harder to do on Windows. It's not as simple as replacing all of the files, which you can easily do on a POSIX system. LInux will happily let you replace files b/c it holds everything in memory, where Windows does not.

[1] https://tickets.puppetlabs.com/browse/MODULES-2040

 

Finally, it seems to me a not reasonable situation, and we can't hope a normal behavior during a such situation.

I did this for quite some time now, let various 3.x versions upgrade themselves to their successors w/o problems on both Linux and Win 2008. The self-upgrade from agent 1.2.2 to 1.2.4 also works fine on Win 2008. It just seems to be special to Win 2012.

It can work, it's just not deterministic. As you are seeing.

 

Bye...

    Dirk

--

Dirk Heinrichs, Senior Systems Engineer, Engineering Solutions
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Tel: +49 2226 1596666 (Ansage) 1149
Email: d...@recommind.com
Skype: dirk.heinrichs.recommind
www.recommind.com

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/55FA9D84.5030406%40recommind.com.

For more options, visit https://groups.google.com/d/optout.

--

Rob Reynolds

Developer, Puppet Labs

PuppetConf 2015 is right around the corner! Join us October 5-9 in Portland, OR. Register now.

[Dirk Heinrichs]

Am 17.09.2015 um 16:03 schrieb Rob Reynolds:

It can work, it's just not deterministic. As you are seeing.

That's not what I'm seeing. I'm seeing that it HAS worked fine on Windows 2008 for the past 2 years or so (and still does), but doesn't on Windows 2012.

[Dirk Heinrichs]

Am 18.09.2015 um 07:56 schrieb Dirk Heinrichs:

Am 17.09.2015 um 16:03 schrieb Rob Reynolds:

It can work, it's just not deterministic. As you are seeing.

That's not what I'm seeing. I'm seeing that it HAS worked fine on Windows 2008 for the past 2 years or so (and still does), but doesn't on Windows 2012.

I'm also seeing that it's not a problem DURING upgrade, but a problem STARTING the installer (at least according to the error message).