Problem to deploy a only partition image using multicast

[Fernando Gietz]

Hi,

I have updated the FOG server version recently from 1.5.2 to 1.5.4 and in this version when I try to deploy an only partition image (for example only the second partition) using a multicast task, if I deploy it with an unicast tasks, works fine, the partclone download in /dev/sda2 the d1p1.img file.
Always the d1p1.img, if you want to deploy the 4th partition, parclone download the d1p1.img in /dev/sda4.

FOG version: 1.5.4
Server OS: RHEL 7

[Sebastian Roth]

@Fernando-Gietz Just so I get this right, it works fine/correct as unicast task - d1p3.img -> /dev/sda3 for example?

But wrong when run as multicast task?

[Fernando Gietz]

@Sebastian-Roth Yes.
I deployed, before update the version 1.5.2 to 1.5.4, without problems one partition using a multicast tasks, but with 1.5.4 doesn’t deploy well.

With unicast d1p3.img --> /dev/sda3
With multicast d1p1.img --> /dev/sda3

[Sebastian Roth]

@Fernando-Gietz I have looked into this. I am very sorry but to me it seems like this could have never worked before. I even setup a 1.5.2 server to test and could only replicate the same issue as reported.

Good two and a half years ago we noticed that deploying a single partition does not even work in unicast mode at all and fixed it - see here. From my point of view we missed to fix that in multicast mode altogether as very few people seem to use it and it has never worked I reckon.

Possibly you have done unicast for a group of machines in 1.5.2?

[Fernando Gietz]

@Sebastian-Roth I don’t test it doing a unicast deploy for a group. I tried it doing a unicast deploy for one computer, and worked well.

I want to report that with the version 1.5.2 worked well for multicast deploy.

[Fernando Gietz]

I have tested a group deploy unicast and works fine. The problem is with the multicast tasks.

[Sebastian Roth]

@Fernando-Gietz said in Problem to deploy a only partition image using multicast:

I want to report that with the version 1.5.2 worked well for multicast deploy.

As I said, I have looked through the code history and even tried 1.5.2 myself and multicast for single partition has not worked in 1.5.2 - I am pretty much sure!

Hope I will find the time to fix this soon. But it’s not a simple fix and needs some time and work.

[Fernando Gietz]

Thanks @Sebastian-Roth , I will wait the fix

[Sebastian Roth]

@Fernando-Gietz Ok, this is fixed in the working branch. Please give updating to the working branch a try if you are keen.

[Fernando Gietz]

Hi @Sebastian-Roth ,

I tried to install the working branch to test it but appears some error:

# more /root/fog_1.4.0/bin/error_logs/fog_error_1.5.4.8.log 
/bin/lsb_release
/bin/systemctl
ln: fallo al crear el enlace simbólico «/usr/lib/systemd/system/mysql.service»: El fichero ya existe
ln: fallo al crear el enlace simbólico «/usr/lib/systemd/system/mysqld.service»: El fichero ya existe
ln: fallo al crear el enlace simbólico «/etc/systemd/system/mysql.service»: El fichero ya existe
ln: fallo al crear el enlace simbólico «/etc/systemd/system/mysqld.service»: El fichero ya existe
/opt/fog/.fogsettings

And the installation process stops here:

 * Here are the settings FOG will use:
 * Base Linux: Redhat
 * Detected Linux Distribution: Red Hat Enterprise Linux Server
 * Server IP Address: 10.0.yyy.xxx
 * Server Subnet Mask: 255.255.255.0
 * Interface: ens192
 * Installation Type: Normal Server
 * Internationalization: 
 * Image Storage Location: /images
 * Using FOG DHCP: No
 * DHCP will NOT be setup but you must setup your
 | current DHCP server to use FOG for PXE services.

 * On a Linux DHCP server you must set: next-server and filename

 * On a Windows DHCP server you must set options 066 and 067

 * Option 066/next-server is the IP of the FOG Server: (e.g. 10.0.yyy.xxx)
 * Option 067/filename is the bootfile: (e.g. undionly.kpxe)


 * Are you sure you wish to continue (Y/N) 
 * Installation Started

 * Installing required packages, if this fails
 | make sure you have an active internet connection.

 * Adding needed repository....................................

[Sebastian Roth]

@Fernando-Gietz What do you mean by “stops here”? It usually takes a couple of seconds at this stage, sometimes a bit longer if your internet connection is slow. But it should finish with “OK” or “Failed”.

[Fernando Gietz]

I waited several minutes and nothing, but I will try again …

[Fernando Gietz]

I rerun the installer with the same results

[Quazz]

@Fernando-Gietz Those ‘errors’ are fine, they’re just pointing out the symbolic link already exists (which is fine)

It stopping on adding repositories is more concerning, perhaps yum is stuck?

[Sebastian Roth]

@Fernando-Gietz Try running: yum update

Ummmm? Just noticed this: /root/fog_1.4.0/bin/error_logs

Sure you’re not mixing thing up here??

[Fernando Gietz]

Hi,

I have rebooted the machine And now works fine

[Sebastian Roth]

@Fernando-Gietz You mean the installer or pushing a single partition to clients via multicast?

[Fernando Gietz]

The installer, I am trying now to deploy one partition and seems that works fine

[Fernando Gietz]

I can confirm that works fine