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:
I observed the behavior of vgcreate has changed, which "vgcreate -f"
doesn't mute fs signature wiping confirmation as before.
The different behaviors between on RHEL-7.2 and RHEL-7.3 shows as:
RHEL-7.2:
-----
[root@ibm-p730-05-lp3 ~]# rpm -q lvm2
lvm2-2.02.130.el7.x86_64
[root@ibm-p730-05-lp3 ~]# uname -a
Linux ibm-p730-05-lp3.rhts.eng.bos.redhat.com 3.10.0-327.el7.ppc64 #1
SMP Thu Oct 29 17:33:57 EDT 2015 ppc64 ppc64 ppc64 GNU/Linux
# create test device and create ext4 on it, so it leaves ext4 signature on the device
fallocate -l 128M dummy.img
losetup /dev/loop0 dummy.img
mkfs.ext4 -F /dev/loop0
# create vg on test device with -f option, no prompt for clearing signature
vgcreate -f vgtest /dev/loop0
Wiping ext4 signature on /dev/loop0.
Physical volume "/dev/loop0" successfully created
Volume group "vgtest" successfully created
-----
RHEL-7.3-20160617.n.0
-----
[root@ibm-p8-04-lp8 ~]# rpm -q lvm2
lvm2-2.02.156.el7.x86_64
[root@ibm-p8-04-lp8 ~]# uname -a
Linux ibm-p8-04-lp8.rhts.eng.bos.redhat.com 3.10.0-442.el7.ppc64 #1
SMP Thu Jun 16 18:35:03 EDT 2016 ppc64 ppc64 ppc64 GNU/Linux
# create test device and create ext4 on it, so it leaves ext4 signature on the device
fallocate -l 128M dummy.img
losetup /dev/loop0 dummy.img
mkfs.ext4 -F /dev/loop0
# create vg on test device with -f option, no prompt for clearing signature
vgcreate -f vgtest /dev/loop0
WARNING: ext4 signature detected on /dev/loop0 at offset 1080. Wipe it? [y/n]:
-----
Version-Release number of selected component (if applicable):
2.02.156
How reproducible:
Always
Steps to Reproduce:
refer to "description"
Actual results:
"vgcreate -f" requires wiping confirmation
Expected results:
"vgcreate -f" doesn't require wiping confirmation
Additional info:
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-2016-1445.html