test: update multus canary test
Update the multus canary test to reflect modern knowledge about how it should be configured. No longer test for the network device in OSD pods. Pods will utterly fail to start if Multus is unable to attach interfaces. Instead, look to the OSD map to test the connections more wholistically. OSDs must have map IPs that include both public and cluster network. This implicitly tests that the interfaces exist in the Pod, and it additionally verifies other details, like Ceph `*_network` configs are set propertly. Signed-off-by: Blaine Gardner <blaine.gardner@ibm.com>
This commit is contained in:
3 files changed
+45
-45
No files matched your search
@@ -603,6 +603,14 @@ function deploy_multus_cluster() {
|
||||
kubectl create -f nfs-test.yaml
|
||||
}
|
||||
|
||||
function test_multus_connections() {
|
||||
EXEC='kubectl -n rook-ceph exec -t deploy/rook-ceph-tools -- ceph --connect-timeout 10'
|
||||
# each OSD should exist on both public and cluster network
|
||||
$EXEC osd dump | grep osd.0 | grep "192.168.20." | grep "192.168.21."
|
||||
# MDSes should exist on public network and NOT on cluster network
|
||||
$EXEC fs dump | grep myfs-a | grep "192.168.20." | grep -v "192.168.21."
|
||||
}
|
||||
|
||||
function create_operator_toolbox() {
|
||||
cd deploy/examples
|
||||
sed -i "s|image: rook/ceph:.*|image: rook/ceph:local-build|g" toolbox-operator-image.yaml
|
||||
|
||||
Reference in new issue
Block a user