-
Bug
-
Resolution: Done
-
Undefined
-
4.14
-
None
-
No
-
False
-
Description of problem:
Error when try to rsh into the running Pod
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Deploy RHEL 9 VM instance 2. Rename VG from rhel to any custom name 3. Install microshift on the VM instance 4. Check Microshift service "Running" 5. Create a PVC using default Storage Class 6. Create a pod/deployemnt using PVC from step-5 7. Pvc bound, new PV provisioned and Pod is running 8. Try to rsh into Pod, getting error => Error from server: error dialing backend: dial tcp: lookup microshift- dev.local on 10.11.5.160:53: no such host
Pvc config yaml: kind: PersistentVolumeClaim apiVersion: v1 metadata: name: mypvc spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi
Deployment config yaml: kind: Deployment apiVersion: apps/v1 metadata: name: my-dep spec: replicas: 1 selector: matchLabels: app: http-server template: metadata: labels: app: http-server spec: containers: - name: http-server image: quay.io/openshifttest/hello-openshift@sha256:b1aabe8c8272f750ce757b6c4263a2712796297511e0c6df79144ee188933623 ports: - name: httpd containerPort: 80 volumeMounts: - name: local mountPath: /mnt/storage volumes: - name: local persistentVolumeClaim: claimName: mypvc
Actual results:
Expected results:
rsh into pod successful
Additional info:
journalctl shows below error: microshift-dev.local microshift[46610]: kube-apiserver E0324 17:11:24.351286 46610 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"error dialing backend: dial tcp: lookup microshift-dev.local on 10.11.5.160:53: no such host"}: error dialing backend: dial tcp: lookup microshift-dev.local on 10.11.5.160:53: no such host
- is duplicated by
-
OCPBUGS-10766 MicroShift pods cannot resolve local host name
- Closed