Very odd.....Maybe try Incognito mode....Maybe browser cache??

With Docker Instances, its hard to get corruption in the source files......Wish I had better thoughts.

Well, two good ideas but neither seems to want to work. Tried y our thoughts in Chrome and Edge and no difference.

I can be available to run diagnostics if Engineering is interested.

Can you try the following commands and then just try accessing zcc? No need to restart any services. It might take a bit longer to load zcc . May be 3-5 seconds. ( I have a feeling the 2nd set of commands should help..)

docker exec -it zenadmin-mgmt bash

rm -rf /opt/microfocus/zenworks/share/tomcat/work/Catalina/localhost

exit

docker exec -it zenclient-mgmt bash

rm -rf /opt/microfocus/zenworks/share/tomcat/work/Catalina/localhost

exit

No luck. I restarted the appliance and cleared cache in Chrome (again) just in case but still the same result.

Happy to give further potential solutions a try or gather diagnostic information as necessary. Appreciate the support!

By any chance, are you accessing ZCC through a proxy or something? If yes, could it be a caching issue at the proxy side?

Can you send the output of docker image ls command?

Here's the output:

Unfortunately, these seems to be ok. As of now, we have checked all the possible suspects.. As you have tried multiple browsers, I hope you would have tried to access ZCC from some other device as well.

Browser cache, proxy, tomcat work folder, docker images.. and everything looks fine. May be we need to have an SR?

Hi everyone.

Old post but same behavior on a nearby same path of upgrade. OSP disabled on server as: https://www.novell.com/documentation/zenworks-23.4/zen_cm_deployment_bp/data/t4h9vomb68gz.html?view=print documented.

Enable OSP and everything fine. Seems like a defect.

For lurkers, OSP IS a best practice.

Regards, Brian.

That is 100% working as Designed.

It gives you a visual representation you are using a different login.

FYI...OSP is well beyond "Best Practice"....

OSP is used MANY places beyond the ZCC login....

--

Disabling OSP is "Break in Case of Fire" as a temporary fix until you resolve your root cause...which may require a ZCC login.

Enabling this will affect services using tokens such as the Antimalware dashboard >
doc says that, you are right, sorry for not getting such as depth, my bad. OSP is massively used right now, I know.