Bug 231752 - Smolt doesn't transmit stats
Smolt doesn't transmit stats
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: smolt (Show other bugs)
6
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike McGrath
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-11 01:59 EST by Marc Wiriadisastra
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: 0.9.2-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-03-11 21:25:45 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)
smoltSendProfile (3.19 KB, text/plain)
2007-03-11 01:59 EST, Marc Wiriadisastra
no flags Details

  None (edit)
Description Marc Wiriadisastra 2007-03-11 01:59:10 EST
Description of problem:
I've installed Smolt using the yum install smolt
Run the command 'smoltSendProfile' as a user and root
It requests to send the information I type 'y' then enter
It then errors with 
Server Message: "Critical: Device Read Failed -
0x0|0x0|tty|Unknown|None|16550A-compatible COM port"

Version-Release number of selected component (if applicable):

smolt-0.9-1.fc6

How reproducible:
Happens all the time

Steps to Reproduce:
1.smoltSendProfile
2.type 'y' enter
  
Actual results:
Fails with Server Message: "Critical: Device Read Failed -
0x0|0x0|tty|Unknown|None|16550A-compatible COM port"

Expected results:
It should upload the results.

Additional info: See attached file for the full Uuid breakdown.
Comment 1 Marc Wiriadisastra 2007-03-11 01:59:10 EST
Created attachment 149787 [details]
smoltSendProfile
Comment 2 Mike McGrath 2007-03-11 21:25:45 EDT
This is because you're runing an outdated version of smolt.  If you cannot find
the update please let us know what mirror it came from, it is out of date.
Comment 3 Marc Wiriadisastra 2007-03-12 08:05:52 EDT
I did a yum clean all then a yum update and it worked so sorry about the bug.

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