The console downloads deployment was updated to handle IPv6 with a graceful fallback to IPv4 under most circumestances:
There are details in the comments on that PR.
If nodes are explicitly configured to disable IPv6 via ipv6.disable=1, then the Python script is likely to fail and cli downloads will be unavailable.
Severity here is unknown, I think it may be fine to bump this to a non-blocking 4.4.z stream bug but will look to confirm.
Does changing target release to 4.5.0 mean this issue is not a 4.4 release blocker? Is this intended? Do we still want to fix for 4.4?
From QE's perspective, it should be fixed in 4.4
Setting severity and target release, let me know if it's wrong
We have not addressed this issue yet.
Bumped to 4.6, not a 4.5 priority.
*** This bug has been marked as a duplicate of bug 1846922 ***