Skip to content

Conversation

@QiaolingTang
Copy link
Contributor

@QiaolingTang QiaolingTang commented Nov 4, 2019

Fix issue: ERROR: metadata.annotations.alm-examples contains invalid json string [4.3/cluster-logging.v4.3.0.clusterserviceversion.yaml] when pushing manifests to quay.

Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1768537

@openshift-ci-robot openshift-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Nov 4, 2019
@richm richm added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 4, 2019
@jcantrill jcantrill changed the title fix issue: metadata.annotations.alm-examples contains invalid json string Bug 1768537: metadata.annotations.alm-examples contains invalid json string Nov 4, 2019
@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Nov 4, 2019
@openshift-ci-robot
Copy link

@QiaolingTang: This pull request references Bugzilla bug 1768537, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Bug 1768537: metadata.annotations.alm-examples contains invalid json string

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot
Copy link

@QiaolingTang: This pull request references Bugzilla bug 1768537, which is valid.

In response to this:

Bug 1768537: metadata.annotations.alm-examples contains invalid json string

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcantrill
Copy link
Contributor

/ok-to-test

@openshift-ci-robot openshift-ci-robot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Nov 4, 2019
@QiaolingTang QiaolingTang force-pushed the fix_invalid_json_string branch from 90b9b1a to bd8c8d9 Compare November 5, 2019 00:16
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 5, 2019
@jcantrill
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 5, 2019
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill, QiaolingTang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 5, 2019
@openshift-merge-robot openshift-merge-robot merged commit 96a907d into openshift:master Nov 5, 2019
@openshift-ci-robot
Copy link

@QiaolingTang: All pull requests linked via external trackers have merged. Bugzilla bug 1768537 has been moved to the MODIFIED state.

In response to this:

Bug 1768537: metadata.annotations.alm-examples contains invalid json string

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@QiaolingTang QiaolingTang deleted the fix_invalid_json_string branch November 6, 2019 00:32
pmoogi-redhat pushed a commit to pmoogi-redhat/cluster-logging-operator that referenced this pull request Apr 26, 2022
…tring

Bug 1768537: metadata.annotations.alm-examples contains invalid json string
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants