Vérification de la configuration de l'hôte

Vérifiez la configuration de votre hôte en exécutant le script sat-host-check après avoir satisfait aux exigences relatives au système, au réseau et aux connexions sortantes.

Le script sat-host-check présente actuellement un bug qui entraîne son échec sur Red Hat Enterprise Linux (RHEL) en raison d’une exigence liée à GLIBC.

Connectez-vous à votre hôte.

ssh root@<IP_address>

Pour les hôtes RHEL, utilisez Secure Shell (SSH) pour vous connecter en tant qu'utilisateur root.

    ssh root@<IP_address>
    ```
1. Pour les hôtes Red Hat CoreOS (RHCOS), copiez votre clé SSH publique dans votre script d'initialisation et connectez-vous en tant qu'utilisateur core.
    1. Téléchargez le script de connexion de l'hôte et ajoutez votre clé SSH publique.

        ```json {: codeblock}
        {
          "ignition": {
            "version": "3.1.0"
          },
          "passwd": {
            "users": [
              {
                "name": "core",
                "sshAuthorizedKeys": [ "PUBLIC-SSH-KEY" ]
              }
            ]
          },
        ...
        }
        ```
    1. Connectez-vous à votre hôte en tant que `core`.
        ```sh {: pre}
        ssh core@<IP_address>
        ```

Téléchargez le script et rendez-le exécutable.

curl https://<region>.containers.cloud.ibm.com/satellite-health/sat-host-check -o sat-host-check && chmod +x sat-host-check

Exemple de commande pour us-south.

curl https://us-south.containers.cloud.ibm.com/satellite-health/sat-host-check -o sat-host-check && chmod +x sat-host-check

Exécutez le script et indiquez la région où vous avez créé votre emplacement.

sudo ./sat-host-check --region $REGION

Exemple de commande pour us-south.

sudo ./sat-host-check --region us-south

Exemple de sortie pour la vérification d'un hôte dans us-south.

===========================
  TEST PHASE: redhatOS
===========================
PASS:  custom Grub configuration (/boot/grub/grub.conf) not present
PASS:  custom Network configuration (/sbin/ifup-local) not present
PASS:  custom Network configuration (/sbin/ifdown-pre-local) not present
PASS:  custom Network configuration (/sbin/ifdown-local) not present
PASS:  custom NTP configuration (/etc/ntp.conf) not present
=== subscription-manager  ===
STDOUT:
Usage: subscription-manager MODULE-NAME [MODULE-OPTIONS] [--help]
PASS:  subscription-manager configured
=== yum info rh-python36 ===
...
===========================
  TEST PHASE: network
===========================
=== ip addr ===
...
FAIL:  wrong number of network interfaces (expected 2, found: 3: [1: lo, 2: eth0, 3: eth1])
=== ip route ===
...
info:  no checks performed on 'ip route' output
=== Check connectivity to google.com:80 ===
PASS:  got response back from google.com:80
=== Check connectivity to our region us-south ===
=== Check connectivity to hosted control plane ===
=== Check connectivity to 169.63.123.154:30000 ===
PASS:  got response back from 169.63.123.154:30000
=== Check connectivity to 169.60.123.162:30000 ===
PASS:  got response back from 169.60.123.162:30000
=== Check connectivity to 52.117.93.26:30000 ===
PASS:  got response back from 52.117.93.26:30000
=== Check connectivity to 52.117.88.42:30000 ===
PASS:  got response back from 52.117.88.42:30000
=== Check connectivity to 169.47.174.106:30000 ===
PASS:  got response back from 169.47.174.106:30000
=== Check connectivity to 169.60.92.50:30000 ===
PASS:  got response back from 169.60.92.50:30000
=== Check connectivity to 169.61.74.210:30000 ===
PASS:  got response back from 169.61.74.210:30000
=== Check connectivity to 169.62.9.250:30000 ===
PASS:  got response back from 169.62.9.250:30000
=== Check connectivity to 169.62.10.162:30000 ===
PASS:  got response back from 169.62.10.162:30000
=== Check 443 ports ===
=== Check connectivity to 169.60.73.142:443 ===
PASS:  got response back from 169.60.73.142:443
=== Check connectivity to 169.60.101.42:443 ===
PASS:  got response back from 169.60.101.42:443
=== Check connectivity to 169.61.83.62:443 ===
PASS:  got response back from 169.61.83.62:443
=== Check connectivity to 169.61.109.34:443 ===
PASS:  got response back from 169.61.109.34:443
=== Check connectivity to 169.62.10.162:443 ===
FAIL:  Could not create request: dial tcp 169.62.10.162:443: connect: connection refused
=== Check connectivity to 169.63.75.82:443 ===
FAIL:  Could not create request: dial tcp 169.63.75.82:443: connect: connection refused
=== Check connectivity to 169.63.88.178:443 ===
PASS:  got response back from 169.63.88.178:443
=== Check connectivity to 169.63.88.186:443 ===
PASS:  got response back from 169.63.88.186:443
=== Check connectivity to 169.63.94.210:443 ===
FAIL:  Could not create request: dial tcp 169.63.94.210:443: connect: connection refused
=== Check connectivity to 169.63.111.82:443 ===
FAIL:  Could not create request: dial tcp 169.63.111.82:443: connect: connection refused
=== Check connectivity to 169.63.149.122:443 ===
FAIL:  Could not create request: dial tcp 169.63.149.122:443: connect: connection refused
=== Check connectivity to 169.63.158.82:443 ===
FAIL:  Could not create request: dial tcp 169.63.158.82:443: connect: connection refused
=== Check connectivity to 169.63.160.130:443 ===
FAIL:  Could not create request: dial tcp 169.63.160.130:443: connect: connection refused
=== Check connectivity to link control plane ===
=== Test Failure Summary: ===
redhatOS - error checking RHN configuration with `subscription-manager`: exit status 1
network - wrong number of network interfaces (expected 2, found: 3: [1: lo, 2: eth0, 3: eth1])
network - Could not create request: dial tcp 169.62.10.162:443: connect: connection refused
network - Could not create request: dial tcp 169.63.75.82:443: connect: connection refused
network - Could not create request: dial tcp 169.63.94.210:443: connect: connection refused
network - Could not create request: dial tcp 169.63.111.82:443: connect: connection refused
network - Could not create request: dial tcp 169.63.149.122:443: connect: connection refused
network - Could not create request: dial tcp 169.63.158.82:443: connect: connection refused
network - Could not create request: dial tcp 169.63.160.130:443: connect: connection refused
cleaned up temp dir: `/tmp/sathostcheck-3139302841`

Consultez le récapitulatif des échecs de test. En fonction de l'échec, consultez les exigences et mettez à jour vos hôtes.
- Configuration requise du système hôte
- Conditions requises pour le stockage hôte
- Configuration requise pour le réseau hôte
- Exigences de connectivité sortante de l'hôte et exigences de connectivité sortante spécifiques à la région pour la région où vous avez créé votre emplacement.
Si la vérification de l'hôte aboutit, vous pouvez continuer à connecter l'hôte à votre emplacement.