|
When running puppet agent with the debug flag, there's no indication as to whether a package was successfully upgraded, or what version it was upgraded to, requiring customers and support to fish for this information on the command line.
Example debug output from a failed package upgrade:
[[0;36mDebug: Facter: resolving Xen facts.^[[0m
|
1531 ^[[0;36mDebug: Evicting cache entry for environment 'production'^[[0m
|
1532 ^[[0;36mDebug: Caching environment 'production' (ttl = 0 sec)^[[0m
|
1533 ^[[mNotice: Compiled catalog for cmh1vlatgps003d.dev2a.dswd1.com in environment production in 0.05 seconds^[[0m
|
1534 ^[[0;36mDebug: Creating default schedules^[[0m
|
1535 ^[[0;36mDebug: Loaded state in 0.11 seconds^[[0m
|
1536 ^[[0;36mDebug: Loaded state in 0.08 seconds^[[0m
|
1537 ^[[0;32mInfo: Applying configuration version '1500483207'^[[0m
|
1538 ^[[0;36mDebug: Prefetching yum resources for package^[[0m
|
1539 ^[[0;36mDebug: Executing: '/bin/rpm --version'^[[0m
|
1540 ^[[0;36mDebug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''^[[0m
|
1541 ^[[0;36mDebug: Executing: '/usr/bin/yum check-update'^[[0m
|
1542 ^[[0;36mDebug: Finishing transaction 22088640^[[0m
|
1543 ^[[0;36mDebug: Storing state^[[0m
|
1544 ^[[0;36mDebug: Stored state in 0.12 seconds^[[0m
|
1545 ^[[mNotice: Applied catalog in 2.38 seconds^[[0m
|
1546 ^
|
Since we see this situation quite frequently in support, and lengthens time to resolution, and seems trivial to add this the debug logging, I wanted to get this issue submitted and tracked, along with a recent Zendesk example.
|