You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was decided that yum provider messages should only be a warning in https://tickets.puppetlabs.com/browse/PUP-5594. This can then go undetected until puppet attempts to manage packages and then causes a failed puppet run. Warnings are not visible on PE dashboards unless viewing the reports directly.
Describe the Solution You Would Like
A fact should either check yum check-update comes back clean or check the logs for "Warning: Puppet::Type::package::ProviderYum: Could not check for updates, '/bin/yum check-update' exited with 1" messages
Describe Alternatives You've Considered
This issue could be worked around by users setting repos correctly to ignore broken sources but this is rarely done and outside of our control.
Additional Context
Customers have missed configurations for months and then been impacted during key events such as upgrades.
The text was updated successfully, but these errors were encountered:
Use Case
It was decided that yum provider messages should only be a warning in https://tickets.puppetlabs.com/browse/PUP-5594. This can then go undetected until puppet attempts to manage packages and then causes a failed puppet run. Warnings are not visible on PE dashboards unless viewing the reports directly.
Describe the Solution You Would Like
A fact should either check yum check-update comes back clean or check the logs for "Warning: Puppet::Type::package::ProviderYum: Could not check for updates, '/bin/yum check-update' exited with 1" messages
Describe Alternatives You've Considered
This issue could be worked around by users setting repos correctly to ignore broken sources but this is rarely done and outside of our control.
Additional Context
Customers have missed configurations for months and then been impacted during key events such as upgrades.
The text was updated successfully, but these errors were encountered: