Skip to content
This repository has been archived by the owner on Jul 27, 2022. It is now read-only.

when a container has no parent pod, the /cluster/resources/containers throws an error #70

Closed
supriyagarg opened this issue Jun 3, 2015 · 1 comment
Closed

when a container has no parent pod, the /cluster/resources/containers throws an error #70

supriyagarg opened this issue Jun 3, 2015 · 1 comment
Assignees
@EranGabber
Labels
bug priority/P1

Comments

@supriyagarg
Copy link
Contributor

It is possible to have a container with no parent pod. So when the parent_pod_id is None, instead of throwing an error, we should record the container.

E.g. of such a scenario:

When the cluster-insight container was started on a minion directly (rather than using the replication controller), this error was thrown.
@EranGabber
Copy link
Contributor

The error message is:
"error_message": "u'missing or invalid parent pod ID in container cluster-insight'",

@EranGabber EranGabber mentioned this issue Jun 16, 2015
Closed
EranGabber added a commit to EranGabber/cluster-insight that referenced this issue Jun 18, 2015
@EranGabber
Handle containers without parent pods correctly.
e90e6a9 
Fixes google#37, google#70.
@EranGabber EranGabber mentioned this issue Jun 18, 2015
Merged
EranGabber added a commit to EranGabber/cluster-insight that referenced this issue Jun 20, 2015
@EranGabber
Create unique names for containers running outide pods.
defe577 
This is a problem caused by handling issue google#70.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@EranGabber EranGabber

Labels
bug priority/P1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@EranGabber @supriyagarg