)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":24245,"name":"Harald Jensås","email":"hjensas@redhat.com","username":"harald.jensas"},"change_message_id":"fb349598446e62d0f2369161e96d9da411c5f8e7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e9bb850e_cf04d5ed","updated":"2021-11-09 21:24:16.000000000","message":"I put a comment on bug: https://bugs.launchpad.net/tripleo/+bug/1950137/comments/3\n\nWhile looking at this with Julia it seems there is NBD_DISCONNECT -\u003e shutdown sockets. But then some IO errors are logged. Later when connecting the nbd again, there is an error that the device is being set up by another task.\n\nLet\u0027s merge this revert, and keep investigating.","commit_id":"221c275a9bc13b20a75d6467eb1a6da63043ed1d"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"ecdca369f862bdcabdf46011687fb80c575d0246","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7006d73e_1621e7e9","updated":"2021-11-09 21:26:25.000000000","message":"It *looks* like the execution ends up trying to reuse the same nbd entry twice, and it *may* be that the first usage of the nbd entry does not actually exit, or is still locked when we try to re-use.\n\nIn https://logserver.rdoproject.org/51/817251/1/openstack-check/tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset001/7430611/logs/undercloud/var/log/extra/journal.txt.gz we can see io errors after the first session disconnect, then we try to run again  with nbd0 already apparently being locked \"kernel: block nbd0: Device being setup by another task\".\n\nFor the first execution, we see the filesystem interaction. The second, we appear to just exit upon failure to setup the attachment. It looks like, at least based on the very first commit of the tool that we don\u0027t ensure the pv is gone/removed, we\u0027re just looking for changes in volume groups. So it may be the LVM layer is still locking the device up.\n\nRealistically, we need to auto-increment and move to nbd1 and also ensure we\u0027ve done everything possible to cause the device lock to be dropped.","commit_id":"221c275a9bc13b20a75d6467eb1a6da63043ed1d"},{"author":{"_account_id":9976,"name":"Ronelle Landy","email":"rlandy@redhat.com","username":"rlandy"},"change_message_id":"cdbdddad2f3756854e37e16100154eb5b7fcb513","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d79eab5d_efa64a79","updated":"2021-11-09 18:38:09.000000000","message":"testing","commit_id":"221c275a9bc13b20a75d6467eb1a6da63043ed1d"}]}