Logging the sunbeam command - [feature request supportability]

Bug #2068575 reported by Marcin Wilk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Snap
Triaged
Wishlist
Unassigned

Bug Description

Every execution of the 'sunbeam' command creates a distinct log file under $HOME/snap/openstack/common/logs/ directory. Although it is possible to analyze a log file to get a grasp of which particular sunbeam subcommand was executed, but it will be way more convenient for troubleshooting if every logs starts with the exact copy to the full command string including all the parameters provided. For example, after running:
'sunbeam cluster bootstrap'

the corresponding log could start with something similar to the following:
07:37:14,426 root DEBUG Logging to '/home/ubuntu/snap/openstack/common/logs/sunbeam-20240606-073714.425891.log'
07:37:14,426 sunbeam.provider.commands DEBUG Running "sunbeam cluster bootstrap" ...
...

Tags: open-2203
Revision history for this message
Guillaume Boutry (gboutry) wrote :

This is a fairly simple request that would really help debugging sunbeam, here's the proposed change: https://github.com/canonical/snap-openstack/pull/248

Changed in snap-openstack:
status: New → Triaged
importance: Undecided → Wishlist
tags: added: open-2203
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.