Upstream PR: https://github.com/storaged-project/libblockdev/pull/414

Hello

Sorry, I need reproduces for the bug, Could you please share some test code for it ?

```
import gi 
gi.require_version('BlockDev', '2.0') 

from gi.repository import BlockDev 
BlockDev.switch_init_checks(False) 

BlockDev.init(BlockDev.plugin_specs_from_names(["crypto"]))
BlockDev.crypto_luks_resize("/dev/mapper/test", 0, "passphrase")
```

Where "/dev/mapper/test" is an unlocked LUKS2 device and "passphrase" is passphrase for unlocking it.

Hello

Please have a look my failed.

# lsblk
NAME                                MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
loop0                                 7:0    0    15G  0 loop  
loop1                                 7:1    0    15G  0 loop  
loop2                                 7:2    0    15G  0 loop  
loop3                                 7:3    0    15G  0 loop  
loop4                                 7:4    0    15G  0 loop  
loop5                                 7:5    0    15G  0 loop  
loop6                                 7:6    0    15G  0 loop  
└─vg01-lv01                         253:7    0    10G  0 lvm   
  └─mapper                          253:8    0    10G  0 crypt 
sda                                   8:0    0 931.5G  0 disk  
├─sda1                                8:1    0     1G  0 part  /boot
└─sda2                                8:2    0 930.5G  0 part  
  ├─rhel_storageqe--05-root         253:0    0    50G  0 lvm   /
  ├─rhel_storageqe--05-swap         253:1    0   7.9G  0 lvm   [SWAP]
  └─rhel_storageqe--05-home         253:2    0 872.6G  0 lvm   /home



# cat runtest.py 

#!/bin/env/python
import gi 
gi.require_version('BlockDev', '2.0') 
from gi.repository import BlockDev 
BlockDev.switch_init_checks(False) 
BlockDev.init(BlockDev.plugin_specs_from_names(["crypto"]))
BlockDev.crypto_luks_resize("/dev/mapper/mapper",10, "redhat redhat")


# python3 runtest.py 
Traceback (most recent call last):
  File "runtest.py", line 13, in <module>
    BlockDev.crypto_luks_resize("/dev/mapper/mapper",10, "redhat redhat")
  File "/usr/lib64/python3.6/site-packages/gi/overrides/BlockDev.py", line 235, in crypto_luks_resize
    return _crypto_luks_resize(luks_device, size, passphrase, key_file)
GLib.Error: g-bd-crypto-error-quark: Failed to resize device: Invalid argument (4)



# cat runtest.py 
# echo "redhat redhat > key_file"
#!/bin/env/python
import gi 
gi.require_version('BlockDev', '2.0') 
from gi.repository import BlockDev 
BlockDev.switch_init_checks(False) 
BlockDev.init(BlockDev.plugin_specs_from_names(["crypto"]))
BlockDev.crypto_luks_resize("/dev/mapper/mapper",10, "redhat redhat","key_file")


# python3 runtest.py 
Traceback (most recent call last):
  File "runtest.py", line 13, in <module>
    BlockDev.crypto_luks_resize("/dev/mapper/mapper",10, "redhat redhat","key_file")
  File "/usr/lib64/python3.6/site-packages/gi/overrides/BlockDev.py", line 235, in crypto_luks_resize
    return _crypto_luks_resize(luks_device, size, passphrase, key_file)
GLib.Error: g-bd-crypto-error-quark: Failed to activate device: Operation not permitted (0)

I've tested this with a fresh 7.7 installation and it works for me.

Can you please try this again with this script:


```
from __future__ import print_function

import gi 
gi.require_version('BlockDev', '2.0') 

from gi.repository import BlockDev 
BlockDev.switch_init_checks(False)

BlockDev.utils_init_logging(lambda level, msg: print(msg))

BlockDev.init(BlockDev.plugin_specs_from_names(["crypto"]))
BlockDev.crypto_luks_resize("/dev/mapper/test", 0, "passphrase")
```

(The added line enables extra logging and prints cryptsetup log to stdout.)

Also please check libblockdev version and if it's linked against cryptsetup 2.

$ rpm -qa | grep blockdev
libblockdev-2.18-4.el7.x86_64
libblockdev-crypto-2.18-4.el7.x86_64
libblockdev-utils-2.18-4.el7.x86_64
python2-blockdev-2.18-4.el7.x86_64

$ ldd /usr/lib64/libbd_crypto.so.2 | grep cryptsetup
	libcryptsetup.so.12 => /lib64/libcryptsetup.so.12 (0x00007fef516ef000)

Hello

test passed, so move to verified 

thanks
Guazhang

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-2019:2153