replication controller created pods don't show up in pod-list output

[wkh]

When you create a replication controller k8s creates the number of pods specified by the rc's replica value. Most of those pods don't show up in the output of `magnum pod-list`, in fact only the ones that were created prior to the rc and "adopted" by it show up. Worse, there is no way - outside of using kubectl - to delete those "invisible" pods.

pod-list should probably use the k8s API (or kubectl in the interim) to get the list of pods (and their state) rather than trying to manage it in the database.

[Guangya Liu (Jay Lau) (jay-lau-513)]

I think this project is related to k8s client https://blueprints.launchpad.net/magnum/+spec/python-k8sclient , we may need to call client to get pods from rc and then put all pods to database.

A short solution is always using "kubectl get pods" to get all pods, thoughts?

[wkh (wkharold)]

That seems like the simplest thing that could possibly work. Re: the
blueprint, I'm not sure how much value there is to putting the pods in the
database unless we can ensure that the database is updated when ever pods
are destroyed/created ... WkH

From: Jay Lau <email address hidden>
To: Ward K Harold/Austin/IBM@IBMUS
Date: 02/14/2015 11:30 PM
Subject: [Bug 1418719] Re: replication controller created pods
don't show up in pod-list output
Sent by: <email address hidden>

I think this project is related to k8s client
https://blueprints.launchpad.net/magnum/+spec/python-k8sclient , we may
need to call client to get pods from rc and then put all pods to
database.

A short solution is always using "kubectl get pods" to get all pods,
thoughts?

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1418719

Title:
  replication controller created pods don't show up in pod-list output

Status in Magnum - Containers for OpenStack:
  Triaged

Bug description:
  When you create a replication controller k8s creates the number of
  pods specified by the rc's replica value. Most of those pods don't
  show up in the output of `magnum pod-list`, in fact only the ones that
  were created prior to the rc and "adopted" by it show up. Worse, there
  is no way - outside of using kubectl - to delete those "invisible"
  pods.

  pod-list should probably use the k8s API (or kubectl in the interim)
  to get the list of pods (and their state) rather than trying to manage
  it in the database.

To manage notifications about this bug go to:
https://bugs.launchpad.net/magnum/+bug/1418719/+subscriptions

[Andrew Melton (andrew-melton)]

I'm not sure this is a good idea. If the pods that are created by Kubernetes as part of a replication controller are managed by Kubernetes itself, should Magnum really be showing them as pods the user can interact with? Or, should we only show the pods Magnum itself is managing?

[vikas choudhary (choudharyvikas16)]

@Andrew
I think magnum true state of the system to user. Also 'pod-list' means complete pod-list(including rc created) . Let say user created a RC and now he wants to ensure if corresponding pod got created or not.This should be possible to verify using magnum apis only.

[vikas choudhary (choudharyvikas16)]

https://review.openstack.org/#/c/221150/

[vikas choudhary (choudharyvikas16)]

This will get fixed with bp "objects-from-bay" implementation.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Adrian Otto (<email address hidden>) on branch: master
Review: https://review.openstack.org/221150
Reason: Vikas,

It has been almost two weeks since the last patch revision on this patch, and Hongbin placed a -2 vote on it. Unless that -2 vote is removed, this patch can not be merged, and should no longer be considered by reviewers. If you are able to convince Hongbin to change his vote, then we can un-abandon this patch, and continue making revisions.

Thanks,

Adrian

[hongbin (hongbin034)]

Should be fixed now, by this BP https://blueprints.launchpad.net/magnum/+spec/objects-from-bay