Openshift Troubleshooting

Currently 𝐰𝐞 𝐚𝐫𝐞 𝐰𝐨𝐫𝐤𝐢𝐧𝐠 𝐰𝐢𝐭𝐡 𝟒 𝐝𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐭 𝐜𝐥𝐢𝐞𝐧𝐭𝐬 involving hashtag#RedHatOpenShift . On-prem & Cloud setup with Platform plus licensing . 𝐇𝐨𝐰 𝐥𝐢𝐜𝐞𝐧𝐬𝐞 𝐚𝐫𝐞 𝐛𝐞𝐢𝐧𝐠 𝐜𝐚𝐥𝐜𝐮𝐥𝐚𝐭𝐞𝐝 etc ... 𝐖𝐞 𝐫𝐞𝐩𝐥𝐢𝐜𝐚𝐭𝐞 𝐚𝐥𝐥 𝐞𝐫𝐫𝐨𝐫𝐬 𝐢𝐧 𝐨𝐮𝐫 𝐥𝐨𝐜𝐚𝐥 𝐬𝐞𝐭𝐮𝐩 to make sure we try multiple solutions for one issue . 𝐒𝐞𝐯𝐞𝐫𝐚𝐥 𝐮𝐩𝐝𝐚𝐭𝐞𝐬 𝐚𝐧𝐝 𝐟𝐞𝐚𝐭𝐮𝐫𝐞𝐬 𝐢𝐧 𝐎𝐩𝐞𝐧𝐬𝐡𝐢𝐟𝐭 𝐯𝟒.𝟏𝟗. Comparing to older versions, v4.19 is different in many way adding several features .. including ODF updates too 𝐎𝐩𝐞𝐧𝐒𝐡𝐢𝐟𝐭 𝐈𝐧𝐬𝐭𝐚𝐥𝐥𝐚𝐭𝐢𝐨𝐧 & 𝐒𝐞𝐭𝐮𝐩 𝐈𝐬𝐬𝐮𝐞𝐬 👉 DNS resolution failing for internal cluster domains even after proper config 👉 DHCP configuration mismatch caused bootstrap node not resolving cluster DNS. 👉 Incorrect 5533 port value persisted in dns-default ConfigMap despite manual edits. 👉 Need to roll out dns-default and node-resolver daemonsets after config changes. 👉 HAProxy backend misconfiguration affected external API resolution. 𝐎𝐃𝐅 / 𝐒𝐭𝐨𝐫𝐚𝐠𝐞 𝐈𝐬𝐬𝐮𝐞𝐬 👉 ODF StorageCluster stuck in Progressing due to missing csi-rbdplugin and rook-ceph-tools, while the csv status shows succeeded 👉 LocalVolume CR count (replica 3 vs 1, count 24) caused pending PV state. 👉 ODF tools not auto-created after deleting subscription; had to reconcile ocsinitialization. 𝐌𝐓𝐕 (𝐌𝐢𝐠𝐫𝐚𝐭𝐢𝐨𝐧 𝐓𝐨𝐨𝐥𝐤𝐢𝐭 𝐟𝐨𝐫 𝐕𝐢𝐫𝐭𝐮𝐚𝐥𝐢𝐳𝐚𝐭𝐢𝐨𝐧) 𝐈𝐬𝐬𝐮𝐞𝐬 👉 Migration plan imageConversion failed due to DNS not resolving source VM – 👉 Node level Vs Pod level resolutions 👉 Disk Transfer (DiskTransferV2V) phase stalled until DNS fixed. 👉 Warm migration PVC stuck in Pending until cut-over scheduled. 👉 MAC address duplication detected when migrated VM already existed in cluster. 👉 Post-migration VM boot loop (continuous restart) due to duplicate UUID or network policy. 𝐌𝐨𝐧𝐢𝐭𝐨𝐫𝐢𝐧𝐠 & 𝐆𝐫𝐚𝐟𝐚𝐧𝐚 👉 Grafana operator installed, but CRD GrafanaDatasource missing. 👉 Operator-based Grafana vs Helm-based deployment. How it fits the environment an what is the customer ask 👉 Bearer token for Prometheus datasource not documented; had to use ServiceAccount token. 𝐀𝐮𝐭𝐡𝐞𝐧𝐭𝐢𝐜𝐚𝐭𝐢𝐨𝐧 (𝐋𝐃𝐀𝐏 𝐈𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐨𝐧) 👉 Initial htpasswd provider working, LDAP integration took time to reconcile 👉 Wrong OU in URL (OU=ServiceAccounts vs OU=abcd ) caused bind failure. 👉 Missing username (admin) in secret → no bind authentication. 👉 Needed to use CN=admin and sAMAccountName in URL to work properly. sAAMcoutName vs uid , when to use what options 👉 CLI login failed even when console worked .. why 𝐍𝐞𝐭𝐰𝐨𝐫𝐤𝐢𝐧𝐠 / 𝐃𝐍𝐒 / 𝐅𝐢𝐫𝐞𝐰𝐚𝐥𝐥 👉 Different VLAN and bonding issues NNCP , NAD issues 👉 Restart named service after zone update; Serial number not incremented initially.