Bug 1775384
| Summary: | [wmcb] Failed to bootstrap windows node on OCP 4.3 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | sumehta |
| Component: | Windows Containers | Assignee: | sumehta |
| Status: | CLOSED ERRATA | QA Contact: | gaoshang <sgao> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.3.0 | CC: | aos-bugs, gmarkley, rgudimet |
| Target Milestone: | --- | ||
| Target Release: | 4.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-23 11:13:47 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This bug has been verified and passed on OCP 4.3.0-0.nightly-2019-11-24-183610, move status to VERIFIED, thanks.
Version-Release number of selected component (if applicable):
# oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.3.0-0.nightly-2019-11-24-183610 True False 5m35s Cluster version is 4.3.0-0.nightly-2019-11-24-183610
windows-machine-config-operator commit:
# git show
commit 1eb1f983774101b5077828fd2efb4dfb711d5886
Steps:
1. Install OCP 4.3 cluster with ovn-kubernetes
2. Edit ovn-kubernetes as following
# oc edit Network.operator.openshift.io cluster
# oc get Network.operator.openshift.io cluster -o yaml
apiVersion: operator.openshift.io/v1
kind: Network
metadata:
creationTimestamp: "2019-11-25T13:02:46Z"
generation: 2
name: cluster
resourceVersion: "21021"
selfLink: /apis/operator.openshift.io/v1/networks/cluster
uid: c0315a6b-41fa-446d-971f-70c846607467
spec:
clusterNetwork:
- cidr: 10.128.0.0/14
hostPrefix: 23
defaultNetwork:
ovnKubernetesConfig:
hybridOverlayConfig:
hybridClusterNetwork:
- cidr: 10.132.0.0/14
hostPrefix: 23
type: OVNKubernetes
logLevel: ""
serviceNetwork:
- 172.30.0.0/16
status: {}
3. Create windows instance with wni
# ./wni azure create --kubeconfig ~/window_container/azure/cluster/kubeconfig --credentials ~/.azure/osServicePrincipal.json --image-id MicrosoftWindowsServer:WindowsServer:2019-Datacenter-with-Containers:latest --instance-type Standard_D2s_v3
4. Run wsu ansible
# ansible-playbook -i hosts ~/go/src/windows-machine-config-operator/tools/ansible/tasks/wsu/main.yaml
...
PLAY RECAP ******
40.69.171.210 : ok=11 changed=8 unreachable=0 failed=0 skipped=1 rescued=0 ignored=0
localhost : ok=7 changed=6 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
5. Check windows node is added to cluster and kubelet version is v1.16.2
# oc get nodes
NAME STATUS ROLES AGE VERSION
sgao-c-5l5mv-master-0 Ready master 3h38m v1.16.2
sgao-c-5l5mv-master-1 Ready master 3h38m v1.16.2
sgao-c-5l5mv-master-2 Ready master 3h39m v1.16.2
sgao-c-5l5mv-worker-centralus1-nh4zr Ready worker 3h30m v1.16.2
sgao-c-5l5mv-worker-centralus2-xfrvl Ready worker 3h30m v1.16.2
winworker-ay3n2 Ready <none> 117m v1.16.2
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-2020:0062 |
Description of problem: Bootstrapping failed with error. Kubelet service is not started in Windows PS C:\Users\core\AppData\Local\Temp\ansible.dgskivd1.mrp> .\wmcb.exe initialize-kubelet --ignition-file worker.ign --kubelet-path kubelet.exe {"level":"error","ts":1573016930.114901,"logger":"wmcb","msg":"could not run bootstrapper","error":"The service did not respond to the start or control request in a timely fashion.","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/root/go/pkg/mod/github.com/go-logr/zapr.0/zapr.go:128\nmain.runInitializeKubeletCmd\n\t/root/go/src/windows-machine-config-operator/cmd/bootstrapper/initialize_kubelet.go:64\ngithub.com/spf13/cobra.(*Command).execute\n\t/root/go/pkg/mod/github.com/spf13/cobra.5/command.go:830\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/root/go/pkg/mod/github.com/spf13/cobra.5/command.go:914\ngithub.com/spf13/cobra.(*Command).Execute\n\t/root/go/pkg/mod/github.com/spf13/cobra.5/command.go:864\nmain.main\n\t/root/go/src/windows-machine-config-operator/cmd/bootstrapper/main.go:31\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:200"} PS C:\Users\core\AppData\Local\Temp\ansible.r1f5retr.ob0> Get-Service kubelet Status Name DisplayName ------ ---- ----------- Stopped kubelet kubelet Version-Release number of selected component (if applicable): OCP 4.3 build: 4.3.0-0.nightly-2019-11-01-215341 How reproducible: Always Steps to Reproduce: 1. Create a cluster and a Windows 2019 Server Datacenter with Containers instance with relevant security rules 2. Run WSU 3. Run wmcb initialize-kubelet command <Instructions at https://docs.google.com/document/d/1zAidTs8wbWHzamh4G3pwdaPomyT-doSbo9xTAcIK9no/edit#heading=h.1cw91oc2oj04> Actual results: Bootstrapping failed Expected results: Bootstrapping finished successfully and kubelet is in running state Additional info: