Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1713395 - Cannot run systemd in pod in Kubernetes with CRI-O
Summary: Cannot run systemd in pod in Kubernetes with CRI-O
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kubernetes
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Chaloupka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1740730 1743017 1754170
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-23 14:47 UTC by Jan Pazdziora
Modified: 2020-05-26 14:35 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 14:35:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Pazdziora 2019-05-23 14:47:06 UTC
Description of problem:

Attempt to run /usr/sbin/init in container in pod in Kubernetes with CRI-O never gives working pod.

Version-Release number of selected component (if applicable):

kubernetes-node-1.12.5-2.fc29.x86_64
cri-o-1.12.0-12.dev.gitc4f232a.fc29.x86_64

How reproducible:

Deterministic.

Steps to Reproduce:
1. Have Kubernetes all-on-one based on https://kubernetes.io/docs/getting-started-guides/fedora/fedora_manual_config/ but with CRI-O configured instead of docker using

   sed -i 's/docker/crio/' /usr/lib/systemd/system/kubelet.service
   sed -i 's#^\(KUBELET_ARGS=.*\)"#\1 --container-runtime=remote --container-runtime-endpoint=/var/run/crio/crio.sock --runtime-request-timeout=5m"#' /etc/kubernetes/kubelet

2. Check that "normal" pod work, for example using
   kubectl create -f nginx.yaml
   on nginx.yaml containing

apiVersion: v1
kind: Pod
metadata:
  name: nginx
spec:
  containers:
  - name: nginx
    image: nginx:latest
    ports:
    - containerPort: 80

3. Have systemd.yaml with content:

apiVersion: v1
kind: Pod
metadata:
  name: systemd-test
  labels:
    app: systemd-test
spec:
  restartPolicy: Never
  containers:
  - name: systemd-test
    image: registry.fedoraproject.org/fedora:28
    command:
    - /usr/sbin/init
    env:
    - name: container
      value: oci
    readinessProbe:
      exec:
        command: [ "/usr/bin/systemctl", "status" ]
      initialDelaySeconds: 60
      timeoutSeconds: 10
      periodSeconds: 10
      successThreshold: 1
      failureThreshold: 3

4. Run kubectl create -f systemd.yaml
5. Check kubectl get pods

Actual results:

NAME             READY   STATUS    RESTARTS   AGE
nginx            1/1     Running   0          1h
systemd-test     0/1     Running   0          12m

Expected results:

NAME             READY   STATUS    RESTARTS   AGE
nginx            1/1     Running   0          1h
systemd-test     1/1     Running   0          12m

Additional info:

Running  kubectl exec -ti systemd-test systemctl prints

System has not been booted with systemd as init system (PID 1). Can't operate.
command terminated with exit code 1

This is a regression against Fedora 28 with

kubernetes-node-1.10.1-0.fc28.x86_64
cri-o-1.11.2-1.git3eac3b2.fc28.x86_64

Fedora 30 with kubernetes-node-1.13.5-1.fc30.x86_64 and cri-o-2:1.13.0-1.gite8a2525.module_f30+3068+5f412e7f.x86_64 has the same problem.

Comment 1 Jan Pazdziora 2019-05-23 14:49:53 UTC
This issue affects testing FreeIPA container on Kubernetes with CRI-O on Fedora 29+.

Comment 2 Jan Pazdziora 2019-05-23 15:32:38 UTC
With docker instead of CRI-O, things work on Fedora 29 fine.

Comment 3 Ben Cotton 2019-10-31 19:17:31 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Jan Pazdziora 2019-11-01 13:41:19 UTC
Updating version because we have a reason to believe the issue is still present on Fedora 30.

Unfortunately, on Fedora 30, we are currently blocked by bug 1743017 a.k.a. bug 1754170 a.k.a. bug 1740730, so I couldn't test there.

Comment 5 Ben Cotton 2020-04-30 20:47:43 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2020-05-26 14:35:45 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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