Bug 1223498
Summary: | Regression: Unowned directory /etc/vmware-tools | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Richard W.M. Jones <rjones> |
Component: | open-vm-tools | Assignee: | Richard W.M. Jones <rjones> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.2 | CC: | hhei, jingli, ldu, leiwang, ravindrakumar, shwang, yacao |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | open-vm-tools-9.10.0-2.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 09:00:28 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1172833 |
Description
Richard W.M. Jones
2015-05-20 16:31:12 UTC
Oh well. Looks like, I introduced this issue in Fedora too :-( Filed bug 1223587. Verified the bug. The bug related host version:ESXi 5.5 U2 The bug related guest version:rhel7 3.10.0-295.el7.x86_64 Steps to Reproduce: 1.Install a guest rhel7.2 and install the open-vm-tools. 2.Log in the gust and execute the command: [root@rhel7 ~]# rpm -qlp open-vm-tools-9.10.2-2.el7.x86_64.rpm |grep /etc /etc/pam.d/vmtoolsd /etc/vmware-tools /etc/vmware-tools/guestproxy-ssl.conf /etc/vmware-tools/poweroff-vm-default /etc/vmware-tools/poweron-vm-default /etc/vmware-tools/resume-vm-default /etc/vmware-tools/scripts /etc/vmware-tools/scripts/vmware /etc/vmware-tools/scripts/vmware/network /etc/vmware-tools/statechange.subr /etc/vmware-tools/suspend-vm-default The /etc/vmware-tools and /etc/vmware-tools/scripts directories are included in the RPM. The test result: Verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2246.html |