Bug 1462243
Summary: | [ESXi][RHEL7.4]/etc/resolv.conf wrong context when created via vmtoolsd | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Simon Reber <sreber> |
Component: | open-vm-tools | Assignee: | Richard W.M. Jones <rjones> |
Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | boyang, cavery, hhei, jsavanyo, ldu, leiwang, ravindrakumar, sreber, vmware-gos-qa, yacao, ybhasin |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-06-19 06:54:24 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: |
Description
Simon Reber
2017-06-16 13:12:53 UTC
Ravindra, any idea about the above? When creating files offline you need to be careful to set SELinux labels correctly. Unfortunately this is not trivial to do properly, as I know first hand from libguestfs. But in this case I'm not sure how open-vm-tools creates files, or even if open-vm-tools is involved here at all, since AFAIK open-vm-tools only ever runs in the context of the guest when the guest is running. Guest customization scripts are part of vCenter, open-vm-tools is providing the vmtoolsd daemon that help launching the scripts. I will have to open a VMware internal bug for tracking this issue. I'm curious if this can be fixed by having vCenter scripts run additional commands like 'restorecon'? Yes as long as it's all running inside the the guest you can restore the labels on individual files by running: restorecon /path/to/file or on directories (or the whole filesystem) with: restorecon -r / Thanks Rich. I have couple of more questions. 1. What is the version of VMware vCenter used in this test? 2. Is this reported by some customer or RH QA team? VMware internal bug is 1896920. As the fix will not go into open-vm-tools, this bug can be resolved with necessary justification. The fix will go in VMware vCenter. (In reply to Ravindra Kumar from comment #5) > Thanks Rich. I have couple of more questions. > > 1. What is the version of VMware vCenter used in this test? > 2. Is this reported by some customer or RH QA team? Simon, can you help with Ravindra's questions? Looks like the details are not in the customer case. (In reply to Ravindra Kumar from comment #5) > Thanks Rich. I have couple of more questions. > > 1. What is the version of VMware vCenter used in this test? We are testing with 6.5.0 Build 4602587 internally in Red Hat > 2. Is this reported by some customer or RH QA team? We are able to reproduce the issue internally but initial reporting was provided by customer. Note sure which version the customer is running though, he mentioned 6.0. If you need more information let me know and I'll happily ask for it. Thanks Simon, this is good enough detail. Please feel free to resolve this bug because the fix will be in VMware vCenter product. You could inform the customer to follow up with VMware support for the fix/patch. I already shared VMware internal bug ID with you. Closing this bug as the issue is tracked, VMWare internally via #1896920. As per https://bugzilla.redhat.com/show_bug.cgi?id=1462243#c9 the issue resists in VMware vCenter product and can not be fixed via `open-vm-tools` |