[SERVER-63005] SELinix: improve diagnostics of failed tests Created: 26/Jan/22  Updated: 29/Oct/23  Resolved: 13/Jul/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Sergey Galtsev (Inactive) Assignee: Adam Rayner
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File test1.log     File test2.log    
Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Security 2022-07-11, Security 2022-07-25
Participants:
Linked BF Score: 5

 Description   

In BF-23655 the two SELinux tests failed with no good information about the cause. Test1 and Test2. Subsequent re-run of tests was successful

This ticket is to revisit SELinux test scripts to provide more diagnostic information in event of failure



 Comments   
Comment by Githook User [ 13/Jul/22 ]

Author:

{'name': 'Adam Rayner', 'email': 'adam.rayner@gmail.com'}

Message: SERVER-63005: SELinux test logs grep journalctl instead of using --unit
Branch: master
https://github.com/mongodb/mongo/commit/2800bc79c9f36c0dd9215c133503a0ea1f1dc998

Generated at Thu Feb 08 05:56:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.