Bug 1460692 - Pass --yes flag to pvresize to force it
Pass --yes flag to pvresize to force it
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs (Show other bugs)
7.4
Unspecified Unspecified
urgent Severity medium
: rc
: 7.4
Assigned To: Richard W.M. Jones
Virtualization Bugs
: Regression
Depends On: 1460577
Blocks: TRACKER-bugs-affecting-libguestfs
  Show dependency treegraph
 
Reported: 2017-06-12 08:19 EDT by Richard W.M. Jones
Modified: 2017-08-01 18:13 EDT (History)
17 users (show)

See Also:
Fixed In Version: libguestfs-1.36.3-5.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1460577
Environment:
Last Closed: 2017-08-01 18:13:55 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Richard W.M. Jones 2017-06-12 08:19:40 EDT
+++ This bug was initially created as a clone of Bug #1460577 +++

Description of problem:

pvresize-size failed to resize an LVM physical volume.

Version-Release number of selected component (if applicable):
libguestfs-1.36.3-4.el7.x86_64

The reproducer is:

  $ guestfish -N disk:10G pvcreate /dev/sda : pvresize-size /dev/sda 5G
  libguestfs: error: pvresize_size: /dev/sda: /dev/sda: Requested size 5.00 GiB is less than real size 10.00 GiB. Proceed?  [y/n]: [n]
    Physical Volume /dev/sda not resized.

Add -v -x to the command line to see the lvm2 commands being performed.

Actually the problem is not the kernel, but the lvm2 package.

WORKING => lvm2-2.02.166-1.el7_3.4.x86_64
 BROKEN => lvm2-2.02.171-4.el7.x86_64
Comment 6 Xianghua Chen 2017-06-14 08:13:58 EDT
Verified with packages:
libguestfs-1.36.3-5.el7

Steps:
1.
# guestfish -N disk:10G pvcreate /dev/sda : pvresize-size /dev/sda 5G


The command finished successfully.
So verified.
Comment 7 errata-xmlrpc 2017-08-01 18:13:55 EDT
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://access.redhat.com/errata/RHBA-2017:2023

Note You need to log in before you can comment on or make changes to this bug.