Import of VMs failed with: 1406 Data too long for column 'guest_full_name' at row 1

[NeverUsedID]

Current Behavior

15:22:59: Task virtualMachines failed: Storing virtual_machine[m�:�!=b�] failed: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'guest_full_name' at row 1, query was: INSERT INTO virtual_machine (uuid, vcenter_uuid, annotation, hardware_memorymb, hardware_numcpu, hardware_numcorespersocket, template, bios_uuid, instance_uuid, version, connection_state, online_standby, paused, guest_id, guest_full_name, guest_state, guest_host_name, guest_ip_address, guest_tools_status, guest_tools_running_status, resource_pool_uuid, runtime_host_uuid, runtime_last_boot_time, runtime_last_suspend_time, runtime_power_state, boot_network_protocol, boot_order, cpu_hot_add_enabled, memory_hot_add_enabled) VALUES ([...]

Possible Solution

Solved by raising VARCHAR from 128 to 255 for table guest_full_name at table virtual_machine.

Steps to Reproduce (for bugs)

Import an Virtual Appliance with an ugly guest full name like:

"Linux 4.9.194 NAME=Buildroot
VERSION=20xx.xx.x
ID=buildroot
VERSION_ID=20xx.xx.x
PRETTY_NAME="Buildroot 20xx.xx.x"
APPLIANCE_VERSION="vx.x.x"'
"

Your Environment

• Version/GIT-Hash of this module: 1.1.0

[Thomas-Gelf]

@NeverUsedID: out of curiosity, where can I get such an Appliance? guest_full_name usually refers the operating system, like 'Microsoft Windows Server 2016 or later (64-bit)'. What you're showing looks more like a candidate for custom fields or annotations?!

[NeverUsedID]

Its was Vendor Appliance that was deployed directly from their image. No idea how they created that. Looks like they used something like buildroot.org to create there own embedded linux