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

[services] sflow service sets swss service as Requisite=, not Requires= #3819

Merged
merged 1 commit into from
Dec 3, 2019
Merged

[services] sflow service sets swss service as Requisite=, not Requires= #3819

merged 1 commit into from
Dec 3, 2019

Conversation

jleveque
Copy link
Contributor

The sflow service should not start unless the swss service is started. However, if this service is not started, the sflow service should not attempt to start them, instead it should simply fail to start. Using Requisite=, we will achieve this behavior, whereas using Requires= will cause the required service to be started.

@jleveque jleveque requested a review from yxieca November 26, 2019 03:48
@jleveque jleveque self-assigned this Nov 26, 2019
@jleveque
Copy link
Contributor Author

Retest mellanox please

@jleveque
Copy link
Contributor Author

Retest vs please

@jleveque
Copy link
Contributor Author

Retest vsimage please

@lguohan
Copy link
Collaborator

lguohan commented Dec 2, 2019

retest vsimage please

@lguohan lguohan merged commit 100d679 into sonic-net:master Dec 3, 2019
@jleveque jleveque deleted the sflow_requisite branch December 3, 2019 17:53
abdosi pushed a commit that referenced this pull request Jan 3, 2020
…s= (#3819)

The sflow service should not start unless the swss service is started. However, if this service is not started, the sflow service should not attempt to start them, instead it should simply fail to start. Using Requisite=, we will achieve this behavior, whereas using Requires= will cause the required service to be started.
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.

4 participants