-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rule 1.2.4 error in run order #49
Comments
Good Day @animatco Sorry to get to this so late but Im wondering if you are running in a cloud environment or a local system? I believe we have resolved this already and maybe the system type is not being picked up. The order of the tasks are setup in the section1.yml and are calling in the correct order depending on the type of system ansible finds. The default main should not control that. |
No this was on a On-Prem vSphere VM |
Hmmmm ok I will see if i can replicate this. We dont have vSphere internal but I believe it may be having issues figuring out if its a hyper-v and running it the non hyper v way this is where it checks for that. I wonder if vpshere logs the type differently. So in your case it is running the cloud based hardening not the normal one. Which means below the instance is registering the when statement when your running it. but it seems it is not. of course feel free to remove anything that is private info HVM is Amazon AMI's, Hyper-V is Azure's, KVM is used for ('QEMU', 'Amazon EC2', 'DigitalOcean', 'Google', 'Scaleway', 'Nutanix', 'KVM', 'KVM Server', 'Bochs', 'AHV')
|
Describe the Issue
If in the defaults/main.yml file the the rule 1.2.1 is not moved below 1.2.4 the code errors out.
Expected Behavior
1.2.4 should run before 1.2.1
Actual Behavior
1.2.1 is running before 1.2.4
Control(s) Affected
rule 1.2.4
Environment (please complete the following information):
branch being used: devel
Ansible Version: 2.16.3
Host Python Version: 3.12.3
Ansible Server Python Version: 3.12.3
Additional Details:
Additional Notes
Anything additional goes here
Possible Solution
change run order.
The text was updated successfully, but these errors were encountered: