Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3122
** Bug watch added: github.com/canonical/cloud-init/issues #3122
https://github.com/canonical/cloud-init/issues/3122
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
No, unless you were afraid that what ticked open-vm-tools into having
issues here being a wider more general issue. But then given that 16.04
is used widely for quite some time I think we can assume it is a corner
case only.
incomplete on the systemd task is ok.
--
You received this bug
So, is there anything requested to be done with Xenial's systemd in this
bug?
** Changed in: systemd (Ubuntu Xenial)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This bug was fixed in the package open-vm-tools -
2:10.2.0-3~ubuntu0.17.10.1
---
open-vm-tools (2:10.2.0-3~ubuntu0.17.10.1) artful; urgency=medium
* backport Bionic open-vm-tools to Artful (LP: #1741390)
- d/control: B-D for dh-autoreconf and dh-systemd
- d/rules: re-add
This bug was fixed in the package open-vm-tools -
2:10.2.0-3~ubuntu0.16.04.1
---
open-vm-tools (2:10.2.0-3~ubuntu0.16.04.1) xenial; urgency=medium
* backport Bionic open-vm-tools to Xenial (LP: #1741390)
- d/control: B-D for dh-autoreconf and dh-systemd
- d/rules: re-add
1. Upgrade from proposed - this is the same for all associated bugs, so
I only documented details in bug 1741390
2. This bug in particular
Running a few restarts and checking
$ systemctl status -l open-vm-tools.service
This checks if the service rules avoid the issue on these systems with older
Hello ChristianEhrhardt, or anyone else affected,
Accepted open-vm-tools into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/open-vm-
tools/2:10.2.0-3~ubuntu0.17.10.1 in a few hours, and then in the
-proposed repository.
Please help us by
Hello ChristianEhrhardt, or anyone else affected,
Accepted open-vm-tools into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/open-vm-
tools/2:10.2.0-3~ubuntu0.16.04.1 in a few hours, and then in the
-proposed repository.
Please help us by
This will only "become" an issue for Xenial/Artful with the backport.
But lets do it right for tracking - so I added/modified tasks for these
releases which allows me to refer changes and changelog to here.
That way with the backport it will "be an issue" for the former
releases, but also
** Also affects: open-vm-tools (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu Artful)
** Changed in: open-vm-tools (Ubuntu Xenial)
Status: Invalid =>
** Merge proposal unlinked:
https://code.launchpad.net/~paelzer/ubuntu/+source/open-vm-tools/+git/open-vm-tools/+merge/341797
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Note: When we do the Xenial backport of the new version of open-vm-tools
(which we plan to do) this becomes an issue. In the same upload I intend
to fix it right away, so it should never effectively exist in the field
(keep invalid, but there might be a fix-released update to open-vm-tools
here at
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/open-vm-tools/+git/open-vm-tools/+merge/341796
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/open-vm-tools/+git/open-vm-tools/+merge/341797
--
You received this bug notification
** Changed in: open-vm-tools (Debian)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1750780
Title:
Race with local file systems
For open-vm-tools this issue will only exist with the planned backport of the
newer version.
Since we will not ship the broken backport as we found it in pre-checks the
correct state for open-vm-tools in xenial is invalid.
** Changed in: open-vm-tools (Ubuntu Xenial)
Status: Triaged =>
With the former update in mind I retried Xenial/Bionic again.
All of it is racy (as we knew), but it never triggered for Bionic.
Xenial (19/33 fails)
Bionic (0/37 fails)
So for now we continue to assume that it is fixed there (by systemd) and
revert our added dependency.
Note: as with the
Thanks Scott for your cross check.
I wonder why my former test failed on each of my tests without writing, but
never the less your extended example is great for the systemd issue that
remains.
Although all of this is still a race, for example with the job above on a
Xenial container I could
I agree with reverting change in bionic, and that xenial still needs
some fix.
I recreated your failure in xenial and agree with your change there.
I used this job as it actually tries to write to the private tmp.
If I change 'ExecStart' below to be just '/bin/true' like in your job,
it does
I'Ll likely revert the Binonic change tmrw morning as we have discussed.
local-fs.target is actually >> the implicit dependency.
But that does not solve the Xenial issue outlined in the former comment.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Installed another Xenial and Bionic in vmware to take a deper look.
- Xenial (with backported open-vm-tools): affected
- Bionic (with the interim fix reverted): no hit in several retries,
explanation below
Systemd fixed it (via our assumed implicit dependency).
In Bionic the PrivateTmp gives it
20 matches
Mail list logo
