Anyone else seeing a rash of issues with the Admin Console reporting the wrong component versions after applying patches?
I had a 5.1 dev environment that I was running 5.1.0.1, but I didn't realize that the IdP and AG were still being reported as 5.1.0.0-272 under Troubleshooting | Version in the admin console. The Admin console itself was reporting correctly though as 5.1.0.1. I tried applying 5.1.0.2 patch, but the IdP and AG still report in the version screen as 5.1.0.0-272. The Admin console reports as 5.1.0.2-30 now. I tried removing the patches with the patch tool and reinstalling, but it made no difference.
So decided to try patching another environment. This one was 5.1.0.1-22 on all device. They all were reporting properly in Troubleshooting | Version in the Admin console. In this environment there are 2 admin consoles. Applied 5.1.0.2 on both admin consoles and now the admin console reports as 4.4.0.0! Screen shot below.
Crazy!! The version file though on the admin console says it is 5.1.0.2-30. Anyone seen that before?
Lastly, I had a 5.0.4 environment I upgraded to 5.0.4.1 and then applied the latest hot fix. On that one, even though the IdPs show 5.0.4.1 in the local version file, the admin console shows them as 5.0.4.0 still.
I have support cases open on all these, but little action so far. Anyone else seeing anything like this?
I'm starting to get nervous about applying any patches or updates now (I have 14 support cases open on Access Manager right now).
These are all RedHat environments (first two are 8.10 and last one is 8.8). So I'm wondering if that is part of the problem?
Does anyone know exactly how the admin console pulls the version info? I haven't been able to get that answer out of support.
Matt