Tâche #33236
Scénario #33183: Validation des scénario 'cadoles' (39-41)
Valider le scénario Les scripts utilisants SSH doivent exclure l’usage de l’agent
Start date:
10/04/2021
Due date:
% Done:
100%
Remaining (hours):
0.0
Related issues
History
#1 Updated by Daniel Dehennin almost 2 years ago
- Status changed from Nouveau to En cours
#2 Updated by Daniel Dehennin almost 2 years ago
- Assigned To set to Daniel Dehennin
#3 Updated by Daniel Dehennin almost 2 years ago
- Related to Scénario #31712: Les scripts utilisants SSH doivent exclure l’usage de l’agent added
#4 Updated by Daniel Dehennin almost 2 years ago
- % Done changed from 0 to 100
Le fichier /etc/ssh/ssh_config
contient :
- Sur un
aca.amonecole-2.8.1-instance-default
Host web Hostname 192.0.2.51 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host mail Hostname 192.0.2.51 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host dhcp Hostname 192.0.2.52 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host domaine Hostname 192.0.2.56 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host fichier Hostname 192.0.2.52 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host dns Hostname 192.0.2.56 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host mysql Hostname 192.0.2.50 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host postgresql Hostname 192.0.2.50 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host proxy Hostname 192.0.2.53 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host ftp Hostname 192.0.2.52 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host annuaire Hostname 192.0.2.56 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host reseau Hostname 192.0.2.51 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host jabber Hostname 192.0.2.51 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host internet Hostname 192.0.2.53 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host bdd Hostname 192.0.2.50 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host partage Hostname 192.0.2.52 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host addc Hostname 192.0.2.56 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no
- Sur un
aca.scribe-2.7.2-instance-default
etaca.scribe-2.8.0-instance-default
Host annuaire Hostname 127.0.0.1 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host mail Hostname 127.0.0.1 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host dhcp Hostname 127.0.0.1 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host fichier Hostname 127.0.0.1 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host web Hostname 127.0.0.1 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host mysql Hostname 127.0.0.1 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host ftp Hostname 127.0.0.1 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host bdd Hostname 127.0.0.1 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host reseau Hostname 127.0.0.1 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host partage Hostname 127.0.0.1 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host addc Hostname 192.0.2.2 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no
- Sur
aca.scribe-2.8.1-instance-default
Host addc Hostname 192.0.2.2 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no
- Sur un
aca.dc1-2.7.2-instance-default
etaca.dc1-2.8.0-instance-default
Host mail Hostname 127.0.0.1 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no Host dhcp Hostname 127.0.0.1 IdentitiesOnly yes LogLevel ERROR StrictHostKeyChecking no
- Sur un
aca.dc1-2.8.1-instance-default
, il n’y a aucune indication pour des conteneurs (#31004)
J’ai tester en me connectant avec l’agent sur les VMS (ssh -A
) et en me connectant en ssh dans les conteneurs, cela fonctionne sans soucis.
En revanche, la commande Query-Auto
ne fonctionne pas :-/
root@amonecole:~# Query-Auto Mise à jour le mardi 26 octobre 2021 11:05:42 Exécution des scripts /usr/share/eole/majauto_pre run-parts: executing /usr/share/eole/majauto_pre/mitm *** amonecole 2.8.1 (00000003) *** Action check pour le conteneur reseau Maj-Auto - Exécution de apt-eole -o --container current --log-level info check pour le conteneur reseau impossible
#5 Updated by Daniel Dehennin almost 2 years ago
- Status changed from En cours to Résolu
C’est ok avec les paquets
- eole-one-master version 2.8.1-25
- eole-ad-dc version 2.8.1-119
#6 Updated by Daniel Dehennin almost 2 years ago
- Status changed from Résolu to Fermé
- Remaining (hours) set to 0.0