[BUG] Wrong HTTP(S)_PROXY value blocks all CRC usage

[jsliacan]

General information

• OS: Linux

CRC version

CodeReady Containers version: 2.0.1+bf3b1a6
OpenShift version: 4.10.3
Podman version: 3.4.4

CRC status

Machine does not exist. Use 'crc start' to create it

CRC config

- consent-telemetry                     : no
- pull-secret-file                      : /home/jsliacan/Downloads/crc-pull-secret

Steps to reproduce

1. export HTTP_PROXY=localhost:8080 (for instance)
2. crc version (or any other command: help, status, start, setup, ...)

Expected

The corresponding output for that command, i.e. for version I'd expect

CodeReady Containers version: 2.0.1+bf3b1a6
OpenShift version: 4.10.3
Podman version: 3.4.4

Actual

FATA[0000] HTTP proxy URL 'localhost:8080' is not valid: url should start with http://

Logs

jsliacan ~ $ crc version
CodeReady Containers version: 2.0.1+bf3b1a6
OpenShift version: 4.10.3
Podman version: 3.4.4
jsliacan ~ $ crc status
Machine does not exist. Use 'crc start' to create it
jsliacan ~ $ crc config view
- consent-telemetry                     : no
- pull-secret-file                      : /home/jsliacan/Downloads/crc-pull-secret
jsliacan ~ $ export HTTP_PROXY=localhost:8080
jsliacan ~ $ crc status
FATA[0000] HTTP proxy URL 'localhost:8080' is not valid: url should start with http:// 
jsliacan ~ $ crc ip
FATA[0000] HTTP proxy URL 'localhost:8080' is not valid: url should start with http:// 
jsliacan ~ $ crc start
FATA[0000] HTTP proxy URL 'localhost:8080' is not valid: url should start with http:// 
jsliacan ~ $ crc 
FATA[0000] HTTP proxy URL 'localhost:8080' is not valid: url should start with http:// 

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jsliacan]

• might apply to all OSs

[anjannath]

was fixed in #3816