[go.mod]Bump from v0.3.0 to pseudoversion

[gibizer]

Our intention is to track service operator and lib-common dependencies via pseudoversions. However renovate does not automatically bump from a tagged version (e.g. v0.3.0) to a newer but not tagged pseudoversion. So this patch does the manual bump. After this renovate will bump the newer pseduoversions.

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://review.rdoproject.org/zuul/buildset/d328b8ddcc7b4c4b93bc809b84d19441

❌ openstack-k8s-operators-content-provider FAILURE in 17m 46s
⚠️ podified-multinode-edpm-deployment-crc SKIPPED Skipped due to failed job openstack-k8s-operators-content-provider

[vyzigold]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gibizer, vyzigold

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 [vyzigold]

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

[vyzigold]

gotidy...................................................................Failed

• hook id: gotidy
• files were modified by this hook

[jlarriba]

/lgtm

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://review.rdoproject.org/zuul/buildset/5e6d9dfea8d847e1887e83a9b3e2e908

❌ openstack-k8s-operators-content-provider FAILURE in 16m 17s
⚠️ podified-multinode-edpm-deployment-crc SKIPPED Skipped due to failed job openstack-k8s-operators-content-provider

[jlarriba]

There it seems to be an issue with the CI, both the github-check and the kuttl deploy are failing due to the same issue:

++ /bin/bash hack/pin-bundle-images.sh
jq: error (at :1): Cannot iterate over null (null)

[abays]

There it seems to be an issue with the CI, both the github-check and the kuttl deploy are failing due to the same issue:

++ /bin/bash hack/pin-bundle-images.sh jq: error (at :1): Cannot iterate over null (null)

I also see this earlier in the build log:

open tmp/bundle_extract/csvs/manifests/telemetry-operator.clusterserviceversion.yaml: no such file or directorygoroutine 1 [running]:
runtime/debug.Stack()
	/usr/lib/golang/src/runtime/debug/stack.go:24 +0x65
runtime/debug.PrintStack()
	/usr/lib/golang/src/runtime/debug/stack.go:16 +0x19
main.exitWithError({0xc0001d9180?, 0xc0006c8340?})
	/alabama/openstack-operator/cmd/csv-merger/csv-merger.go:71 +0x33
main.main()
	/alabama/openstack-operator/cmd/csv-merger/csv-merger.go:172 +0x7d6

[abays]

/retest

[abays]

Hmm, I wonder if the problem with the build is that @gibizer 's Telemetry Operator repo is called ceilometer-operator instead of telemetry-operator? Maybe that confuses the build script, which assumes the remote forks have the same repo names openstack-k8s-operators?

[vyzigold]

Seems like I've hit the same error in my recent openstack-operator PR as well, so gibizer's repo name may not be the cause: openstack-k8s-operators/openstack-operator#643

[abays]

Seems like I've hit the same error in my recent openstack-operator PR as well, so gibizer's repo name may not be the cause: openstack-k8s-operators/openstack-operator#643

Ah, okay. I think you're probably right then and the repo name variance isn't to blame.

[jlarriba]

This PR has been submitted to all other operators and it is failing on all of them. Apparently, it seems to be related with a change in mariadb-operator. It is being debugged in openstack-k8s-operators/nova-operator#660

[abays]

This PR has been submitted to all other operators and it is failing on all of them. Apparently, it seems to be related with a change in mariadb-operator. It is being debugged in openstack-k8s-operators/nova-operator#660

Hmm. I did a retest of the equivalent Cinder patch yesterday and it succeeded: openstack-k8s-operators/cinder-operator#325. Did we fix something?

[jlarriba]

recheck

Let's try again

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://review.rdoproject.org/zuul/buildset/db84703f60444aeebd90259ac3bb9492

❌ openstack-k8s-operators-content-provider FAILURE in 24m 33s
⚠️ podified-multinode-edpm-deployment-crc SKIPPED Skipped due to failed job openstack-k8s-operators-content-provider

[jlarriba]

The same as all the other times:

error=\"no csv in bundle\"\nError: no csv in bundle\
...
~/src/github.com/openstack-k8s-operators/openstack-operator ~/ci-framework-data/artifacts", "jq: error (at <stdin>:1): Cannot iterate over null (null)", "# FIXME: hardcoded bundle below should use go.mod pinned version for manila bundle"

It seems to be a very specific error regarding manila bundle not having the csv

[abays]

The same as all the other times:

error=\"no csv in bundle\"\nError: no csv in bundle\
...
~/src/github.com/openstack-k8s-operators/openstack-operator ~/ci-framework-data/artifacts", "jq: error (at <stdin>:1): Cannot iterate over null (null)", "# FIXME: hardcoded bundle below should use go.mod pinned version for manila bundle"

It seems to be a very specific error regarding manila bundle not having the csv

That's odd. Now Glance just succeeded as well: openstack-k8s-operators/glance-operator#421. I wonder what the difference is between certain operators and others?

[openshift-ci]

New changes are detected. LGTM label has been removed.

[gibizer]

I did a rebase that picked up some go.sum changes maybe this helps.

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://review.rdoproject.org/zuul/buildset/f2835ee5b2dc46d2a603e4f19c0b9a9a

❌ openstack-k8s-operators-content-provider FAILURE in 15m 44s
⚠️ podified-multinode-edpm-deployment-crc SKIPPED Skipped due to failed job openstack-k8s-operators-content-provider

[openshift-ci]

@gibizer: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/telemetry-operator-build-deploy	3845118	link	false	/test telemetry-operator-build-deploy
ci/prow/telemetry-operator-build-deploy-kuttl	3845118	link	true	/test telemetry-operator-build-deploy-kuttl

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[gibizer]

There is some telemetry specific build error I don't really get.