Although GI owner by design has to be member of OSDBA group in Oracle Restart environment, there's no need for it to be member of the OSOPER group, too. Kept in mind what cluvfy stage -pre hacfg
is intended for, I furthermore guess it might be better to check it for ASMDBA membership instead of OSDBA membership.
roles/oraswgi_install/tasks/runcluvfy.yml IMO should be fixed that way:
index 822b6ba..f6939ca 100644
--- a/roles/oraswgi_install/tasks/runcluvfy.yml
+++ b/roles/oraswgi_install/tasks/runcluvfy.yml
@@ -52,8 +52,8 @@
vars:
cluvfy_args: >-
stage -pre hacfg
- -osdba {{ dba_group }}
- -osoper {{ oper_group }}
+ -osdba {{ asmdba_group }}
+ -osoper {{ asmoper_group }}
-orainv oinstall
register: cmdruncluvfy
become: true
Best regards,
Thilo.