Comment 2 for bug 1418719

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