openshift/machine-config-operator

Illegal colon character causes go mod checksumming failure

porridge opened this issue · 4 comments

porridge commented

Description

I don't fully understand what's going on, but looks like the go mod checksum service does not like the colon in one of the files in this repo. I'm getting an error message in my IDE (GoLand) when editing a project that depends on this one.

Steps to reproduce the issue:

  1. git clone git@github.com:stackrox/stackrox.git
  2. go list -json -m -u -mod=readonly all

Describe the results you received:

go: loading module retractions for github.com/openshift/machine-config-operator@v0.0.1-0.20230815171034-c2bb862bc08a: verifying go.mod: github.com/openshift/machine-config-operator@v3.11.0+incompatible/go.mod: reading https://sum.golang.org/lookup/github.com/openshift/machine-config-operator@v3.11.0+incompatible: 404 Not Found
	server response:
	not found: create zip: pkg/controller/template/test_data/templates/aws/master/files/-etc-docker-certs.d-docker-registry.default.svc:5000-ca.crt: malformed file path "pkg/controller/template/test_data/templates/aws/master/files/-etc-docker-certs.d-docker-registry.default.svc:5000-ca.crt": invalid char ':'
	pkg/controller/template/test_data/templates/aws/worker/files/-etc-docker-certs.d-docker-registry.default.svc:5000-ca.crt: malformed file path "pkg/controller/template/test_data/templates/aws/worker/files/-etc-docker-certs.d-docker-registry.default.svc:5000-ca.crt": invalid char ':'
	[Truncated: too long.]

Describe the results you expected:

No errors.

Additional information you deem important (e.g. issue happens only occasionally):

Output of oc adm release info --commits | grep machine-config-operator:

(paste your output here)

Additional environment details (platform, options, etc.):

openshift-bot commented

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

openshift-bot commented

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci commented

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.