Add pf-status-relay-operator

[lgarciaaco]

No description provided.

[openshift-bot]

Validating 2 file(s)...
Validating images/pf-status-relay-operator.yml...
Traceback (most recent call last):
File "/usr/local/bin/validate-ocp-build-data", line 33, in
sys.exit(load_entry_point('rh-ocp-build-data-validator==0.2.5', 'console_scripts', 'validate-ocp-build-data')())
File "/usr/local/lib/python3.9/site-packages/validator/main.py", line 87, in main
validate(f, args.exclude_vpn, args.schema_only)
File "/usr/local/lib/python3.9/site-packages/validator/main.py", line 23, in validate
support.fail_validation(msg, parsed)
File "/usr/local/lib/python3.9/site-packages/validator/support.py", line 14, in fail_validation
raise exceptions.ValidationFailed(msg)
validator.exceptions.ValidationFailed: Schema mismatch: images/pf-status-relay-operator.yml
Returned error: Additional properties are not allowed ('delivery' was unexpected)

[openshift-bot]

Validating 2 file(s)...
Validating images/pf-status-relay-operator.yml...
Traceback (most recent call last):
File "/usr/local/bin/validate-ocp-build-data", line 33, in
sys.exit(load_entry_point('rh-ocp-build-data-validator==0.2.5', 'console_scripts', 'validate-ocp-build-data')())
File "/usr/local/lib/python3.9/site-packages/validator/main.py", line 87, in main
validate(f, args.exclude_vpn, args.schema_only)
File "/usr/local/lib/python3.9/site-packages/validator/main.py", line 23, in validate
support.fail_validation(msg, parsed)
File "/usr/local/lib/python3.9/site-packages/validator/support.py", line 14, in fail_validation
raise exceptions.ValidationFailed(msg)
validator.exceptions.ValidationFailed: Schema mismatch: images/pf-status-relay-operator.yml
Returned error: Additional properties are not allowed ('delivery' was unexpected)

[openshift-bot]

Validating 2 file(s)...
Validating images/pf-status-relay-operator.yml...
Traceback (most recent call last):
File "/usr/local/bin/validate-ocp-build-data", line 33, in
sys.exit(load_entry_point('rh-ocp-build-data-validator==0.2.5', 'console_scripts', 'validate-ocp-build-data')())
File "/usr/local/lib/python3.9/site-packages/validator/main.py", line 87, in main
validate(f, args.exclude_vpn, args.schema_only)
File "/usr/local/lib/python3.9/site-packages/validator/main.py", line 23, in validate
support.fail_validation(msg, parsed)
File "/usr/local/lib/python3.9/site-packages/validator/support.py", line 14, in fail_validation
raise exceptions.ValidationFailed(msg)
validator.exceptions.ValidationFailed: Schema mismatch: images/pf-status-relay-operator.yml
Returned error: Additional properties are not allowed ('delivery' was unexpected)

[openshift-bot]

Validating 2 file(s)...
Validating images/pf-status-relay-operator.yml...
Traceback (most recent call last):
File "/usr/local/bin/validate-ocp-build-data", line 33, in
sys.exit(load_entry_point('rh-ocp-build-data-validator==0.2.5', 'console_scripts', 'validate-ocp-build-data')())
File "/usr/local/lib/python3.9/site-packages/validator/main.py", line 87, in main
validate(f, args.exclude_vpn, args.schema_only)
File "/usr/local/lib/python3.9/site-packages/validator/main.py", line 23, in validate
support.fail_validation(msg, parsed)
File "/usr/local/lib/python3.9/site-packages/validator/support.py", line 14, in fail_validation
raise exceptions.ValidationFailed(msg)
validator.exceptions.ValidationFailed: Schema mismatch: images/pf-status-relay-operator.yml
Returned error: Additional properties are not allowed ('delivery' was unexpected)

[vfreex]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vfreex

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:

• OWNERS [vfreex]

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

[lgarciaaco]

/cherry-pick main

[openshift-cherrypick-robot]

@lgarciaaco: #5771 failed to apply on top of branch "main":

Applying: chore: add pf-status-relay-operator
Using index info to reconstruct a base tree...
A	images/pf-status-relay.yml
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): images/pf-status-relay.yml deleted in HEAD and modified in chore: add pf-status-relay-operator. Version chore: add pf-status-relay-operator of images/pf-status-relay.yml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 chore: add pf-status-relay-operator

In response to this:

/cherry-pick main

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-sigs/prow repository.

[lgarciaaco]

/cherry-pick openshift-4.18

[openshift-cherrypick-robot]

@lgarciaaco: #5771 failed to apply on top of branch "openshift-4.18":

Applying: chore: add pf-status-relay-operator
Applying: Update pf-status-relay.yml
Using index info to reconstruct a base tree...
M	images/pf-status-relay.yml
Falling back to patching base and 3-way merge...
Auto-merging images/pf-status-relay.yml
CONFLICT (content): Merge conflict in images/pf-status-relay.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0002 Update pf-status-relay.yml

In response to this:

/cherry-pick openshift-4.18

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-sigs/prow repository.