Bug 1529478 - pods were in ContainerCreating status while enabling cri-o behind proxy [NEEDINFO]
Summary: pods were in ContainerCreating status while enabling cri-o behind proxy
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer   
(Show other bugs)
Version: 3.9.0
Hardware: Unspecified Unspecified
Target Milestone: ---
: 3.9.0
Assignee: Giuseppe Scrivano
QA Contact: Gan Huang
Depends On:
TreeView+ depends on / blocked
Reported: 2017-12-28 09:44 UTC by Gan Huang
Modified: 2018-03-28 14:17 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-03-28 14:17:25 UTC
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
gscrivan: needinfo? (mpatel)

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 None None None 2018-03-28 14:17 UTC

Description Gan Huang 2017-12-28 09:44:56 UTC
Description of problem:
Trigger installation with cri-o enabled behind proxy, it turned out that all the pods were in ContainerCreating status.

Version-Release number of the following components:
# crio --version
crio version 1.0.6

How reproducible:

Steps to Reproduce:
1. Trigger installation with cri-o enabled behind proxy
# cat inventory


Actual results:
# oc get pods
NAME                        READY     STATUS              RESTARTS   AGE
docker-registry-1-deploy    0/1       ContainerCreating   0          55m
registry-console-1-deploy   0/1       ContainerCreating   0          45m
router-1-deploy             0/1       ContainerCreating   0          1h

# oc describe po registry-console-1-deploy


  Type     Reason                  Age                From                    Message
  ----     ------                  ----               ----                    -------
  Normal   Scheduled               45m                default-scheduler       Successfully assigned registry-console-1-deploy to
  Normal   SuccessfulMountVolume   45m                kubelet,  MountVolume.SetUp succeeded for volume "deployer-token-n9rhs"
  Warning  FailedCreatePodSandBox  5m (x33 over 44m)  kubelet,  Failed create pod sandbox.

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 2 Giuseppe Scrivano 2018-01-04 19:16:56 UTC
The Environment= in the service file won't affect the syscontainer.

Could you try adding the same information to the /var/lib/containers/atomic/cri-o.0/config.json file (under env) and restarting the cri-o service?  Does that solve the problem?

As I've opened a PR for using /etc/sysconfig/crio-storage and /etc/sysconfig/crio-network from within the system container.

Just to be sure, Mrunal, passing these env variables is enough or is there need to do something more?

Comment 3 Giuseppe Scrivano 2018-01-04 19:21:25 UTC
link to the PR for CRI-O system containers: https://github.com/kubernetes-incubator/cri-o/pull/1245

Comment 4 Gan Huang 2018-01-05 04:49:03 UTC
(In reply to Giuseppe Scrivano from comment #2)
> The Environment= in the service file won't affect the syscontainer.
> Could you try adding the same information to the
> /var/lib/containers/atomic/cri-o.0/config.json file (under env) and
> restarting the cri-o service?  Does that solve the problem?

Thanks Giuseppe! That's helpful.

Comment 5 Giuseppe Scrivano 2018-01-05 09:11:38 UTC
Thanks for confirming it.  I've opened a PR for openshift-ansible here:


Comment 7 Gan Huang 2018-01-30 08:42:05 UTC
Tested in openshift-ansible-3.9.0-0.31.0.git.0.e0a0ad8.el7.noarch.rpm

# crio --version
crio version 1.9.1

The configurations have been added:
# cat /etc/sysconfig/crio-network 

Pods are still in ContainerCreating status, same error as comment 1.

Comment 8 Giuseppe Scrivano 2018-01-30 09:35:20 UTC
@Gan, thanks for the info.  Could you try to modify "/etc/sysconfig/crio-network" and set it to:

export HTTP_PROXY=http://file.rdu.redhat.com:3128
export HTTPS_PROXY=http://file.rdu.redhat.com:3128
export NO_PROXY=.cluster.local,.svc,,

then restart cri-o.

Does it make any difference?

Comment 9 Gan Huang 2018-01-30 09:41:36 UTC
Yes, the pods running now.

Comment 10 Giuseppe Scrivano 2018-01-30 10:16:46 UTC
Thanks, I opened a PR here:


Comment 11 Xiaoli Tian 2018-03-07 03:15:01 UTC
The PR has been merged

Comment 12 Gan Huang 2018-03-08 06:53:02 UTC
Verified in openshift-ansible-3.9.3-1.git.0.e166207.el7.noarch.rpm

Comment 15 errata-xmlrpc 2018-03-28 14:17:25 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.