The following defects were closed without code changes in ExtremeCloud Orchestrator 3.2.0.
| Parent Defect ID: | XCO-3443 | Issue ID: | XCO-3443 |
|---|---|---|---|
| Reason Code: | Working as Designed | ||
| Product: | XCO | Reported in Release: | EFA 3.1.0 |
| Symptom: | After fresh installation of XCO or after IP change, browser shows the 'Certificate is not Valid'. | ||
| Workaround: |
Add EFA CA to the trust store in the browser. Incase of an IP change, regenerate the EFA server certificate using CLI. Refer to Administration guide for details. |
||
| Parent Defect ID: | XCO-4137 | Issue ID: | XCO-4137 |
|---|---|---|---|
| Reason Code: | Insufficient Information | ||
| Product: | XCO | Reported in Release: | EFA 2.5.5 |
| Symptom: | EFA can not connect to SLX switch until a reload is performed Case | ||
| Parent Defect ID: | XCO-4139 | Issue ID: | XCO-4139 |
|---|---|---|---|
| Reason Code: | Insufficient Information | ||
| Product: | XCO | Reported in Release: | EFA 2.7.2 |
| Symptom: |
In a CLOS fabric, multiple fabric ports belonging to different fabric devices can have the same IP address assigned incorrectly. For example: interface ethernet 0/x on device D1 and ethernet 0/y on device D2 can have an ip-address 10.1.1.1/31 assigned. |
||
| Recovery: |
1. Disable the LLDP protocol under the interfaces ethernet 0/x on D1 and ethernet 0/y on D2 2. Execute "efa inventory device update --ip <device-ip>" for both D1 and D2 3. Execute "efa fabric configure --name <fabric-name>" |
||
| Parent Defect ID: | XCO-4141 | Issue ID: | XCO-4141 |
|---|---|---|---|
| Reason Code: | Insufficient Information | ||
| Product: | XCO | Reported in Release: | EFA 2.7.1 |
| Symptom: | EPG update with operation vrf-delete fails with reason record not found. | ||
| Condition: |
1. Create L3 EPG with vrf1 2. In the background trigger inventory device update 3. Execute EPG update vrf-delete/add consecutively. 4. Inv.vrf_created for vrf1 is received with reason: manual update, hence its gets vrf1 gets added as oob_Created vrf. and same gets consumed in the vrf-add operation. 5. One of the vrf-delete fails with the reason: record not found |
||
| Recovery: |
1. Delete EPG 2. Manually delete VRF from the device. |
||
| Parent Defect ID: | XCO-4145 | Issue ID: | XCO-4145 |
|---|---|---|---|
| Reason Code: | Insufficient Information | ||
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | Firmware-download progress is stuck in state 'Device Reload Completed' | ||
| Parent Defect ID: | XCO-4151 | Issue ID: | XCO-4151 |
|---|---|---|---|
| Reason Code: | Already Reported | ||
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | Certificate Expiry warning is shown on 'efa login' after certificate has expired. | ||
| Workaround: | Renew EFA server certificate. | ||
| Parent Defect ID: | XCO-4155 | Issue ID: | XCO-4155 |
|---|---|---|---|
| Reason Code: | Already Implemented | ||
| Product: | XCO | Reported in Release: | EFA 3.1.0 |
| Symptom: | Renewal of K3s server certificate fails after a time-shift. | ||
| Condition: | K3s CA certificate has been renewed and immediately K3s server certificate renewal is tried again. | ||
| Workaround: | During K3s CA certificate renewal, the K3s server certificate is generated as well. If the time-shift is very quick, then wait for few hours and then retry the same operation again. | ||
| Parent Defect ID: | XCO-4178 | Issue ID: | XCO-4178 |
|---|---|---|---|
| Reason Code: | Not Applicable | ||
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | SLX not sending NTP traps | ||
| Parent Defect ID: | XCO-4186 | Issue ID: | XCO-4186 |
|---|---|---|---|
| Reason Code: | Not Reproducible | ||
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | Unable to logon to EFA due to no resources found in efa namespace | ||
| Parent Defect ID: | XCO-4191 | Issue ID: | XCO-4191 |
|---|---|---|---|
| Reason Code: | Insufficient Information | ||
| Product: | XCO | Reported in Release: | EFA 2.7.0 |
| Symptom: | Device reporting as going through firmware download when trying to update epg | ||
| Parent Defect ID: | XCO-4414 | Issue ID: | XCO-4414 |
|---|---|---|---|
| Reason Code: | Already Implemented | ||
| Product: | XCO | Reported in Release: | EFA 2.5.5 |
| Symptom: | Port adding to EPG is failing | ||
| Parent Defect ID: | XCO-5237 | Issue ID: | XCO-5237 |
|---|---|---|---|
| Reason Code: | Not Reproducible | ||
| Product: | XCO | Reported in Release: | EFA 3.0.1 |
| Symptom: | EFA - After TPVM incremental upgrades (4.5.6>>4.5.7) and followed by SLX reloads the EFA application intermittently fails | ||
| Parent Defect ID: | XCO-5614 | Issue ID: | XCO-5614 |
|---|---|---|---|
| Reason Code: | Already Implemented | ||
| Product: | XCO | Reported in Release: | EFA 3.0.1 |
| Symptom: | EFA login failed for about 30 minutes after EFA restore backup | ||
| Parent Defect ID: | XCO-5621 | Issue ID: | XCO-5621 |
|---|---|---|---|
| Reason Code: | Not a Software Defect | ||
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | Port-channel config lost after applying the workaround for the defect: 67907 | ||
| Parent Defect ID: | XCO-5622 | Issue ID: | XCO-5622 |
|---|---|---|---|
| Reason Code: | Not a Software Defect | ||
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | CNIS 1.8: Vlan/epg configuration inconsistency between EFA and SLX | ||
| Parent Defect ID: | XCO-5923 | Issue ID: | XCO-5923 |
|---|---|---|---|
| Reason Code: | Working as Designed | ||
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | EFA Tenant Update is not working properly[ bgp listen-limit for particular vrf is not getting updated]. | ||
| Parent Defect ID: | XCO-5925 | Issue ID: | XCO-5925 |
|---|---|---|---|
| Reason Code: | Already Implemented | ||
| Product: | XCO | Reported in Release: | EFA 3.1.0 |
| Symptom: | breakout ports found together with parent interface, DRC fails | ||
| Parent Defect ID: | XCO-5928 | Issue ID: | XCO-5928 |
|---|---|---|---|
| Reason Code: | Already Implemented | ||
| Product: | XCO | Reported in Release: | EFA 3.1.0 |
| Symptom: | Health-Check DRC Removed Cluster Peer Configuration | ||
| Parent Defect ID: | XCO-5933 | Issue ID: | XCO-5933 |
|---|---|---|---|
| Reason Code: | Already Implemented | ||
| Product: | XCO | Reported in Release: | EFA 2.5.4 |
| Symptom: | Standby EFA is showing as down and also Backup is not happening | ||
| Parent Defect ID: | XCO-5935 | Issue ID: | XCO-5935 |
|---|---|---|---|
| Reason Code: | Insufficient Information | ||
| Product: | XCO | Reported in Release: | EFA 2.7.0 |
| Symptom: | EFA failed to register the SLX nodes | ||
| Parent Defect ID: | XCO-5936 | Issue ID: | XCO-5936 |
|---|---|---|---|
| Reason Code: | Already Implemented | ||
| Product: | XCO | Reported in Release: | EFA 2.7.0 |
| Symptom: | kubelet Readiness probe failed: Failed to read status file /status/status.json | ||
| Condition: | This particular issue of liveness/readiness probe failure and the subsequent calico-kube-controller crashloop was caused by the file permission issue. | ||
| Workaround: | The issue has been fixed as a part of the updated hardening script with the tpvm release 4.5.10. | ||
| Recovery: | EFA redeploy. | ||
| Parent Defect ID: | XCO-6212 | Issue ID: | XCO-6212 |
|---|---|---|---|
| Reason Code: | Working as Designed | ||
| Product: | XCO | Reported in Release: | EFA 3.1.1 |
| Symptom: | EFA tenant creation intermittently fails after initial fabric creation - ports are not available | ||
| Parent Defect ID: | XCO-6430 | Issue ID: | XCO-6430 |
|---|---|---|---|
| Reason Code: | Not Applicable | ||
| Product: | XCO | Reported in Release: | EFA 2.7.0 |
| Symptom: | .EFA 2.7.0 after spine node reload EFA is non-operational | ||