I recently had a storage network outage in my lab environment, and after powering back on my vCenter Server Appliance (VCSA) I was rudely greeted with the following information at the console:
Ouch! I’ve never dealt with file system corruption in a VCSA before, and the internet doesn’t seem to contain much information on what to do next. This post is my effort towards changing that.
In yesterday’s post, I updated my VCSA 6.0 appliance to version 6.5. Today, logged into the Appliance MUI and noticed that my appliance was not able to check for updates using the default web repository.
Before we really start, a quick note on terminology. The Appliance MUI (which means Appliance Management UI) is the new name for the old VAMI (vSphere Appliance Management Interface). The MUI is a HTML5 web interface for configuring basic and low-level settings for the VCSA. It’s accessible by connecting to your VCSA on port 5480.
So, what’s the deal? Well, when browsing to the update section of the MUI and checking for updates, I would receive the following error:
With today’s exciting release of VMware vSphere 6.5, I thought I’d celebrate by upgrading the vCenter Server Appliance (VCSA) in my lab from version 6.0 u2 to version 6.5. Since I’m doing this more or less blind, without having read any documentation whatsoever, I thought I would write a (hopefully short) post about the problems that arise during the upgrade process, and how to get past them.