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 1679224 - Traceback IsADirectoryError on vdo create --logfile=$directory
Summary: Traceback IsADirectoryError on vdo create --logfile=$directory
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: vdo
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: John Wiele
QA Contact: vdo-qe
URL:
Whiteboard:
Depends On: 1682564
Blocks: 1688481
TreeView+ depends on / blocked
 
Reported: 2019-02-20 16:10 UTC by Jakub Krysl
Modified: 2021-09-06 15:22 UTC (History)
4 users (show)

Fixed In Version: 6.2.1.22
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1688481 (view as bug list)
Environment:
Last Closed: 2019-11-05 22:12:27 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3548 0 None None None 2019-11-05 22:12:42 UTC

Description Jakub Krysl 2019-02-20 16:10:18 UTC 
Description of problem:
Using --logfile with existing directory as value produces uncaught traceback.

Version-Release number of selected component (if applicable):
vdo-6.2.0.293-10.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1.vdo create --logfile='/mnt/vdo_test' --device='/dev/mapper/vg-lv' --name='vdo_test'

Actual results:
Traceback (most recent call last):                                                            
  File "/usr/bin/vdo", line 150, in <module>
    main()                                                                                    
  File "/usr/bin/vdo", line 115, in main                                                     
    arguments.logfile, arguments.debug)                                                      
  File "/usr/bin/vdo", line 70, in configureLogger                                           
    handler = logging.FileHandler(logfile)                                                   
  File "/usr/lib64/python3.6/logging/__init__.py", line 1032, in __init__                    
    StreamHandler.__init__(self, self._open())                                                                                                                                                                    
  File "/usr/lib64/python3.6/logging/__init__.py", line 1061, in _open                                                                                                                                            
    return open(self.baseFilename, self.mode, encoding=self.encoding)
IsADirectoryError: [Errno 21] Is a directory: '/mnt/vdo_test'

Expected results:
vdo: ERROR - [Errno 21] Is a directory: '/mnt/vdo_test' 

Additional info:
Comment 1 Dennis Keefe 2019-02-20 19:24:13 UTC 
I was able to reproduce this issue.  The open --logfile works fine, but if you create a directory with the same path and name, then create the vdo volume a traceback is seen.
Comment 4 Jakub Krysl 2019-05-16 08:52:21 UTC 
Tested with vdo-6.2.1.48-10.el8.x86_64:

# mkdir /mnt/vdo_test
# vdo create --logfile='/mnt/vdo_test' --device='/dev/sda' --name='vdo_test'
usage: vdo create [-h] -n <volume> --device <devicepath>
                  [--activate {disabled,enabled}]
                  [--blockMapCacheSize <megabytes>]
                  [--blockMapPeriod <period>]
                  [--compression {disabled,enabled}]
                  [--deduplication {disabled,enabled}]
                  [--emulate512 {disabled,enabled}] [--force]
                  [--indexMem <gigabytes>] [--maxDiscardSize <megabytes>]
                  [--sparseIndex {disabled,enabled}]
                  [--vdoAckThreads <threadCount>]
                  [--vdoBioRotationInterval <ioCount>]
                  [--vdoBioThreads <threadCount>]
                  [--vdoCpuThreads <threadCount>]
                  [--vdoHashZoneThreads <threadCount>]
                  [--vdoLogicalSize <megabytes>]
                  [--vdoLogicalThreads <threadCount>]
                  [--vdoLogLevel {critical,error,warning,notice,info,debug}]
                  [--vdoPhysicalThreads <threadCount>]
                  [--vdoSlabSize <megabytes>]
                  [--writePolicy {async,sync,auto}] [-f <file>]
                  [--logfile <pathname>] [--verbose]
vdo create: error: argument --logfile: /mnt/vdo_test is a directory
Comment 7 errata-xmlrpc 2019-11-05 22:12:27 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:3548
Note You need to log in before you can comment on or make changes to this bug.