operator [N] [CI] nri-plugins-operator (0.3.2)

[fmuyassarov]

Submit nri-plugins-operator (0.3.2) initial version.

[github-actions]

Dear @fmuyassarov,
Some errors and/or warnings were found while doing the check of your operator (nri-plugins-operator/0.3.0) against the entire suite of validators for Operator Framework with Operator-SDK version v1.30.0 and the command $ operator-sdk bundle validate <bundle-path> --select-optional suite=operatorframework.

Errors (:bug:) must be fixed while warnings (:warning:) are informative, and fixing them might improve the quality of your solution.

Type	Message
🐛	Value : (nri-plugins-operator.v0.3.0) csv.Metadata.Annotations["categories"] value Performance is not in the set of custom categories

[fmuyassarov]

Hi @Allda @mporrato
In our operator GitHub repo we are using custom categories.json. But when we bundled the operator for submission PR checks failed because it doesn’t recognize our custom category.

We can fix the category in the operator but then we need to cut a release again and then bundle it - just for the category change right? Or is there a way to avoid cutting a new release in our operator to pass this failed check here?

[fmuyassarov]

Hi @Allda @mporrato In our operator GitHub repo we are using custom categories.json. But when we bundled the operator for submission PR checks failed because it doesn’t recognize our custom category.

We can fix the category in the operator but then we need to cut a release again and then bundle it - just for the category change right? Or is there a way to avoid cutting a new release in our operator to pass this failed check here?

We did cut a new release v0.3.1 and bundle is now updated accordingly.

[fmuyassarov]

/test all

[openshift-ci]

@fmuyassarov: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test all

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.

[fmuyassarov]

/hold

[fmuyassarov]

/test kiwi

[openshift-ci]

@fmuyassarov: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test kiwi

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.

[fmuyassarov]

/hold cancel

[framework-automation]

/merge possible

[framework-automation]

/merge possible

[framework-automation]

/merge possible

[framework-automation]

/merge possible

[fmuyassarov]

/approve
/lgtm

[openshift-ci]

@fmuyassarov: you cannot LGTM your own PR.

In response to this:

/approve
/lgtm

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.

[framework-automation]

/merge possible

[framework-automation]

/merge possible

[kad]

Looks good.

[openshift-ci]

@kad: changing LGTM is restricted to collaborators

In response to this:

/lgtm
/approve

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.

[fmuyassarov]

Hi @Allda,
Would you mind to give authorized label or approve the PR? I think it is not getting merged since it is a new operator but probably for the following releases we will be able to merge it ourselves.

[framework-automation]

/merge possible

[Allda]

@fmuyassarov Hey, yes that's correct. New operator needs to be reviewd by some of us. Followup will be merged automatically based on you ci.yaml config. Thanks for your contribution!