Defects Closed without Code Changes

The following defects were closed in Extreme Fabric Automation 3.0.0.

Parent Defect ID: EFA-9591 Issue ID: EFA-9591
Reason Code: Working as Designed Severity: S2 - Major
Product: Extreme Fabric Automation Reported in Release: EFA 2.5.0
Symptom: "efa fabric configure" fails with error after previously changing the fabric password in the configured fabric
Condition: This condition was seen when "efa fabric configure --name <fabric name>" was issued after modifying the MD5 password. Issue is observed when certain BGP sessions are not in an ESTABLISHED state after clearing the BGP sessions as part of fabric configure.
Workaround: Wait for BGP sessions to be ready by checking the status of BGP sessions using "efa fabric topology show underlay --name <fabric name>"
Recovery: Wait for BGP sessions to be ready. Check the status of BGP sessions using "efa fabric topology show underlay --name <fabric name>"
Parent Defect ID: EFA-12237 Issue ID: EFA-12237
Reason Code: Already Implemented Severity: S2 - Major
Product: Extreme Fabric Automation Reported in Release: EFA 2.5.4
Symptom: EPG update port-group-delete operation results in the runtime error "Execution error: service is not available or internal server error has occurred, please try again later"
Condition:

Below are the steps to reproduce the issue:

1. Create a BD based tenant under a CLOS or Non-CLOS fabric.

2. Create a BD based EPG (under the ownership of the tenant created in step 1) with some ctags and some member port-channels.

3. For the reasons unknown, the BD (Bridge Domain) configuration pertaining to one of the member port-channel got deleted from the EFA DB, causing the DB to be in an inconsistent state.

4. Execute EPG update "port-group-delete" operation to remove the member port-channel whose BD configuration is inconsistent.

Recovery:

No recovery through EFA CLI.

The inconsistent DB needs to be corrected by creating dummy BD (Bridge Domain) entries in the database followed by EPG update "port-group-delete".

Parent Defect ID: EFA-13281 Issue ID: EFA-13281
Reason Code: Not Reproducible Severity: S2 - Major
Product: Extreme Fabric Automation Reported in Release: EFA 2.7.0
Symptom: When 'efa system backup' command is executed with copy to the remote system enabled and the error 'local error: tls: bad record MAC' is seen.
Workaround: The backup will be copied to the remote location and the error is harmless.
Parent Defect ID: EFA-13584 Issue ID: EFA-13584
Reason Code: Not Reproducible Severity: S2 - Major
Product: Extreme Fabric Automation Reported in Release: EFA 2.7.0
Symptom: EFA failure during/after TPVM upgrade from 4.4.0 to 4.5.0-7
Workaround: None: The customer is expecting a new version of TPVM 20.4.1b patch. with TPVM 4.5.1. Reopen case if the issue persists.
Parent Defect ID: EFA-13993 Issue ID: EFA-13993
Reason Code: Configuration/User Error Severity: S3 - Moderate
Product: Extreme Fabric Automation Reported in Release: EFA 2.7.0
Symptom: L3-ENG-ESC | SEV: Medium - C3 | Case#(02614144) | Ericsson United states | |EFA 2.7.0|Installation of EFA Mutimode on Bare Metal External servers,EFA on VM1 status is down. ERROR 1045 (28000).
Parent Defect ID: EFA-14055 Issue ID: EFA-14055
Reason Code: Insufficient Information Severity: S3 - Moderate
Product: Extreme Fabric Automation Reported in Release: EFA 2.5.5
Symptom: EFA: Resource temporarily unavailable
Parent Defect ID: EFA-14577 Issue ID: EFA-14577
Reason Code: Not a Software Defect Severity: S2 - Major
Product: Extreme Fabric Automation Reported in Release: EFA 2.5.5
Symptom: FlexiLab - initial EFA installation failed
Parent Defect ID: EFA-14615 Issue ID: EFA-14615
Reason Code: Question Answered Severity: S3 - Moderate
Product: Extreme Fabric Automation Reported in Release: EFA 2.7.0
Symptom: Incomplete route map config add to EFA after upgrade from CNIS 1.4 to 1.6
Parent Defect ID: EFA-14784 Issue ID: EFA-14784
Reason Code: Third Party Issue Severity: S2 - Major
Product: Extreme Fabric Automation Reported in Release: EFA 2.6.1
Symptom: HTTPS connection refused while registering device in EFA even after HTTP restart on SLX
Recovery: Its tracked from SLX defect