Issues after upgrading Identity Manager 3.1 to 3.3

[Andervale]

After upgrading Identity Manager to 3.3, the first node stopped work.The second and third node are funcional and up to date. We tried to clone the second e third node, changing the IP adress, but when boot started, they not recognize the new ip, changed previously. These changes was made in YAst and vAPP interface, but was not make effect. Could you help us to resolve this issue?

regards

[David1Black]

We ran into similar issues this week.  We build out a new 3.3 appliances, and during the cloning of the 2nd and 3rd it did not reset the IP address so they all have the same.  Changing it in Yast works until a reboot, and it reverts back to the 1st IP.  I'm able to get things working by stopping and starting services, but ACS health still shows RED. And if/when we reboot all will break again.

[David1Black]

Check out this KB article.  It worked well for me:  VMware Knowledge Base

[Andervale]

Hi David

My issue was solved using this steps below :

Move the files below to another directory :

•    /etc/sysconfig/network/routes.bak

•    /etc/resolv.conf.bak

•    /etc/sysconfig/networking/devices/ifcfg-eth0.bak

- Make a boot in the server

- When the server starts, reconfigure IP, Mask, GW...

- Make a validation, verifying the new ip address and finally test, using a URL https://<server_url>/SAAS/auth/Login

Using this steps, my problem was solved.

Regards

Anderson Lemos