Your vg03 volume group must already exist (as a regular non-cluster VG) and be imported to both nodes at the time you run your cmcheckconf/cmapplyconf.

Bottom line: you *cannot* use “vgchange -c y” until your cluster is running. That command is useful only when adding new packages to an existing, running cluster. So don’t get hung up on it now.

As you don’t have a cluster yet, you cannot have any cluster-aware VGs. But the lock VG needs to be cluster-aware.

The solution is: when you run cmapplyconf to create a cluster, the cmapplyconf procedure will simultaneously switch the VGs listed in the cluster ASCII file to cluster mode.

To make vg03 switch to cluster mode at the cluster creation time (which is a requirement for using it as a cluster lock VG), you should add:

VOLUME_GROUP /dev/vg03

to the very end of your /etc/cmcluster/cseb.ascii file.

The appropriate FIRST_CLUSTER_LOCK_VG and FIRST_CLUSTER_LOCK_PV lines should also exist and be uncommented in the cseb.ascii file.

If you’re planning to use vg02 and/or other VGs as cluster packages, you have the option of adding VOLUME_GROUP lines for them in the cseb.ascii file too. If you do this, you don’t have to use “vgchange -c y” on those VGs later.

In a nutshell:
there are two methods to mark a VG as cluster-aware.

1.) specify it in a cluster ASCII file using a VOLUME_GROUP line, then apply the new
cluster configuration

2.) use “vgchange -c y”

When the cluster is down or not yet set up, only method 1 is available. Once your cluster is up and running, both methods will be available.

source