Closed uk-bolly closed 2 months ago
Workflow will cause issues due to time amazon now taking before we are able to connect, unable to adjust timeout on the workflow as it stands Have run locally on two different systems to prove output
ok: [cent7_bios] => {
"msg": [
"The pre remediation results are: Count: 623, Failed: 208, Skipped: 30, Duration: 6.052s.",
"The post remediation results are: Count: 623, Failed: 11, Skipped: 2, Duration: 7.655s.",
"Full breakdown can be found in /opt",
""
]
}
ok: [cent7_efi] => {
"msg": [
"The pre remediation results are: Count: 623, Failed: 208, Skipped: 30, Duration: 5.739s.",
"The post remediation results are: Count: 623, Failed: 13, Skipped: 2, Duration: 8.939s.",
"Full breakdown can be found in /opt",
""
]
}
TASK [/Users/uk-bolly/RHEL7-CIS : Output Warning count and control IDs affected] ***************************
ok: [cent7_bios] => {
"msg": "You have 6 warning(s) that require investigating that are related to the following benchmark ID(s) [1.1.2.2.1] [1.2.4] [2.2.22] [3.4.2.3] [3.4.2.4] [Reboot_required]"
}
ok: [cent7_efi] => {
"msg": "You have 6 warning(s) that require investigating that are related to the following benchmark ID(s) [1.1.2.2.1] [1.2.4] [2.2.22] [3.4.2.3] [3.4.2.4] [Reboot_required]"
}
Due to how the pipeline works and some changes the devel pipeline action will fail. This has been tested successfully locally.
Overall Review of Changes: New v4.0 CIS benchmark playbook - refer to CIS documentation for changes New workflow setup
How has this been tested?: Manually