Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[regression] odo login Error : 'tls: failed to verify certificate: x509: certificate signed by unknown authority' #7257

Open
sbouchet opened this issue Jul 3, 2024 · 2 comments
Labels
area/openshift Issues or PRs related to OpenShift kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.

Comments

@sbouchet
Copy link

sbouchet commented Jul 3, 2024

/kind bug

What versions of software are you using?

Operating System:
Fedora 39

Output of odo version:

odo v3.16.1 (v3.16.1)

Server: https://clusterurl:6443
Kubernetes: v1.26.5+7d22122
Podman Client: 4.9.4

How did you run odo exactly?

odo login -p p -u u https://clusterurl:6443 --insecure-skip-tls-verify with unsecure certificate

Actual behavior

command result :

Connecting to the OpenShift cluster

 ✗  tls: failed to verify certificate: x509: certificate signed by unknown authority

Expected behavior

with odo 3.15.0, exact same command results with;

/home/sbouchet/.odo/cache/3.15.0/odo login -p p -u u https://clusterurl:6443 --insecure-skip-tls-verify
Connecting to the OpenShift cluster

Login successful.

You have access to the following projects and can switch between them with 'odo set project <projectname>':

Any logs, error output, etc?

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Jul 3, 2024
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Jul 3, 2024
@rm3l
Copy link
Member

rm3l commented Jul 5, 2024

@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?

@rm3l rm3l added the area/openshift Issues or PRs related to OpenShift label Jul 5, 2024
@sbouchet
Copy link
Author

sbouchet commented Jul 5, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/openshift Issues or PRs related to OpenShift kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.
Projects
Status: No status
Development

No branches or pull requests

2 participants