Verifica del setup dell'host

Dopo aver creato host che soddisfano i requisiti di sistema, requisiti di rete e i requisiti di connettività in uscita, è possibile verificare il setup dell'host eseguendo il seguente script sat-host-check.

Attualmente esiste un bug con lo script sat-host-check che lo fa fallire su RHEL a causa di un requisito GLIBC.

Accedi al tuo host.

ssh root@<IP_address>

Per gli host RHEL, SSH come root.

    ssh root@<IP_address>
    ```
1. Per gli host RHCOS, copiare il tuo tasto SSH pubblico nel tuo script di accensione e accedere come core.
    1. Scarica lo script di collegamento dell'host e aggiungi la tua chiave SSH pubblica.

        ```json {: codeblock}
        {
          "ignition": {
            "version": "3.1.0"
          },
          "passwd": {
            "users": [
              {
                "name": "core",
                "sshAuthorizedKeys": [ "PUBLIC-SSH-KEY" ]
              }
            ]
          },
        ...
        }
        ```
    1. Accedi al tuo host come `core`.
        ```sh {: pre}
        ssh core@<IP_address>
        ```

Scaricare lo script e renderlo eseguibile.

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

Comando di esempio per us-south.

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

Eseguire lo script e specificare la regione in cui hai creato la tua posizione.

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

Comando di esempio per us-south.

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

{: pre}

Esempio di output per la verifica di un host in 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`

Rivedere il riepilogo del fallimento del test. A seconda del guasto, rivedere i requisiti e aggiornare i tuoi host.
- Requisiti del sistema host
- Requisiti di memoria host
- Requisiti di rete host
- Requisiti di connettività in uscita host e i requisiti di connettività in uscita specifici per regione per la regione in cui hai creato la tua posizione.
Se il controllo host riesce, è possibile continuare ad allegare l'host alla propria posizione.