The following defects, which were previously disclosed as open, were resolved in Extreme Fabric Automation 3.0.1.
| Parent Defect ID: | EFA-15472 | Issue ID: | EFA-15472 |
|---|---|---|---|
| Severity: | S2 – Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 3.0.0 |
| Symptom: | Supportsave has incomplete log files or missing information. | ||
| Condition: | When user is logged in to efa through command line, then supportsave should have valid content for the device locks and running configuration. | ||
| Parent Defect ID: | EFA-15691 | Issue ID: | EFA-15691 |
|---|---|---|---|
| Severity: | S1 – Critical | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 3.0.0 |
| Symptom: | No resources found in efa namespace | ||
| Condition: | After a double fault or active reload after reboot of standby | ||
| Parent Defect ID: | EFA-16008 | Issue ID: | XCO-4182 |
|---|---|---|---|
| Severity: | S3 – Medium | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 3.0.0 |
| Symptom: | RabbitMQ logs from terminated instances are not being purged or archived via logrotate | ||
| Condition: |
Cleanup older rabbitmq pod logs which are present after failover. This cleanups logs that are not from the current running pod, older than 5 days. |
||
| Workaround: | Delete the rabbitmq logs manually at /apps/efa_logs/rabbitmq/ on TPVM and /var/log/efa/rabbitmq/ on server. | ||