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.
Description of problem:
In WALA new version(2.2.11),add an event on azurelinuxagent/ga/update.py (line 263-268).So,this cause too many logs to /var/log/waagent.log(roughly 3-4second/item).Too many this kind of logs are unless and maybe waste resource.
Version-Release number of selected component (if applicable):
WALinuxAgent-2.2.11 upstream
How reproducible:
100%
RHEL Version:
RHEL-7.4/6.9
Steps to Reproduce:
1.Prepare a RHEL7.4 VM and install WALA 2.2.11
2.Start the VM and check /var/log/waagent.log
Actual results:
2017/05/12 15:47:23.209433 INFO Event: name=WALinuxAgent, op=ProcessGoalState, message=
2017/05/12 15:47:27.390004 INFO Event: name=WALinuxAgent, op=ProcessGoalState, message=
2017/05/12 15:47:30.591457 INFO Event: name=WALinuxAgent, op=ProcessGoalState, message=
2017/05/12 15:47:33.762246 INFO Event: name=WALinuxAgent, op=ProcessGoalState, message=
2017/05/12 15:47:37.947431 INFO Event: name=WALinuxAgent, op=ProcessGoalState, message=
......
Expected results:
1.Maybe should reduce the print rate of this kind of log
2.Maybe modify this kind of log level(INFO ==> DEBUG),maybe better
Additional info: