Scénario #29489
Faire fonctionner bind9 (Amon) sur EOLE 2.8.0
Status:
Terminé (Sprint)
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
03/03/2020
Due date:
03/20/2020
% Done:
100%
Story points:
4.0
Remaining (hours):
0.00 hour
Velocity based estimate:
Release:
Release relationship:
Auto
Description
https://dev-eole.ac-dijon.fr/jenkins/job/2.8.0/job/test-instance-etb1amon-2.8.0-amd64/5/console
root@amon:~# /usr/share/eole/posttemplate/00-dns cp: impossible d'évaluer '/etc/bind/db.root': Aucun fichier ou dossier de ce type
root@amon:~# service bind9 status
● bind9.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/bind9.service.d
└─override.conf
Active: failed (Result: exit-code) since Tue 2020-01-21 16:13:34 CET; 8min ago
Docs: man:named(8)
Process: 12352 ExecStart=/usr/sbin/named -u bind (code=exited, status=1/FAILURE)
janv. 21 16:13:34 amon named[12360]: listening on IPv4 interface vlan21, 10.1.21.1#53
janv. 21 16:13:34 amon named[12360]: listening on IPv4 interface vlan22, 10.1.22.1#53
janv. 21 16:13:34 amon named[12360]: generating session key for dynamic DNS
janv. 21 16:13:34 amon named[12360]: sizing zone task pool based on 150 zones
janv. 21 16:13:34 amon named[12360]: could not configure root hints from 'db.cache': file not found
janv. 21 16:13:34 amon named[12360]: loading configuration: file not found
janv. 21 16:13:34 amon named[12360]: exiting (due to fatal error)
janv. 21 16:13:34 amon systemd[1]: bind9.service: Control process exited, code=exited, status=1/FAILURE
janv. 21 16:13:34 amon systemd[1]: bind9.service: Failed with result 'exit-code'.
janv. 21 16:13:34 amon systemd[1]: Failed to start BIND Domain Name Server.
Solutions à mettre en œuvre¶
- Mettre à niveau la configuration de bind9 et/ou nos scripts pour obtenir une solution fonctionnelle
Critères d'acceptation¶
- Le démarrage du service bind9 est OK dans https://dev-eole.ac-dijon.fr/jenkins/job/2.8.0/job/test-instance-etb1amon-2.8.0-amd64/
- Le test squash AM-T06-001 - BIND est passant
Subtasks
Related issues
History
#1 Updated by Joël Cuissinat over 3 years ago
- Subject changed from Faire fonctionner bind9 sur EOLE 2.8.0 to Faire fonctionner bind9 (Amon) sur EOLE 2.8.0
- Description updated (diff)
#2 Updated by Joël Cuissinat over 3 years ago
- Parent task deleted (
#29463)
#3 Updated by Joël Cuissinat over 3 years ago
- Tracker changed from Tâche to Scénario
- Target version deleted (
sprint 2020 04-06 Equipe MENSR) - Start date deleted (
01/21/2020) - Release set to EOLE 2.8.0
- Story points set to 4.0
#4 Updated by Joël Cuissinat over 3 years ago
- Project changed from Distribution EOLE to eole-dns
- Description updated (diff)
#5 Updated by Joël Cuissinat over 3 years ago
- Due date set to 03/20/2020
- Target version set to Prestation Cadoles MEN 10-12
- Start date set to 03/02/2020
#6 Updated by Joël Cuissinat over 3 years ago
- Description updated (diff)
#7 Updated by Joël Cuissinat over 3 years ago
- Related to Tâche #29718: Validation du scénario : Faire fonctionner bind9 (Amon) sur EOLE 2.8.0 added
#8 Updated by Joël Cuissinat over 3 years ago
- Assigned To set to Emmanuel GARETTE
#9 Updated by Joël Cuissinat over 3 years ago
- Test squash exécuté avec succès : https://dev-eole.ac-dijon.fr/squash/executions/10191
- Test Jenkins OK : https://dev-eole.ac-dijon.fr/jenkins/job/2.8.0/job/test-instance-etb1amon-2.8.0-amd64/ (job 19)
Service bind9 is running [ OK ]
*** DNS local . DNS 127.0.0.1 => Ok
#10 Updated by Joël Cuissinat over 3 years ago
- Status changed from Nouveau to Terminé (Sprint)