Rancher logs spammed with "Updating workload [ingress-nginx/nginx-ingress-controller]" and "Updating service [frontend] with public endpoints" on a rollback #35798
Description
Rancher Server Setup
- Rancher version: 2.5.11 to 2.6-head
e4db3eto 2.5.11 - Installation option (Docker install/Helm Chart): docker install
Information about the Cluster
- Downstream clusters:
Describe the bug
- Deployed the clusters
- Deployed few resources including workloads, ingress and services. Deployed fleet bundles
- Followed rancher docs to upgrade a single node docker install and rollback
- On a rollback, rancher logs have these messages, but it does stop after a couple of minutes
2021/12/08 06:38:01 [INFO] Updating workload [ingress-nginx/nginx-ingress-controller] with public endpoints [[{"nodeName":"c-t6mq2:m-29kfb","addresses":["ip1"],"port":80,"protocol":"TCP","podName":"ingress-nginx:nginx-ingress-controller-5bj94","allNodes":false},{"nodeName":"c-t6mq2:m-29kfb","addresses":["ip1"],"port":443,"protocol":"TCP","podName":"ingress-nginx:nginx-ingress-controller-5bj94","allNodes":false},{"nodeName":"c-t6mq2:m-vbtqs","addresses":["ip2"],"port":80,"protocol":"TCP","podName":"ingress-nginx:nginx-ingress-controller-86cfr","allNodes":false},{"nodeName":"c-t6mq2:m-vbtqs","addresses":["ip2"],"port":443,"protocol":"TCP","podName":"ingress-nginx:nginx-ingress-controller-86cfr","allNodes":false}]]
2021/12/08 06:38:01 [INFO] Updating workload [kube-system/aws-node] with public endpoints [[{"nodeName":"c-bnx9l:machine-7wc6j","addresses":["ip3"],"port":61678,"protocol":"TCP","podName":"kube-system:aws-node-zj6zl","allNodes":false},{"nodeName":"c-bnx9l:machine-hc6q7","addresses":["ip4"],"port":61678,"protocol":"TCP","podName":"kube-system:aws-node-d5mcb","allNodes":false}]]
2021/12/08 06:38:01 [INFO] Updating workload [fleet-mc-helm-example/frontend] with public endpoints [[{"addresses":["ip4"],"port":30596,"protocol":"TCP","serviceName":"fleet-mc-helm-example:frontend","allNodes":true}]]
- and
2021/12/08 06:38:13 [INFO] Updating service [frontend] with public endpoints [[{"addresses":["<>"],"port":31061,"protocol":"TCP","serviceName":"fleet-helm-example:frontend","allNodes":true}]]
2021/12/08 06:38:13 [INFO] Updating service [frontend] with public endpoints [[{"addresses":["<>"],"port":30596,"protocol":"TCP","serviceName":"fleet-mc-helm-example:frontend","allNodes":true}]]
2021/12/08 06:38:13 [INFO] Updating workload [fleet-mc-helm-example/frontend] with public endpoints [[{"addresses":["<>"],"port":30596,"protocol":"TCP","serviceName":"fleet-mc-helm-example:frontend","allNodes":true}]]
- The existing ingresses. are functional. and the clusters are Active.