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

failed calling webhook "issuers.admission.certmanager.k8s.io" #23557

Closed
l00p5 opened this issue Oct 20, 2019 · 2 comments
Closed

failed calling webhook "issuers.admission.certmanager.k8s.io" #23557

l00p5 opened this issue Oct 20, 2019 · 2 comments

Comments

@l00p5
Copy link

l00p5 commented Oct 20, 2019

What kind of request is this (question/bug/enhancement/feature request):
bug

Steps to reproduce (least amount of steps as possible):
Upgraded rancher from v2.2.8 to v2.2.9

First I did follow https://rancher.com/docs/rancher/v2.x/en/installation/options/upgrading-cert-manager/ to upgrade cert-manager (UPGRADING CERT-MANAGER WITH INTERNET ACCESS), everything worked fine, no errors at all.

Then when upgrading rancher...

Followed the steps from https://rancher.com/docs/rancher/v2.x/en/upgrades/upgrades/ha/

helm repo update
helm repo list
helm fetch rancher-stable/rancher

and finally when running:

helm upgrade rancher rancher-stable/rancher -f values.yml

values.yml:

hostname: [[ -- ]]
ingress:
  tls:
    source: letsEncrypt
letsEncrypt:
  email: [[ -- ]]

Result:

UPGRADE FAILED
Error: failed to create resource: Internal error occurred: failed calling webhook "issuers.admission.certmanager.k8s.io": the server is currently unable to handle the request
Error: UPGRADE FAILED: failed to create resource: Internal error occurred: failed calling webhook "issuers.admission.certmanager.k8s.io": the server is currently unable to handle the request

It says UPGRADE FAILED but rancher did upgrade to v2.2.9

Other details that may be helpful:

Environment information

  • Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): UI
Rancher v2.2.9
User Interface v2.2.98
Helm v2.10.0-rancher11
Machine v0.15.0-rancher8-1
  • Installation option (single install/HA): HA (1 node)

Cluster information

  • Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
  • Machine type (cloud/VM/metal) and specifications (CPU/memory): VPS 4gb ram 4gb cpu
  • Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"20c265fef0741dd71a66480e35bd69f18351daea", GitTreeState:"clean", BuildDate:"2019-10-15T19:16:51Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"20c265fef0741dd71a66480e35bd69f18351daea", GitTreeState:"clean", BuildDate:"2019-10-15T19:07:57Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
  • Helm version
Client: &version.Version{SemVer:"v2.14.3", GitCommit:"0e7f3b6637f7af8fcfddb3d2941fcc7cbebb0085", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.3", GitCommit:"0e7f3b6637f7af8fcfddb3d2941fcc7cbebb0085", GitTreeState:"clean"}
  • Docker version (use docker version):
Client: Docker Engine - Community
 Version:           19.03.4
 API version:       1.40
 Go version:        go1.12.10
 Git commit:        9013bf583a
 Built:             Fri Oct 18 15:52:22 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.4
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.10
  Git commit:       9013bf583a
  Built:            Fri Oct 18 15:50:54 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683
@adeleglise
Copy link

Hi, I can confirm I observe the same message when installing a brand new rancher 2.2.9
I didn't saw this message in 2.2.8

@stale
Copy link

stale bot commented Jul 12, 2021

This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.

@stale stale bot added the status/stale label Jul 12, 2021
@stale stale bot closed this as completed Jul 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants