persist event notifier service boots #386
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This bug is a result of applying level 3 security of the new USM introduced on SNMP V3. When the Event Notification Service is restarts , it creates a new USM object but does not update the number of time its was rebooted. This makes the service suspected by SNMP V3 and it stops getting traps from it in snmptrapd. The solution is to add a new configuration value NotificationServiceBoots which is set by default to 0. Each time the Event Notification Service is rebooted, this value is incremented by 1 and stored in the configuration table (vdc_options) When a new USM object is created on Event Notification Service run method, it set the number of boots accordint to the persisted value. This solves the problem and Event Notification Service can be restated several times and still keep getting traps on which it is listening according to its "FILTER" settings. Signed-off-by: Eli Mesika <emesika@redhat.com> Bug-Url: https://bugzilla.redhat.com/2072626
emesika
requested review from
mwperina,
ahadas,
bennyz,
michalskrivanek,
oliel,
sgratch and
didib
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This bug is a result of applying level 3 security of the new USM
introduced on SNMP V3.
When the Event Notification Service is restarts , it creates a new USM
object but does not update the number of time its was rebooted.
This makes the service suspected by SNMP V3 and it stops getting traps
from it in snmptrapd.
The solution is to add a new configuration value
NotificationServiceBoots which is set by default to 0.
Each time the Event Notification Service is rebooted, this value is
incremented by 1 and stored in the configuration table (vdc_options)
When a new USM object is created on Event Notification Service run
method, it set the number of boots accordint to the persisted value.
This solves the problem and Event Notification Service can be restated
several times and still keep getting traps on which it is listening
according to its "FILTER" settings.
Signed-off-by: Eli Mesika emesika@redhat.com
Bug-Url: https://bugzilla.redhat.com/2072626