Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

podman kube play fails with containers starting before infra container #2450

Closed
ikke-t opened this issue Feb 26, 2019 · 1 comment
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@ikke-t
Copy link

ikke-t commented Feb 26, 2019

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

podman play kube starts container before infra container, and thus fails starting due dependency problem.

Steps to reproduce the issue:

  1. create yaml file:
apiVersion: v1
kind: Pod
metadata:
  labels:
    app: postgres
  name: postgres-pod
spec:
  containers:
  - command:
    - docker-entrypoint.sh
    - postgres
    env:
    - name: PATH
      value: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/postgresql/9.6/bin
    - name: TERM
      value: xterm
    - name: HOSTNAME
    - name: container
      value: podman
    - name: GOSU_VERSION
      value: "1.11"
    - name: LANG
      value: en_US.utf8
    - name: POSTGRES_PASSWORD
      value: pg
    - name: POSTGRES_DB
      value: test
    - name: PG_VERSION
      value: 9.6.11-1.pgdg90+1
    - name: PGDATA
      value: /var/lib/postgresql/data/pgdata
    - name: POSTGRES_USER
      value: pg
    - name: PG_MAJOR
      value: "9.6"
    image: docker.io/library/postgres:9.6
    name: postgres
    resources: {}
    securityContext:
      allowPrivilegeEscalation: true
      capabilities: {}
      privileged: false
      readOnlyRootFilesystem: false
    workingDir: /
status: {}
  1. run podman play kube postgres.yml
$ sudo podman play kube postgres.yml

Describe the results you received:

Error for dependency:

$ sudo podman play kube postgres.yml
9f50d3ecea7f1833a6091fe4292904eeff1c865c9a8030d00d6c7bce6ca205ae
Error: some dependencies of container 88e482ad10967460ead5700a1bec2cde62037805ec182c61ff45467d0a55d0b9 are not started: 739cd68a3d1f672d1a339a88445
f172d16b5288ee3b265fb72ed1a39e59936a5: container state improper

Describe the results you expected:

starting posgres pod

Additional information you deem important (e.g. issue happens only occasionally):

$ sudo podman ps -a
CONTAINER ID  IMAGE                                   COMMAND               CREATED         STATUS         PORTS                                                                                             NAMES
88e482ad1096  docker.io/library/postgres:9.6          docker-entrypoint...  12 minutes ago  Created                                                                                                          postgres
739cd68a3d1f  k8s.gcr.io/pause:3.1                                          12 minutes ago  Created                                                                                                          9f50d3ecea7f-infra

Output of podman version:

see from: #2445

Output of podman info --debug:

latest nightly

see from: #2445

Additional environment details (AWS, VirtualBox, physical, etc.):

@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Feb 26, 2019
@baude
Copy link
Member

baude commented Feb 26, 2019

this is already fixed upstream

@baude baude closed this as completed Feb 26, 2019
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

3 participants