Added an SRU Template here as well, while we did drive this more as an MRE in the past while I was cleaning up on Steve's request lets make all related bugs proper SRUs to be sure on the next round.
** Description changed: + [Impact] + + * Upstream identified an issue that can occur on aborted (or + due to communication issues while doing) quiesced snapshots. + + * Backport the upstream changes as part of our work getting the latest + 10.3.5 to the latest Ubuntu LTS (Bionic) + + [Test Case] + + * This is hard to test, but fortunately VMWare who have the right setup + for this tested our change from a PPA. I'll ask for that again on SRU. + Never the less I'll outline roughly what is needed to trigger [1]: + 1. Use the host side interface to trigger a quiesced snapshot + 2. this is the hard part - have communication failures between vmtools + (guest) and VMX (host) while this is ongoing. + 3. From the Hosts POV the operation is aborted, but vmtools sends a + manifest eventually + 4. Receiving this will make VMX reply a error (as it didn't wait for + anything like it) + 5. Finally this broke the state machine and in subsequent cases vmtools + will not send a manifest again + * Further related fixes make sure vmtoolsd give up if VMX aborted the + snapshot [2] and another [3] makes sure manifests are always sent to + avoid any desync between VMX and vmtoolsd + + [1]: https://github.com/vmware/open-vm-tools/commit/a1306fcbb6de6eae5344d5d74747068ea89aa5fc + [2]: https://github.com/vmware/open-vm-tools/commit/0c9174716ba828899418ba07efc3aab0bff004cc + [3]: https://github.com/vmware/open-vm-tools/commit/c31710b3942f48b1c11ebde36f34e7e159d1cbf0 + + [Regression Potential] + + * This is quite a change to the snapshot handling, so in theory there a + regression has to be assumed. Due to a lack of testcases and expertise + on our side that was handed to VMWare itself who have a much wider + matrix of tests and setups to run them on. + This was tested and confirmed good (even before the change made + it upstream). + * Furthermore those kind of snapshots are relevant to those + who use them (and they most likely want the fix for reliability as you + could get into a state where no further snapshots were possible). But + OTOH the majority of users of the open-vm-tools package most likely + don't use the feature at all. Fortunately changes are local to only the + vmbackup functionality. + + [Other Info] + + * n/a + + --- + Customers may hit issues with quiesced snapshots under certain circumstances. This is fixed in a branch forked from 10.3.5: https://github.com/vmware/open-vm-tools/tree/stable-10.3.5-quiesced- snapshot A more detailed description of the issue can be found in the individual commit messages. Also filed at Debian: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=921470 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814832 Title: Correct and/or improve handling of certain quiesced snapshot failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1814832/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
