SAS VIYA 3.5 UPGRADE ON Distributed Machines

[AliZiya]

Hello All, 

I am trying to upgrade my SAS Viya 3.5 on linux. There 7 different machine here. You can see below ss the IP's and their duties. In previous deployment xx.xx.xx.208 Virtual IP address used for the HA Pgpool. This Virtual IP address can not be usable for now. And client gives us an new virtual IP address called xx.xx.xx.209. When we run the upgrade command we got 3 failed about ( HA Pgpool ) on the upgrade process. Do you have any best practices ? What should we do? 

Also, we tried to run services via via-ark command in the old deployment sas-viya-playbook directory after the change settings HA pgpool IP address in the vars.yml 208 to 209. Then, when we run the stop.yml and then we get an error in the below ss. Maybe it helps.

Thank you

[gwootton]

So the currently configured Virtual IP no longer works? You may wish to engage SAS Technical Support, I suspect you'd need to perform some steps on the pool outside of ansible to use the new IP and then ensure vars.yml values match that new configuration to allow ansible commands to work.

Documentation on the SAS Infrastructure Data Server can be found here:
https://go.documentation.sas.com/doc/en/calcdc/3.5/calsrvinf/n00000sasinfrdatasrv000admin.htm

[AliZiya]

NEW UPDATES!! 

The customers changed the name of xx.xx.xx.209 to 208. Thus we have fixed name issue. We run ansible update command but deployment was failed. SAS ticket told us https://documentation.sas.com/doc/en/calcdc/3.5/dplyml0phy0lax/n0fk6oairnlkuon1bgjg97jen3b8.htm verify the virtual IP in this document and it should be reachable. Although the virtual IP added the 3 microsevices but our arpying command reciev 0 response. How will we fix that ? 

[gwootton]

That documentation indicates the virtual IP address would only be ping-able when at least two nodes in the HA pgpool-II cluster are running. Is that true in your case?
If that is true and this is failing would suggest an issue with the virtual IP configuration.