Backport open-vm-tools 12.1.0 for jammy

[Bryce Harrington]

[Impact]

 * Without SRUing the newer version users get issues running on more
   recent hypervisors - this is a case of [1] in the SRU policy.

 * Furthermore Upstream releases this as a collection of fixes which is
   usually worth it to pick up.

 * This is not backporting a single fix, but the version of a latter
   Ubuntu release.

 * Two new plugins are provided via new binary packages,
   open-vm-tools-containerinfo and open-vm-tools-salt-minion

[Test Case]

 * TL;DR is "use open-vm-tools" but that can be quite complex for the
   variety of potential Host versions.

 * VMWare itself took ownership of verifying these backports and will test
   the same bits from a PPA and the SRU for the official "ack"

 * Users are invited to test upgrading their own different setups.

 * In general we recommend giving this some extra time in -proposed to see
   if anybody uncovers issues.

[Regression Potential]

 * It is a new version which might contain new issues. This is being
   shipped in kinetic-devel for some weeks, with no new bug reports filed.

 * The addition of new binaries open-vm-tools-containerinfo and
   open-vm-tools-salt-minion are new features and as such may have
   issues, but mitigating that concern is that they're separately
   packaged and not installed by default.

[Other Info]

 * This time the MRE also fixes one bug. We're also backporting that
   fix to earlier LTS's.
 * As agreed back when processing bug 1741390 the real verification of
   open-vm-tools for having the proper test matrix and project ownership
   is on VMWare.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases

[Christian Ehrhardt  (paelzer)]

Now that this is in Kinetic we can update that.

 open-vm-tools | 2:12.1.0-1 | kinetic | source, amd64, arm64

[Christian Ehrhardt  (paelzer)]

We usually only backport the latest version to the latest LTS (as per the agreement with VMware on testing those) trying to balance the SRU regression vs the (virtual) HW compatibility tradeoff.

So I expect this current 12.1.0 only to land in Jammy, but not in B/F also impish is now no more an active release.

[Christian Ehrhardt  (paelzer)]

For awareness - assigning Bryce who looked after open-vm-tools recently.
This isn't a hard assignment, if someone else wants to grab that, let us know.

[Timo Aaltonen (tjaalton)]

Hello Bryce, or anyone else affected,

Accepted open-vm-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/open-vm-tools/2:12.1.0-1~ubuntu0.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[John Wolfe (johnwvmw)]

I have requested the QA team to help with the validation of these open-vm-tools packages from the jammy-proposed repo.

[vmware-gos-Yuhua (yhzou)]

Sanity check with ubuntu 22.04 live server and desktop images

   1) install / upgrade / remove open-vm-tools from -proposed
   2) Install / upgrade / remove open-vm-tools-desktop (only for ubuntu 22.04 desktop image)
   3) tools service and VGAuth service are running when install / upgrade open-vm-tools
   4) tools service and VGAuth service are running after reboot VM
   5) check guestInfo from vmtools
   6) install/remove optional packages:
         open-vm-tools-sdmp
         open-vm-tools-salt-minion
         open-vm-tools-containerinfo

Output suspicious message as above in terminal when I install/remove optional package open-vm-tools-sdmp/ open-vm-tools-salt-minion/open-vm-tools-containerinfo with command "apt-get install/remove xxxx":
    Unknown option: q
    active

Take "apt-get remove open-vm-tools-containerinfo" as example:
 Reading package lists...
 Building dependency tree...
 Reading state information...
 The following packages were automatically installed and are no longer required:
   libc-ares2 libgrpc++1 libgrpc10
 Use 'apt autoremove' to remove them.
 The following packages will be REMOVED:
   open-vm-tools-containerinfo
 0 upgraded, 0 newly installed, 1 to remove and 249 not upgraded.
 After this operation, 997 kB disk space will be freed.
 (Reading database ...
 (Reading database ... 5%
 (Reading database ... 10%
 (Reading database ... 15%
 (Reading database ... 20%
 (Reading database ... 25%
 (Reading database ... 30%
 (Reading database ... 35%
 (Reading database ... 40%
 (Reading database ... 45%
 (Reading database ... 50%
 (Reading database ... 55%
 (Reading database ... 60%
 (Reading database ... 65%
 (Reading database ... 70%
 (Reading database ... 75%
 (Reading database ... 80%
 (Reading database ... 85%
 (Reading database ... 90%
 (Reading database ... 95%
 (Reading database ... 100%
 (Reading database ... 198508 files and directories currently installed.)
 Removing open-vm-tools-containerinfo (2:12.1.0-1~ubuntu0.22.04.1) ...
 Unknown option: q
 active

Ignore the suspicious output message "Unknown option: q" or not ? Thanks very much.

Best regards
Yuhua Zou

[Paride Legovini (paride)]

Thanks for doing the verification. Looks like deb-systemd-invoke is being called with the -q flag in the maintainer scripts, but the tool doesn't actually support it. The tools behaves well even with that extra flag (the return codes are the expected ones), but it's not quiet (that's where that "active" string comes from in your log excerpt).

The extra flag has been introduces in Debian in [1], and apparently his issue also affects Debian, but I see no bug report about it. As far as I can tell it's a cosmetic thing, but I won't modify the SRU verification tags for now: I prefer to leave the final word to Bryce.

[1] https://salsa.debian.org/vmware-packaging-team/pkg-open-vm-tools/-/commit/3ece93a147fb6e52517c469e0da27d7f498d1176

[Bryce Harrington (bryce)]

I've filed LP: #1999945 and assigned myself for the -q flag fix. Since the commit that added it was from 2 years ago, this issue's already in the wild. I think we can ignore it for the sake of this SRU. I will be doing another open-vm-tools MRE next month (LP: #1998558) and will include the fix there.

[Launchpad Janitor (janitor)]

This bug was fixed in the package open-vm-tools - 2:12.1.0-1~ubuntu0.22.04.1

---------------
open-vm-tools (2:12.1.0-1~ubuntu0.22.04.1) jammy; urgency=medium

  * Backport recent open-vm-tools (LP: #1975767)
    - Fixes issue with "udevadm trigger" affecting all devices
      that can cause unwanted side-effects.
      (LP: #1968354)
    - Adds new binary open-vm-tools-containerinfo that installs the
      vRealize Container Info plugin, which captures and publishes
      information about running containers inside the guest.
    - Adds new binary open-vm-tools-salt-minion that installs the Salt
      Minion plugin for event driven IT automation, remote task execution,
      and configuration management.

 -- Bryce Harrington <email address hidden> Mon, 19 Sep 2022 17:52:55 +0000

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for open-vm-tools has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Christian Ehrhardt  (paelzer)]

This was a backport, but not an MRE, while cleaning up ambiguity I'm fixing the title of this old bug.