Under the puppet 4 agent ubuntu trusty hosts emit Error: /Stage[main]/Apparmor/Service[apparmor]: Provider init is not functional on this host during a puppet run. This error does not break the puppet run, nor trigger a "puppet last run" alert. Still, it should be addressed.
Interestingly in modules/apparmor/manifests/init.pp the apparmor service explicitly specifies init as the provider. Could this be removed to let puppet select the provider automatically?
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| apparmor: remove service provider attribute | operations/puppet | production | +0 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | aborrero | T178717 Upgrade wmcs instances and masters to puppet 4.8 | |||
| Resolved | None | T177254 Upgrade to puppet 4 (4.8 or newer) | |||
| Resolved | jbond | T184561 Modernize Puppet Configuration Management (2017-18 Q3 Goal) | |||
| Resolved | herron | T182894 Trusty puppet 4 approach | |||
| Resolved | herron | T184017 Puppet - Error: /Stage[main]/Apparmor/Service[apparmor]: Provider init is not functional on this host |
I noticed this on the labvirts and labcontrol servers this morning too. I believe there is no reason for the init specification.
Change 401748 had a related patch set uploaded (by Herron; owner: Herron):
[operations/puppet@production] apparmor: remove service provider attribute
Change 401748 merged by Herron:
[operations/puppet@production] apparmor: remove service provider attribute
Looking better now!
Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Info: Caching catalog for labtestvirt2001.codfw.wmnet Notice: /Stage[main]/Base::Environment/Tidy[/var/tmp/core]: Tidying 0 files Info: Applying configuration version '1514997324' Notice: Applied catalog in 9.52 seconds