Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2110015

Summary:	Changes to PTP configuration will cause unnecessary updates in customer configurations
Product:	OpenShift Container Platform	Reporter:	Ian Miller <imiller>
Component:	Telco Edge	Assignee:	Ian Miller <imiller>
Telco Edge sub component:	ZTP	QA Contact:	yliu1
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	medium
Priority:	unspecified
Version:	4.11
Target Milestone:	---
Target Release:	4.12.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-04-30 18:04:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2115875

Description Ian Miller 2022-07-22 18:16:29 UTC

Description of problem: The change to logSyncInterval and summary_interval in the base sourceCRs and reference PolicyGenTemplates will cause unneeded updates to the customers configurations. Due to BZ 2057566 this will cause a duplicate entry in the PTP config causing additional work on the customer to resolve.

The changes are not required because the underlying issue for BZ 2040799 (validating webhook in PTP operator) was fixed. The configuration changes should be reverted.


Version-Release number of selected component (if applicable): 4.12, 4.11


How reproducible: 100%


Steps to Reproduce:
1. Note changes to summary_interval and logSyncInterval (both set to 0 instead of prior -4) in the source CRs in the ZTP container.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 yliu1 2022-08-05 15:33:41 UTC

Mark as verified to unblock backporting as qe can't verify on 4.12 yet. Will verify on 4.11 once backported.

Comment 2 Rory Thrasher 2024-04-30 18:04:53 UTC

OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary