© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
It looks like when the extend happens, the target has "problems", which results in an iSCSI connection failure [1]:
Sep 24 10:55:24 ubuntu-
Which in turn results in the iscsiadm tool returning an error when being called [2]:
Sep 24 10:55:26.759691 ubuntu-
Sep 24 10:55:26.760040 ubuntu-
But just a couple of seconds later the "iscsiadm -m session" command is run successfully [3] for another test.
And the connection for the first device seems to get fixed, and the size change detected [4]:
Sep 24 10:55:28 ubuntu-
Sep 24 10:55:28 ubuntu-
Sep 24 10:55:28 ubuntu-
In summary, it looks like the extend is the cause of the issue, as it creates connection errors that then make the iscsiadm command fail.
This can probably be fixed in os-brick by adding a simple retry decorator with exponential backoff on the extend_volume method.
But if extending a volume breaks "iscsiadm -m session", that means that the extend probably needs to be a mutually exclusive operation, or we need a new way of retrieving that information without relying on iscsiadm.
[1]: http://
[2]: http://
[3]: http://
[4]: http://