Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Affects current open-vm-tools 11.0.5
'The patch converts what previously was a warning message to a debug message and thus avoids the log spew.'
--
https://github.com/vmware/open-vm-tools/issues/404https://github.com/vmware/open-vm-tools/commit/4ee0bd3c8ead89541ab7d196fb54e940e397420d
--
Rectify a log spew in vmsvc logging (vmware-vmsvc-root.log )
When a LSI Logic Parallel SCSI controller sits in PCI bus 0
(SCSI controller 0), the Linux disk device enumeration does not provide
a "label" file with the controller name. This results in messages like
"GuestInfoGetDiskDevice: Missing disk device name; VMDK mapping unavailable for "/var/log", fsName: "/dev/sda2"
repeatedly appearing in the vmsvc logging. The patch converts what previously
was a warning message to a debug message and thus avoids the log spew.
--
Verified this bug on open-vm-tools-11.0.5-3.el7_9.2.x86_64.rpm, after install the test open-vm-tools package then check the vmware-vmsvc-root.log log file, the message "[2021-02-18T00:49:30.529Z] [ warning] [guestinfo] GuestInfoGetDiskDevice: Missing disk device name; VMDK mapping unavailable for "/", fsName: "/dev/mapper/rhel-root"
[2021-02-18T00:49:30.530Z] [ warning] [guestinfo] GuestInfoGetDiskDevice: Missing disk device name; VMDK mapping unavailable for "/boot", fsName: "/dev/sda1"" in log gone away. Also run some regression test, all test case passed.
Verified this bug on RHEL7.9 with open-vm-tools-11.0.5-3.el7_9.2.x86_64.rpm, the build had fix this bug, and also run regression test all test cases passed.
so change status to 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 (open-vm-tools bug fix and enhancement update), 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://access.redhat.com/errata/RHEA-2021:0866
hi team,
We have got a case reporting this issue with RHEL 7.9 installed and open-vm-tools-11.0.5-3.el7_9.2.x86_64
>> Missing disk device name; VMDK mapping unavailable for "/var/mqm/vols/sasabb_ipx_xxx", fsName: "/dev/drxx301"
Should we discuss here or create a new Bug? Any pre-checks or configuration checks we need to do.
(In reply to Ulhas Surse from comment #31)
> hi team,
>
> We have got a case reporting this issue with RHEL 7.9 installed and
> open-vm-tools-11.0.5-3.el7_9.2.x86_64
>
> >> Missing disk device name; VMDK mapping unavailable for
> "/var/mqm/vols/sasabb_ipx_xxx", fsName: "/dev/drxx301"
>
> Should we discuss here or create a new Bug? Any pre-checks or configuration
> checks we need to do.
The fix was verified in open-vm-tools-11.0.5-3.el7_9.2.x86_64.rpm comment 18. Please check to make sure that they do not have debug log enabled. https://kb.vmware.com/s/article/1007873
Thanks,
Cathy
I have retest on RHEL7.9 with open-vm-tools-11.0.5-3.el7_9.2 and open-vm-tools-11.0.5-3.el7_9.3, both could not reproduce this issue.
before upgrade the open-vm-tools, indeed could observe log "[2022-04-19T02:49:38.667Z] [ warning] [guestinfo] GuestInfoGetDiskDevice: Missing disk device name; VMDK mapping unavailable for "/", fsName: "/dev/mapper/rhel-root"" in /var/log/vmware-vmsvc-root.log file.
Comment 34Red Hat Bugzilla
2023-09-18 00:24:04 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days