Linux VDA 1903 + Ubuntu 18.04 - Running deploymcs.sh breaks the system

[Sara Passarelli]

Hello,

 

I have an intriguing issue here. Following the Linux VDA 1903 release, I've been trying to create a Ubuntu 18.04 template (golden image) to deploy several VDIs using MCS.

 

My underlying virtualization environment is VMware vSphere 6.0. Because of that, I've installed one more package in my template: open-vm-tools.

 

I can register my template on a machine catalog after following all the steps on https://docs.citrix.com/en-us/linux-virtual-delivery-agent/current-release/installation-overview/ubuntu.html.

It works flawlessly.

 

However, the next step is to prepare it to use MCS (https://docs.citrix.com/en-us/linux-virtual-delivery-agent/current-release/installation-overview/use-mcs-to-create-linux-vms.html).

When I run deploymcs.sh and turn off my template, it won't boot again, the system gets broken. If I check the boot messages, it gets stuck in starting Network Manager, Login Manager, Gnome Display Manager and so on.

Please check the first attached image.

 

Sometimes the following kernel message appears "vmwgfx:  error - topology is beyond supported limits" or something like that.

Do you guys have any idea?

 

Kind regards,

 

Roberto

[paulius Sernius]

Hi,

 

In order to create MCS template do not configure the full VDA using: https://docs.citrix.com/en-us/linux-virtual-delivery-agent/current-release/installation-overview/ubuntu.html. 

 

Only use the MCS document to configure the MCS part nothing else: https://docs.citrix.com/en-us/linux-virtual-delivery-agent/current-release/installation-overview/use-mcs-to-create-linux-vms.html

 

deploymcs.sh prepares the template image for you so you do not have to configure it to register etc as it is not meant to.

 

[Sara Passarelli]

On 16/05/2019 at 5:23 AM, paulius Sernius said:

Hi,

 

In order to create MCS template do not configure the full VDA using: https://docs.citrix.com/en-us/linux-virtual-delivery-agent/current-release/installation-overview/ubuntu.html. 

 

Only use the MCS document to configure the MCS part nothing else: https://docs.citrix.com/en-us/linux-virtual-delivery-agent/current-release/installation-overview/use-mcs-to-create-linux-vms.html

 

deploymcs.sh prepares the template image for you so you do not have to configure it to register etc as it is not meant to.

 

 

Still no success... I'll wait for the next VDA release in order to test again.

 

Thank you!

[Rob Hugg]

I have the same issue. Here is my workaround. I open a case but I am getting nowhere with them...

 

In the ad_join.log I see Error: NEW_HOSTNAME is empty. Exiting...". I also see the script trying to mount /dev/loop#

 

Dbus fails to start because of the ad_join.sh fails on checking if NEW_HOSTNAME is empty and it exits with 1.

 

The script is called by ExecStartPre=/var/xdl/mcs/ad_join.sh as part of the dbus.service. The ad_join.sh script also calls /var/xdl/mcs/mcs_util.sh. This script tries to mount the identity disk but it is picking the wrong disk. It is choosing a loop device rather than the correct identity disk.

 

Line 180 of /var/xdl/mcs/mcs_util.sh tries to pick the right disk using 

           iddisk_dev_name=$(lsblk | grep 13M | sed 's/^[^[:alnum:]]*\([[:alnum:]]\+\).*$/\1/')

I rewrote that line as 

           iddisk_dev_name=$(cat /proc/partitions | grep sd | awk '{if ($3 > 13000 && $3 < 14000) print $4;}')

 

After doing this, I was able to successfully boot and create MCS machines. 

 

I did run into other issues like the gray screen and such but fixes are out there for those.