The following defects were closed without code changes in ExtremeCloud Orchestrator 3.3.0.
| Parent Defect ID: | XCO-3438 | Issue ID: | XCO-3438 |
|---|---|---|---|
| Reason Code: | Cannot Fix | ||
| Product: | XCO | Reported in Release: | EFA 2.7.0 |
| Symptom: | When endpoint group create or update operation REST requests of multiple endpoint groups each with 50+ ctags are issued concurrently, one or two of the requests can fail with "Error 1452: Cannot add or update a child row: a foreign key constraint fails" or with an error indicating database timeout or an error indicating failure of network property delete. | ||
| Condition: | When multiple endpoint group requests are processed concurrently, some of the database requests initiated by EFA can cause database to end one of the request with the above mentioned error | ||
| Workaround: | Execute the commands sequentially | ||
| Recovery: | EFA database and SLX device configurations are always not affected by this error and hence no recovery is required. The failed commands shall be rerun sequentially to successful completion of the expected operations | ||
| Parent Defect ID: | XCO-5171 | Issue ID: | XCO-5171 |
|---|---|---|---|
| Reason Code: | Not Reproducible | ||
| Product: | XCO | Reported in Release: | EFA 3.1.0 |
| Symptom: | EFA status takes longer time to settle after SLX power cycle. | ||
| Parent Defect ID: | XCO-5235 | Issue ID: | XCO-5235 |
|---|---|---|---|
| Reason Code: | Already Implemented | ||
| Product: | XCO | Reported in Release: | EFA 3.1.0 |
| Symptom: | High Memory utilization by litestream process | ||
| Condition: | Condition not known. | ||
| Workaround: | Not Applicable | ||
| Recovery: |
Following steps need to be followed. 1. Check for litestream process on active using ps aux | grep litestream 2. Use following command to restart. systemctl restart litestream. |
||
| Parent Defect ID: | XCO-5795 | Issue ID: | XCO-5795 |
|---|---|---|---|
| Reason Code: | Insufficient Information | ||
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | The data in the previous page has the ethernet interfaces as well as other interfaces even though the page is supposed to contain only the Ethernet interfaces | ||
| Condition: |
Below are the steps to reproduce the issue: 1. In the XCO GUI Device Inventory view, the user selects the "Network Essentials" options from the row action menu. 2. The user navigates to page next page 2. And then comes back to the previous page |
||
| Parent Defect ID: | XCO-6464 | Issue ID: | XCO-6464 |
|---|---|---|---|
| Reason Code: | Already Implemented | ||
| Product: | XCO | Reported in Release: | EFA 3.1.0 |
| Symptom: | DC_APP_Events_Q_Notification messages stacking up causing Disk Space issues in RabbitMQ directory | ||
| Parent Defect ID: | XCO-6465 | Issue ID: | XCO-6465 |
|---|---|---|---|
| Reason Code: | Already Implemented | ||
| Product: | XCO | Reported in Release: | EFA 3.1.1 |
| Symptom: | Pods from Active node of EFA went down and recovered after some time. | ||
| Parent Defect ID: | XCO-6468 | Issue ID: | XCO-6468 |
|---|---|---|---|
| Reason Code: | Not Reproducible | ||
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | Why after recovering from EFA-8779, one EFA server recovered but other remained down and to finally recover it, we had to redeploy EFA. | ||
| Parent Defect ID: | XCO-6574 | Issue ID: | XCO-6574 |
|---|---|---|---|
| Reason Code: | Question Answered | ||
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | Post EFA upgrade, EFA not able to communicate Switches. | ||
| Parent Defect ID: | XCO-6630 | Issue ID: | XCO-6630 |
|---|---|---|---|
| Reason Code: | Not a Software Defect | ||
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | XCO- MGMT subinterface IP address is not contained in netstat -tuplen | grep 443. | ||
| Parent Defect ID: | XCO-6759 | Issue ID: | XCO-6759 |
|---|---|---|---|
| Reason Code: | Not Applicable | ||
| Product: | XCO | Reported in Release: | EFA 3.1.1 |
| Symptom: | TPVM incremental downgrade is failing. | ||
| Parent Defect ID: | XCO-6886 | Issue ID: | XCO-6886 |
|---|---|---|---|
| Reason Code: | Already Implemented | ||
| Product: | XCO | Reported in Release: | EFA 2.7.2 |
| Symptom: | vrf deletion Error : Cannot delete the VRF vrf_VPN01562_354373 as it is configured on the device(s). | ||
| Parent Defect ID: | XCO-6954 | Issue ID: | XCO-6954 |
|---|---|---|---|
| Reason Code: | Working as Designed | ||
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | SNMP configuration not in sync with EFA | ||
| Parent Defect ID: | XCO-7475 | Issue ID: | XCO-7475 |
|---|---|---|---|
| Reason Code: | Not Reproducible | ||
| Product: | XCO | Reported in Release: | XCO 3.2.1 |
| Symptom: | UC1: XCO deletes IPv4/v6 addresses from Ve interfaces after Leaf reboot & DRC | ||
| Parent Defect ID: | XCO-7612 | Issue ID: | XCO-7612 |
|---|---|---|---|
| Reason Code: | Not a Software Defect | ||
| Product: | XCO | Reported in Release: | XCO 3.2.1 |
| Symptom: | Configuration pushed using execute-cli is removed by XCO during DRC | ||
| Parent Defect ID: | XCO-8144 | Issue ID: | XCO-8144 |
|---|---|---|---|
| Reason Code: | Not a Software Defect | ||
| Product: | XCO | Reported in Release: | XCO 3.2.1 |
| Symptom: | XCO 3.2.1: EFA manage firmware-downlad status as a “failed” after upgrade. | ||