Tâche #27315
Scénario #27100: Traitement express MEN (13-15)
L'instanciation du module Seth 2.6.1 échoue lors des tests "enregistrement Zéphir"
Start date:
03/18/2019
Due date:
% Done:
0%
Remaining (hours):
0.0
Description
Cela se termine toujours en timeout (indépendamment de la version du Zéphir) :
- http://jenkins.eole.lan/jenkins/job/2.6.1/job/test-zephir-enregistrement-aca-261-2.6.1-amd64/buildTimeTrend
- http://jenkins.eole.lan/jenkins/job/2.6.2/job/test-zephir-enregistrement-aca-261-2.6.2-amd64/buildTimeTrend
- http://jenkins.eole.lan/jenkins/job/2.7.0/job/test-zephir-enregistrement-aca-261-2.7.0-amd64/buildTimeTrend
- http://jenkins.eole.lan/jenkins/job/2.7.1/job/test-zephir-enregistrement-aca-261-2.7.1-amd64/buildTimeTrend
01:51:50.616 Export one principal to /var/lib/samba/eole-ad-dc.keytab 01:51:50.616 Redémarrage service 01:51:50.617 Waiting Samba 127.0.0.1:445 to be alive 01:51:50.617 Test connection kerberos/AD 01:53:23.697 Set Administrator password never expire 01:53:23.697 Expiry for user 'Administrator' disabled. 01:53:23.697 Waiting Samba 127.0.0.1:445 to be alive 02:27:58.291 MONITOR: TIMEOUT action:$TIMEOUT
Related issues
Associated revisions
lib/eole/samba4.sh : remove useless & dirty waiting loop
Ref: #27315
History
#1 Updated by Joël Cuissinat over 4 years ago
- Description updated (diff)
#2 Updated by Joël Cuissinat over 4 years ago
- Status changed from Nouveau to En cours
- Assigned To set to Joël Cuissinat
Tentative de reproduction :
- aca.zephir-2.6.1.1-AvecConf
- aca.dc1-2.6.1.1-Daily
#3 Updated by Joël Cuissinat over 4 years ago
- Related to Tâche #21064: Modifier le dico, template et le code added
#4 Updated by Joël Cuissinat over 4 years ago
Le code problématique (supprimé en 2.6.2) :
echo Waiting Samba 127.0.0.1:445 to be alive for i in `seq 600` do tcpcheck 1 127.0.0.1:445 |grep -q alive && PORT445OK=ok done if [ "$PORT445OK" != "ok" ]; then EchoRouge "Le service samba-ad-dc n'a pas démarré dans le temps imparti" exit 1 fi
Au mieux, il manque un break dans la boucle for du coup le tcpcheck est exécuté 600 fois pour rien !
Le "maître" y passe entre 3 et 7 minutes et les lames... plus que le timeout !
#5 Updated by Scrum Master over 4 years ago
- Status changed from En cours to Résolu
#6 Updated by Joël Cuissinat over 4 years ago
- Parent task changed from #26618 to #27100
#7 Updated by Laurent Flori over 4 years ago
- Status changed from Résolu to Fermé
- Remaining (hours) set to 0.0