-
Notifications
You must be signed in to change notification settings - Fork 34
Error on "purge_unmanaged_queues" with CUPS stopped #251
Comments
Something about this does not look right. The error stems from Lines 100 to 102 in 33ac076
and |
The error happens while Puppet discovers existing resources instances. That's before the catalog is applied. Dependencies and ordering are only considered during catalog application, when Puppet reconciles the discovered state with the desired state. To illustrate with the error above:
IOW, no amount of resource ordering will fix this. Resource instance discovery must work no matter the current node state (CUPS running, stopped, not yet installed, ...). |
Given
When I apply the manifest
In order to remove old queues.
Then I get the error message:
The error message doesn't prevent the Puppet run from succeeding, but "normal errors" impede log monitoring, encourage bad practices from operators etc.
NB: additionally, the module does not achieve the desired state because it does not purge any queue on that run, but that would be hard to fix for little gain: on the second run, the CUPS service will be started, the queues will be detected and purged. That's a separate issue and I am not considering it here.
The text was updated successfully, but these errors were encountered: