This bug indicates it was fixed in 1.0.2.0 in July 2019 however 1.0.2.0 is no longer available for download https://software.cisco.com/download/home/286314846/type/282463166/release/1.0.1.7
Is this bug which was found in 1.0.1.4 fixed in 1.0.1.7 or does this bug need to be re-opened until a fix is actually released?
Also how do I get notifications when released firmware is downgraded?
