My customer is being advised by TAC to upgrade their CUPS 6.0(5) to V7.0(7) and so we decided to try out upgrade in the lab, which is built on VMware ESX V3.5. My CUPS server was initially 6.0(2) and was upgraded to V6.0(5) in this environment (or so I understand). I did a remote upgrade to the V7.0(7) upgrade kit and the upgrade proceeded and stated it had completed successfully. I then did a UTILS Switch-version, which reported that V7.0(7) was on my inactiver partition, so I said proceed. The gutest CUPS machine restarted but did not return to service, when I checked the console, the server was displaying a "Kernel panic - Not syncing: attempted to kill init", which as I understand Linux is the equivalent to the Windows "Inaccessible boot device".
Unfortunately, now it is in this state I can't fathom out how to restart it in the previous 6.0(5) partition. I tried the recovery disk but that ends up at same point (Kernel panic) and does nothing as far as I can tell. I need to test this upgrade in the lab before trying production and whilst I can rebuild the guest server from clean V6.0(2) I would love to know why this has happened and how to either recover to my previous version of CUPS or how to get this upgrade working :-)
Is there some specific version of Linux environment configuration we should use when building on VMware ?