Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LogAnalyzer] Ignore "sflowmgrd process is not running" warning in LogAnalyzer for master #2261

Closed

Conversation

bingwang-ms
Copy link
Collaborator

Description of PR

Summary:
sflowmgrd is configured in Monit, but not included in current master branch image. As a result, there will be a warning in syslog.

ERR monit[522]: 'sflowmgrd' process is not running

To workaroud this error temporarily, this PR add a patch to ignore the pattern for master branch.

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Approach

Add a patch to ignore 'sflowmgrd' process is not running for master branch.

What is the motivation for this PR?

This PR is to ignore test errors caused by 'sflowmgrd' process is not running in syslog.

How did you do it?

Add a new pattern to ignore_list of LogAnalyzer.

How did you verify/test it?

Verified on dx010 running master branch.

Any platform specific information?

No.

Supported testbed topology if it's a new test case?

No.

Documentation

No.

@bingwang-ms bingwang-ms requested review from a team, daall and yxieca September 23, 2020 08:55
@gord1306
Copy link
Contributor

Is this related to this PR sonic-net/sonic-buildimage#5153 ?

@bingwang-ms
Copy link
Collaborator Author

Is this related to this PR Azure/sonic-buildimage#5153 ?

Yes. I think so. Before the monit config is fixed, we need to ignore this error.

# sflowmgrd is configed in Monit, but not included in current master branch image
# So a workaround is added for master branch. Once the issue is adressed, we should
# rm this patch
if "master" in duthost.os_version:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

os_version contains 'master' is a very specific check that only works for images built by public Jenkins and/or no tag on the latest commit. not sure if we should keep it here or ignore the event in general until the fix is in?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about adding a negative check?
if '201911' not in duthost.os_version:

Copy link
Collaborator Author

@bingwang-ms bingwang-ms Sep 24, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

os_version contains 'master' is a very specific check that only works for images built by public Jenkins and/or no tag on the latest commit. not sure if we should keep it here or ignore the event in general until the fix is in?

I add the check for master intendedly because I expect this patch only work for mater branch in a few days, as PR sonic-net/sonic-buildimage#5153 will address it. Will this issue exist in next 201911 build?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this ignore will only be needed for a few days, maybe it is better to update the common ignore file in jenkins just before running the tests?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh. That's quite a creative idea. I will apply this easy patch on Jenkins now. Thanks Xin.

@bingwang-ms
Copy link
Collaborator Author

A patch is applied on Jenkins, and no need to update code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants