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.
Bug 1654583 - ssm resize fails with python stack trace
Summary: ssm resize fails with python stack trace
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: system-storage-manager
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Lukáš Czerner
QA Contact: Boyang Xue
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-29 07:15 UTC by nikhil kshirsagar
Modified: 2021-12-10 18:19 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 12:55:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2133 0 None None None 2019-08-06 12:55:13 UTC

Description nikhil kshirsagar 2018-11-29 07:15:22 UTC
Description of problem:
[root@cvmarc ~]# ssm resize -s +100%free /dev/rhel_cvmarc/root
Traceback (most recent call last):
  File "/usr/bin/ssm", line 48, in <module>
    sys.exit(main.main())
  File "/usr/lib/python2.7/site-packages/ssmlib/main.py", line 2110, in main
    args.func(args)
  File "/usr/lib/python2.7/site-packages/ssmlib/main.py", line 1150, in resize
    ret = args.volume['fs_info'].resize()
  File "/usr/lib/python2.7/site-packages/ssmlib/main.py", line 256, in resize
    return self._get_fs_func("resize", *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/ssmlib/main.py", line 246, in _get_fs_func
    return func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/ssmlib/main.py", line 355, in xfs_resize
    new_size = int(new_size)
TypeError: int() argument must be a string or a number, not 'NoneType'

Version-Release number of selected component (if applicable):
system-storage-manager-0.4-7.el7.noarch

Steps to Reproduce:
see https://access.redhat.com/solutions/3606431

Comment 3 Jan Tulak 2018-11-29 09:26:46 UTC
I confirm I can reproduce the bug, and it isn't specific to RHEL.

Comment 4 Jan Tulak 2019-03-11 11:08:59 UTC
The upstream has a patch for this issue.

Comment 6 Boyang Xue 2019-03-20 04:49:12 UTC
TEST PASS.

Setup
---
[root@host-8-247-225 tests1minutetip_bringup]# ssm create --fs xfs -p ssm_vg -n ssm_lv /dev/loop1
  Physical volume "/dev/loop1" successfully created.
  Volume group "ssm_vg" successfully created
  Logical volume "ssm_lv" created.
meta-data=/dev/ssm_vg/ssm_lv     isize=512    agcount=4, agsize=130816 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=0, sparse=0
data     =                       bsize=4096   blocks=523264, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
[root@host-8-247-225 tests1minutetip_bringup]# ssm list
-------------------------------------------------------------
Device         Free     Used     Total  Pool      Mount point
-------------------------------------------------------------
/dev/loop0  0.00 KB  5.00 GB   5.00 GB  lvm_pool
/dev/loop1  0.00 KB  2.00 GB   2.00 GB  ssm_vg
/dev/vda                      20.00 GB            PARTITIONED
/dev/vda1                     20.00 GB            /
-------------------------------------------------------------
--------------------------------------------------
Pool      Type  Devices     Free     Used    Total
--------------------------------------------------
lvm_pool  lvm   1        0.00 KB  5.00 GB  5.00 GB
ssm_vg    lvm   1        0.00 KB  2.00 GB  2.00 GB
--------------------------------------------------
------------------------------------------------------------------------------------------
Volume                 Pool      Volume size  FS    FS size      Free  Type    Mount point
------------------------------------------------------------------------------------------
/dev/lvm_pool/lvol001  lvm_pool      5.00 GB  xfs   4.99 GB   4.95 GB  linear  /media
/dev/ssm_vg/ssm_lv     ssm_vg        2.00 GB  xfs   1.99 GB   1.99 GB  linear
/dev/vda1                           20.00 GB  xfs  19.99 GB  14.28 GB  part    /
------------------------------------------------------------------------------------------
[root@host-8-247-225 tests1minutetip_bringup]# mkdir /ssmtest
[root@host-8-247-225 tests1minutetip_bringup]# mount /dev/ssm_vg/ssm_lv /ssmtest/
---

Reproduced with ssm version 0.4-8.el7
---
[root@host-8-247-225 tests1minutetip_bringup]# ssm resize -s +100%FREE /dev/ssm_vg/ssm_lv /dev/sdc
Traceback (most recent call last):
  File "/usr/bin/ssm", line 48, in <module>
    sys.exit(main.main())
  File "/usr/lib/python2.7/site-packages/ssmlib/main.py", line 2110, in main
    args.func(args)
  File "/usr/lib/python2.7/site-packages/ssmlib/main.py", line 1150, in resize
    ret = args.volume['fs_info'].resize()
  File "/usr/lib/python2.7/site-packages/ssmlib/main.py", line 256, in resize
    return self._get_fs_func("resize", *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/ssmlib/main.py", line 246, in _get_fs_func
    return func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/ssmlib/main.py", line 355, in xfs_resize
    new_size = int(new_size)
TypeError: int() argument must be a string or a number, not 'NoneType'
---

Verified with ssm version 0.4-9.el7
---
[root@host-8-247-225 tests1minutetip_bringup]# ssm resize -s +100%FREE /dev/ssm_vg/ssm_lv /dev/sdc
meta-data=/dev/mapper/ssm_vg-ssm_lv isize=512    agcount=4, agsize=130816 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=0 spinodes=0
data     =                       bsize=4096   blocks=523264, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
log      =internal               bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
---

Comment 9 errata-xmlrpc 2019-08-06 12:55:09 UTC
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:2133


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