Bug 799107 - misspelled word in error message when push with no account
Summary: misspelled word in error message when push with no account
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: rubygem-aeolus-cli
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
Assignee: Martyn Taylor
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-01 19:30 UTC by Dave Johnson
Modified: 2012-05-15 19:54 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-05-15 19:54:41 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0591 0 normal SHIPPED_LIVE new packages: rubygem-aeolus-cli 2012-05-15 22:31:17 UTC

Description Dave Johnson 2012-03-01 19:30:08 UTC 
Description of problem:
===============================

Trying to push a image without the --account parmeter

[root@hp-nehalem-02 ~]# aeolus-image push --image <uuid>
Error: You must specifcy an account to push to

'specify' is misspelled


Version-Release number of selected component (if applicable):
==============================================================
aeolus-configure-2.5.0-15.el6.noarch
Comment 1 Martyn Taylor 2012-03-06 14:56:52 UTC 
commit 20dfe5f78d991c91e68dafdea451c3334f1cc4a3
Author: Martyn Taylor <mtaylor>
Date:   Mon Mar 5 15:55:25 2012 +0000

    BZ#799107 Fixed Typo in Push Command
Comment 3 Aziza Karol 2012-03-07 06:03:29 UTC 
No typo error.

#aeolus-image push --image 53a59a8c-6817-11e1-8a58-0015c5f603a0
Error: You must specify an account to push to

rpm  -qa | grep aeolus
aeolus-conductor-doc-0.8.0-41.el6.noarch
aeolus-conductor-daemons-0.8.0-41.el6.noarch
rubygem-aeolus-cli-0.3.0-13.el6.noarch
aeolus-all-0.8.0-41.el6.noarch
aeolus-conductor-0.8.0-41.el6.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-configure-2.5.0-18.el6.noarch
Comment 4 errata-xmlrpc 2012-05-15 19:54:41 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/RHEA-2012-0591.html
Note You need to log in before you can comment on or make changes to this bug.