Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Previously, VDSM did not log every networking change, which made it much more difficult to determine the nature and cause of bugs. VDSM now logs more networking operations than it did before (ifup, ifdown, config file removal, persistent backups of config files, network service stops and starts, vlan removal, bridge removal, declaring network configurations 'safe'), which decreases the amount of time necessary to fix networking bugs.
(In reply to comment #5)
> Posted a first version of a patch that extends the amount of information, I
> would appreciate some feedback:
> http://gerrit.ovirt.org/#/c/7662/2
Hi Antoni,
could you please describe how was the log extended? What are the new things in log to look for?
Info from Antoni on log extenstion:
on ifup and ifdown
on config file removal
on persistent backup of config files
on network service stop and start
on vlan removal
on bridge removal
on declaring network configuration as safe
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/RHSA-2012-1508.html
Description of problem: VDSM network logs need to be more detailed, every network command that pass to the system need to be on the log. Like: ifup, ifdown, create and delete files etc.... Example from VDSM storage log: Thread-20::INFO::2012-08-26 14:05:29,297::logUtils::37::dispatcher::(wrapper) Run and protect: connectStorageServer(domType=3, spUUID='694bd554-9051-4bfa-9020-e196d9ee152b', conList=[{'connection': '10.35.160.7', 'iqn': 'iqn.2008-05.com.xtremio:001b21b545c0', 'portal': '1', 'user': '', 'password': '******', 'id': 'a9e0938a-36db-45b8-9bfa-2379232eba2e', 'port': '3260'}], options=None) Thread-20::DEBUG::2012-08-26 14:05:29,298::__init__::1164::Storage.Misc.excCmd::(_log) '/usr/bin/sudo -n /sbin/iscsiadm -m node -T iqn.2008-05.com.xtremio:001b21b545c0 -I default -p 10.35.160.7:3260 --op=new' (cwd None) Thread-20::DEBUG::2012-08-26 14:05:29,316::__init__::1164::Storage.Misc.excCmd::(_log) SUCCESS: <err> = ''; <rc> = 0 Thread-20::DEBUG::2012-08-26 14:05:29,317::__init__::1164::Storage.Misc.excCmd::(_log) '/usr/bin/sudo -n /sbin/iscsiadm -m node -T iqn.2008-05.com.xtremio:001b21b545c0 -I default -p 10.35.160.7:3260 -l' (cwd None) Thread-20::DEBUG::2012-08-26 14:05:29,334::__init__::1164::Storage.Misc.excCmd::(_log) SUCCESS: <err> = ''; <rc> = 0 Thread-20::DEBUG::2012-08-26 14:05:29,335::__init__::1164::Storage.Misc.excCmd::(_log) '/usr/bin/sudo -n /sbin/iscsiadm -m node -T iqn.2008-05.com.xtremio:001b21b545c0 -I default -p 10.35.160.7:3260 -n node.startu p -v manual --op=update' (cwd None) Thread-20::DEBUG::2012-08-26 14:05:29,350::__init__::1164::Storage.Misc.excCmd::(_log) SUCCESS: <err> = ''; <rc> = 0 Thread-20::DEBUG::2012-08-26 14:05:29,351::lvm::460::OperationMutex::(_invalidateAllPvs) Operation 'lvm invalidate operation' got the operation mutex Thread-20::DEBUG::2012-08-26 14:05:29,352::lvm::462::OperationMutex::(_invalidateAllPvs) Operation 'lvm invalidate operation' released the operation mutex Thread-20::DEBUG::2012-08-26 14:05:29,352::lvm::472::OperationMutex::(_invalidateAllVgs) Operation 'lvm invalidate operation' got the operation mutex Thread-20::DEBUG::2012-08-26 14:05:29,352::lvm::474::OperationMutex::(_invalidateAllVgs) Operation 'lvm invalidate operation' released the operation mutex Thread-20::DEBUG::2012-08-26 14:05:29,353::lvm::493::OperationMutex::(_invalidateAllLvs) Operation 'lvm invalidate operation' got the operation mutex Thread-20::DEBUG::2012-08-26 14:05:29,353::lvm::495::OperationMutex::(_invalidateAllLvs) Operation 'lvm invalidate operation' released the operation mutex Thread-20::INFO::2012-08-26 14:05:29,354::logUtils::39::dispatcher::(wrapper) Run and protect: connectStorageServer, Return response: {'statuslist': [{'status': 0, 'id': 'a9e0938a-36db-45b8-9bfa-2379232eba2e'}]} Thread-20::DEBUG::2012-08-26 14:05:29,354::task::1172::TaskManager.Task::(prepare) Task=`307f7093-df8e-42ec-bb53-51b5280f3b05`::finished: {'statuslist': [{'status': 0, 'id': 'a9e0938a-36db-45b8-9bfa-2379232eba2e'} ]} 6000624a-598a-4f75-b444-1d7e810b36ae::DEBUG::2012-08-26 14:05:55,096::__init__::1164::q::(_log) '/bin/dd iflag=direct skip=0 bs=2048 if=/dev/f76aef57-519d-4340-bfa5-ddd7ea40692d/metadata count=1' (cwd None)