Description of problem: 'wallaby feature-import' run with no file name prints following error: fatal: #<TypeError: can't convert nil into String> It will be better if it prints something like: A file name must be specified Version-Release number of selected component (if applicable): wallaby-0.10.4-2 How reproducible: Steps to Reproduce: 1. run 'wallaby feature-import' # wallaby feature-import fatal: #<TypeError: can't convert nil into String>
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: C: Running "wallaby feature-import" without a file name may have resulted in an unclear internal error message. C: This is confusing for users. F: "wallaby feature-import" now traps the error appropriately and displays a suitable, clear error message. R: The feature-import command now exits with a user-friendly error message in this case.
Retested over all supported archs x86,x86_64 with RHEL5/RHEL6: # rpm -q wallaby-utils wallaby-utils-0.10.5-3.el6.noarch # wallaby feature-import fatal: you must specify exactly one file name (use --help for more information) >>> VERIFIED
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,4 +1,6 @@ C: Running "wallaby feature-import" without a file name may have resulted in an unclear internal error message. C: This is confusing for users. F: "wallaby feature-import" now traps the error appropriately and displays a suitable, clear error message. -R: The feature-import command now exits with a user-friendly error message in this case.+R: The feature-import command now exits with a user-friendly error message in this case. + +Release Note Entry: Previously, running the "wallaby feature-import" command without supplying a file name resulted in an unclear error message. The "wallaby feature-import" command can now trap the error to display a clearer error message when run without a file name.
Technical note can be viewed in the release notes for 2.0 at the documentation stage here: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2.0/html-single/MRG_Release_Notes/index.html#tabl-MRG_Release_Notes-GRID_Update_Notes-RHM_Known_Issues
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2011-0889.html