Skip to content

Check for issues with yum provider #126

@davidsandilands

Description

@davidsandilands

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions