Bug 2000253 - oc edit ptpconfig causes cloudevent sidecar to crash and restart
Summary: oc edit ptpconfig causes cloudevent sidecar to crash and restart
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Native Events
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.9.0
Assignee: Aneesh Puttur
QA Contact: or marziano
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-01 16:40 UTC by Aneesh Puttur
Modified: 2021-10-18 17:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:50:51 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 63 0 None None None 2021-09-01 16:47:24 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:51:03 UTC

Description Aneesh Puttur 2021-09-01 16:40:49 UTC
Description of problem:
Editing ptpconfig via oc edit crashes event sidecar 


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


How reproducible:
oc edit ptp-config.yaml and save



Actual results:
 sidecar crashes and restarts 


Expected results:
  containers should run all fine 

Additional info:

Comment 2 or marziano 2021-09-13 10:43:07 UTC
When i apply new ptpConfig or edit, the container stays up.

version: v4.9.0.202109080733.p0.git.e5b504a.assembly.art3171-1

Comment 5 errata-xmlrpc 2021-10-18 17:50:51 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.9.0 bug fix and 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-2021:3759


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