[debezium-operator] Fixed skip ranges

[jcechace]

No description provided.

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run7jbzr
Start Time: 2024-12-03 11:21:16+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2024-12-03 11:21:18+00:00	6 seconds
✔️	acquire-lease	2024-12-03 11:21:27+00:00	7 seconds
✔️	set-github-started-label	2024-12-03 11:21:38+00:00	9 seconds
✔️	set-github-status-pending	2024-12-03 11:21:52+00:00	9 seconds
✔️	set-env	2024-12-03 11:22:06+00:00	6 seconds
✔️	clone-repository	2024-12-03 11:22:16+00:00	44 seconds
✔️	clone-repository-base	2024-12-03 11:22:17+00:00	44 seconds
❌	detect-changes	2024-12-03 11:23:04+00:00	53 seconds

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/2d5a87a5e2faa4c63b01d8a1fd5a136f

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-hosted-pipeline in case of pipeline failure to restart a pipeline.

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-runcvzbt
Start Time: 2024-12-04 10:20:17+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2024-12-04 10:20:19+00:00	7 seconds
✔️	acquire-lease	2024-12-04 10:20:30+00:00	7 seconds
✔️	set-github-started-label	2024-12-04 10:20:42+00:00	11 seconds
✔️	set-github-status-pending	2024-12-04 10:20:55+00:00	7 seconds
✔️	set-env	2024-12-04 10:21:05+00:00	8 seconds
✔️	clone-repository	2024-12-04 10:21:17+00:00	35 seconds
✔️	clone-repository-base	2024-12-04 10:21:17+00:00	31 seconds
❌	detect-changes	2024-12-04 10:21:57+00:00	a minute

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/d5de8435485b8416906af11583a31eb5

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-hosted-pipeline in case of pipeline failure to restart a pipeline.

[jcechace]

@mporrato @Allda Is there anything that can be done to resolve the problem? Technically the bug which we introduced in older version now prevents us from publishing new version in the same channel (as they would be broken). It doesn't seem reasonable to only have this fixable by migrating to FBC --- that would technically.

The fix works as we have tested this in k8s community operators.