Tâche #29745
Scénario #29652: Traitement express MEN (10-12)
Erreurs apparmor au démarrage du conteneur addc en 2.8.0
100%
Description
Comme dans le test Jenkins, le démarrage a du mal
Conteneur addc en cours de démarrage : degraded
Voila ce que l'on peut trouver dans /var/log/syslog :
Mar 18 14:36:40 eole systemd-udevd[22282]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Mar 18 14:36:40 eole networkd-dispatcher[764]: WARNING:Unknown index 7 seen, reloading interface list Mar 18 14:36:40 eole systemd-udevd[22282]: Using default interface naming scheme 'v243'. Mar 18 14:36:40 eole systemd-udevd[22282]: vethYJY76U: Could not generate persistent MAC: No data available Mar 18 14:36:40 eole systemd-networkd[1151]: addc_0: rtnl: received neighbor message with invalid family, ignoring. Mar 18 14:36:40 eole systemd-networkd[1151]: addc_0: rtnl: received neighbor message with invalid family, ignoring. Mar 18 14:36:40 eole systemd-networkd[1151]: addc_0: Link UP Mar 18 14:36:40 eole systemd-udevd[22274]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Mar 18 14:36:40 eole systemd-udevd[22274]: Using default interface naming scheme 'v243'. Mar 18 14:36:40 eole systemd-udevd[22280]: mcAFBZAM: Process 'vlan-network-interface UDEV' failed with exit code 1. Mar 18 14:36:40 eole systemd-udevd[22282]: vethYJY76U: Process 'vlan-network-interface UDEV' failed with exit code 1. Mar 18 14:36:40 eole systemd-udevd[22274]: addc_0: Process 'vlan-network-interface UDEV' failed with exit code 1. Mar 18 14:36:41 eole kernel: [ 696.860134] eth0: renamed from mcAFBZAM Mar 18 14:36:41 eole kernel: [ 696.880261] containers: renamed from vethYJY76U Mar 18 14:36:41 eole kernel: [ 696.897217] IPv6: ADDRCONF(NETDEV_CHANGE): addc_0: link becomes ready Mar 18 14:36:41 eole kernel: [ 696.897281] br0: port 1(addc_0) entered blocking state Mar 18 14:36:41 eole kernel: [ 696.897284] br0: port 1(addc_0) entered forwarding state Mar 18 14:36:41 eole kernel: [ 696.897536] IPv6: ADDRCONF(NETDEV_CHANGE): br0: link becomes ready Mar 18 14:36:41 eole kernel: [ 696.898036] audit: type=1400 audit(1584542201.055:61): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/usr/bin/lxc-start" name="/proc/sys/kernel/random/boot_id" pid=22350 comm="lxc-start" srcname="/dev/.lxc-boot-id" flags="rw, bind" Mar 18 14:36:41 eole systemd-networkd[1151]: addc_0: Gained carrier Mar 18 14:36:41 eole systemd-networkd[1151]: br0: Gained carrier Mar 18 14:36:41 eole systemd-networkd[1151]: br0: Gained IPv6LL Mar 18 14:36:41 eole networkd-dispatcher[22388]: openssh-server: AdministrativeState is 'unmanaged', exit Mar 18 14:36:41 eole kernel: [ 697.748750] audit: type=1400 audit(1584542201.907:62): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=22446 comm="(resolved)" flags="rw, rslave" Mar 18 14:36:41 eole kernel: [ 697.820815] audit: type=1400 audit(1584542201.979:63): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=22454 comm="(modprobe)" flags="rw, rslave" Mar 18 14:36:42 eole systemd-networkd[1151]: addc_0: Gained IPv6LL
Associated revisions
addc: “ubuntu-advantage-pro” package is not working at first start
This package is useless for us, just remove it.
- scripts/eolead: remove the “ubuntu-advantage-pro”
Ref: #29745
History
#1 Updated by Daniel Dehennin over 3 years ago
- Status changed from Nouveau to Résolu
- Assigned To set to Daniel Dehennin
#2 Updated by Daniel Dehennin over 3 years ago
- Status changed from Résolu to En cours
#3 Updated by Daniel Dehennin over 3 years ago
Le système est vue comme dégradé car le service ua-auto-attach.service
ne démarre pas correctement (et c’est le seul dans ce cas).
Ce service est fourni par le paquet ubuntu-advantage-pro
dont nous n’avons que faire.
Je propose donc de le supprimer juste après la création du conteneur.
#4 Updated by Daniel Dehennin over 3 years ago
- Status changed from En cours to Résolu
- % Done changed from 0 to 100
Les messages apparmor
n’étaient pas la cause du problème de démarrage du conteneur.
Le test jenkins test-instance-acascribe-2.8.0-amd64
est en erreur pour une autre raison maintenant (il faudrait peut-être désactiver l’ead3 en 2.8 pour l’instant).
#5 Updated by Joël Cuissinat over 3 years ago
- Status changed from Résolu to Fermé
- Remaining (hours) set to 0.0
OK