Bug 2004721 - ptp/worker custom threshold doesn't change ptp events threshold
Summary: ptp/worker custom threshold doesn't change ptp events threshold
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Native Events
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.10.0
Assignee: Nishant Parekh
QA Contact: obochan
URL:
Whiteboard:
Depends On:
Blocks: 2004137
TreeView+ depends on / blocked
 
Reported: 2021-09-15 19:35 UTC by Nishant Parekh
Modified: 2022-03-10 16:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2004137
Environment:
Last Closed: 2022-03-10 16:10:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github redhat-cne cloud-event-proxy pull 71 0 None open Bug 2004721: Fixed ptp threshold updates not updating values for CLOCK_REALTIME 2021-09-16 15:45:14 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:11:36 UTC

Comment 4 obochan 2022-01-19 19:15:18 UTC
issue was tested with only SNO with version :

Client Version: 4.8.0
Server Version: 4.10.0-0.nightly-2021-12-21-130047
Kubernetes Version: v1.22.1+6859754

when testing testing it the SNO had 2 master and we changed the thresholds to 40 and 60 , we were able to see that the system after around 1 min started sync with the new offset moving to FREERUN and LOCKED for the active nics - the events were generated properly

Comment 8 errata-xmlrpc 2022-03-10 16:10:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0056


Note You need to log in before you can comment on or make changes to this bug.