Disparity between "must" and "error-message"

[AjeyBharadwaj]

OpenROADM_MSA_Public/model/Common/org-openroadm-manifest-file.yang

Line 477 in aaa5a0e

must "is-async != 'true'" {

The "must" constraint expects "is-async" field to be false. But, error says : "sw-activate is only supported as async command"

[fgruman]

I'll investigate and sent a query to the modeling team. But I believe you are correct.
If so, then all of the must statements associated with is-async may be incorrect in this module (3 instances identified).

EXISTING:
container sw-activate {
when "../command = 'sw-activate'";
must "is-async != 'true'" {
error-message "sw-activate is only supported as async command";
}
CHECKING if it should be:
grouping sw-activate-command {
description
"sw-activate-command";
container sw-activate {
when "../command = 'sw-activate'";
must "is-async = 'true'" {
error-message "sw-activate is only supported as async command";
}

[fgruman]

@AjeyBharadwaj
this is planned to be fixed in the MSAv8.0 release

[fgruman]

@AjeyBharadwaj
This has been fixed in MSAv8.0.

[fgruman]

@orenais @beegeesquare
cc: @AjeyBharadwaj

I believe this can be closed.

[orenais]

No objection! I am not really familiar with the manifest file usage and I trust your analysis.