OBM 2022.05 upgrade to OA 12.27 issue

Problem after upgrade of OA from 12.22 to 12.27 on the 2022.05 OBM GW servers.  I already have a high priority case open on this, but I'd like to know if anyone has seen this. Every little bit helps.  2 DPs 2 GWs so it's a distributed environment on win2022 servers and the DPs are set as HA, Oracle DB, no LB.  We're having to upgrade OA to 12.27 on every server with an agent due to a CVE.  We're not prepared just yet for an OBM upgrade, which I know normally is the best way to upgrade OA on the OBM servers with the OBM install itself.  I upgraded to OA 12.27 on the DPs and the DPs start with no issues and OA looks good on both.  I upgraded to 12.27 on the GWs and every thing starts, but OA on the OBM servers and the managed nodes/agents starts buffering.  I reverted back to 12.22 on one GW to restore service.  It seems OA 12.27 runs fine until the GW is started then OA can't communicate.  I start seeing a lot of IO and SSL errors in the logs and when running opcagt it does not show a buffering status at the bottom of the output when ran on the GWs.  In our test environment we do not see this issue.  We only have 10 or so managed nodes/agents connected to our test environment, but in prod we have thousands.  Thank you.

Parents Reply Children
  • 0 in reply to   

    Hi Tim,

    I used to understand the same, but I found you can upgrade OA on the OBM servers without an OBM upgrade.  I sure it's best to upgrade OBM and let it upgrade OA, but timing to fix this CVE is not allowing me a complete upgrade of OBM.  Again we are on OBM 2022.05 and I'm trying to upgrade to 12.27 to fix CVE-2024-5532.  The SUMA shows that OA 12.27 is supported and co-exist with OBM 2022.05.

    https://portal.microfocus.com/s/article/KM000035731?language=en_US

    The upgrade on our test servers worked great and when starting the OBM gateways I see no issues.  It's in prod that OA has issues after starting the GW.  In prod OA 12.27 runs with no issue until the GW is started.