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:
Since few weeks (development release 1.27.32), libguestfs uses a copy of the upstream lvm.aug lens, with a simple modification to handle negative integer values, to properly edit /etc/lvm/lvm.conf.
We did that (carrying a copy) because this the old way (i.e. manually editing /etc/lvm/lvm.conf with manual search & replace) was too fragile, and it broke with newer lvm2 releases.
The proposed changes for lvm.aug have been sent upstream [1], although they have not been reviewed yet at this current time.
Thus, it would be nice if the Augeas in RHEL 7.1 could provide these improvements, which would ease our implementation a bit (especially because libguestfs 1.27.x/1.28.x is in RHEL 7.1).
[1] https://github.com/hercules-team/augeas/pull/155
Version-Release number of selected component (if applicable):
1.1.0-15.el7
Verify with augeas-1.1.0-16.el7
Steps to verify:
1. #find /usr/share/augeas/lenses/dist/ -name lvm.aug
/usr/share/augeas/lenses/dist/lvm.aug
2. #augtool print /augeas/files/etc/lvm/lvm.conf
/augeas/files/etc/lvm/lvm.conf
/augeas/files/etc/lvm/lvm.conf/path = "/files/etc/lvm/lvm.conf"
/augeas/files/etc/lvm/lvm.conf/mtime = "1414473460"
/augeas/files/etc/lvm/lvm.conf/lens = "@LVM"
/augeas/files/etc/lvm/lvm.conf/lens/info = "/usr/share/augeas/lenses/dist/lvm.aug:67.11-.26:"
3. #augtool print /files/etc/lvm/lvm.conf
/files/etc/lvm/lvm.conf
/files/etc/lvm/lvm.conf/#comment[1] = "This is an example configuration file for the LVM2 system."
/files/etc/lvm/lvm.conf/#comment[2] = "It contains the default settings that would be used if there was no"
/files/etc/lvm/lvm.conf/#comment[3] = "/etc/lvm/lvm.conf file."
/files/etc/lvm/lvm.conf/#comment[4] = "Refer to 'man lvm.conf' for further information including the file layout."
/files/etc/lvm/lvm.conf/#comment[5] = "To put this file in a different directory and override /etc/lvm set"
/files/etc/lvm/lvm.conf/#comment[6] = "the environment variable LVM_SYSTEM_DIR before running the tools."
/files/etc/lvm/lvm.conf/#comment[7] = "N.B. Take care that each setting only appears once if uncommenting"
/files/etc/lvm/lvm.conf/#comment[8] = "example settings in this file."
/files/etc/lvm/lvm.conf/#comment[9] = "This section allows you to set the way the configuration settings are handled."
[...]
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-0399.html