05:30:02Démarré par le projet amont "Internes/pull-scanNodes" de numéro de build 71581005:30:02Causé à l'origine par :
05:30:02 Lancé par une alarme périodique
05:30:02Exécution en tant que SYSTEM
05:30:02Construction à distance sur gw-jenkins (daily controler) dans le répertoire de travail /home/jenkins/workspace/infra/updateii-ubuntu-24.04-server-amd64.daily
05:30:02[WS-CLEANUP] Deleting project workspace...
05:30:02[WS-CLEANUP] Deferred wipeout is used...
05:30:02[updateii-ubuntu-24.04-server-amd64.daily] $ /bin/bash -xe /tmp/jenkins8872543219985789409.sh
05:30:02+ /bin/bash /mnt/eole-ci-tests/jenkins/EoleNebula/runOneTestGG.sh -c UpdateImageIntermediaire -I ubuntu-24.04-server-amd64.daily -a amd64
05:30:04ONE_AUTH=/home/jenkins/.one/one_auth par défaut (/home/jenkins)
05:30:04ARGUMENTS = -c UpdateImageIntermediaire -I ubuntu-24.04-server-amd64.daily -a amd64 -U timer
05:30:04Début à 2026/03/28 05:30:04
05:30:04Mode AGENT
05:30:05Utilisateur authentifié : jenkins
05:30:05updateCacheImage
05:30:13doUpdateImageExistante : ubuntu-24.04-server-amd64.daily
05:30:13 TO_UPDATE_FROM_TRIGGER : ubuntu-24.04-server-amd64.daily 2026/03/14 04:58:38 deltaHeure=216
05:30:13 Change ubuntu-24.04-server-amd64.daily persistante = true
05:30:13 Génération mode persistant ubuntu-24.04-server-amd64.daily
05:30:23 Attente Etat 'ACTIVE/RUNNING' (360) : ACTIVE/BOOT ACTIVE/RUNNING ==> Ok, Duree=4s
05:30:27 Vm démarrée : ubuntu-24.04-server-amd64.daily id=1687452 on nebula82.eole.lan
05:30:39 monitorFichier 'contextualisation.log'
05:30:44 Machine update : Début ciContextualizeMachine : update,
05:30:44 Machine update : Debut ciContextualizeUpdate
05:30:44 Machine update : OS Ubuntu 24.04.4 LTS Version=24.04
05:30:44 Machine update : machine Update ==> utilise le dhcp!
05:30:44 --------------------------------------------
05:30:44 cat /etc/machine-id
05:30:44 69bd040943ed418a8bc86df843af4443
05:30:44 --------------------------------------------
05:30:44 Machine update : Inject 01-netcfg avec 'dhcp-identifier: mac'
05:30:44 Machine update : netplan generate --debug
05:30:44 Machine update : Inject /etc/resolv.conf ?
05:30:44 lrwxrwxrwx 1 root root 37 févr. 7 03:51 /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf
05:30:44 -rw-r--r-- 1 root root 1551 avril 19 2024 /etc/systemd/resolved.conf
05:30:44 -rw-r--r-- 1 systemd-resolve systemd-resolve 920 mars 28 04:30 /run/systemd/resolve/stub-resolv.conf
05:30:44 # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
05:30:44 # Do not edit.
05:30:44 #
05:30:44 # This file might be symlinked as /etc/resolv.conf. If you're looking at
05:30:44 # /etc/resolv.conf and seeing this text, you have followed the symlink.
05:30:44 #
05:30:44 # This is a dynamic resolv.conf file for connecting local clients to the
05:30:44 # internal DNS stub resolver of systemd-resolved. This file lists all
05:30:44 # configured search domains.
05:30:44 #
05:30:44 # Run "resolvectl status" to see details about the uplink DNS servers
05:30:44 # currently in use.
05:30:44 #
05:30:44 # Third party programs should typically not access this file directly, but only
05:30:44 # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
05:30:44 # different way, replace this symlink by a static file or a different symlink.
05:30:44 #
05:30:44 # See man:systemd-resolved.service(8) for details about the supported modes of
05:30:44 # operation for /etc/resolv.conf.
05:30:44 nameserver 127.0.0.53
05:30:44 options edns0 trust-ad
05:30:44 search .
05:30:44 Machine update : Fin ciContextualizeUpdate
05:30:44 Machine update : Contextualization Machine OK
05:30:44 Machine update : jenkins 1687452 update Contextualization Machine : OK
05:30:44 Machine update : Fin ciContextualizeMachine : ok à 2026-03-28 04:30:39
05:30:54 monitorFichier 'instanceAutomatique.log'
05:30:59 Machine update : Debut ciConfigurationUpdate
05:30:59 Machine update : systemctl is-active network.target : active
05:30:59 Machine update : systemctl is-active network-online.target : active
05:30:59 Machine update : systemctl is-system-running : running
05:30:59 total 8
05:30:59 -rw------- 1 root root 112 mars 28 04:30 01-netcfg.yaml
05:30:59 -rw------- 1 root root 391 avril 29 2024 50-cloud-init.yaml
05:30:59 --------------------------------------------
05:30:59 cat /etc/netplan/01-netcfg.yaml
05:30:59 network:
05:30:59 version: 2
05:30:59 renderer: networkd
05:30:59 ethernets:
05:30:59 enp4s0:
05:30:59 dhcp4: yes
05:30:59 dhcp-identifier: mac
05:30:59 --------------------------------------------
05:30:59 --------------------------------------------
05:30:59 cat /etc/netplan/50-cloud-init.yaml
05:30:59 # This file is generated from information provided by the datasource. Changes
05:30:59 # to it will not persist across an instance reboot. To disable cloud-init's
05:30:59 # network configuration capabilities, write a file
05:30:59 # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
05:30:59 # network: {config: disabled}
05:30:59 network:
05:30:59 ethernets:
05:30:59 enp2s0:
05:30:59 dhcp4: true
05:30:59 version: 2
05:30:59 --------------------------------------------
05:30:59 --------------------------------------------
05:30:59 cat /etc/systemd/resolved.conf
05:30:59 # This file is part of systemd.
05:30:59 #
05:30:59 # systemd is free software; you can redistribute it and/or modify it under the
05:30:59 # terms of the GNU Lesser General Public License as published by the Free
05:30:59 # Software Foundation; either version 2.1 of the License, or (at your option)
05:30:59 # any later version.
05:30:59 #
05:30:59 # Entries in this file show the compile time defaults. Local configuration
05:30:59 # should be created by either modifying this file (or a copy of it placed in
05:30:59 # /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in
05:30:59 # the /etc/systemd/resolved.conf.d/ directory. The latter is generally
05:30:59 # recommended. Defaults can be restored by simply deleting the main
05:30:59 # configuration file and all drop-ins located in /etc/.
05:30:59 #
05:30:59 # Use 'systemd-analyze cat-config systemd/resolved.conf' to display the full config.
05:30:59 #
05:30:59 # See resolved.conf(5) for details.
05:30:59 [Resolve]
05:30:59 # Some examples of DNS servers which may be used for DNS= and FallbackDNS=:
05:30:59 # Cloudflare: 1.1.1.1#cloudflare-dns.com 1.0.0.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 2606:4700:4700::1001#cloudflare-dns.com
05:30:59 # Google: 8.8.8.8#dns.google 8.8.4.4#dns.google 2001:4860:4860::8888#dns.google 2001:4860:4860::8844#dns.google
05:30:59 # Quad9: 9.9.9.9#dns.quad9.net 149.112.112.112#dns.quad9.net 2620:fe::fe#dns.quad9.net 2620:fe::9#dns.quad9.net
05:30:59 #DNS=
05:30:59 #FallbackDNS=
05:30:59 #Domains=
05:30:59 #DNSSEC=no
05:30:59 #DNSOverTLS=no
05:30:59 #MulticastDNS=no
05:30:59 #LLMNR=no
05:30:59 #Cache=no-negative
05:30:59 #CacheFromLocalhost=no
05:30:59 #DNSStubListener=yes
05:30:59 #DNSStubListenerExtra=
05:30:59 #ReadEtcHosts=yes
05:30:59 #ResolveUnicastSingleLabel=no
05:30:59 #StaleRetentionSec=0
05:30:59 --------------------------------------------
05:30:59 Machine update : Inject /etc/resolv.conf ?
05:30:59 lrwxrwxrwx 1 root root 37 févr. 7 03:51 /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf
05:30:59 -rw-r--r-- 1 root root 1551 avril 19 2024 /etc/systemd/resolved.conf
05:30:59 -rw-r--r-- 1 systemd-resolve systemd-resolve 929 mars 28 04:30 /run/systemd/resolve/stub-resolv.conf
05:30:59 # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
05:30:59 # Do not edit.
05:30:59 #
05:30:59 # This file might be symlinked as /etc/resolv.conf. If you're looking at
05:30:59 # /etc/resolv.conf and seeing this text, you have followed the symlink.
05:30:59 #
05:30:59 # This is a dynamic resolv.conf file for connecting local clients to the
05:30:59 # internal DNS stub resolver of systemd-resolved. This file lists all
05:30:59 # configured search domains.
05:30:59 #
05:30:59 # Run "resolvectl status" to see details about the uplink DNS servers
05:30:59 # currently in use.
05:30:59 #
05:30:59 # Third party programs should typically not access this file directly, but only
05:30:59 # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
05:30:59 # different way, replace this symlink by a static file or a different symlink.
05:30:59 #
05:30:59 # See man:systemd-resolved.service(8) for details about the supported modes of
05:30:59 # operation for /etc/resolv.conf.
05:30:59 nameserver 127.0.0.53
05:30:59 options edns0 trust-ad
05:30:59 search ac-test.fr
05:30:59 ** ip addr
05:30:59 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
05:30:59 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
05:30:59 inet 127.0.0.1/8 scope host lo
05:30:59 valid_lft forever preferred_lft forever
05:30:59 inet6 ::1/128 scope host noprefixroute
05:30:59 valid_lft forever preferred_lft forever
05:30:59 2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
05:30:59 link/ether 02:00:c0:a8:00:67 brd ff:ff:ff:ff:ff:ff
05:30:59 inet 192.168.0.153/24 metric 100 brd 192.168.0.255 scope global dynamic enp4s0
05:30:59 valid_lft 7198sec preferred_lft 7198sec
05:30:59 inet6 fe80::c0ff:fea8:67/64 scope link
05:30:59 valid_lft forever preferred_lft forever
05:30:59 ** ip route
05:30:59 default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.153 metric 100
05:30:59 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.153 metric 100
05:30:59 192.168.0.1 dev enp4s0 proto dhcp scope link src 192.168.0.153 metric 100
05:30:59 192.168.232.2 via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.153 metric 100
05:30:59 GW actuelle : 192.168.0.1 OK
05:30:59 ** Test GW
05:30:59 Machine update : ciPingHost enp4s0 => 192.168.0.1 ping=0 ==> OK (exit 0)
05:30:59 Machine update : Fin ciConfigurationUpdate
05:30:59 Command d'update : /mnt/eole-ci-tests/scripts/update-non-eole.sh ubuntu-24.04-server-amd64.daily ubuntu-24.04-server-amd64.daily
05:31:19 CheckUpdate.sh: /root/mount.eole-ci-tests A JOUR
05:31:19 CheckUpdate.sh: /root/getVMContext.sh A JOUR
05:31:19 CheckUpdate.sh: /root/EoleCiFunctions.sh A JOUR
05:31:19 CheckUpdate.sh: /root/.EoleCiTestsContext.sh A JOUR
05:31:19 CheckUpdate.sh: /root/.EoleCiTestsDaemon.sh A JOUR
05:31:19 FRESHINSTALL_IMAGE=ubuntu-24.04-server-amd64.fi
05:31:19 DAILY_IMAGE=
05:31:19 IMAGE_SOURCE=ubuntu-24.04-server-amd64.daily
05:31:19 IMAGE_FINALE=ubuntu-24.04-server-amd64.daily
05:31:19 ** ciCheckInterface0Up
05:31:19 Machine update : Inject /etc/resolv.conf ?
05:31:19 lrwxrwxrwx 1 root root 37 févr. 7 03:51 /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf
05:31:19 -rw-r--r-- 1 root root 1551 avril 19 2024 /etc/systemd/resolved.conf
05:31:19 -rw-r--r-- 1 systemd-resolve systemd-resolve 929 mars 28 04:30 /run/systemd/resolve/stub-resolv.conf
05:31:19 # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
05:31:19 # Do not edit.
05:31:19 #
05:31:19 # This file might be symlinked as /etc/resolv.conf. If you're looking at
05:31:19 # /etc/resolv.conf and seeing this text, you have followed the symlink.
05:31:19 #
05:31:19 # This is a dynamic resolv.conf file for connecting local clients to the
05:31:19 # internal DNS stub resolver of systemd-resolved. This file lists all
05:31:19 # configured search domains.
05:31:19 #
05:31:19 # Run "resolvectl status" to see details about the uplink DNS servers
05:31:19 # currently in use.
05:31:19 #
05:31:19 # Third party programs should typically not access this file directly, but only
05:31:19 # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
05:31:19 # different way, replace this symlink by a static file or a different symlink.
05:31:19 #
05:31:19 # See man:systemd-resolved.service(8) for details about the supported modes of
05:31:19 # operation for /etc/resolv.conf.
05:31:19 nameserver 127.0.0.53
05:31:19 options edns0 trust-ad
05:31:19 search ac-test.fr
05:31:19 Machine update : * doUbuntu
05:31:19 Machine update : * waitAptStopped
05:31:29 10, lock :
05:31:29 Ok, Stop
05:31:29 Machine update : * removeServicesGenant
05:31:29 * --------------------------------------------------------------------
05:31:29 * doAptGet remove -y ufw (10)
05:31:29 Lecture des listes de paquets…
05:31:29 Construction de l'arbre des dépendances…
05:31:29 Lecture des informations d'état…
05:31:29 Le paquet « ufw » n'est pas installé, et ne peut donc être supprimé
05:31:29 AUTOMATE : detect 'mise à jour,' => 0
05:31:29 AUTOMATE : detect 'nouvellement installés,' => 0
05:31:29 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
05:31:29 * doAptGet remove -y ufw --> 0
05:31:29 * --------------------------------------------------------------------
05:31:29 * --------------------------------------------------------------------
05:31:29 * doAptGet remove -y unattended-upgrades (11)
05:31:29 Lecture des listes de paquets…
05:31:29 Construction de l'arbre des dépendances…
05:31:29 Lecture des informations d'état…
05:31:29 Le paquet « unattended-upgrades » n'est pas installé, et ne peut donc être supprimé
05:31:29 AUTOMATE : detect 'mise à jour,' => 0
05:31:29 AUTOMATE : detect 'nouvellement installés,' => 0
05:31:29 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
05:31:29 * doAptGet remove -y unattended-upgrades --> 0
05:31:29 * --------------------------------------------------------------------
05:31:29 * --------------------------------------------------------------------
05:31:29 * doAptGet remove -y linux-kvm (11)
05:31:29 Lecture des listes de paquets…
05:31:29 Construction de l'arbre des dépendances…
05:31:29 Lecture des informations d'état…
05:31:29 Le paquet « linux-kvm » n'est pas installé, et ne peut donc être supprimé
05:31:29 AUTOMATE : detect 'mise à jour,' => 0
05:31:29 AUTOMATE : detect 'nouvellement installés,' => 0
05:31:29 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
05:31:29 * doAptGet remove -y linux-kvm --> 0
05:31:29 * --------------------------------------------------------------------
05:31:29 * --------------------------------------------------------------------
05:31:29 * doAptGet remove -y cloud-init (12)
05:31:29 Lecture des listes de paquets…
05:31:29 Construction de l'arbre des dépendances…
05:31:29 Lecture des informations d'état…
05:31:34 Le paquet « cloud-init » n'est pas installé, et ne peut donc être supprimé
05:31:34 AUTOMATE : detect 'mise à jour,' => 0
05:31:34 AUTOMATE : detect 'nouvellement installés,' => 0
05:31:34 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
05:31:34 * doAptGet remove -y cloud-init --> 0
05:31:34 * --------------------------------------------------------------------
05:31:34 * --------------------------------------------------------------------
05:31:34 * doAptGet -y --purge autoremove (12)
05:31:34 Lecture des listes de paquets…
05:31:34 Construction de l'arbre des dépendances…
05:31:34 Lecture des informations d'état…
05:31:34 AUTOMATE : detect 'mise à jour,' => 0
05:31:34 AUTOMATE : detect 'nouvellement installés,' => 0
05:31:34 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
05:31:34 * doAptGet -y --purge autoremove --> 0
05:31:34 * --------------------------------------------------------------------
05:31:34 The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
05:31:34 Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
05:31:34 template units). This means they are not meant to be enabled or disabled using systemctl.
05:31:34 Possible reasons for having these kinds of units are:
05:31:34 • A unit may be statically enabled by being symlinked from another unit's
05:31:34 .wants/, .requires/, or .upholds/ directory.
05:31:34 • A unit's purpose may be to act as a helper for some other unit which has
05:31:34 a requirement dependency on it.
05:31:34 • A unit may be started when needed via activation (socket, path, timer,
05:31:34 D-Bus, udev, scripted systemctl call, ...).
05:31:34 • In case of template units, the unit is meant to be enabled with some
05:31:34 instance name specified.
05:31:34 The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
05:31:34 Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
05:31:34 template units). This means they are not meant to be enabled or disabled using systemctl.
05:31:34 Possible reasons for having these kinds of units are:
05:31:34 • A unit may be statically enabled by being symlinked from another unit's
05:31:34 .wants/, .requires/, or .upholds/ directory.
05:31:34 • A unit's purpose may be to act as a helper for some other unit which has
05:31:34 a requirement dependency on it.
05:31:34 • A unit may be started when needed via activation (socket, path, timer,
05:31:34 D-Bus, udev, scripted systemctl call, ...).
05:31:34 • In case of template units, the unit is meant to be enabled with some
05:31:34 instance name specified.
05:31:34 /usr/sbin/dhclient
05:31:34 Machine update : * conf Grub to 1024x768
05:31:34 Machine update : * doUpgrade
05:31:34 The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
05:31:34 Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
05:31:34 template units). This means they are not meant to be enabled or disabled using systemctl.
05:31:34 Possible reasons for having these kinds of units are:
05:31:34 • A unit may be statically enabled by being symlinked from another unit's
05:31:34 .wants/, .requires/, or .upholds/ directory.
05:31:34 • A unit's purpose may be to act as a helper for some other unit which has
05:31:34 a requirement dependency on it.
05:31:34 • A unit may be started when needed via activation (socket, path, timer,
05:31:34 D-Bus, udev, scripted systemctl call, ...).
05:31:34 • In case of template units, the unit is meant to be enabled with some
05:31:34 instance name specified.
05:31:34 * cat /etc/apt/sources.list
05:31:34 Machine update : * waitAptStopped
05:31:44 10, lock :
05:31:44 Ok, Stop
05:31:44 Machine update : * doAptGetWithRetry with retry : update
05:31:44 * --------------------------------------------------------------------
05:31:44 * doAptGet update (0)
05:31:44 Atteint :1 http://fr.archive.ubuntu.com/ubuntu noble InRelease
05:31:44 Réception de :2 http://fr.archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB]
05:31:44 Réception de :3 http://security.ubuntu.com/ubuntu noble-security InRelease [126 kB]
05:31:44 Réception de :4 http://fr.archive.ubuntu.com/ubuntu noble-backports InRelease [126 kB]
05:31:44 Réception de :5 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages [1 846 kB]
05:31:44 Réception de :6 http://fr.archive.ubuntu.com/ubuntu noble-updates/main Translation-en [339 kB]
05:31:44 Réception de :7 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 Components [177 kB]
05:31:44 Réception de :8 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 c-n-f Metadata [16,9 kB]
05:31:44 Réception de :9 http://fr.archive.ubuntu.com/ubuntu noble-updates/restricted amd64 Packages [2 837 kB]
05:31:44 Réception de :10 http://fr.archive.ubuntu.com/ubuntu noble-updates/restricted Translation-en [656 kB]
05:31:44 Réception de :11 http://fr.archive.ubuntu.com/ubuntu noble-updates/restricted amd64 Components [212 B]
05:31:44 Réception de :12 http://fr.archive.ubuntu.com/ubuntu noble-updates/universe amd64 Packages [1 666 kB]
05:31:44 Réception de :13 http://fr.archive.ubuntu.com/ubuntu noble-updates/universe Translation-en [323 kB]
05:31:44 Réception de :14 http://fr.archive.ubuntu.com/ubuntu noble-updates/universe amd64 Components [386 kB]
05:31:44 Réception de :15 http://fr.archive.ubuntu.com/ubuntu noble-updates/universe amd64 c-n-f Metadata [34,2 kB]
05:31:44 Réception de :16 http://fr.archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 Packages [32,1 kB]
05:31:44 Réception de :17 http://fr.archive.ubuntu.com/ubuntu noble-updates/multiverse Translation-en [7 520 B]
05:31:44 Réception de :18 http://fr.archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 Components [940 B]
05:31:44 Réception de :19 http://fr.archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 c-n-f Metadata [500 B]
05:31:44 Réception de :20 http://fr.archive.ubuntu.com/ubuntu noble-backports/main amd64 Packages [40,4 kB]
05:31:44 Réception de :21 http://fr.archive.ubuntu.com/ubuntu noble-backports/main amd64 Components [7 368 B]
05:31:44 Réception de :22 http://fr.archive.ubuntu.com/ubuntu noble-backports/restricted amd64 Components [216 B]
05:31:44 Réception de :23 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages [1 551 kB]
05:31:44 Réception de :24 http://fr.archive.ubuntu.com/ubuntu noble-backports/universe amd64 Packages [30,7 kB]
05:31:44 Réception de :25 http://fr.archive.ubuntu.com/ubuntu noble-backports/universe Translation-en [18,2 kB]
05:31:44 Réception de :26 http://fr.archive.ubuntu.com/ubuntu noble-backports/universe amd64 Components [13,2 kB]
05:31:44 Réception de :27 http://fr.archive.ubuntu.com/ubuntu noble-backports/universe amd64 c-n-f Metadata [1 480 B]
05:31:44 Réception de :28 http://fr.archive.ubuntu.com/ubuntu noble-backports/multiverse amd64 Components [212 B]
05:31:44 Réception de :29 http://security.ubuntu.com/ubuntu noble-security/main Translation-en [249 kB]
05:31:44 Réception de :30 http://security.ubuntu.com/ubuntu noble-security/main amd64 Components [21,6 kB]
05:31:44 Réception de :31 http://security.ubuntu.com/ubuntu noble-security/main amd64 c-n-f Metadata [10,7 kB]
05:31:44 Réception de :32 http://security.ubuntu.com/ubuntu noble-security/restricted amd64 Packages [2 701 kB]
05:31:44 Réception de :33 http://security.ubuntu.com/ubuntu noble-security/restricted Translation-en [627 kB]
05:31:44 Réception de :34 http://security.ubuntu.com/ubuntu noble-security/restricted amd64 Components [212 B]
05:31:44 Réception de :35 http://security.ubuntu.com/ubuntu noble-security/universe amd64 Packages [1 166 kB]
05:31:44 Réception de :36 http://security.ubuntu.com/ubuntu noble-security/universe Translation-en [225 kB]
05:31:44 Réception de :37 http://security.ubuntu.com/ubuntu noble-security/universe amd64 Components [74,1 kB]
05:31:44 Réception de :38 http://security.ubuntu.com/ubuntu noble-security/universe amd64 c-n-f Metadata [22,9 kB]
05:31:44 Réception de :39 http://security.ubuntu.com/ubuntu noble-security/multiverse Translation-en [6 980 B]
05:31:44 Réception de :40 http://security.ubuntu.com/ubuntu noble-security/multiverse amd64 Components [212 B]
05:31:59 15,5 Mo réceptionnés en 3s (5 317 ko/s)
05:31:59 Lecture des listes de paquets…
05:32:04 * doAptGet update --> 0
05:32:04 * --------------------------------------------------------------------
05:32:04 Ok, Stop
05:32:04 Machine update : * doAptGetWithRetry with retry : -y --force-yes upgrade
05:32:04 * --------------------------------------------------------------------
05:32:04 * doAptGet -y --force-yes upgrade (0)
05:32:04 Lecture des listes de paquets…
05:32:04 Construction de l'arbre des dépendances…
05:32:04 Lecture des informations d'état…
05:32:04 Calcul de la mise à jour…
05:32:04 Les paquets suivants seront mis à jour :
05:32:04 bind9-dnsutils bind9-host bind9-libs coreutils libnss-systemd libpam-systemd
05:32:04 libssh-4 libsystemd-shared libsystemd0 libtiff6 libudev1
05:32:04 python3-cryptography python3-openssl snapd systemd systemd-dev
05:32:04 systemd-resolved systemd-sysv systemd-timesyncd ubuntu-drivers-common udev
05:32:04 vim vim-common vim-runtime vim-tiny xxd
05:32:04 AUTOMATE : detect 'mise à jour,' => 26
05:32:04 AUTOMATE : detect 'nouvellement installés,' => 26
05:32:04 26 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
05:32:04 Il est nécessaire de prendre 58,0 Mo dans les archives.
05:32:04 Après cette opération, 17,4 ko d'espace disque supplémentaires seront utilisés.
05:32:04 Réception de :1 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 coreutils amd64 9.4-3ubuntu6.2 [1 412 kB]
05:32:04 Réception de :2 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 libnss-systemd amd64 255.4-1ubuntu8.14 [159 kB]
05:32:04 Réception de :3 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 systemd-dev all 255.4-1ubuntu8.14 [106 kB]
05:32:04 Réception de :4 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 systemd-timesyncd amd64 255.4-1ubuntu8.14 [35,3 kB]
05:32:04 Réception de :5 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 systemd-resolved amd64 255.4-1ubuntu8.14 [296 kB]
05:32:04 Réception de :6 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 libsystemd-shared amd64 255.4-1ubuntu8.14 [2 074 kB]
05:32:04 Réception de :7 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 libsystemd0 amd64 255.4-1ubuntu8.14 [435 kB]
05:32:04 Réception de :8 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 systemd-sysv amd64 255.4-1ubuntu8.14 [11,9 kB]
05:32:04 Réception de :9 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 libpam-systemd amd64 255.4-1ubuntu8.14 [235 kB]
05:32:04 Réception de :10 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 systemd amd64 255.4-1ubuntu8.14 [3 475 kB]
05:32:04 Réception de :11 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 udev amd64 255.4-1ubuntu8.14 [1 875 kB]
05:32:04 Réception de :12 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 libudev1 amd64 255.4-1ubuntu8.14 [177 kB]
05:32:04 Réception de :13 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 ubuntu-drivers-common amd64 1:0.9.7.6ubuntu3.6 [66,1 kB]
05:32:04 Réception de :14 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 vim amd64 2:9.1.0016-1ubuntu7.10 [1 882 kB]
05:32:04 Réception de :15 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 vim-common all 2:9.1.0016-1ubuntu7.10 [387 kB]
05:32:04 Réception de :16 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 vim-tiny amd64 2:9.1.0016-1ubuntu7.10 [804 kB]
05:32:04 Réception de :17 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 vim-runtime all 2:9.1.0016-1ubuntu7.10 [7 282 kB]
05:32:04 Réception de :18 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 xxd amd64 2:9.1.0016-1ubuntu7.10 [64,3 kB]
05:32:04 Réception de :19 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 bind9-dnsutils amd64 1:9.18.39-0ubuntu0.24.04.3 [156 kB]
05:32:04 Réception de :20 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 bind9-host amd64 1:9.18.39-0ubuntu0.24.04.3 [50,5 kB]
05:32:04 Réception de :21 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 bind9-libs amd64 1:9.18.39-0ubuntu0.24.04.3 [1 257 kB]
05:32:04 Réception de :22 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 libssh-4 amd64 0.10.6-2ubuntu0.4 [190 kB]
05:32:04 Réception de :23 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 libtiff6 amd64 4.5.1+git230720-4ubuntu2.5 [200 kB]
05:32:04 Réception de :24 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 python3-cryptography amd64 41.0.7-4ubuntu0.4 [815 kB]
05:32:04 Réception de :25 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 python3-openssl all 23.2.0-1ubuntu0.1 [48,1 kB]
05:32:04 Réception de :26 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 snapd amd64 2.73+ubuntu24.04.2 [34,6 MB]
05:32:04 Préconfiguration des paquets...
05:32:04 58,0 Mo réceptionnés en 1s (87,9 Mo/s)
05:32:04 (Lecture de la base de données...
05:32:04 (Lecture de la base de données... 124262 fichiers et répertoires déjà installés.)
05:32:04 Préparation du dépaquetage de .../coreutils_9.4-3ubuntu6.2_amd64.deb ...
05:32:04 Dépaquetage de coreutils (9.4-3ubuntu6.2) sur (9.4-3ubuntu6.1) ...
05:32:04 Paramétrage de coreutils (9.4-3ubuntu6.2) ...
05:32:04 (Lecture de la base de données...
05:32:04 (Lecture de la base de données... 124262 fichiers et répertoires déjà installés.)
05:32:04 Préparation du dépaquetage de .../0-libnss-systemd_255.4-1ubuntu8.14_amd64.deb ...
05:32:04 Dépaquetage de libnss-systemd:amd64 (255.4-1ubuntu8.14) sur (255.4-1ubuntu8.12) ...
05:32:04 Préparation du dépaquetage de .../1-systemd-dev_255.4-1ubuntu8.14_all.deb ...
05:32:04 Dépaquetage de systemd-dev (255.4-1ubuntu8.14) sur (255.4-1ubuntu8.12) ...
05:32:04 Préparation du dépaquetage de .../2-systemd-timesyncd_255.4-1ubuntu8.14_amd64.deb ...
05:32:04 Dépaquetage de systemd-timesyncd (255.4-1ubuntu8.14) sur (255.4-1ubuntu8.12) ...
05:32:04 Préparation du dépaquetage de .../3-systemd-resolved_255.4-1ubuntu8.14_amd64.deb ...
05:32:04 Dépaquetage de systemd-resolved (255.4-1ubuntu8.14) sur (255.4-1ubuntu8.12) ...
05:32:04 Préparation du dépaquetage de .../4-libsystemd-shared_255.4-1ubuntu8.14_amd64.deb ...
05:32:04 Dépaquetage de libsystemd-shared:amd64 (255.4-1ubuntu8.14) sur (255.4-1ubuntu8.12) ...
05:32:04 Préparation du dépaquetage de .../5-libsystemd0_255.4-1ubuntu8.14_amd64.deb ...
05:32:04 Dépaquetage de libsystemd0:amd64 (255.4-1ubuntu8.14) sur (255.4-1ubuntu8.12) ...
05:32:04 Paramétrage de libsystemd0:amd64 (255.4-1ubuntu8.14) ...
05:32:04 (Lecture de la base de données...
05:32:04 (Lecture de la base de données... 124262 fichiers et répertoires déjà installés.)
05:32:04 Préparation du dépaquetage de .../systemd-sysv_255.4-1ubuntu8.14_amd64.deb ...
05:32:04 Dépaquetage de systemd-sysv (255.4-1ubuntu8.14) sur (255.4-1ubuntu8.12) ...
05:32:04 Préparation du dépaquetage de .../libpam-systemd_255.4-1ubuntu8.14_amd64.deb ...
05:32:04 Dépaquetage de libpam-systemd:amd64 (255.4-1ubuntu8.14) sur (255.4-1ubuntu8.12) ...
05:32:04 Préparation du dépaquetage de .../systemd_255.4-1ubuntu8.14_amd64.deb ...
05:32:04 Dépaquetage de systemd (255.4-1ubuntu8.14) sur (255.4-1ubuntu8.12) ...
05:32:04 Préparation du dépaquetage de .../udev_255.4-1ubuntu8.14_amd64.deb ...
05:32:04 Dépaquetage de udev (255.4-1ubuntu8.14) sur (255.4-1ubuntu8.12) ...
05:32:04 Préparation du dépaquetage de .../libudev1_255.4-1ubuntu8.14_amd64.deb ...
05:32:04 Dépaquetage de libudev1:amd64 (255.4-1ubuntu8.14) sur (255.4-1ubuntu8.12) ...
05:32:04 Paramétrage de libudev1:amd64 (255.4-1ubuntu8.14) ...
05:32:04 (Lecture de la base de données...
05:32:04 (Lecture de la base de données... 124262 fichiers et répertoires déjà installés.)
05:32:04 Préparation du dépaquetage de .../00-ubuntu-drivers-common_1%3a0.9.7.6ubuntu3.6_amd64.deb ...
05:32:04 Dépaquetage de ubuntu-drivers-common (1:0.9.7.6ubuntu3.6) sur (1:0.9.7.6ubuntu3.5) ...
05:32:04 Préparation du dépaquetage de .../01-vim_2%3a9.1.0016-1ubuntu7.10_amd64.deb ...
05:32:04 Dépaquetage de vim (2:9.1.0016-1ubuntu7.10) sur (2:9.1.0016-1ubuntu7.9) ...
05:32:04 Préparation du dépaquetage de .../02-vim-common_2%3a9.1.0016-1ubuntu7.10_all.deb ...
05:32:04 Dépaquetage de vim-common (2:9.1.0016-1ubuntu7.10) sur (2:9.1.0016-1ubuntu7.9) ...
05:32:04 Préparation du dépaquetage de .../03-vim-tiny_2%3a9.1.0016-1ubuntu7.10_amd64.deb ...
05:32:04 Dépaquetage de vim-tiny (2:9.1.0016-1ubuntu7.10) sur (2:9.1.0016-1ubuntu7.9) ...
05:32:04 Préparation du dépaquetage de .../04-vim-runtime_2%3a9.1.0016-1ubuntu7.10_all.deb ...
05:32:04 Dépaquetage de vim-runtime (2:9.1.0016-1ubuntu7.10) sur (2:9.1.0016-1ubuntu7.9) ...
05:32:09 Préparation du dépaquetage de .../05-xxd_2%3a9.1.0016-1ubuntu7.10_amd64.deb ...
05:32:09 Dépaquetage de xxd (2:9.1.0016-1ubuntu7.10) sur (2:9.1.0016-1ubuntu7.9) ...
05:32:09 Préparation du dépaquetage de .../06-bind9-dnsutils_1%3a9.18.39-0ubuntu0.24.04.3_amd64.deb ...
05:32:09 Dépaquetage de bind9-dnsutils (1:9.18.39-0ubuntu0.24.04.3) sur (1:9.18.39-0ubuntu0.24.04.2) ...
05:32:09 Préparation du dépaquetage de .../07-bind9-host_1%3a9.18.39-0ubuntu0.24.04.3_amd64.deb ...
05:32:09 Dépaquetage de bind9-host (1:9.18.39-0ubuntu0.24.04.3) sur (1:9.18.39-0ubuntu0.24.04.2) ...
05:32:09 Préparation du dépaquetage de .../08-bind9-libs_1%3a9.18.39-0ubuntu0.24.04.3_amd64.deb ...
05:32:09 Dépaquetage de bind9-libs:amd64 (1:9.18.39-0ubuntu0.24.04.3) sur (1:9.18.39-0ubuntu0.24.04.2) ...
05:32:09 Préparation du dépaquetage de .../09-libssh-4_0.10.6-2ubuntu0.4_amd64.deb ...
05:32:09 Dépaquetage de libssh-4:amd64 (0.10.6-2ubuntu0.4) sur (0.10.6-2ubuntu0.3) ...
05:32:09 Préparation du dépaquetage de .../10-libtiff6_4.5.1+git230720-4ubuntu2.5_amd64.deb ...
05:32:09 Dépaquetage de libtiff6:amd64 (4.5.1+git230720-4ubuntu2.5) sur (4.5.1+git230720-4ubuntu2.4) ...
05:32:09 Préparation du dépaquetage de .../11-python3-cryptography_41.0.7-4ubuntu0.4_amd64.deb ...
05:32:09 Dépaquetage de python3-cryptography (41.0.7-4ubuntu0.4) sur (41.0.7-4ubuntu0.3) ...
05:32:09 Préparation du dépaquetage de .../12-python3-openssl_23.2.0-1ubuntu0.1_all.deb ...
05:32:09 Dépaquetage de python3-openssl (23.2.0-1ubuntu0.1) sur (23.2.0-1) ...
05:32:09 Préparation du dépaquetage de .../13-snapd_2.73+ubuntu24.04.2_amd64.deb ...
05:32:09 Dépaquetage de snapd (2.73+ubuntu24.04.2) sur (2.73+ubuntu24.04) ...
05:32:09 Paramétrage de bind9-libs:amd64 (1:9.18.39-0ubuntu0.24.04.3) ...
05:32:09 Paramétrage de systemd-dev (255.4-1ubuntu8.14) ...
05:32:09 Paramétrage de xxd (2:9.1.0016-1ubuntu7.10) ...
05:32:09 Paramétrage de vim-common (2:9.1.0016-1ubuntu7.10) ...
05:32:09 Paramétrage de python3-cryptography (41.0.7-4ubuntu0.4) ...
05:32:09 Paramétrage de libsystemd-shared:amd64 (255.4-1ubuntu8.14) ...
05:32:09 Paramétrage de libssh-4:amd64 (0.10.6-2ubuntu0.4) ...
05:32:09 Paramétrage de libtiff6:amd64 (4.5.1+git230720-4ubuntu2.5) ...
05:32:09 Paramétrage de vim-runtime (2:9.1.0016-1ubuntu7.10) ...
05:32:09 Paramétrage de bind9-host (1:9.18.39-0ubuntu0.24.04.3) ...
05:32:09 Paramétrage de vim (2:9.1.0016-1ubuntu7.10) ...
05:32:09 Paramétrage de python3-openssl (23.2.0-1ubuntu0.1) ...
05:32:09 Paramétrage de systemd (255.4-1ubuntu8.14) ...
05:32:09 Paramétrage de vim-tiny (2:9.1.0016-1ubuntu7.10) ...
05:32:09 Paramétrage de systemd-timesyncd (255.4-1ubuntu8.14) ...
05:32:09 Paramétrage de udev (255.4-1ubuntu8.14) ...
05:32:14 Paramétrage de bind9-dnsutils (1:9.18.39-0ubuntu0.24.04.3) ...
05:32:14 Paramétrage de systemd-resolved (255.4-1ubuntu8.14) ...
05:32:14 Paramétrage de snapd (2.73+ubuntu24.04.2) ...
05:32:14 snapd.service is a disabled or a static unit not running, not starting it.
05:32:14 snapd.failure.service is a disabled or a static unit not running, not starting it.
05:32:14 snapd.gpio-chardev-setup.target is a disabled or a static unit not running, not starting it.
05:32:14 snapd.seeded.service is a disabled or a static unit not running, not starting it.
05:32:14 snapd.snap-repair.service is a disabled or a static unit not running, not starting it.
05:32:14 Paramétrage de systemd-sysv (255.4-1ubuntu8.14) ...
05:32:14 Paramétrage de ubuntu-drivers-common (1:0.9.7.6ubuntu3.6) ...
05:32:14 Paramétrage de libnss-systemd:amd64 (255.4-1ubuntu8.14) ...
05:32:14 Paramétrage de libpam-systemd:amd64 (255.4-1ubuntu8.14) ...
05:32:14 Traitement des actions différées (« triggers ») pour initramfs-tools (0.142ubuntu25.8) ...
05:32:14 update-initramfs: Generating /boot/initrd.img-6.8.0-106-generic
05:32:24 Traitement des actions différées (« triggers ») pour libc-bin (2.39-0ubuntu8.7) ...
05:32:24 Traitement des actions différées (« triggers ») pour man-db (2.12.0-4build2) ...
05:32:29 Traitement des actions différées (« triggers ») pour dbus (1.14.10-4ubuntu4.1) ...
05:32:29 Traitement des actions différées (« triggers ») pour install-info (7.1-3build2) ...
05:32:29 packages have been installed but needrestart is suspended
05:32:29 W: --force-yes est obsolète, veuillez plutôt utiliser l'une des options commençant par --allow.
05:32:29 * doAptGet -y --force-yes upgrade --> 0
05:32:29 * --------------------------------------------------------------------
05:32:29 Ok, Stop
05:32:29 Machine update : * doAptGetWithRetry with retry : -y --force-yes dist-upgrade
05:32:29 * --------------------------------------------------------------------
05:32:29 * doAptGet -y --force-yes dist-upgrade (0)
05:32:29 Lecture des listes de paquets…
05:32:29 Construction de l'arbre des dépendances…
05:32:29 Lecture des informations d'état…
05:32:29 Calcul de la mise à jour…
05:32:29 AUTOMATE : detect 'mise à jour,' => 26
05:32:29 AUTOMATE : detect 'nouvellement installés,' => 26
05:32:29 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
05:32:29 W: --force-yes est obsolète, veuillez plutôt utiliser l'une des options commençant par --allow.
05:32:29 * doAptGet -y --force-yes dist-upgrade --> 0
05:32:29 * --------------------------------------------------------------------
05:32:29 Ok, Stop
05:32:29 ** doAptGet -y --purge autoremove
05:32:29 * --------------------------------------------------------------------
05:32:29 * doAptGet -y --purge autoremove (1)
05:32:29 Lecture des listes de paquets…
05:32:29 Construction de l'arbre des dépendances…
05:32:29 Lecture des informations d'état…
05:32:29 AUTOMATE : detect 'mise à jour,' => 26
05:32:29 AUTOMATE : detect 'nouvellement installés,' => 26
05:32:29 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
05:32:29 * doAptGet -y --purge autoremove --> 0
05:32:29 * --------------------------------------------------------------------
05:32:29 Machine update : * removeServicesGenant
05:32:29 * --------------------------------------------------------------------
05:32:29 * doAptGet remove -y ufw (2)
05:32:29 Lecture des listes de paquets…
05:32:29 Construction de l'arbre des dépendances…
05:32:29 Lecture des informations d'état…
05:32:34 Le paquet « ufw » n'est pas installé, et ne peut donc être supprimé
05:32:34 AUTOMATE : detect 'mise à jour,' => 26
05:32:34 AUTOMATE : detect 'nouvellement installés,' => 26
05:32:34 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
05:32:34 * doAptGet remove -y ufw --> 0
05:32:34 * --------------------------------------------------------------------
05:32:34 * --------------------------------------------------------------------
05:32:34 * doAptGet remove -y unattended-upgrades (2)
05:32:34 Lecture des listes de paquets…
05:32:34 Construction de l'arbre des dépendances…
05:32:34 Lecture des informations d'état…
05:32:34 Le paquet « unattended-upgrades » n'est pas installé, et ne peut donc être supprimé
05:32:34 AUTOMATE : detect 'mise à jour,' => 26
05:32:34 AUTOMATE : detect 'nouvellement installés,' => 26
05:32:34 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
05:32:34 * doAptGet remove -y unattended-upgrades --> 0
05:32:34 * --------------------------------------------------------------------
05:32:34 * --------------------------------------------------------------------
05:32:34 * doAptGet remove -y linux-kvm (3)
05:32:34 Lecture des listes de paquets…
05:32:34 Construction de l'arbre des dépendances…
05:32:34 Lecture des informations d'état…
05:32:34 Le paquet « linux-kvm » n'est pas installé, et ne peut donc être supprimé
05:32:34 AUTOMATE : detect 'mise à jour,' => 26
05:32:34 AUTOMATE : detect 'nouvellement installés,' => 26
05:32:34 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
05:32:34 * doAptGet remove -y linux-kvm --> 0
05:32:34 * --------------------------------------------------------------------
05:32:34 * --------------------------------------------------------------------
05:32:34 * doAptGet remove -y cloud-init (3)
05:32:34 Lecture des listes de paquets…
05:32:34 Construction de l'arbre des dépendances…
05:32:34 Lecture des informations d'état…
05:32:34 Le paquet « cloud-init » n'est pas installé, et ne peut donc être supprimé
05:32:34 AUTOMATE : detect 'mise à jour,' => 26
05:32:34 AUTOMATE : detect 'nouvellement installés,' => 26
05:32:34 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
05:32:34 * doAptGet remove -y cloud-init --> 0
05:32:34 * --------------------------------------------------------------------
05:32:34 * --------------------------------------------------------------------
05:32:34 * doAptGet -y --purge autoremove (4)
05:32:34 Lecture des listes de paquets…
05:32:34 Construction de l'arbre des dépendances…
05:32:34 Lecture des informations d'état…
05:32:34 AUTOMATE : detect 'mise à jour,' => 26
05:32:34 AUTOMATE : detect 'nouvellement installés,' => 26
05:32:34 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
05:32:34 * doAptGet -y --purge autoremove --> 0
05:32:34 * --------------------------------------------------------------------
05:32:34 The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
05:32:34 Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
05:32:34 template units). This means they are not meant to be enabled or disabled using systemctl.
05:32:34 Possible reasons for having these kinds of units are:
05:32:34 • A unit may be statically enabled by being symlinked from another unit's
05:32:34 .wants/, .requires/, or .upholds/ directory.
05:32:34 • A unit's purpose may be to act as a helper for some other unit which has
05:32:34 a requirement dependency on it.
05:32:34 • A unit may be started when needed via activation (socket, path, timer,
05:32:34 D-Bus, udev, scripted systemctl call, ...).
05:32:34 • In case of template units, the unit is meant to be enabled with some
05:32:34 instance name specified.
05:32:34 The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
05:32:34 Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
05:32:34 template units). This means they are not meant to be enabled or disabled using systemctl.
05:32:34 Possible reasons for having these kinds of units are:
05:32:34 • A unit may be statically enabled by being symlinked from another unit's
05:32:34 .wants/, .requires/, or .upholds/ directory.
05:32:34 • A unit's purpose may be to act as a helper for some other unit which has
05:32:34 a requirement dependency on it.
05:32:34 • A unit may be started when needed via activation (socket, path, timer,
05:32:34 D-Bus, udev, scripted systemctl call, ...).
05:32:34 • In case of template units, the unit is meant to be enabled with some
05:32:34 instance name specified.
05:32:34 /usr/sbin/dhclient
05:32:34 Impose ubuntu pour 127.0.1.1
05:32:34 Machine update : * sshAccesRoot
05:32:34 Machine update : * AllowAgentForwarding
05:32:49 Before poweroff EoleCommandImageExterne
05:32:49 Before poweroff
05:32:49 poweroff VM ubuntu-24.04-server-amd64.daily state=ACTIVE/RUNNING timeout=360
05:32:59 Attente Etat 'POWEROFF/LCM_INIT' (360) : . ==> Ok, Duree=0s
05:32:59 Suppresion VM : ubuntu-24.04-server-amd64.daily 1687452
05:33:09 Attente Etat 'DONE/LCM_INIT' (50) : . ==> Ok, Duree=0s
05:33:10 Change ubuntu-24.04-server-amd64.daily persistante = false
05:33:10 Change droit image 'ubuntu-24.04-server-amd64.daily' pour eole
05:33:10 Change les droits du template : PUBLIQUE
05:33:10Fin doUpdateImageExistante : ubuntu-24.04-server-amd64.daily Duree=176s
05:33:10Fin ok à 2026/03/28 05:33:10
05:33:10nettoyage : /home/jenkins/workspace/infra/updateii-ubuntu-24.04-server-amd64.daily/111
05:33:10Archiving artifacts
05:33:10Aucun artefact ne correspond au pattern "ws/**". Erreur de configuration?
05:33:10Sending e-mails to: jenkins@listeseole.ac-dijon.fr
05:33:10Started calculate disk usage of build
05:33:10Finished Calculation of disk usage of build in 0 seconds
05:33:10Started calculate disk usage of workspace
05:33:10Finished Calculation of disk usage of workspace in 0 seconds
05:33:10Finished: SUCCESS
