Open sbouchet opened 6 days ago
@sbouchet I just tried against a ClusterBot-provided cluster using an insecure cert, and it worked with odo
3.16.1. Can you please re-run the command with more logs (by adding -v=9
) and share the output please?
I0705 11:47:45.199274 2319100 implem.go:114] The path for preference file is /home/sbouchet/.odo/preference.yaml
I0705 11:47:45.199345 2319100 util.go:779] HTTPGetRequest: https://raw.githubusercontent.com/redhat-developer/odo/main/build/VERSION
I0705 11:47:45.199406 2319100 segment.go:273] Checking telemetry enable status
I0705 11:47:45.199417 2319100 segment.go:303] Sending telemetry enabled by preference
I0705 11:47:45.199432 2319100 segment.go:273] Checking telemetry enable status
I0705 11:47:45.199439 2319100 segment.go:303] Sending telemetry enabled by preference
I0705 11:47:45.199649 2319100 httpcache.go:45] Removing cache file 6e3240eb18c192c1e690e4ba818285ca, because it is older than 1h0m0s
I0705 11:47:45.199688 2319100 util.go:800] Response will be cached in /tmp/odohttpcache for 1h0m0s
Connecting to the OpenShift cluster
I0705 11:47:45.594731 2319100 implem.go:114] The path for preference file is /home/sbouchet/.odo/preference.yaml
I0705 11:47:45.595096 2319100 segment.go:273] Checking telemetry enable status
I0705 11:47:45.595135 2319100 segment.go:303] Sending telemetry enabled by preference
✗ tls: failed to verify certificate: x509: certificate signed by unknown authority
/kind bug
What versions of software are you using?
Operating System: Fedora 39
Output of
odo version
:How did you run odo exactly?
odo login -p p -u u https://clusterurl:6443 --insecure-skip-tls-verify
with unsecure certificateActual behavior
command result :
Expected behavior
with odo 3.15.0, exact same command results with;
Any logs, error output, etc?