Description of problem: Cri-o pod has no "HOSTNAME" environment variable Version-Release number of selected component (if applicable): # openshift version openshift v3.7.0-0.188.0 kubernetes v1.7.6+a08f5eeb62 etcd 3.2.8 crio -v crio version 1.0.2 commit: "29077fa6fbd85f0ca9c453ab1bf1ff7b02bc3f5c" How reproducible: Always Steps to Reproduce: 1.oc run hello --image=aosqe/hello-openshift 2.oc exec -it hello-1-jd2bx env|grep -i hostname 3. Actual results: 2. Output has no "HOSTNAME" Expected results: 2. Output should display "HOSTNAME=balabala" Additional info: For docker runtime, have no this issue.
https://github.com/kubernetes-incubator/cri-o/pull/1113 is the PR for fixing it. This will be available in next release of 1.0.3
Checked with v3.9.0 which cri-o is enabled, and env HOSTNAME work well now. # oc version oc v3.9.0-0.9.0 kubernetes v1.8.1+0d5291c features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://172.16.120.75:8443 openshift v3.9.0-0.9.0 kubernetes v1.8.1+0d5291c
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-2018:0489