Question & Answer
Question
Why might PowerVC upgrade to 2.3.2 fail reporting
/fatal: [hostname]: FAILED! => {"changed": false, "msg": "Unable to add or update user: hostname:27017: ("VerificationError(errors=[DNSMismatch(mismatched_id=DNS_ID(hostname=b'hostnameinwrongcase'))])",) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms), Timeout: 30s, Topology Description: <TopologyDescription id: 6961251c5d7b5a7617878228, topology_type: Single, servers: [<ServerDescription ('hostname', 27017) server_type: Unknown, rtt: None, error=AutoReconnect('hostname':27017: ("VerificationError(errors=[DNSMismatch(mismatched_id=DNS_ID(hostname=b\'hostname\'))])",) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms)')>]>"}
Cause
PowerVC 2.3.1 and later now enforce case sensivity for the certificate used against the resolvable host name.
Answer
Check the existing certifcate
openssl x509 -text -noout -in /etc/pki/db/server/mongodb-server.pem
Example output
X509v3 Subject Alternative Name:
IP Address:x.x.x.x IP Address:x.x.x.x, IP Address:127.0.0.1, DNS:powervcnew.rchland.ibm.com, DNS:powervcnew, DNS:PVCIGS232VIP, DNS:powervcnew
Note the name powervcnew in lower case.
If the hostname is in uppercase..
nmcli general hostname
POWERVCNEW
the upgrade will fail,
The host now must match the certificate to case sensitivity.
nmcli general hostname powervcnew
would set the host to lower case.
reboot the host, then retry the 2.3.2 install.
Historical Number
TS021162073
Was this topic helpful?
Document Information
Modified date:
04 February 2026
UID
ibm17259621