Zun

Init container which host is None

Bug #1736897 reported by chengyang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zun
Triaged
Medium
chengyang

Bug Description

Sometimes, restart zun-api service during create a new container will cause host is None. So during zun-compute service restart, we need to filter container which host is None and init its status

chengyang (chengyang)
Changed in zun:
assignee: nobody → chengyang (chengyang)
description: updated
hongbin (hongbin034)
Changed in zun:
status: New → Triaged
importance: Undecided → Low
importance: Low → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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