After following these instructions (https://github.com/openshift/windows-machine-config-bootstrapper/blob/master/tools/ansible/docs/azure/azure-with-windows-server.md) my cluster appears to be up and running -

$ oc get node
NAME                                STATUS   ROLES    AGE   VERSION
ocp447-nffjf-master-0               Ready    master   19h   v1.17.1+f5fb168
ocp447-nffjf-master-1               Ready    master   19h   v1.17.1+f5fb168
ocp447-nffjf-master-2               Ready    master   19h   v1.17.1+f5fb168
ocp447-nffjf-worker-eastus1-959mg   Ready    worker   19h   v1.17.1+f5fb168
ocp447-nffjf-worker-eastus2-pxtzc   Ready    worker   19h   v1.17.1+f5fb168
ocp447-nffjf-worker-eastus3-vtrqr   Ready    worker   19h   v1.17.1+f5fb168
win-worker1                         Ready    worker   17h   v1.17.1

But when running the test on the default namespace I see -

$ oc create -f https://gist.githubusercontent.com/suhanime/683ee7b5a2f55c11e3a26a4223170582/raw/d893db98944bf615fccfe73e6e4fb19549a362a5/WinWebServer.yaml -n default
service/win-webserver created
deployment.apps/win-webserver created

But then -

$ oc describe pod/win-webserver-6f5bdc5b95-nl7rz
...
Events:
  Type     Reason                  Age                  From                  Message
  ----     ------                  ----                 ----                  -------
  Normal   Scheduled               116s                 default-scheduler     Successfully assigned default/win-webserver-6f5bdc5b95-nl7rz to win-worker1
  Warning  FailedCreatePodSandBox  114s                 kubelet, win-worker1  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "d63e0d5ebef238519b4ac6329558db3eaefadfc0c5a7005afc8705b5986c0592" network for pod "win-webserver-6f5bdc5b95-nl7rz": networkPlugin cni failed to set up pod "win-webserver-6f5bdc5b95-nl7rz_default" network: error while GETHNSNewtorkByName(OVNKubernetesHybridOverlayNetwork): Network OVNKubernetesHybridOverlayNetwork not found

Any advice to diagnose and fix this ? Thanks.

The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

• release-4.5
• release-4.6
• release-4.4

Contact the Test Platform or Automated Release teams for more information.

At https://github.com/openshift/windows-machine-config-bootstrapper/blob/master/tools/ansible/docs/azure/azure-with-windows-server.md we have -

... ConfigureR emotingForAnsible ...

This should be -

... ConfigureRemotingForAnsible ...

ie we have an extra space

The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

• release-4.8
• release-4.9

Contact the Test Platform or Automated Release teams for more information.

The document for tools: windows-node-installer should be refined. The docs should be comprehensive and free of errors. The format of the file should be checked to avoid random text coloring. The edits requested might be trivial but are important for other users to take this work seriously.

https://github.com/openshift/windows-machine-config-operator/blob/master/tools/windows-node-installer/README.md

I have a set of a OpenShift worker nodes with IPs 192.168.200.2, 192.168.200.22, 192.168.200.234 etc. where '192.168.200.2' is a common string in all the IP addresses.

Due to this, the below line in windows-machine-config-bootstrapper/tools/ansible/tasks/wsu/main.yaml (line 329) breaks the ansible automation, since the output of it contains multiple nodes, not just the node I am trying to bootstrap.
shell: "oc get node -o wide |awk '/{{ inventory_hostname }}/ || /{{ private_ip }}/ {print $1}'"

For example, I am trying to bootstrap a Windows node with 192.168.200.2 IP. But since I have other nodes with this common string in the IP address, the ansible steps fails because it outputs all the nodes with similar IP addresses.

If I run above command,

# oc get node -o wide |awk '/192.168.200.2/ || /192.168.200.2/ {print $1}'
win2k19dc
worker-00
worker-01
worker-02

It was supposed to show only the node 'win2k19dc' where I was trying to bootstrap. But it shows the other 3 nodes which also has '192.168.200.2' in the beginning of the IP.

As a workaround I modified the line to have a space in the end, not sure if this is the right way.
shell: "oc get node -o wide |awk '/{{ inventory_hostname }} / || /{{ private_ip }} / {print $1}'"

The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

• release-4.16
• release-4.17

For more information, see the branching documentation.

The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

• release-4.5
• release-4.6
• release-4.4

Contact the Test Platform or Automated Release teams for more information.

With ocp 4.4.7 I see :

$ oc version -o json | jq -r '.serverVersion.gitVersion'
v1.17.1+f5fb168

This breaks tools/ansible/tasks/wsu/main.yaml ... I think we need to remove the +f5fb168 suffix

With this configuration on azure, I found pulling from the ImageStream didn't work. I see -

$ oc describe pod pmml-scoring-service-77757499d7-qqjnq
...
Events:
  Type     Reason     Age                From                      Message
  ----     ------     ----               ----                      -------
  Normal   Scheduled  <unknown>          default-scheduler         Successfully assigned default/pmml-scoring-service-77757499d7-qqjnq to winworker-svad8
  Warning  Failed     27s (x3 over 54s)  kubelet, winworker-svad8  Back-off pulling image "image-registry.openshift-image-registry.svc:5000/default/scoring-service-base-win:latest"
  Normal   Pulling    12s (x3 over 54s)  kubelet, winworker-svad8  Pulling image "image-registry.openshift-image-registry.svc:5000/default/scoring-service-base-win:latest"
  Warning  Failed     12s (x3 over 54s)  kubelet, winworker-svad8  Failed to pull image "image-registry.openshift-image-registry.svc:5000/default/scoring-service-base-win:latest": rpc error: code = Unknown desc = Error response from daemon: Get https://image-registry.openshift-image-registry.svc:5000/v2/: dial tcp: lookup image-registry.openshift-image-registry.svc: no such host

However I found the following did work -

• login to windows server
• add public imagestream address to C:\PrograData\doker\config\daemon.json as an insecure registry
• Restart-Service *docker*
• docker login ... public imagestream address
• docker pull public imagestream address/default/scoring-service-base-win:latest
• docker tag public imagestream address/default/scoring-service-base-win:latest scoring-service-base-win:latest
• update the yaml to use image address scoring-service-base-win:latest

It would be good to know if this configuration is designed to use the ImageStream, or if there is a way to push a image to the windows server.

Thanks !