Bug 2069310

Is this the correct 4.8 backport bug because the target release shows as 4.9.z?

kewang,
https://github.com/openshift/kubernetes/pull/1233 needs cherry pick approval to merge and then verified. Once verified on 4.9 we will open a new PR for 4.8. Customer is blocked and waiting in the 4.8 fix.

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.0-0.nightly-2022-04-18-075504   True        False         2m27s   Cluster version is 4.9.0-0.nightly-2022-04-18-075504
 
Created the ruby app and get the Service and pod assigned ip series.
$ oc get svc
NAME         TYPE           CLUSTER-IP   EXTERNAL-IP                            PORT(S)   AGE
kubernetes   ClusterIP      172.30.0.1   <none>                                 443/TCP   24m
openshift    ExternalName   <none>       kubernetes.default.svc.cluster.local   <none>    16m
 
$ oc get pods -o wide
NAME                       READY   STATUS    RESTARTS   AGE   IP            NODE                                                        NOMINATED NODE   READINESS GATES
ruby-hello-world-1-build   1/1     Running   0          17s   10.129.2.15   xxxxx-hmk-6zhcf-worker-b-txdgz.c.openshift-qe.internal   <none>           <none>
 
Get the nodes and chosen one of master node & remove the node to pod networking routes entries.
$ oc get nodes | grep master
xxxxx-hmk-6zhcf-master-0.c.openshift-qe.internal         Ready    master   22m   v1.22.8+c02bd9d
xxxxx-hmk-6zhcf-master-1.c.openshift-qe.internal         Ready    master   22m   v1.22.8+c02bd9d
xxxxx-hmk-6zhcf-master-2.c.openshift-qe.internal         Ready    master   22m   v1.22.8+c02bd9d
 
$ oc debug node/xxxxx-hmk-6zhcf-master-0.c.openshift-qe.internal
Starting pod/xxxxx-hmk-6zhcf-master-0copenshift-qeinternal-debug ...
To use host binaries, run `chroot /host`
Pod IP: 10.0.0.4
If you don't see a command prompt, try pressing enter.
sh-4.4# chroot /host
sh-4.4# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.0.0.1        0.0.0.0         UG    100    0        0 ens4
10.0.0.1        0.0.0.0         255.255.255.255 UH    100    0        0 ens4
10.128.0.0      0.0.0.0         255.252.0.0     U     0      0        0 tun0
172.30.0.0      0.0.0.0         255.255.0.0     U     0      0        0 tun0
sh-4.4# route del -net 10.128.0.0 gw 0.0.0.0 netmask 255.252.0.0 tun0
sh-4.4# route del -net 172.30.0.0 gw 0.0.0.0 netmask 255.255.0.0 tun0
sh-4.4# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.0.0.1        0.0.0.0         UG    100    0        0 ens4
10.0.0.1        0.0.0.0         255.255.255.255 UH    100    0        0 ens4
 
Created inline job object , checked job status.
$ cat job.yaml
apiVersion: batch/v1
kind: Job
metadata:
  name: pi
spec:
  parallelism: 1    
  completions: 1    
  activeDeadlineSeconds: 1800
  backoffLimit: 6  
  template:        
    metadata:
      name: pi
    spec:
      containers:
      - name: pi
        image: perl
        command: ["perl",  "-Mbignum=bpi", "-wle", "print bpi(2000)"]
      restartPolicy: OnFailure    
$ oc create -f job.yaml
job.batch/pi created
 
$ oc get jobs
NAME   COMPLETIONS   DURATION   AGE
pi     1/1           33s        40s
 
Delete the existing pod and check the status.
 
$ oc delete pod ruby-hello-world-7d96bd5c7f-rw9xf
pod "ruby-hello-world-7d96bd5c7f-rw9xf" deleted
 
$ oc get pods
NAME                                READY   STATUS      RESTARTS   AGE
pi--1-5s449                         0/1     Completed   0          102s
ruby-hello-world-1-build            0/1     Completed   0          3m18s
ruby-hello-world-7d96bd5c7f-phvt6   1/1     Running     0          32s
 
Both jobs & pods are Completed/Running without any issue. Hence marked BZ verified

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 (OpenShift Container Platform 4.9.31 bug fix update), 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-2022:1605