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 832798 - [text] Typo in exception "raise Exception("Could not like to directory. Path does not exist ") - like -> link
Summary: [text] Typo in exception "raise Exception("Could not like to directory. Path ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Greg Padgett
QA Contact: Leonid Natapov
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-17 13:30 UTC by Yaniv Kaul
Modified: 2022-07-09 05:36 UTC (History)
11 users (show)

Fixed In Version: vdsm-4.9.6-21
Doc Type: Bug Fix
Doc Text:
Previously there was a typo in the text for "raise exception" that read "could not like to directory. Path does not exist." This has been corrected to read "could not link to directory. Path does not exist."
Clone Of:
Environment:
Last Closed: 2012-12-04 18:59:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1508 0 normal SHIPPED_LIVE Important: rhev-3.1.0 vdsm security, bug fix, and enhancement update 2012-12-04 23:48:05 UTC

Description Yaniv Kaul 2012-06-17 13:30:18 UTC
Description of problem:
Upstream already has this typo fixed.
From /usr/share/vdsm/storage/storageServer.py :

    def connect(self):
        if not self.checkTarget():
            #TODO: Use proper exception
            raise Exception("Could not like to directory. Path does not exist "
                    "or isn't a directory")


Version-Release number of selected component (if applicable):
vdsm-4.9.6-16.0.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 4 Haim 2012-07-25 13:34:15 UTC
tested via looking into source code in  /usr/share/vdsm/storage/storageServer.py    
def connect(self):
        if not self.checkTarget():
            #TODO: Use proper exception
            raise Exception("Could not link to directory. Path does not exist "
                    "or isn't a directory

fixed tested in vdsm-4.9.6-23

Comment 7 errata-xmlrpc 2012-12-04 18:59:55 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.

http://rhn.redhat.com/errata/RHSA-2012-1508.html


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