From my understanding it is desired that the cm-pass was generated during oom deployment, but it seems that the password can be set to value that cannot be later accepted by cfy profiles set -p command.

Example:

I manually set password using set-admin-password.sh script (by providing CMPASS env) to value: 'Mupq6~LoduCal' which was a password generated by OOM using the same method, so I guess same thing can happen for cloudify pass.

Password was set to the value in DB and actually works fine for curl:

curl -Ss --user admin:Mupq6~LoduCal -H "Tenant: default_tenant" "https://dcae-cloudify-manager:443/api/v3.1/deployments?_include=id" -k

but fails for:

cfy profiles set -p 'Mupq6~LoduCal'

error:

401: User unauthorized: No authentication info provided.

This prevents cloudify readiness probe from succeding, as plugins are never loaded:

Readiness probe failed: + [[ -f /opt/manager/plugins-loaded ]] + exit 1

That could explain issues with gating seen on: https://gerrit.onap.org/r/c/oom/+/111599

But issues with: https://gerrit.onap.org/r/c/oom/+/112693 may indicate some other problem.

Can someone verify?