Linked ticket: https://github.com/openvstorage/framework/issues/790
When using the API and sending the wrong data (or missed some requirements eg. DB role)
You are unable to manage this vpool and you lose the write cache because of the unusable vpool.
This only occurs when extending using the API itself and supplying the wrong information. The vpool immediately starts to setup/extend but the checks come to late and the vpool cannot recover.
Packages
ii openvstorage 2.7.9-rev.4463.0761b63-1 amd64 openvStorage
ii openvstorage-backend 1.7.9-rev.889.63f8d79-1 amd64 openvStorage Backend plugin
ii openvstorage-backend-core 1.7.9-rev.889.63f8d79-1 amd64 openvStorage Backend plugin core
ii openvstorage-backend-webapps 1.7.9-rev.889.63f8d79-1 amd64 openvStorage Backend plugin Web Applications
ii openvstorage-core 2.7.9-rev.4463.0761b63-1 amd64 openvStorage core
ii openvstorage-hc 1.7.9-rev.889.63f8d79-1 amd64 openvStorage Backend plugin HyperConverged
ii openvstorage-sdm 1.6.9-rev.508.9903a29-1 amd64 Open vStorage Backend ASD Manager
ii openvstorage-webapps 2.7.9-rev.4463.0761b63-1 amd64 openvStorage Web Applications
Problem description
Linked ticket: https://github.com/openvstorage/framework/issues/790 When using the API and sending the wrong data (or missed some requirements eg. DB role) You are unable to manage this vpool and you lose the write cache because of the unusable vpool.
This only occurs when extending using the API itself and supplying the wrong information. The vpool immediately starts to setup/extend but the checks come to late and the vpool cannot recover.
Packages