Deleting a pod that doesn't exist in kubernetes fails with latest kubernetes
Bug #1435575 reported by
Andrew Melton
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Magnum |
Fix Released
|
Undecided
|
Andrew Melton | ||
Bug Description
The log message has changed from "pod 'x' not found" to "pods 'x' not found".
| Changed in magnum: | |
| assignee: | nobody → Andrew Melton (andrew-melton) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to magnum (master) | #1 |
| Changed in magnum: | |
| status: | In Progress → Fix Committed |
| Changed in magnum: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 375f7c272c59390
Author: Andrew Melton <email address hidden>
Date: Mon Mar 23 15:06:21 2015 -0700
Update pod_delete call for new log message
The latest kubernetes has changed the log message when a pod
is not found, from "pod 'x' not found" to "pods 'x' not found".
To handle this, and maintain compatibility, this removes the
check for 'pod ' and just checks the log message for
"'x' not found".
Change-Id: Id3a847a576beed
Closes-Bug: #1435575