VIC Appliance 1.4.4 registration with VCSA 6.7u1 has failed. Wrong Appliance UUID

[tsimchev]

Summary

When I started my fresh VIC Appliance 1.4.4 into my vCenter 6.7u1 and registered the vCenter I received an error "failed to get product vm : can't find the hosting vm". When I checked the code I saw that VIC appliance is reading VM UUID from "/sys/class/dmi/id/product_serial" and this UUID was different than the one in my vCenter VIC Appliance VM.

When I updated my vCenter VIC Appliance VM UUID with the one from "/sys/class/dmi/id/product_serial" VIC Appliance registered successfully.

Environment information

vSphere and vCenter Server version

vSphere 6.7u1

VIC Appliance version

vic-v1.4.4-6375-0a6da3d4.ova

Configuration

• Embedded or external PSC: yes
• How was the OVA deployed? (Flex client, HTML5 client, ovftool): HTML5 client
• Does the VIC appliance recieve configuration by DHCP?no
• What stage of the Appliance Lifecycle is the VIC appliance in?

• IP address of VIC appliance:
• Hostname of VIC appliance:
• IP address of vCenter Server:
• Hostname of vCenter Server:

Details

Steps to reproduce

Actual behavior

Expected behavior

Support information

Logs

After generating /etc/vmware/support/appliance-support.sh --include-private --outdir logs
The error was located in "appliance/systemctl_status_fileserver"

● fileserver.service - VIC Appliance Web Server
Loaded: loaded (/usr/lib/systemd/system/fileserver.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-01-04 12:07:44 UTC; 40min ago
Docs: https://vmware.github.io/vic-product/index.html#getting-started
Process: 782 ExecStartPre=/usr/bin/bash /etc/vmware/fileserver/configure_fileserver.sh (code=exited, status=0/SUCCESS)
Process: 775 ExecStartPre=/usr/bin/systemctl stop landing_server.service (code=exited, status=0/SUCCESS)
Main PID: 788 (start_fileserve)
Tasks: 11
Memory: 25.0M
CPU: 669ms
CGroup: /system.slice/fileserver.service
├─788 /usr/bin/bash /etc/vmware/fileserver/start_fileserver.sh
└─791 /usr/local/bin/ova-webserver --addr :9443 --cert /storage/data/certs/server.crt --key /storage/data/certs/server.key

Jan 04 12:47:40 vic-l-01a.corp.local start_fileserver.sh[788]: Jan 4 2019 12:47:40.314Z DEBUG op=791.8: Cached folders:
Jan 04 12:47:40 vic-l-01a.corp.local start_fileserver.sh[788]: Jan 4 2019 12:47:40.314Z DEBUG op=791.8: Error count populating vSphere cache: (1)
Jan 04 12:47:40 vic-l-01a.corp.local start_fileserver.sh[788]: Jan 4 2019 12:47:40.314Z DEBUG [ END ] [vic-product/installer/lib.(*LoginInfo).VerifyLogin:43] [188.502554ms]
Jan 04 12:47:40 vic-l-01a.corp.local start_fileserver.sh[788]: Jan 4 2019 12:47:40.314Z INFO op=791.8: Validation succeeded
Jan 04 12:47:41 vic-l-01a.corp.local start_fileserver.sh[788]: Jan 4 2019 12:47:41.148Z DEBUG op=791.8: failed to get product vm : can't find the hosting vm
Jan 04 12:47:41 vic-l-01a.corp.local start_fileserver.sh[788]: Jan 4 2019 12:47:41.158Z ERROR op=791.8: Install failed: Failed to locate VIC Appliance. Please check the vCenter Server provided and try again
Jan 04 12:47:41 vic-l-01a.corp.local start_fileserver.sh[788]: Jan 4 2019 12:47:41.158Z DEBUG [BEGIN] [vic-product/installer/fileserver/routes.RenderTemplate:45]
Jan 04 12:47:41 vic-l-01a.corp.local start_fileserver.sh[788]: Jan 4 2019 12:47:41.158Z INFO op=791.8: render: html/index.html
Jan 04 12:47:41 vic-l-01a.corp.local start_fileserver.sh[788]: Jan 4 2019 12:47:41.160Z DEBUG [ END ] [vic-product/installer/fileserver/routes.RenderTemplate:45] [2.174624ms]
Jan 04 12:47:41 vic-l-01a.corp.local start_fileserver.sh[788]: Jan 4 2019 12:47:41.160Z DEBUG [ END ] [vic-product/installer/fileserver/routes.(*IndexHTMLRenderer).IndexHandler:47] [1.034929878s]

See also

Troubleshooting attempted

Check the UUID in VIC Appliance /sys/class/dmi/id/product_serial and vCenter VIC Appliance VM, they differ.

4210903f-c890-7ea7-479b-42a366686987 from /sys/class/dmi/id/product_serial
422e2b4e-4e01-a9cb-b653-7d5f94fca189 from vCenter MOB

• Searched GitHub for existing issues. (Mention any similar issues under "See also", above.)
• Searched the documentation for relevant troubleshooting guidance.
• Searched for a relevant VMware KB article.

[zjs]

@renmaosheng: It looks like this issue from a month ago has not yet been triaged.