Bug 1771249 - There is invalid json string in ptp manifests
Summary: There is invalid json string in ptp manifests
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.3.0
Assignee: zenghui.shi
QA Contact: huirwang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-12 03:41 UTC by huirwang
Modified: 2020-01-23 11:12 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-23 11:12:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ptp-operator pull 18 0 'None' closed BUG 1771249: fix syntax errors in manifests 2021-01-07 08:19:37 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:12:36 UTC

Description huirwang 2019-11-12 03:41:49 UTC
Description of problem:
There is something wrong in ptp manifests in json format

How reproduce :
Always

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


How reproducible:
Always

Steps to Reproduce:
1. Download ptp-operator repo
git clone https://github.com/openshift/ptp-operator.git
2. Verify the manifests files by
operator-courier verify manifests/

Actual results:

ERROR: metadata.annotations.alm-examples contains invalid json string [4.3/ptp-operator.v4.3.0.clusterserviceversion.yaml]
ERROR: metadata.annotations.alm-examples contains invalid json string [4.4/ptp-operator.v4.4.0.clusterserviceversion.yaml]
operatorcourier.errors.OpCourierBadBundle: Resulting bundle is invalid, input yaml is improperly defined.
Resulting bundle is invalid, input yaml is improperly defined.


Expected results:
No errors in above verify.


Additional info:

Comment 4 errata-xmlrpc 2020-01-23 11:12:18 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, 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/RHBA-2020:0062


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