The upgrade-requirements.log file had several "Fatal" errors since I've tried this upgrade several times. The last one w/ errors is listed below.
2018-10-03T00:25:03.901Z INFO upgrade_commands Creating OpsManager (Ssh based).
2018-10-03T00:25:03.901Z INFO networking_utils isHostReachable(): try getaddrinfo('vhost2.example.local', '443', 0, SocketKind.SOCK_STREAM, 6)...
2018-10-03T00:25:03.903Z INFO networking_utils isHostReachable(): getaddrinfo() found 1 entries (first is used):
FAMILY: AddressFamily.AF_INET, TYPE=SocketKind.SOCK_STREAM, PROTO=6, CANONNAME=, ADDR=('10.1.1.15', 443)
2018-10-03T00:25:03.904Z INFO networking_utils isHostReachable() succeeded: address //vhost2.example.local:443 is reachable
2018-10-03T00:25:04.87Z ERROR transport.guestops GuestOpsOperationManager is not initialized. Missing guest.guestFamily property
2018-10-03T00:25:04.98Z ERROR transport.guestops GuestOpsOperationManager is not initialized. Missing guest.guestFamily property
2018-10-03T00:25:04.98Z ERROR upgrade_commands Vmware Tools driver is not initialized on source vCSA (vcsa01.example.local), Error: GuestOpsOperationManager is not initialized. Missing guest.guestFamily property
2018-10-03T00:25:04.99Z ERROR root Could not create command factory.
2018-10-03T00:25:04.99Z ERROR __main__ ERROR: Fatal error during upgrade REQUIREMENTS. For more details take a look at: /var/log/vmware/upgrade/requirements-upgrade-runner.log
2018-10-03T00:25:04.100Z INFO root Exiting with exit-code 1
Also here's the output of the command you asked for. Looking at the error above and the output below, it's finally making sense why this is failing. I presume the guestId, guestFamily, and guestFullName are set by vmtoolsd running on the vm. I looked at the VM config but couldn't find anywhere they could be set.
# vim-cmd vmsvc/get.guest 69 | grep -i guest
Guest information:
(vim.vm.GuestInfo) {
toolsVersionStatus = "guestToolsUnmanaged",
toolsVersionStatus2 = "guestToolsUnmanaged",
toolsRunningStatus = "guestToolsRunning",
toolsUpdateStatus = (vim.vm.GuestInfo.ToolsUpdateStatus) null,
guestId = <unset>,
guestFamily = <unset>,
guestFullName = "",
net = (vim.vm.GuestInfo.NicInfo) [
(vim.vm.GuestInfo.NicInfo) {
ipStack = (vim.vm.GuestInfo.StackInfo) [
(vim.vm.GuestInfo.StackInfo) {
disk = (vim.vm.GuestInfo.DiskInfo) [
(vim.vm.GuestInfo.DiskInfo) {
(vim.vm.GuestInfo.DiskInfo) {
(vim.vm.GuestInfo.DiskInfo) {
(vim.vm.GuestInfo.DiskInfo) {
(vim.vm.GuestInfo.DiskInfo) {
(vim.vm.GuestInfo.DiskInfo) {
(vim.vm.GuestInfo.DiskInfo) {
(vim.vm.GuestInfo.DiskInfo) {
(vim.vm.GuestInfo.DiskInfo) {
(vim.vm.GuestInfo.DiskInfo) {
screen = (vim.vm.GuestInfo.ScreenInfo) {
guestState = "running",
guestKernelCrashed = <unset>,
guestOperationsReady = true,
interactiveGuestOperationsReady = false,
guestStateChangeSupported = true,
To try something different, I moved the vcsa VM to a different vhost but got the same results from the vim-cmd vmsvc/get.guest command.
Thoughts?
Scott
