18:30:02Démarré par le projet amont "Internes/pull-scanNodes" de numéro de build 68756018:30:02Causé à l'origine par :
18:30:02 Lancé par une alarme périodique
18:30:02Exécution en tant que SYSTEM
18:30:02Construction à distance sur gw-jenkins (daily controler) dans le répertoire de travail /home/jenkins/workspace/infra/fiii-debian-13-amd64-eole-ci-tests.daily
18:30:02[WS-CLEANUP] Deleting project workspace...
18:30:02[WS-CLEANUP] Deferred wipeout is used...
18:30:02[fiii-debian-13-amd64-eole-ci-tests.daily] $ /bin/bash -xe /tmp/jenkins4515309208966468322.sh
18:30:02+ /bin/bash /mnt/eole-ci-tests/jenkins/EoleNebula/runOneTestGG.sh -c BuildImagePrepare -I debian-13-amd64-eole-ci-tests.daily -a amd64
18:30:04ONE_AUTH=/home/jenkins/.one/one_auth par défaut (/home/jenkins)
18:30:04ARGUMENTS = -c BuildImagePrepare -I debian-13-amd64-eole-ci-tests.daily -a amd64 -U timer
18:30:04Début à 2025/12/18 17:30:04
18:30:04Mode AGENT
18:30:05Utilisateur authentifié : jenkins
18:30:05updateCacheImage
18:30:12debian-13-amd64-eole-ci-tests.daily rebuild car une nouvelle FI aura été reconstruite
18:30:12Génération debian-13-amd64-eole-ci-tests.daily
18:30:12 Daily : /mnt/eole-ci-tests/scripts/update-non-eole.sh 'debian-13-amd64-eole-ci-tests.daily' 'debian-13-amd64-eole-ci-tests.fi'
18:30:12 Pas de maj de daily ==> TO_REBUILD from FI
18:30:12 Génération Mode non persistant debian-13-amd64-eole-ci-tests.daily depuis debian-13-amd64-eole-ci-tests.fi
18:30:23 Attente Etat 'ACTIVE/RUNNING' (360) : PENDING/LCM_INIT ACTIVE/PROLOG ACTIVE/RUNNING ==> Ok, Duree=8s
18:30:31 Vm démarrée : debian-13-amd64-eole-ci-tests.daily id=1632598 on nebula84.eole.lan
18:30:43 monitorFichier 'contextualisation.log'
18:30:48 Machine update : Début ciContextualizeMachine : update,
18:30:48 Machine update : Debut ciContextualizeUpdate
18:30:48 Machine update : OS Debian GNU/Linux 13 (trixie) Version=13
18:30:48 Machine update : machine Update ==> utilise le dhcp!
18:30:48 --------------------------------------------
18:30:48 cat /etc/machine-id
18:30:48 dee73de80d47410b8d4a67200f33510f
18:30:48 --------------------------------------------
18:30:48 Machine update : Fin ciContextualizeUpdate
18:30:48 Machine update : Contextualization Machine OK
18:30:48 Machine update : jenkins 1632598 update Contextualization Machine : OK
18:30:48 Machine update : Fin ciContextualizeMachine : ok à 2025-12-18 18:30:40
18:30:58 monitorFichier 'instanceAutomatique.log'
18:31:03 Machine update : Debut ciConfigurationUpdate
18:31:03 Machine update : systemctl is-active network.target : active
18:31:03 Machine update : systemctl is-active network-online.target : inactive
18:31:03 Machine update : systemctl is-system-running : running
18:31:03 ** ip addr
18:31:03 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
18:31:03 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
18:31:03 inet 127.0.0.1/8 scope host lo
18:31:03 valid_lft forever preferred_lft forever
18:31:03 inet6 ::1/128 scope host noprefixroute
18:31:03 valid_lft forever preferred_lft forever
18:31:03 2: ens4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
18:31:03 link/ether 02:00:c0:a8:00:67 brd ff:ff:ff:ff:ff:ff
18:31:03 altname enp0s4
18:31:03 altname enx0200c0a80067
18:31:03 inet6 fe80::6d22:b751:9c0d:d163/64 scope link tentative
18:31:03 valid_lft forever preferred_lft forever
18:31:03 ** ip route
18:31:03 GW actuelle : OK
18:31:03 ** Test GW
18:31:03 ping: Warning: source address might be selected on device other than: ens4
18:31:03 [3172mMachine update : ATTENTION: ciPingHost ens4 => 192.168.0.1 ping=1 ==> K.O. (exit 1)
18:31:03 Machine update : Fin ciConfigurationUpdate
18:31:18 CheckUpdate.sh: /root/mount.eole-ci-tests A JOUR
18:31:18 CheckUpdate.sh: /root/getVMContext.sh A JOUR
18:31:18 CheckUpdate.sh: /root/EoleCiFunctions.sh A JOUR
18:31:18 CheckUpdate.sh: /root/.EoleCiTestsContext.sh A JOUR
18:31:18 CheckUpdate.sh: /root/.EoleCiTestsDaemon.sh A JOUR
18:31:18 FRESHINSTALL_IMAGE=debian-13-amd64-eole-ci-tests.fi
18:31:18 DAILY_IMAGE=
18:31:18 IMAGE_SOURCE=debian-13-amd64-eole-ci-tests.fi
18:31:18 IMAGE_FINALE=debian-13-amd64-eole-ci-tests.daily
18:31:18 IMAGE_FINALE = debian-13-amd64-eole-ci-tests.daily : inconnu, doUpgrade
18:31:18 Machine update : * doUbuntu
18:31:18 Machine update : * waitAptStopped
18:31:28 10, lock :
18:31:28 Ok, Stop
18:31:28 Machine update : * removeServicesGenant
18:31:28 * --------------------------------------------------------------------
18:31:28 * doAptGet remove -y ufw (10)
18:31:28 Lecture des listes de paquets…
18:31:28 Construction de l'arbre des dépendances…
18:31:28 Lecture des informations d'état…
18:31:33 Le paquet « ufw » n'est pas installé, et ne peut donc être supprimé
18:31:33 AUTOMATE : detect 'mise à jour,' => 0
18:31:33 AUTOMATE : detect 'nouvellement installés,' => 0
18:31:33 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
18:31:33 * doAptGet remove -y ufw --> 0
18:31:33 * --------------------------------------------------------------------
18:31:33 * --------------------------------------------------------------------
18:31:33 * doAptGet remove -y unattended-upgrades (11)
18:31:33 Lecture des listes de paquets…
18:31:33 Construction de l'arbre des dépendances…
18:31:33 Lecture des informations d'état…
18:31:33 Le paquet « unattended-upgrades » n'est pas installé, et ne peut donc être supprimé
18:31:33 AUTOMATE : detect 'mise à jour,' => 0
18:31:33 AUTOMATE : detect 'nouvellement installés,' => 0
18:31:33 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
18:31:33 * doAptGet remove -y unattended-upgrades --> 0
18:31:33 * --------------------------------------------------------------------
18:31:33 * --------------------------------------------------------------------
18:31:33 * doAptGet remove -y linux-kvm (11)
18:31:33 Lecture des listes de paquets…
18:31:33 Construction de l'arbre des dépendances…
18:31:33 Lecture des informations d'état…
18:31:33 E: Impossible de trouver le paquet linux-kvm
18:31:33 * doAptGet remove -y linux-kvm --> 100
18:31:33 * --------------------------------------------------------------------
18:31:33 * --------------------------------------------------------------------
18:31:33 * doAptGet remove -y cloud-init (11)
18:31:33 Lecture des listes de paquets…
18:31:33 Construction de l'arbre des dépendances…
18:31:33 Lecture des informations d'état…
18:31:33 Le paquet « cloud-init » n'est pas installé, et ne peut donc être supprimé
18:31:33 AUTOMATE : detect 'mise à jour,' => 0
18:31:33 AUTOMATE : detect 'nouvellement installés,' => 0
18:31:33 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
18:31:33 * doAptGet remove -y cloud-init --> 0
18:31:33 * --------------------------------------------------------------------
18:31:33 * --------------------------------------------------------------------
18:31:33 * doAptGet -y --purge autoremove (12)
18:31:33 Lecture des listes de paquets…
18:31:33 Construction de l'arbre des dépendances…
18:31:33 Lecture des informations d'état…
18:31:33 AUTOMATE : detect 'mise à jour,' => 0
18:31:33 AUTOMATE : detect 'nouvellement installés,' => 0
18:31:33 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
18:31:33 * doAptGet -y --purge autoremove --> 0
18:31:33 * --------------------------------------------------------------------
18:31:33 Removed '/etc/systemd/system/timers.target.wants/apt-daily.timer'.
18:31:33 Disabling 'apt-daily.service', but its triggering units are still active:
18:31:33 apt-daily.timer
18:31:33 The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
18:31:33 Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
18:31:33 template units). This means they are not meant to be enabled or disabled using systemctl.
18:31:33 Possible reasons for having these kinds of units are:
18:31:33 • A unit may be statically enabled by being symlinked from another unit's
18:31:33 .wants/, .requires/, or .upholds/ directory.
18:31:33 • A unit's purpose may be to act as a helper for some other unit which has
18:31:33 a requirement dependency on it.
18:31:33 • A unit may be started when needed via activation (socket, path, timer,
18:31:33 D-Bus, udev, scripted systemctl call, ...).
18:31:33 • In case of template units, the unit is meant to be enabled with some
18:31:33 instance name specified.
18:31:33 Removed '/etc/systemd/system/timers.target.wants/apt-daily-upgrade.timer'.
18:31:33 Disabling 'apt-daily-upgrade.service', but its triggering units are still active:
18:31:33 apt-daily-upgrade.timer
18:31:33 The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
18:31:33 Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
18:31:33 template units). This means they are not meant to be enabled or disabled using systemctl.
18:31:33 Possible reasons for having these kinds of units are:
18:31:33 • A unit may be statically enabled by being symlinked from another unit's
18:31:33 .wants/, .requires/, or .upholds/ directory.
18:31:33 • A unit's purpose may be to act as a helper for some other unit which has
18:31:33 a requirement dependency on it.
18:31:33 • A unit may be started when needed via activation (socket, path, timer,
18:31:33 D-Bus, udev, scripted systemctl call, ...).
18:31:33 • In case of template units, the unit is meant to be enabled with some
18:31:33 instance name specified.
18:31:33 Created symlink '/etc/systemd/system/sysinit.target.wants/debug-shell.service' → '/usr/lib/systemd/system/debug-shell.service'.
18:31:33 Machine update : * conf Grub to 1024x768
18:31:33 Machine update : * doUpgrade
18:31:33 Stopping 'apt-daily.service', but its triggering units are still active:
18:31:33 apt-daily.timer
18:31:33 Disabling 'apt-daily.service', but its triggering units are still active:
18:31:33 apt-daily.timer
18:31:33 The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
18:31:33 Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
18:31:33 template units). This means they are not meant to be enabled or disabled using systemctl.
18:31:33 Possible reasons for having these kinds of units are:
18:31:33 • A unit may be statically enabled by being symlinked from another unit's
18:31:33 .wants/, .requires/, or .upholds/ directory.
18:31:33 • A unit's purpose may be to act as a helper for some other unit which has
18:31:33 a requirement dependency on it.
18:31:33 • A unit may be started when needed via activation (socket, path, timer,
18:31:33 D-Bus, udev, scripted systemctl call, ...).
18:31:33 • In case of template units, the unit is meant to be enabled with some
18:31:33 instance name specified.
18:31:33 * cat /etc/apt/sources.list
18:31:33 deb http://ftp.fr.debian.org/debian/ trixie main non-free-firmware
18:31:33 deb-src http://ftp.fr.debian.org/debian/ trixie main non-free-firmware
18:31:33 deb http://security.debian.org/debian-security trixie-security main non-free-firmware
18:31:33 deb-src http://security.debian.org/debian-security trixie-security main non-free-firmware
18:31:33 deb http://ftp.fr.debian.org/debian/ trixie-updates main non-free-firmware
18:31:33 deb-src http://ftp.fr.debian.org/debian/ trixie-updates main non-free-firmware
18:31:33 Machine update : * waitAptStopped
18:31:43 10, lock :
18:31:43 Ok, Stop
18:31:43 Machine update : * doAptGetWithRetry with retry : update
18:31:43 * --------------------------------------------------------------------
18:31:43 * doAptGet update (0)
18:31:43 Atteint : 1 http://security.debian.org/debian-security trixie-security InRelease
18:31:43 Atteint : 2 http://ftp.fr.debian.org/debian trixie InRelease
18:31:43 Atteint : 3 http://ftp.fr.debian.org/debian trixie-updates InRelease
18:31:43 Lecture des listes de paquets…
18:31:43 * doAptGet update --> 0
18:31:43 * --------------------------------------------------------------------
18:31:43 Ok, Stop
18:31:43 Machine update : * doAptGetWithRetry with retry : -y --force-yes upgrade
18:31:43 * --------------------------------------------------------------------
18:31:43 * doAptGet -y --force-yes upgrade (0)
18:31:43 Lecture des listes de paquets…
18:31:43 Construction de l'arbre des dépendances…
18:31:43 Lecture des informations d'état…
18:31:43 Calcul de la mise à jour…
18:31:48 AUTOMATE : detect 'mise à jour,' => 0
18:31:48 AUTOMATE : detect 'nouvellement installés,' => 0
18:31:48 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
18:31:48 W: --force-yes est obsolète, veuillez plutôt utiliser l'une des options commençant par --allow.
18:31:48 * doAptGet -y --force-yes upgrade --> 0
18:31:48 * --------------------------------------------------------------------
18:31:48 Ok, Stop
18:31:48 Machine update : * doAptGetWithRetry with retry : -y --force-yes dist-upgrade
18:31:48 * --------------------------------------------------------------------
18:31:48 * doAptGet -y --force-yes dist-upgrade (0)
18:31:48 Lecture des listes de paquets…
18:31:48 Construction de l'arbre des dépendances…
18:31:48 Lecture des informations d'état…
18:31:48 Calcul de la mise à jour…
18:31:48 AUTOMATE : detect 'mise à jour,' => 0
18:31:48 AUTOMATE : detect 'nouvellement installés,' => 0
18:31:48 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
18:31:48 W: --force-yes est obsolète, veuillez plutôt utiliser l'une des options commençant par --allow.
18:31:48 * doAptGet -y --force-yes dist-upgrade --> 0
18:31:48 * --------------------------------------------------------------------
18:31:48 Ok, Stop
18:31:48 ** doAptGet -y --purge autoremove
18:31:48 * --------------------------------------------------------------------
18:31:48 * doAptGet -y --purge autoremove (0)
18:31:48 Lecture des listes de paquets…
18:31:48 Construction de l'arbre des dépendances…
18:31:48 Lecture des informations d'état…
18:31:48 AUTOMATE : detect 'mise à jour,' => 0
18:31:48 AUTOMATE : detect 'nouvellement installés,' => 0
18:31:48 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
18:31:48 * doAptGet -y --purge autoremove --> 0
18:31:48 * --------------------------------------------------------------------
18:31:48 Machine update : * removeServicesGenant
18:31:48 * --------------------------------------------------------------------
18:31:48 * doAptGet remove -y ufw (1)
18:31:48 Lecture des listes de paquets…
18:31:48 Construction de l'arbre des dépendances…
18:31:48 Lecture des informations d'état…
18:31:48 Le paquet « ufw » n'est pas installé, et ne peut donc être supprimé
18:31:48 AUTOMATE : detect 'mise à jour,' => 0
18:31:48 AUTOMATE : detect 'nouvellement installés,' => 0
18:31:48 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
18:31:48 * doAptGet remove -y ufw --> 0
18:31:48 * --------------------------------------------------------------------
18:31:48 * --------------------------------------------------------------------
18:31:48 * doAptGet remove -y unattended-upgrades (1)
18:31:48 Lecture des listes de paquets…
18:31:48 Construction de l'arbre des dépendances…
18:31:48 Lecture des informations d'état…
18:31:48 Le paquet « unattended-upgrades » n'est pas installé, et ne peut donc être supprimé
18:31:48 AUTOMATE : detect 'mise à jour,' => 0
18:31:48 AUTOMATE : detect 'nouvellement installés,' => 0
18:31:48 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
18:31:48 * doAptGet remove -y unattended-upgrades --> 0
18:31:48 * --------------------------------------------------------------------
18:31:48 * --------------------------------------------------------------------
18:31:48 * doAptGet remove -y linux-kvm (2)
18:31:48 Lecture des listes de paquets…
18:31:48 Construction de l'arbre des dépendances…
18:31:48 Lecture des informations d'état…
18:31:48 E: Impossible de trouver le paquet linux-kvm
18:31:48 * doAptGet remove -y linux-kvm --> 100
18:31:48 * --------------------------------------------------------------------
18:31:48 * --------------------------------------------------------------------
18:31:48 * doAptGet remove -y cloud-init (2)
18:31:48 Lecture des listes de paquets…
18:31:48 Construction de l'arbre des dépendances…
18:31:48 Lecture des informations d'état…
18:31:48 Le paquet « cloud-init » n'est pas installé, et ne peut donc être supprimé
18:31:48 AUTOMATE : detect 'mise à jour,' => 0
18:31:48 AUTOMATE : detect 'nouvellement installés,' => 0
18:31:48 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
18:31:48 * doAptGet remove -y cloud-init --> 0
18:31:48 * --------------------------------------------------------------------
18:31:48 * --------------------------------------------------------------------
18:31:48 * doAptGet -y --purge autoremove (3)
18:31:48 Lecture des listes de paquets…
18:31:48 Construction de l'arbre des dépendances…
18:31:48 Lecture des informations d'état…
18:31:48 AUTOMATE : detect 'mise à jour,' => 0
18:31:48 AUTOMATE : detect 'nouvellement installés,' => 0
18:31:48 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
18:31:48 * doAptGet -y --purge autoremove --> 0
18:31:48 * --------------------------------------------------------------------
18:31:48 Disabling 'apt-daily.service', but its triggering units are still active:
18:31:48 apt-daily.timer
18:31:48 The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
18:31:48 Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
18:31:48 template units). This means they are not meant to be enabled or disabled using systemctl.
18:31:48 Possible reasons for having these kinds of units are:
18:31:48 • A unit may be statically enabled by being symlinked from another unit's
18:31:48 .wants/, .requires/, or .upholds/ directory.
18:31:48 • A unit's purpose may be to act as a helper for some other unit which has
18:31:48 a requirement dependency on it.
18:31:48 • A unit may be started when needed via activation (socket, path, timer,
18:31:48 D-Bus, udev, scripted systemctl call, ...).
18:31:48 • In case of template units, the unit is meant to be enabled with some
18:31:48 instance name specified.
18:31:48 Disabling 'apt-daily-upgrade.service', but its triggering units are still active:
18:31:48 apt-daily-upgrade.timer
18:31:48 The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
18:31:48 Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
18:31:48 template units). This means they are not meant to be enabled or disabled using systemctl.
18:31:48 Possible reasons for having these kinds of units are:
18:31:48 • A unit may be statically enabled by being symlinked from another unit's
18:31:48 .wants/, .requires/, or .upholds/ directory.
18:31:48 • A unit's purpose may be to act as a helper for some other unit which has
18:31:48 a requirement dependency on it.
18:31:48 • A unit may be started when needed via activation (socket, path, timer,
18:31:48 D-Bus, udev, scripted systemctl call, ...).
18:31:48 • In case of template units, the unit is meant to be enabled with some
18:31:48 instance name specified.
18:31:48 Impose ubuntu pour 127.0.1.1
18:31:48 Machine update : * sshAccesRoot
18:31:48 #PermitRootLogin prohibit-password
18:31:48 # the setting of "PermitRootLogin prohibit-password".
18:31:48 Machine update : * AllowAgentForwarding
18:32:03 Before poweroff EoleCommandImageExterne
18:32:03 Before poweroff
18:32:03 Creation debian-13-amd64-eole-ci-tests.daily
18:32:03 Création image (avec renommage si besoin) debian-13-amd64-eole-ci-tests.daily depuis debian-13-amd64-eole-ci-tests.fi
18:32:03 Deffered ==> Poweroff + disksaveas + delete
18:32:03 poweroff VM debian-13-amd64-eole-ci-tests.daily state=ACTIVE/RUNNING timeout=360
18:32:13 Attente Etat 'POWEROFF/LCM_INIT' (360) : . ==> Ok, Duree=0s
18:32:23 Attente Etat 'POWEROFF/LCM_INIT' (1440) : . ==> Ok, Duree=0s
18:32:23 Suppresion VM : debian-13-amd64-eole-ci-tests.daily 1632598
18:32:33 Attente Etat 'DONE/LCM_INIT' (50) : . ==> Ok, Duree=0s
18:32:33 Création image debian-13-amd64-eole-ci-tests.daily-1632598(201577) : OK
18:32:33 Fin Création image (avec renommage si besoin) debian-13-amd64-eole-ci-tests.daily depuis debian-13-amd64-eole-ci-tests.fi Duree=30s
18:32:33 Publication debian-13-amd64-eole-ci-tests.daily
18:32:33 Change droit image 'debian-13-amd64-eole-ci-tests.daily' pour eole
18:32:33 Change les droits du template : PUBLIQUE
18:32:33 deleteVirtFsDirectory : /mnt/eole-ci-tests/output/jenkins/1632598 false
18:32:33 Création debian-13-amd64-eole-ci-tests.daily terminée : OK
18:32:33 Suppresion VM : debian-13-amd64-eole-ci-tests.daily 1632598
18:32:33 Fin Daily : /mnt/eole-ci-tests/scripts/update-non-eole.sh 'debian-13-amd64-eole-ci-tests.daily' 'debian-13-amd64-eole-ci-tests.fi' Duree=140s
18:32:33 Création image terminée : OK
18:32:33Fin Génération debian-13-amd64-eole-ci-tests.daily Duree=140s
18:32:33Fin ok à 2025/12/18 17:32:33
18:32:33nettoyage : /home/jenkins/workspace/infra/fiii-debian-13-amd64-eole-ci-tests.daily/1
18:32:33Archiving artifacts
18:32:33Aucun artefact ne correspond au pattern "ws/**". Erreur de configuration?
18:32:33Started calculate disk usage of build
18:32:33Finished Calculation of disk usage of build in 0 seconds
18:32:33Started calculate disk usage of workspace
18:32:33Finished Calculation of disk usage of workspace in 0 seconds
18:32:33Finished: SUCCESS
