Bug 493272 - smoltSendProfile fails with FAS account
smoltSendProfile fails with FAS account
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: smolt (Show other bugs)
10
All Linux
low Severity medium
: ---
: ---
Assigned To: Mike McGrath
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-01 04:24 EDT by David Nečas
Modified: 2009-06-22 16:08 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-06-22 16:08:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David Nečas 2009-04-01 04:24:50 EDT
Description of problem:
Running smoltSendProfile with Fedora Account System username and password fails with a python AttributeError.


Version-Release number of selected component (if applicable):
smolt-1.1.1.1-9.fc10.noarch


How reproducible:
Always.


Steps to Reproduce:
1. Run smolt -a --username=... --password=...
  

Actual results:
The profile to be sent is printed and then this error occurs:

Traceback (most recent call last):
  File "/usr/bin/smoltSendProfile", line 187, in <module>
    if profile.register(userName=opts.userName, password=password, user_agent=opts.user_agent, smoonURL=opts.smoonURL, timeout=opts.timeout):
AttributeError: Hardware instance has no attribute 'register'


Expected results:
The profile is printed and sent, some errata found.


Additional info:
If I do not use Fedora Account System username and password, it works.  If I use bogus username and password it fails with the same error.  However, I am pretty sure that the Fedora Account System username and password are the same that work for me for logging in.
Comment 1 Mike McGrath 2009-06-22 16:08:36 EDT
This feature was never actually completed, just some test stuff made it into a release, I've removed it now.

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