Provision

⦾ Why doesn’t my newly discovered server list a MAC ID in the cluster.nodeinfo table?

Due to internal MAC ID conflicts on the target nodes, the MAC address will be listed against the target node using this format MAC ADDRESS 1 | MAC ADDRESS 2! *NOIP* in the xCAT node object.

../../../_images/MACConflict.png

⦾ Why does we see TASK [provision_validation : Failed - Assign admin nic IP] while executing discovery_provision.yml playbook?

../../../_images/AdminNICErrors.png

Potential Cause: Omnia validates the admin NIC IP on the OIM. If the user has not assigned an admin NIC IP in case of dedicated network interface type, an error message is returned. There is a parsing logic that is being applied on the blank IP and hence, the error displays twice.

Resolution: Ensure a OIM IP is assigned to the admin NIC.

⦾ Why are some target servers not reachable after PXE booting them?

Potential Causes:

  1. The server hardware does not allow for auto rebooting

  2. The process of PXE booting the node has stalled.

Resolution:

  1. Login to the iDRAC console to check if the server is stuck in boot errors (F1 prompt message). If true, clear the hardware error or disable POST (PowerOn Self Test).

  2. Hard-reboot the server to bring up the server and verify that the boot process runs smoothly. (If it gets stuck again, disable PXE and try provisioning the server via iDRAC.)

⦾ Why does PXE boot fail with tftp timeout or service timeout errors?

Potential Causes:

  • RAID is configured on the server.

  • Two or more servers in the same network have xCAT services running.

  • The target cluster node does not have a configured PXE device with an active NIC.

Resolution:

  • Create a Non-RAID or virtual disk on the server.

  • Check if other systems except for the OIM have xcatd running. If yes, then stop the xCAT service using the following commands: systemctl stop xcatd.

  • On the server, go to BIOS Setup -> Network Settings -> PXE Device. For each listed device (typically 4), configure an active NIC under PXE device settings

⦾ The discovery_provision.yml playbook fails to check for duplicate disk_partition values in input/provision_config.yml .

Resolution: User needs to ensure that there are no duplicate entries for the same partition in provision_config.yml.

⦾ After executing disocvery_provision.yml , why is the node status in OmniaDB being displayed as “standingby”?

Resolution: For any discovery mechanism other than switch-based, do the following:

  1. Execute the following command:

    chdef <node> status=””

  2. Then run:

    rinstall <node>

Where <node> refers to the node column in the OmniaDB, which has a “standingby” status.

⦾ Why does the discovery_provision.yml playbook execution fail at task: “prepare_oim needs to be executed”?

Potential Cause: Invalid input provided in network_spec.yml for admin_network or bmc_network fields.

Resolution: Perform a cleanup using oim_cleanup.yml with --tags provision & then re-run the discovery_provision.yml playbook. Execute the following command:

ansible-playbook utils/oim_cleanup.yml --tags provision
ansible-playbook discovery_provision.yml

⦾ While executing discovery_provision.yml playbook from the OIM, some of the cluster nodes fail to boot up and omniadb captures the node status as “failed”.

../../../_images/waco_node_boot_failure.png

Potential Cause: This issue is encountered due to any configuration failure during node provisioning.

Resolution: Perform the following steps:

  1. Delete the failed node from the db using delete_node.yml playbook utility. For more information, click here.

  2. Re-provision the node by re-running the discovery_provision.yml playbook.

If you have any feedback about Omnia documentation, please reach out at omnia.readme@dell.com.