This is a common scenario for some customers on AWS, where they either
have strict rules for allow-listing external endpoints (so, instead of
getting a quick response for pro with the error, they only get a
timeout) and airgapped customers with no knowledge about setting up an
airgapped-contract se
Public bug reported:
pro collect-logs takes more than 1:30 minutes to complete on air-gapped
envs, while `pro status` and `pro help` won't work at all. After the
same amount of time they throw the `[Errno 101] Network is unreachable`
message.
Tested on 24.04 Pro on AWS and pro client version 31.2
We have seen this bug quite often on AWS when the customer is using
imported VMs. This means that cloud-init was initialized before the
image being imported to AWS, therefore, customers get that error when
converting to Pro. It has been quite a headache to be honest and while
the workaround works,
