The following defects were closed without code changes in ExtremeCloud Orchestrator 3.2.1.
| Parent Defect ID: | XCO-4183 | Issue ID: | XCO-4183 |
|---|---|---|---|
| Reason Code: | Not Reproducible | ||
| Product: | XCO | Reported in Release: | EFA 2.7.0 |
| Symptom: | EFA inventory device execute-cli command fails randomly for devices with "HTTP adapter login error : : connection refused". | ||
| Condition: | Concurrent running of multiple execute-cli commands at the same time causes this failure. | ||
| Workaround: | Run the commands sequentially. | ||
| Recovery: | Since it is an operational command failure, there are no impacts to EFA database and SLX device configurations. Hence, no recovery is required. The failed command can be re-run sequentially for successful completion of the expected operations. | ||
| Parent Defect ID: | XCO-5259 | Issue ID: | XCO-5259 |
|---|---|---|---|
| Reason Code: | Not Reproducible | ||
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | EFA drift reconcile (DRC) fails on sequential reboot of the non-clos pair. | ||
| Condition: | During a series of SLX reboots, the DRC failed and did not re-initiate upon EFA failover. | ||
| Workaround: | Not applicable. | ||
| Recovery: | Reinitiate DRC manually. | ||
| Parent Defect ID: | XCO-5926 | Issue ID: | XCO-5926 |
|---|---|---|---|
| Reason Code: | Insufficient Information | ||
| Product: | XCO | Reported in Release: | EFA 2.7.0 |
| Symptom: | EFA execute-cli reports SLX switches as unreachable. | ||
| Condition: | This condition is caused when a password is changed, and an old password is used even after a password is changed. | ||
| Workaround: | Use updated new password. | ||
| Recovery: | Use updated new password. | ||
| Parent Defect ID: | XCO-6467 | Issue ID: | XCO-6467 |
|---|---|---|---|
| Reason Code: | Already Implemented | ||
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | XCO pods are in Pending state and login is not successful. | ||
| Condition: | As rabbitmq logs continues to grow, disk utilization goes beyond the threshold of 87% and XCO pods restarts. If 'docker_k3s_images.tar' is not present in /apps/efa/docker_images/ folder, XCO pods stuck in Pending state. | ||
| Workaround: |
Run the following commands to resolve this issue: On TPVM: sudo cp /apps/efa/docker_images/docker_k3s_images.tar /apps/rancher/k3s/agent/images/ sudo k3s ctr image import /apps/efa/docker_images/docker_k3s_images.tar On Server: cp /opt/efa/docker_images//opt/efa/docker_images /var/lib/rancher/k3s/agent/images/ k3s ctr image import docker_k3s_images.tar |
||
| Recovery: | Re-import the docker_k3s_images.tar file. | ||