Bug 1522754

Summary: vdo create --noRun ends with "ERROR - 'NoneType' object has no attribute 'read'"
Product: Red Hat Enterprise Linux 7 Reporter: Jakub Krysl <jkrysl>
Component: vdoAssignee: bjohnsto
Status: CLOSED ERRATA QA Contact: Jakub Krysl <jkrysl>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: awalsh, bjohnsto, jkrysl, sweettea
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 6.1.0.97 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 15:49:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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