Pod status not synced from kubernetes to magnum

Bug #1448332 reported by Andrew Melton
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Magnum
Invalid
High
Unassigned

Bug Description

After creating a pod, kubectl will status as running, but magnum pod-show will show it as still pending. Those statuses should be synced.

Example: http://paste.openstack.org/show/205817/

Revision history for this message
Madhuri Kumari (madhuri-rai07) wrote :

What approach should we follow to sync the status?
1. Sync each time whenever pod-show is called.
2. Poll and sync.

I think for now syncing the status with pod-show is better.
We can discuss for this in irc as we have other Kubernetes resources and their status also need to be synced.

Changed in magnum:
assignee: nobody → Madhuri Kumari (madhuri-rai07)
Revision history for this message
Steven Dake (sdake) wrote :

Should be fixed by the native clients work.

Changed in magnum:
assignee: Madhuri Kumari (madhuri-rai07) → Steven Dake (sdake)
status: New → Confirmed
importance: Undecided → High
Changed in magnum:
status: Confirmed → In Progress
Revision history for this message
vikas choudhary (choudharyvikas16) wrote :

Hi StDake,

I have done changes required for read path and pushed for review. Now each read is from k8s api and then syncing local magnum db. Assigning bug to me.

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

Changed in magnum:
assignee: Steven Dake (sdake) → vikas choudhary (choudharyvikas16)
Revision history for this message
vikas choudhary (choudharyvikas16) wrote :

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

Changed in magnum:
assignee: vikas choudhary (choudharyvikas16) → nobody
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on magnum (master)

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

Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
Revision history for this message
hongbin (hongbin034) wrote :
Changed in magnum:
status: In Progress → Fix Committed
Drago (dragorosson)
Changed in magnum:
status: Fix Committed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.