Mitchell Locke said:

Support had me check the SHA which was confusing because it's not correct on the sld. But I do have the correct SHA.

If you have downloaded the Updated OES 23.4 ISO from SLD (available since 29th March 2024) then, the checksum must match 6eb493dfeb53036c26a57af8838abaf009da0e8c1953da80ee7f50d0fbfe630b (sha256).  

I have not run into this specific case, so test this before applying it to production.  My OES 24.x servers are running PHP 8.  All three screen shots show resolution option 2 as de-installing some PHP 5 component.  My guess is that choosing option 2 would remove the PHP 5 conflict and allow the upgrade to complete.  But again, please test this first to see if it provides the desired outcome.

Thank you! I checked and the checksum matches.

Thanks for checking. We will investigate this and get back to you at the earliest.

I ran into the same issue on the weekend (all replica, DNS, DHCP server, so not as many things complaining) , and knowing that was an old php, I selected the deinstallation of it, and had a successful upgrade.

I agree with Ken, but before blindly deinstalling php5 stuff, ask yourself if you have any non-OES php5-based application of your company (or maybe some 3rd-party application?) running on this server?

If yes, check first if this application can be easily ported to php8 or moved to another server.

If no, just do as Ken said and choose the deinstallation of all the php5 and ganglia stuff (ganglia monitoring is no longer supported with OES2023 and later). This choice is fine as nothing of OES23.4 uses php5 or ganglia. It's probably just an installer glitch. My guess is that your system had ganglia monitoring installed before, that's about the only thing in OES2018SP3 that still required php5.

Thank you everyone for the replies. I did end up checking option 2 for deinstallation and everything is working as expected after the upgrade. Luckily these servers just run OES and no third-party applications.

Hi Everyone, we acknowledge this issue seen while upgrading from OES 2018 SP3 to OES 23.4. Engineering is actively working on providing a fix and should be made available very soon. We will keep this thread updated as soon as the fix is published. Thank you.

Not having seen this with the original OES 23.4 ISO, would that be the preferred instance for OES 2018.3 upgrades for now? Leaving the newest 23.4 iso for the 2023 instances to upgrade?

Based on investigation so far, it isn't related to the new ISO and we suspect the new 23.4 Pool channel.