Bug 2097671

Summary: [RFE] Collect TigerVNC-related information
Product: Red Hat Enterprise Linux 9 Reporter: Pavel Moravec <pmoravec>
Component: sosAssignee: Pavel Moravec <pmoravec>
Status: CLOSED DUPLICATE QA Contact: Upgrades and Supportability <upgrades-and-supportability>
Severity: medium Docs Contact:
Priority: high    
Version: 9.1CC: agk, bmr, plambri, sbradley, theute
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-16 10:13:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Pavel Moravec 2022-06-16 09:38:21 UTC 
This bug was initially created as a copy of Bug #2062908

I am copying this bug because: 

To be in par with 8.7 / 9.1 .


Since TigerVNC moved to systemd-based operation with the 1.10 release, it has had configuration files that aren't collected by sos. This means more time spent collecting TigerVNC-specific configuration files.

As such, we'd like to request that sos collect all files under /etc/tigervnc, which contains the new configuration files we need. No passwords are shared in these files (they live in users' home directories).

Also, we like to ask that the status of tigervnc services be tracked. They can be found with "systemctl --list-units" under the designation tigervnc@:$VNCDISPLAY.service, where $VNCDISPLAY is a number starting at 1 stating the TigerVNC display number.
Comment 2 Pavel Moravec 2022-06-16 10:13:59 UTC 
Oh, I missed already existing clone  https://bugzilla.redhat.com/show_bug.cgi?id=2066181 :(

*** This bug has been marked as a duplicate of bug 2066181 ***