Hi Christian,
I have filed a new bug as below.
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1773931
If have any problems, please kindly tell me!
Thanks!
Yanhui
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Yanhui,
thanks for the retest the issues are not part of the ppa/SRU.
Also this is released already, so no need for the ppa anymore.
#2 is intentional if you had a modified tools.conf due to conffile
handling
#1 we can look at when working on the next version.
If you could outline - best
Env:
VMs:
* ubuntu-16.04.4-desktop-amd64
* ubuntu-16.04.4-server-amd64
* ubuntu-17.10-desktop-amd64
* ubuntu-17.10-server-amd64
open-vm-tools version: 10.2.0.1608(build-7253323) from ppa:ci-train-ppa-
service/3152 or using the default repository
Result:
open-vm-tools can be installed and
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
The Upload was also tested by the reporter against another bug that will be
fixed by the backport.
So I dup'ed 1668244 onto this bug here.
+1 on the backport adressing more issues :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you all for your help!
I'll get this version and test as soon as I'm able.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390
Title:
Please backport open-vm-tools 2:10.2.0-3 (main) from
1. Upgrade from proposed
Binaries usually installed are open-vm-tools and open-vm-tools-desktop
I see 10.2.0-3~... in Xenial and Artful, checking if the upgrade works without
issues.
On the upgrade one sees a list of new dependencies libdrm2, libudev,
libxml2 libxmlsec1 libxmlsec1-openssl
Hello evade, 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 testing this
Hello evade, 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 testing this
Thanks Andreas for the ping, yes this update will include the upstream fix to
bug 1668244 as well.
If it fixes the issue of the reporter I'm not 100% sure, but I'll update and
subscribe to the other bug if not. We really don't need another unrelated bug
stopping this backport :-)
Actually we
Is https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1668244
still an issue with this update? The udev rules look different
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390
Title:
Is https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1668244
still an issue with this update? The udev rules look different
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1741390
Ok, all dependent bugs were sorted out:
- 1758428 is in Bionic, ready to be included in the backport SRU
- 1750780 is only an issue pre-Bionic, ready to be included in the backport SRU
- 1741390 (this bug) was well tested along with the others
Version numbers for Xenial and Artful were adapted so
bug 1758428 unlocked, it's fix is on the way into Bionic.
Once that completes I can propose the changes as prepared to Artful and Xenial.
** Also affects: open-vm-tools (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: open-vm-tools (Ubuntu Artful)
Status: New =>
FYI: PPA build with the fix for privateTmp is available in a PPA
Versioning changes slightly (better to do these SRUs regularly).
So the new version is below the old one, be sure to update correctly when
testing this.
Consider using
sudo ppa-purge ppa:ci-train-ppa-service/3152
Before using the
While waiting for a Bionic confirm/deny to bug 1758428:
- X version squashed to 2:10.2.0-3~ubuntu0.16.04.1 for the next upload (thanks
for the hint).
- Start preparing Artful now ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've reviewed the SRU upload to Xenial in the Unapproved queue.
SRU policy requires fixes to be in Bionic first. I understand the spirit
of this to be not just to both to stop users regressing upon future
upgrade, but also for us to gain some confidence in quality in the
development release to
Due to SRU regulations - thanks rbasak for pointing it out, we have to prep the
upload for Artful as well.
Given how much backport-special cases we hit I'm already happy :-/
Also the state of 1758428 in Bionic has to be resolved.
So for now tasks:
1. for me - prepare an Artful SRU upload as
@SRU Team
The xenial-unapproved queue has now a fixed version in regard to our findings
in the prechecks:
=> 2:10.2.0-3ubuntu0.16.04.2
No need to cancel the old one, just consider accepting the new upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
> ChristianEhrhardt (paelzer) wrote on 2018-03-21: #46
> I prepared the SRU Template for this, there are two things to complete
> before pushing:
> 1. VMWare will run more regression testing using the ovt automation
> package over the next
days
> 2. I added an MP
I found a fix for bug #1758428 and updated the issue. It's related to
the use of PrivateTmp=yes in the service file.
Since this is a backport from 18.04, I expect the same issue there, and
in Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
We do see weird issues with that build similar to bug #1758428, so
please hold on with the upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390
Title:
Please backport open-vm-tools
@paelzer Seeing Charle's comment, could you re-assess if the SRU is
still valid for upload? Should I reject it from the queue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390
Title:
Please
Details of the issue we hit:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1758428
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390
Title:
Please backport open-vm-tools
I spoke to soon :-( https://bugs.launchpad.net/ubuntu/+source/open-vm-
tools/+bug/1741390/comments/47
We're having to back this version out from our deploy. More details
coming soon...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi evade,
yes it is taken care of.
In Packaging there are source and binary packages.
When we say "we update X" we mean we upload a new src:X
But from your consumption point of view you use binary packages (that is what
you install).
And src:open-vm-tools creates open-vm-tools-dev,
Thank you all for your work on this!
Christian, my original bug (which this came out of) was about needing
updates for both open-vmtools AND the open-vm-tools-desktop package. I
understand that the open-vm-tools-desktop packages needs to be updated
in step with OVT. Is it being addressed
The upload is in the SRU queue [3] for xenial to be reviewed one last time (by
the SRU Team now).
We have plenty of tests on the PPA already which is the same as what we
propose, once it is in proposed [1][2] (there will be an update here) I'd ask
you to test that instead.
[1]:
I did some quick testing with vsphere 6 and esx for the merge proposal, copied
below:
- upgrade from previous version, including dev and desktop subpackages
- used an ESXi xenial vm for testing
- some actions in the vsphere GUI failed with the previous version, worked
out-of-the box with the new
I did some quick testing with vsphere 6 and esx for the merge proposal, copied
below:
- upgrade from previous version, including dev and desktop subpackages
- used an ESXi xenial vm for testing
- some actions in the vsphere GUI failed with the previous version, worked
out-of-the box with the new
** Merge proposal linked:
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
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1741390
Title:
** Merge proposal linked:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390
Title:
Please
FWIW we've been trying out open-vm-tools version
2:10.2.0-3ubuntu0.16.04.1~ppa6 and its been working great for us. Thanks
very much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390
Title:
I prepared the SRU Template for this, there are two things to complete
before pushing:
1. VMWare will run more regression testing using the ovt automation package
over the next days
2. I added an MP with the packaging changes to be reviewed [1]
Once both complete we can push it for the actual
** Description changed:
- TODO - SRU Template
+ [Impact]
+
+ * Without SRUing the never version users get issues running on more
+recent hipervisors.
+
+ * See comment #6 for where we decided to consider this SRU-worthy
+
+ * This is not backporting a single fix, but the version of a
** Also affects: open-vm-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: open-vm-tools (Ubuntu Xenial)
Status: New => In Progress
** Changed in: open-vm-tools (Ubuntu)
Status: Triaged => Fix Released
** Changed in: open-vm-tools (Ubuntu Xenial)
> The new version in the ppa 10.2.0-3ubuntu0.16.04.1~ppa6 is good for
a retest.
verified. It works well with the new package version.
Env:
VMs:ubuntu-16.04-desktop-amd64 and ubuntu-16.04.1-server-amd64
open-vm-tools/open-vm-tools-desktop version: 10.2.0-3ubuntu0.16.04.1~ppa6 from
File is \x2d
Name has to be escaped as \\x2d for e.g. systemctl
This is exactly as we have it in later releases with the fix - so the
file names are "ok" despite still feeling odd to have it named that way.
It turns out that the old 'deb-systemd-helper' is fine with the name - that is
the
Hmm, I had the service running in my test, but I started it on my own.
Maybe the remaining issue now is that it is not started by default - we know
there were some issues due to the special name of this service making dh tools
stumble over it (and those changed in different versions).
I'll take
Ok, I can reproduce the issue with a full purge and reinstall.
The enable part is good on install - the service is enabled and not just
dropped on disk as a file.
But the follow on start is what fails - which also explains why it worked after
a reboot without further modification.
That is enough
> Checks for reported deficiencies:
> 1. vmware-toolbox-cmd works (e.g. timesync status)
> 2. run-vmblock\x2dfuse.mount exists and starts without errors
> 3. vgauth.service exists and starts without errors
> That said at everybody, please re-evaluate the ppa [1].
>[1]:
Checks for reported deficiencies:
1. vmware-toolbox-cmd works (e.g. timesync status)
2. run-vmblock\x2dfuse.mount exists and starts without errors
3. vgauth.service exists and starts without errors
That said at everybody, please re-evaluate the ppa [1].
[1]:
Latest build in the ppa looks fine from a build POV.
I'm going to test this tomorrow morning for the open issues, but please
everybody that can easily test things (e.g. automation available) feel free to
retest already.
--
You received this bug notification because you are a member of Ubuntu
For #1 VGAuathServices this is already built against libxmlsec1-dev (was the
fix for bug 1677196 ).
It must be an artifact of the backport, maybe the older version lacks something.
I found in the build log:
checking xmlsec/xmlsec.h usability... no
checking xmlsec/xmlsec.h presence... no
checking
> [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3152
> Please give this PPA a test and let us know if its a good candidate
for an SRU to xenial.
Env:
VMs:ubuntu-16.04-desktop-amd64 and ubuntu-16.04.1-server-amd64
open-vm-tools version: 10.2.0.1608(build-7253323) from
@John, @Oliver, @vmware-gos-qa
[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3152
Please give this PPA a test and let us know if its a good candidate for
an SRU to xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I now have several leads which raise my mood on this.
I already had one party testing the locally which made us spot an issue with
the latest version in regard to xenials systemd (bug 1750780). But that is
fixed already in the proposed ppa.
We now also got vmware itself taking a look at the
Hi Emily,
I'm sorry, I posted my previous message in a hurry without checking out
what the vulnerabilities involved.
Thanks for your response and the CVE link for open-vm-tools. That's
helpful!
Can you please tell me the URL for the companion open-vm-tools-desktop
package? It wasn't obvious.
VMSA-2017-0013 describes the following CVEs: CVE-2017-4921,
CVE-2017-4922, CVE-2017-4923, CVE-2015-5191. Of these, only
CVE-2015-5191 is applicable to open-vm-tools and it is partially
mitigated via symlink restrictions. It is on the list to be fixed, but
is currently rated low.
VMSA-2018-0003
Update: There are security vulnerabilities in the current version OVT
10.0.7. Can you please update this ticket appropriately?
I don't yet know where the CVE's are publicly published but VMware support tell
me:
"
Later releases of VMware Tools specifically 10.0.9 for CVE listed in VMSA -
PS: IMO this ticket should address the issue of rebasing OVT across LTS
releases, not just backporting one package from bionic to xenial.
We need to rely on the latest stable OVT being available in all LTS
releases when we upgrade to 18.04 later this year.
--
You received this bug notification
Hi,
VMware Tools Product Management Team (indirectly) responded to me. They
are also disappointed that Canonical is not rebasing open-vm-tools for
LTS releases. (I too would suggest it is in Canonical's interest to
keep open-vm-tools updated for LTS releases)
I don't know what discussions you
I added Xenial-Backports for an ack of the backports Team.
I updated the bug description with a full backport-request template for this
case (as you'd do on an SRU with the SRU template).
This is my first backport to the actual -backports pocket, please let me know
who of us eventually uploads
54 matches
Mail list logo
