Problem with role_separation=False in oraswgi-install

[Rendanic]

There is a problem with role_separation=false:
Role separation should use different users for GI_HOME and ORACLE_HOME of the databases and not different group assignments in the responsefile for GI_HOMEs.
Information from grid-tbr_oraha.rsp with role_separation=false

oracle.install.asm.OSASM=dba
oracle.install.asm.OSDBA=dba
oracle.install.asm.OSOPER=oper

gridSetup.sh is reporting the following warnings:

[WARNING] [INS-41808] Possible invalid choice for OSASM Group.
   CAUSE: The name of the group you selected for the OSASM group is commonly used to grant other system privileges (For example: asmdba, asmoper, dba, oper).
   ACTION: Oracle recommends that you designate asmadmin as the OSASM group.
[WARNING] [INS-41809] Possible invalid choice for OSDBA Group.
   CAUSE: The group name you selected as the OSDBA for ASM group is commonly used for Oracle Database administrator privileges.
   ACTION: Oracle recommends that you designate asmdba as the OSDBA for ASM group, and that the group should not be the same group as an Oracle Database OSDBA group.
[WARNING] [INS-41810] Possible invalid choice for OSOPER Group.
   CAUSE: The group name you selected as the OSOPER for ASM group is commonly used for Oracle Database administrator privileges.
   ACTION: Oracle recommends that you designate asmoper as the OSOPER for ASM group, and that the group should not be the same group as an Oracle Database OSOPER group.
[WARNING] [INS-41812] OSDBA and OSASM are the same OS group.
   CAUSE: The chosen values for OSDBA group and the chosen value for OSASM group are the same.
   ACTION: Select an OS group that is unique for ASM administrators. The OSASM group should not be the same as the OS groups that grant privileges for Oracle ASM access, or for database administration.

[oravirt]

Hi,
Yes, I know.
I need to do a bit of a overhaul of the group assignments.

It works as it is, but I will change it.