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.
I don't consider this as a bug. These two lines can be quite useful for debugging and since the messages are only on the DEBUG level, I think it's OK to have them there.
On the other hand, it could be useful to increase the level of "Sending update..." log message to INFO.
Do you agree with suggested solution?
Yes, I agree with you , increase the level of "Sending update..." log message to INFO should be more clear.
(In reply to Radek Novacek from comment #2)
> I don't consider this as a bug. These two lines can be quite useful for
> debugging and since the messages are only on the DEBUG level, I think it's
> OK to have them there.
>
> On the other hand, it could be useful to increase the level of "Sending
> update..." log message to INFO.
>
> Do you agree with suggested solution?
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/RHBA-2014-1513.html
Description of problem: virt-who running in hyper-V mode normally, Check the /etc/rhsm/rhsm.log, everytime before "Sending update in hosts-to-guests mapping",it will generate two line of "Using NTLM authentication" and "NTLM authentication successful" Version-Release number of selected component (if applicable): subscription-manager-1.9.6-1.el6.x86_64 python-rhsm-1.9.6-1.el6.x86_64 virt-who-0.8-9.el6.noarch katello-headpin-1.4.3-15.el6sam_splice.noarch candlepin-0.8.26-1.el6sam.noarch How reproducible: Always Steps to Reproduce: 1. Prepare RHEL6.5 with latest virt-who installed. 2. Configure virt-who in Hyper-V mode as the following: [root@hp-z220-03 ~]# cat /etc/sysconfig/virt-who VIRTWHO_BACKGROUND=1 # Enable debugging output. VIRTWHO_DEBUG=1 VIRTWHO_INTERVAL=5 # Register ESX machines using vCenter VIRTWHO_HYPERV=1 # Option for ESX mode VIRTWHO_HYPERV_OWNER=ACME_Corporation VIRTWHO_HYPERV_ENV=Library VIRTWHO_HYPERV_SERVER=10.66.13.22 VIRTWHO_HYPERV_USERNAME=administrator VIRTWHO_HYPERV_PASSWORD=qwer1234P 3.Start virt-who service [root@hp-z220-03 ~]# service virt-who start [root@hp-z220-03 ~]# service virt-who status virt-who (pid 15975) is running... 4. Register the RHEL6.5 to SAM server # Subscription-manager register --username=admin --password=admin 5. Monitor the rhsm log : # tail -f /var/log/rhsm/rhsm.log Actual results: it will generate the duplicate log info as the following: 2013-09-25 14:00:42,392 [DEBUG] @virt-who.py:522 - Starting infinite loop with 5 seconds interval and event handling 2013-09-25 14:00:42,396 [DEBUG] @hyperv.py:215 - Using NTLM authentication 2013-09-25 14:00:42,404 [DEBUG] @hyperv.py:242 - NTLM authentication successful 2013-09-25 14:00:43,239 [DEBUG] @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {'60527517-6284-7593-6AAB-75BF2A6375EF': []} 2013-09-25 14:00:44,036 [INFO] @virt-who.py:217 - Created host: 60527517-6284-7593-6AAB-75BF2A6375EF with guests: [] 2013-09-25 14:00:49,044 [DEBUG] @hyperv.py:215 - Using NTLM authentication 2013-09-25 14:00:49,051 [DEBUG] @hyperv.py:242 - NTLM authentication successful 2013-09-25 14:00:49,916 [DEBUG] @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {'60527517-6284-7593-6AAB-75BF2A6375EF': []} 2013-09-25 14:00:55,112 [DEBUG] @hyperv.py:215 - Using NTLM authentication 2013-09-25 14:00:55,119 [DEBUG] @hyperv.py:242 - NTLM authentication successful 2013-09-25 14:00:55,985 [DEBUG] @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {'60527517-6284-7593-6AAB-75BF2A6375EF': []} 2013-09-25 14:01:01,226 [DEBUG] @hyperv.py:215 - Using NTLM authentication 2013-09-25 14:01:01,233 [DEBUG] @hyperv.py:242 - NTLM authentication successful 2013-09-25 14:01:02,084 [DEBUG] @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {'60527517-6284-7593-6AAB-75BF2A6375EF': []} Expected results: it shouldn't generate two line of "Using NTLM authentication" and "NTLM authentication successful" before "Sending update in hosts-to-guests mapping" everytime. Additional info: virt-who running in the ESX , libvirt mode hasn't this problem.