Bug 988627 - "Transaction failed" in ovirt.log [NEEDINFO]
"Transaction failed" in ovirt.log
Product: oVirt
Classification: Community
Component: ovirt-node (Show other bugs)
All Linux
medium Severity medium
: ---
: 3.4.1
Assigned To: Fabian Deutsch
Depends On:
  Show dependency treegraph
Reported: 2013-07-25 22:42 EDT by bohai
Modified: 2014-04-30 06:28 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-04-30 06:28:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
fdeutsch: needinfo? (bohai)

Attachments (Terms of Use)

  None (edit)
Description bohai 2013-07-25 22:42:34 EDT
Description of problem:
error log in ovirt.log

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

How reproducible:

Steps to Reproduce:
1.boot the system
2.read the ovirt.log

Actual results:
"Transaction failed" occured

Expected results:
no this error log,everything is normal

Additional info:
Jul 25 02:35:08 Synchronizing log files
No handlers could be found for logger "ovirt.node.utils"
Traceback (most recent call last):
  File "<stdin>", line 3, in <module>
  File "/usr/lib/python2.7/site-packages/ovirtnode/network.py", line 55, in
    return Network().commit()
  File "/usr/lib/python2.7/site-packages/ovirt/node/config/defaults.py", line
106, in commit
    return tx()
  File "/usr/lib/python2.7/site-packages/ovirt/node/utils/__init__.py", line
240, in __call__
    return self.run()
  File "/usr/lib/python2.7/site-packages/ovirt/node/utils/__init__.py", line
235, in run
    "%s" % e.message)
ovirt.node.exceptions.TransactionError: 'Transaction failed: unicode() argument
2 must be string, not None'
2013-07-25 02:35:12,245 - INFO - ovirtfunctions - Won't update /etc/hosts, it's
not empty.
Redirecting to /bin/systemctl restart  systemd-journald.service
Jul 25 02:35:12 Hardware virtualization detected
Comment 1 Fabian Deutsch 2013-11-28 07:37:10 EST

can you see if this is still reproducable on on 3.0.3?
Comment 2 Sandro Bonazzola 2014-03-04 04:21:55 EST
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
Comment 3 Fabian Deutsch 2014-04-30 06:28:38 EDT
This should be fixed in 3.0.4

Please reopen if necessary

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