When l2 agent execute ipset command, we should pass
parameter 'check_exit_code' to self.execute acording to
action.
The intention is to safely fail if we try to destroy a
non existing set, or delete a non existing member.
Otherwise the agent gets stuck in a loop if such situation
happens. Such kind of event would be logged as errors.
Reviewed: https:/ /review. openstack. org/224967 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=e82733f5d9a defaf4ee2a9ff4e a615c5e0cb91a9
Committed: https:/
Submitter: Jenkins
Branch: master
commit e82733f5d9adefa f4ee2a9ff4ea615 c5e0cb91a9
Author: shihanzhang <email address hidden>
Date: Fri Sep 18 10:38:43 2015 +0800
Execute ipset command using check_exit_code
When l2 agent execute ipset command, we should pass
parameter 'check_exit_code' to self.execute acording to
action.
The intention is to safely fail if we try to destroy a
non existing set, or delete a non existing member.
Otherwise the agent gets stuck in a loop if such situation
happens. Such kind of event would be logged as errors.
Change-Id: If67330523d114d 6da13d0280851e7 138a51d08f7
Closes-bug: #1497074