rancher: Cannot edit load-balancer or service discovery yaml

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

Steps to reproduce (least amount of steps as possible): Upgrade Rancher v. 2.1.7 to 2.2.2 and then try to edit Load Balance via “View/Edit Yaml” option.

Result: You will see an “[Object object]” error in popup, instead of actual yaml. Screenshot 2019-04-19 at 19 01 23

Other details that may be helpful: Chrome console gives error: net::ERR_SPDY_PROTOCOL_ERROR 200

Workloads yaml editor works fine.

Environment information

  • Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.2.2
  • Installation option (single install/HA): HA

Cluster information

  • Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom
  • Machine type (cloud/VM/metal) and specifications (CPU/memory): metal, 2x12 CPU, 2x32 Gb RAM
  • Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-10T11:44:36Z", GoVersion:"go1.11", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:30:26Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
  • Docker version (use docker version):
Client:
 Version:           18.09.5
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        e8ff056
 Built:             Thu Apr 11 04:43:57 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.5
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       e8ff056
  Built:            Thu Apr 11 04:10:53 2019
  OS/Arch:          linux/amd64
  Experimental:     false

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 11
  • Comments: 40 (12 by maintainers)

Most upvoted comments

A temporary method:Go to local cluster and switch to system project\resource\config-maps page, find nginx-configurationand edit it,add use-http2= false . Check that the edit yaml is working properly?If external load balancer use the L7 layer proxy, you also need to disable HTTP2 image

This issue only happens with an HA upgrade from older Rancher v2.1.x to v2.2.2

Note: The issue does not happen to me on latest master with HA setup (fresh install non-upgrade). I believe that either the issue is fixed in master or that you must perform an HA upgrade to observe the issue (as outlined in my last comment).

@stevenklar and @cdbyrd I appologize for any confusion. I was initially confused too 😃 Refer to Logan’s comment above: https://github.com/rancher/rancher/issues/19723#issuecomment-492727475

v2.2.3 doesn’t include fixes we had in the v2.2.3 release candidates. Thus you need to wait for a fix at least until v2.2.4 (which is now the milestone of the backport issue #20032 )

We had an urgent need to fix a monitoring issue in v2.2.3 so we cut a release for that without the rc fixes. v2.2.4 will have the fix for this. Let me know if you have any questions.

Since I have already validated in the latest master (v2.3) I am going to re-close this issue. Use #20032 for upcoming v2.2.4

@stevenklar can you confirm your rancher set up is HA? Issue should only be happening on HA and only when upgrade from older version to newer v2.2.3 When we originally tested we never saw the issue without upgrade and without HA rancher

Yep we got a L4 nginx stream load balancing round-robin 3 node cluster with ranger on all nodes. Deployed with the helm chart as mentioned in the documentation for HA setups.

setup

@ChrisMcKee Does this method work for you?

@xvonabur as far as I know so far yes. Soon product management and development will look at the issue. If there are any possible workarounds we’ll find out sometime soon.