In some situations, the commit might pass but commit-check might fail.

Below is one example.

user@QFX10K-1# show | compare

[edit groups GLOBAL interfaces et-0/0/13]

- cascade-port;

[edit groups GLOBAL interfaces et-0/0/15]

- cascade-port;

[edit interfaces]

+ et-0/0/13 {

+ ether-options {

+ 802.3ad ae16;

+ }

+ }

+ et-0/0/15 {

+ ether-options {

+ 802.3ad ae16;

+ }

+ }

+ ae16 {

+ aggregated-ether-options {

+ lacp {

+ active;

+ system-id 00:01:02:03:04:0e;

+ admin-key 16;

+ }

+ mc-ae {

+ mc-ae-id 16;

+ redundancy-group 1;

+ chassis-id 1;

+ mode active-active;

+ status-control active;

+ init-delay-time 240;

+ }

+ }

+ }

{master:0}[edit]

user@QFX10K# commit check

[edit interfaces ae16 aggregated-ether-options mc-ae redundancy-group]

'redundancy-group 1'

The redundancy group must match with one defined at

error: configuration check-out failed: (statements constraint check failed)

user@QFX10K# commit

configuration check succeeds

commit complete

In such cases, it is not advisable to use the committed config as it may lead to unforeseen impact. It recommended to rollback these configs.