problème rencontrer lors du déploiement

[julio]

Bonjour quelqu’un pourrais m’expliquer quelle est la solution ici svp la ligne /dev/sda1, 10) failed: no such file or directory j’étais en plein déploiement de ma distribution ubuntuclient 18.04 et j’ai eu cette erreur.

[Sebastian Roth]

@julio If you need rename and domain join on Linux systems you’ll have to manually add scripts to do that work for you. Rename can be done woth post-deploy scripts I would think but domain join is another story. You might even need to add systemd/initd scripts to do that for you. Currently this is way beyond what FOG or the fog-client can do for you I have to admit.

[julio]

@sebastian-roth Bonjour roth. oui je veux bien que le nom de mon système linux puisse changer après le déploiement. mon projet consiste à déployer des postes linux via le réseau et je ne sais pas si je dois aussi installer fog-client sur des postes linux qui pourra renommer le nom de ma machine après le déploiement. je dois deployer des distributions ubuntu client, debian client etc. puis joindre un domaine et les machines doivent etre preconfigurer comme le hostname de la machine qui dois changer etc.

[Sebastian Roth]

@julio As you mention domain join I am wondering if you now talk about Windows deployment or still Linux systems? It’s a different story.

Windows:

• Rename should happen at the end of the deployment automatically (FOG settings -> CHANGE_HOSTNAME_EARLY is enabled by default)
• Beyond that you need to have the fog-client software installed on the image you deploy to the machine -> that can do the rename as well and join a Windows AD domain when things are setup correctly

Linux:

• You can use the fog-client software mentioned above as well but this is not tested very well and I am not sure it works on current Linux systems. So I can’t promise this is working.
• You can use post-deploy scripts (explained here) to set the hostname on you Linux systems right after deploy.
• People have discussed AD join on Linux systems in the forum as well but this is pretty old: https://forums.fogproject.org/topic/9638/join-active-directory-using-fog-on-ubuntu-linux

[julio]

@sebastian-roth
j’avais une autres questions: comment je pourrais joindre le domaine avec la machine et avoir le nom de ma machine qui change. j’utilise fog 1.5.9 mais je n’arrive pas à joindre mon domaine. et apres le déploiement le nom de ma machine n’a pas changer. quelle est réellement le problème.

[julio]

@sebastian-roth
salut roth, oui le déploiement fonctionne comme tu me la suggerer de faire mais le nom de ma machine n’a pas changer et pourtant elle le devrait. la machine que j’ai capturer quand je la déploie sur une machine cible, le nom de la machine reste intact pas de changement. es ce normal

[Sebastian Roth]

@julio While I am not exactly sure I would imagine you can ignore this message because it happens when FOG does the “Erasing current [meaning old] MBR/GPT Tables [or partition table]”. So it could happen that the devd daemon watching for device files still had /dev/sda1 on it’s list when it got wiped that moment.

Again, this is usually not an issue as long as the rest of the deployment runs fine. And it seems like it does in your case.

The next time the machine boots it will try to PXE boot again (if you don’t switch to boot from disk manually) and this will fail because of a known issue with VirtualBox and iPXE’s undionly.kpxe file. So you have a few options here:

1. Use ipxe.pxe instead in your DHCP config
2. Shut down the VM after a deploy and start it up manually again and let it PXE boot
3. Stop the VM after deploy and switch to boot from disk directly.