This document was generated from CDN thread
Created by: Ben Sunderland on 18-01-2012 09:48:14 PM
Hi,
I have been upgrading my dev box from 251 to 252 and it seems to have gone ok, but for one thing, after upgrading to 252, all the nodes reported the correct version in director EXCEPT cache node and search master node. When SSH'ing into each, the header presented on login indicated the correct upgraded version.
I decided to apply SR1 to see if that fixed, but the two above nodes are stillreporting as 251 in director, but now 252SR1 via SSH.
Can I clean up some how ? have tried service puppet debug on each and a few restarts of the OS / services.
Note, director can communicate with both nodes, since I can enable / disable via director.
regards,.
Ben.
Subject: RE: WebEx Social upgrade to 252 - version mismatch.
Replied by: Ben Sunderland on 23-01-2012 07:30:22 PM
FYI,
I just decided to rebuild the nodes and now all report the correct version in the shell AND via director.
for a clean rebuild I :-
1) power off and delete the node
2) remoce the puppet master certificate on director
3) remove and re-add the role on director control panel
4) redepoly VM
5) check that the certificate on director comes back (automatically as part of node install), and check version status.
Because I was deploying search master, I had to then deploy search slave (as per above) , and then rebuild the search index.
Ben
