search

openvstorage / integrationtests

Open vStorage automated integration tests.
Other
0 stars 1 forks source link

Failed test: advanced_dtl_vdisk_test #583

Open jake9050 opened 7 years ago

jake9050 commented 7 years ago

This test complains about non-existing namespaces:

10.100.199.191 - ovs-volumedriver_myvpool01.service: 2017-07-28 02:17:56 751703 +0200 - ovs-node01-1604 - 31708/0x00007f303a7fc700 - volumedriverfs/AlbaConnection - 000000000000bb99 - error - convert_exceptions_: read object: caught Alba proxy exception: Proxy_protocol.Protocol.Error.NamespaceDoesNotExist 10.100.199.191 - ovs-volumedriver_myvpool01.service: 2017-07-28 02:17:56 751859 +0200 - ovs-node01-1604 - 31708/0x00007f303a7fc700 - volumedriverfs/BackendConnectionInterfaceLogger - 000000000000bb9a - error - ~Logger: Exiting read for 4e8a8079-d93b-487e-ae2c-b0466f78bd8d snapshots.xml with exception 10.100.199.191 - ovs-volumedriver_myvpool01.service: 2017-07-28 02:17:56 751885 +0200 - ovs-node01-1604 - 31708/0x00007f303a7fc700 - volumedriverfs/BackendConnectionInterfaceLogger - 000000000000bb9b - error - ~Logger: Exiting read for 4e8a8079-d93b-487e-ae2c-b0466f78bd8d 10.100.199.191 - ovs-volumedriver_myvpool01.service: 2017-07-28 02:17:56 751954 +0200 - ovs-node01-1604 - 31708/0x00007f303a7fc700 - volumedriverfs/BackendInterface - 000000000000bb9c - error - fillObject: Problem getting snapshots.xml from 4e8a8079-d93b-487e-ae2c-b0466f78bd8d: BackendException: namespace does not exist

This is most likely caused by the automatic snapshotting that is not aware of dissapeared test namespace. The namespace is already deleted when the system tries to snapshot it, and throws this.

Workaround is disabling automatic snapshotting @ start of testing

JeffreyDevloo commented 7 years ago

The namespace should still be present as this test is only killing the proxies to verify the DTL. This seems like an issue with Alba? @jake9050 Was the volume still present at the time that snapshotting would occur?