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 1522754 - vdo create --noRun ends with "ERROR - 'NoneType' object has no attribute 'read'"
Summary: vdo create --noRun ends with "ERROR - 'NoneType' object has no attribute 'read'"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: vdo
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: bjohnsto
QA Contact: Jakub Krysl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-06 11:35 UTC by Jakub Krysl
Modified: 2019-03-06 01:12 UTC (History)
4 users (show)

Fixed In Version: 6.1.0.97
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 15:49:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0871 0 None None None 2018-04-10 15:49:49 UTC

Description Jakub Krysl 2017-12-06 11:35:54 UTC 
Description of problem:
# vdo create --name vdo --device /dev/sdc --verbose --noRun
Creating VDO vdo
    pvcreate -qq --test /dev/sdc
    modprobe kvdo
New configuration (not written):
config: !Configuration
  vdos:
    vdo: !VDOService
      _operationState: beginCreate
      ackThreads: 1
      activated: enabled
      bioRotationInterval: 64
      bioThreads: 4
      blockMapCacheSize: 128M
      blockMapPeriod: 16380
      compression: enabled
      cpuThreads: 2
      deduplication: enabled
      device: /dev/sdc
      hashZoneThreads: 1
      indexCfreq: 0
      indexMemory: 0.25
      indexSparse: disabled
      indexThreads: 0
      logicalBlockSize: 4096
      logicalSize: 0M
      logicalThreads: 1
      name: vdo
      physicalSize: 0M
      physicalThreads: 1
      readCache: disabled
      readCacheSize: 0M
      slabSize: 0M
      writePolicy: sync
  version: 538380551

    vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 /dev/sdc
    vdodumpconfig /dev/sdc
Removing VDO vdo
Stopping VDO vdo
    dmsetup status vdo
    mount
    udevadm settle
    dmsetup remove vdo
    dd if=/dev/zero of=/dev/sdc oflag=direct bs=4096 count=1
    rm /etc/vdoconf.yml
vdo: ERROR - 'NoneType' object has no attribute 'read'

Version-Release number of selected component (if applicable):
vdo-6.1.0.72-12

How reproducible:
100%

Steps to Reproduce:
1. vdo create --name vdo --device device --noRun

Actual results:
vdo: ERROR - 'NoneType' object has no attribute 'read'

Expected results:
no error

Additional info:
Comment 2 bjohnsto 2017-12-11 22:04:41 UTC 
We've merged a change to remove the noRun option for now. It doesn't have a strong enough purpose to keep it and try to fix all the errors it throws.
Comment 4 Jakub Krysl 2017-12-14 11:18:37 UTC 
In vdo 6.1.0.98-13 argument --noRun is no longer recognized. Is this intentional?

# vdo create --name vdo --device /dev/sdc --verbose --noRun
usage: vdo [-h]

           {activate,changeWritePolicy,create,deactivate,disableCompression,disableDeduplication,enableCompression,enableDeduplication,growLogical,growPhysical,list,modify,printConfigFile,remove,start,status,stop}
           ...
vdo: error: unrecognized arguments: --noRun
Comment 5 Jakub Krysl 2017-12-14 15:14:30 UTC 
As per discussion, this has been resolved by removing the --noRun option at this version. Creating RFE to possibly add similar functionality in future.
Comment 8 errata-xmlrpc 2018-04-10 15:49:25 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/RHEA-2018:0871
Note You need to log in before you can comment on or make changes to this bug.