Description of problem: update machineset replicas controller-manager logs output nil Version-Release number of selected component (if applicable): $ ./openshift-install version ./openshift-install v0.4.0-8-gcc10f8027c30a37a8c3d78b793587126208c9d68-dirty Terraform v0.11.8 $ oc version oc v4.0.0-alpha.0+9750828-637 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO How reproducible: always Steps to Reproduce: 1. $ oc edit machineset qe-zhsun-1-worker-us-east-2a 2. $ oc logs -f clusterapi-manager-controllers-5b4996fb88-bzst7 -c controller-manager 3. Actual results: controller-manager logs output nil $ oc logs -f clusterapi-manager-controllers-5b4996fb88-bzst7 -c controller-manager 2018/11/26 02:13:13 Registering Components. 2018/11/26 02:13:13 Starting the Cmd. E1126 02:13:14.009211 1 controller.go:370] <nil> E1126 02:13:14.129338 1 controller.go:370] <nil> E1126 02:13:14.248753 1 controller.go:370] <nil> E1126 02:13:41.332806 1 reflector.go:322] sigs.k8s.io/cluster-api-provider-aws/vendor/sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126: Failed to watch *v1.Node: Get https://172.30.0.1:443/api/v1/nodes?resourceVersion=3347&timeoutSeconds=346&watch=true: dial tcp 172.30.0.1:443: connect: connection refused E1126 02:13:41.333000 1 reflector.go:322] sigs.k8s.io/cluster-api-provider-aws/vendor/sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126: Failed to watch *v1alpha1.MachineDeployment: Get https://172.30.0.1:443/apis/cluster.k8s.io/v1alpha1/machinedeployments?resourceVersion=867&timeoutSeconds=506&watch=true: dial tcp 172.30.0.1:443: connect: connection refused E1126 02:13:41.333062 1 reflector.go:322] sigs.k8s.io/cluster-api-provider-aws/vendor/sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126: Failed to watch *v1alpha1.MachineSet: Get https://172.30.0.1:443/apis/cluster.k8s.io/v1alpha1/machinesets?resourceVersion=2231&timeoutSeconds=319&watch=true: dial tcp 172.30.0.1:443: connect: connection refused E1126 07:46:59.884834 1 controller.go:370] <nil> Expected results: controller-manager logs no nil info Additional info:
https://github.com/kubernetes-sigs/cluster-api/pull/626
Merged upstream, next step is to sync cluster-api dep.
We have recently merged PR [1] that carries the upstream PR [2] (mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1653626#c1). See [3] for details. [1] https://github.com/openshift/cluster-api-provider-aws/pull/127 [2] https://github.com/kubernetes-sigs/cluster-api/pull/626 [3] https://github.com/openshift/cluster-api-provider-aws/pull/127/commits/44661f6ee1eec5ecb7b3e079cce05c7097ae2b86#diff-f9f7cdf568e7ecf8fda70cb304e31ad8R339
Verified. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-01-11-000044 True False 1h Cluster version is 4.0.0-0.nightly-2019-01-11-000044 $ oc edit machineset zhsun-worker-us-east-2a machineset.cluster.k8s.io/zhsun-worker-us-east-2a edited controller-manager logs no nil info.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758