Skip to content

[action] [PR:3698] Fix monit connection failure when doing routeCheck/contianerCheck monitor enable after config reload (#3698) #3699

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

Merged
merged 1 commit into from
Dec 27, 2024

Conversation

mssonicbld
Copy link
Collaborator

Fix:
sonic-net/sonic-buildimage#21268

How I did:
Reorder the sequence of doing enabling container_cheek and routeCheck before doing monit reload to avoid transient issue of monit sock error.

Also I add a sleep of 1 sec to make sure monitor enable configuration takes effect before we do reload.

…itor enable after config reload (sonic-net#3698)

Fix:
sonic-net/sonic-buildimage#21268

How I did:
Reorder the sequence of doing enabling container_cheek and routeCheck before doing monit reload to avoid transient issue of monit sock error.

Also I add a sleep of 1 sec to make sure monitor enable configuration takes effect before we do reload.
@mssonicbld
Copy link
Collaborator Author

Original PR: #3698

@mssonicbld
Copy link
Collaborator Author

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld mssonicbld merged commit e0a268a into sonic-net:202405 Dec 27, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants