skip frr_bmp container from monit#22588
Conversation
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Please update "How to verify it" in PR description |
|
lgtm. |
|
hi @FengPan-Frank could you help to clarify why we don't capture this in nightly? |
Hi @StormLiangMS previously we were trading-off on using frr_bmp first or using bmp feature as one time enablement, thus for not missing last image update window, refer https://github.com/sonic-net/sonic-buildimage/pull/22148/files feature switch implementation supports either of them, as a result of that existing mgmt test overwrite golden_config test with bmp feature switch was not broken. I add one more test for frr_bmp feature switch sonic-net/sonic-mgmt#18346 |
|
@FengPan-Frank We could add this to 202411, let me know. |
Thanks @kperumalbfn. Yes please add this into 202411 |
|
Cherry-pick PR to 202411: #22603 |
|
@FengPan-Frank cherry pick PR didn't pass PR checker. Please check!!! |
…h to block regression (#18615) Approach What is the motivation for this PR? Add monit test case with disable bmp but enable frr_bmp feature switch to block regression How did you do it? Add one more test for monit syslog checking and disable bmp in advance which reflects real production config. How did you verify/test it? New test case passed without issue Used old image which does not have monit fix sonic-net/sonic-buildimage#22588 it broke the test case With new image all test verification with frr_bmp enable + bmp disable are also passed, result could be found https://dev.azure.com/mssonic/build/_build/results?buildId=859705&view=results
…h to block regression (sonic-net#18615) Approach What is the motivation for this PR? Add monit test case with disable bmp but enable frr_bmp feature switch to block regression How did you do it? Add one more test for monit syslog checking and disable bmp in advance which reflects real production config. How did you verify/test it? New test case passed without issue Used old image which does not have monit fix sonic-net/sonic-buildimage#22588 it broke the test case With new image all test verification with frr_bmp enable + bmp disable are also passed, result could be found https://dev.azure.com/mssonic/build/_build/results?buildId=859705&view=results
|
Cherry-pick PR to msft-202412: Azure/sonic-buildimage-msft#1212 |
test_posttest.py::test_recover_rsyslog_rate_limit iterates over the results of show feature status and executes the following commands: docker exec -i frr_bmp sed -i 's/^#\\$SystemLogRateLimit/\\$SystemLogRateLimit/g' /etc/rsyslog.conf docker exec -i frr_bmp supervisorctl restart rsyslogd frr_bmp shows up in show feature status but it isn't a real docker container so we should skip it. Similar PR: sonic-net/sonic-buildimage#22588 Summary: Fixes #18753
test_posttest.py::test_recover_rsyslog_rate_limit iterates over the results of show feature status and executes the following commands: docker exec -i frr_bmp sed -i 's/^#\\$SystemLogRateLimit/\\$SystemLogRateLimit/g' /etc/rsyslog.conf docker exec -i frr_bmp supervisorctl restart rsyslogd frr_bmp shows up in show feature status but it isn't a real docker container so we should skip it. Similar PR: sonic-net/sonic-buildimage#22588 Summary: Fixes sonic-net#18753
…h to block regression (sonic-net#18615) Approach What is the motivation for this PR? Add monit test case with disable bmp but enable frr_bmp feature switch to block regression How did you do it? Add one more test for monit syslog checking and disable bmp in advance which reflects real production config. How did you verify/test it? New test case passed without issue Used old image which does not have monit fix sonic-net/sonic-buildimage#22588 it broke the test case With new image all test verification with frr_bmp enable + bmp disable are also passed, result could be found https://dev.azure.com/mssonic/build/_build/results?buildId=859705&view=results Signed-off-by: opcoder0 <110003254+opcoder0@users.noreply.github.com>
test_posttest.py::test_recover_rsyslog_rate_limit iterates over the results of show feature status and executes the following commands: docker exec -i frr_bmp sed -i 's/^#\$SystemLogRateLimit/\$SystemLogRateLimit/g' /etc/rsyslog.conf docker exec -i frr_bmp supervisorctl restart rsyslogd frr_bmp shows up in show feature status but it isn't a real docker container so we should skip it. Similar PR: sonic-net/sonic-buildimage#22588 Summary: Fixes sonic-net#18753 Signed-off-by: opcoder0 <110003254+opcoder0@users.noreply.github.com>
test_posttest.py::test_recover_rsyslog_rate_limit iterates over the results of show feature status and executes the following commands: docker exec -i frr_bmp sed -i 's/^#\\$SystemLogRateLimit/\\$SystemLogRateLimit/g' /etc/rsyslog.conf docker exec -i frr_bmp supervisorctl restart rsyslogd frr_bmp shows up in show feature status but it isn't a real docker container so we should skip it. Similar PR: sonic-net/sonic-buildimage#22588 Summary: Fixes sonic-net#18753 Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
…h to block regression (sonic-net#18615) Approach What is the motivation for this PR? Add monit test case with disable bmp but enable frr_bmp feature switch to block regression How did you do it? Add one more test for monit syslog checking and disable bmp in advance which reflects real production config. How did you verify/test it? New test case passed without issue Used old image which does not have monit fix sonic-net/sonic-buildimage#22588 it broke the test case With new image all test verification with frr_bmp enable + bmp disable are also passed, result could be found https://dev.azure.com/mssonic/build/_build/results?buildId=859705&view=results Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
test_posttest.py::test_recover_rsyslog_rate_limit iterates over the results of show feature status and executes the following commands: docker exec -i frr_bmp sed -i 's/^#\\$SystemLogRateLimit/\\$SystemLogRateLimit/g' /etc/rsyslog.conf docker exec -i frr_bmp supervisorctl restart rsyslogd frr_bmp shows up in show feature status but it isn't a real docker container so we should skip it. Similar PR: sonic-net/sonic-buildimage#22588 Summary: Fixes sonic-net#18753 Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
…h to block regression (sonic-net#18615) Approach What is the motivation for this PR? Add monit test case with disable bmp but enable frr_bmp feature switch to block regression How did you do it? Add one more test for monit syslog checking and disable bmp in advance which reflects real production config. How did you verify/test it? New test case passed without issue Used old image which does not have monit fix sonic-net/sonic-buildimage#22588 it broke the test case With new image all test verification with frr_bmp enable + bmp disable are also passed, result could be found https://dev.azure.com/mssonic/build/_build/results?buildId=859705&view=results Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
test_posttest.py::test_recover_rsyslog_rate_limit iterates over the results of show feature status and executes the following commands: docker exec -i frr_bmp sed -i 's/^#\\$SystemLogRateLimit/\\$SystemLogRateLimit/g' /etc/rsyslog.conf docker exec -i frr_bmp supervisorctl restart rsyslogd frr_bmp shows up in show feature status but it isn't a real docker container so we should skip it. Similar PR: sonic-net/sonic-buildimage#22588 Summary: Fixes sonic-net#18753 Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
test_posttest.py::test_recover_rsyslog_rate_limit iterates over the results of show feature status and executes the following commands: docker exec -i frr_bmp sed -i 's/^#\\$SystemLogRateLimit/\\$SystemLogRateLimit/g' /etc/rsyslog.conf docker exec -i frr_bmp supervisorctl restart rsyslogd frr_bmp shows up in show feature status but it isn't a real docker container so we should skip it. Similar PR: sonic-net/sonic-buildimage#22588 Summary: Fixes sonic-net#18753
skip frr_bmp container from monit
…h to block regression (sonic-net#18615) Approach What is the motivation for this PR? Add monit test case with disable bmp but enable frr_bmp feature switch to block regression How did you do it? Add one more test for monit syslog checking and disable bmp in advance which reflects real production config. How did you verify/test it? New test case passed without issue Used old image which does not have monit fix sonic-net/sonic-buildimage#22588 it broke the test case With new image all test verification with frr_bmp enable + bmp disable are also passed, result could be found https://dev.azure.com/mssonic/build/_build/results?buildId=859705&view=results Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
test_posttest.py::test_recover_rsyslog_rate_limit iterates over the results of show feature status and executes the following commands: docker exec -i frr_bmp sed -i 's/^#\\$SystemLogRateLimit/\\$SystemLogRateLimit/g' /etc/rsyslog.conf docker exec -i frr_bmp supervisorctl restart rsyslogd frr_bmp shows up in show feature status but it isn't a real docker container so we should skip it. Similar PR: sonic-net/sonic-buildimage#22588 Summary: Fixes sonic-net#18753 Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
test_posttest.py::test_recover_rsyslog_rate_limit iterates over the results of show feature status and executes the following commands: docker exec -i frr_bmp sed -i 's/^#\\$SystemLogRateLimit/\\$SystemLogRateLimit/g' /etc/rsyslog.conf docker exec -i frr_bmp supervisorctl restart rsyslogd frr_bmp shows up in show feature status but it isn't a real docker container so we should skip it. Similar PR: sonic-net/sonic-buildimage#22588 Summary: Fixes sonic-net#18753 Signed-off-by: Yael Tzur <ytzur@nvidia.com>
Why I did it
frr_bmp is only feature switch used for bgpd to start as "/usr/lib/frr/bgpd -A 127.0.0.1 -M bmp", so that bmp container later rollout could work, thus is should be skipped from container check.
Work item tracking
How I did it
skip container check from monit.
How to verify it
before fix

after fix, the error log disappears.
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)