Problem with delete clusters
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
magnum (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After forming a cluster of kubernetes machines
the process inserts & builds various LVM based volumes.
However the process seems flawed.
the Base volume is given a name say:
volume-
But a the process evolves the docker volumes that reside INSIDE the clusters are called:
docker-pool docker twi-a-t--- 2.00g
a cluster of 2 machines produces the following:
docker-pool docker twi-a-t--- 2.00g
docker-pool docker twi---t-p- 2.00g
Two IDENTICALLY named units....
When the cluster is ready to be torn down with delete the process fails:
Stderr: u'File descriptor 20 (/dev/urandom) leaked on lvremove invocation. Parent PID 15349: /usr/bin/python2\n Logical volume cinder-
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
2018-06-16 11:08:06.884 4492 ERROR oslo_messaging.
The delete is against the LVM NAMED root volume, it fails because the "docker" volumes STILL exist so it fails.
ALSO since multiple clusters can be instigated and they all build volumes called "docker-pool"
you cannot remove them with a simple:
lvremove -f docker/docker-pool
Multiple VGs found with the same name: skipping docker
Use --select vg_uuid=<uuid> in place of the VG name.
Magnum fails to correctly handle the naming of LVM volumes and fails to retrieve the UUID associated with the named LVM container. this leads to potential failure when mutiple devices exist during takedown of the container.
this then cascades up the stack