Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

OCP4 - first path segment in URL cannot contain colon #2174

Closed
mvazquezc opened this issue Jun 20, 2019 · 2 comments
Closed

OCP4 - first path segment in URL cannot contain colon #2174

mvazquezc opened this issue Jun 20, 2019 · 2 comments
Labels
blocked-needs-validation Issue is waiting to be validated before we can proceed bug

Comments

@mvazquezc
Copy link

Describe the bug
When running flux on OpenShift 4, it fails to parse the image-registry url.

To Reproduce
Steps to reproduce the behaviour:

Deploy flux on OpenShift 4 following the steps documented here

Tail the flux logs.

Expected behavior
The image-registry url is parsed correctly.

Logs

172.31.76.157 corresponds to the image-registry service:

image-registry ClusterIP 172.31.76.157 5000/TCP

ts=2019-06-20T10:15:25.794557659Z caller=images.go:106 resource=flux:deployment/flux err="parse 172.31.76.157:5000: first path segment in URL cannot contain colon"
ts=2019-06-20T10:15:25.802524618Z caller=images.go:106 resource=flux:deployment/memcached err="parse 172.31.76.157:5000: first path segment in URL cannot contain colon"
ts=2019-06-20T10:16:25.784916558Z caller=images.go:106 resource=flux:deployment/flux err="parse 172.31.76.157:5000: first path segment in URL cannot contain colon"
ts=2019-06-20T10:16:25.79297563Z caller=images.go:106 resource=flux:deployment/memcached err="parse 172.31.76.157:5000: first path segment in URL cannot contain colon"

Additional context

  • Flux version: docker.io/weaveworks/flux:1.13.0
  • Helm Operator version: N/A
  • Kubernetes version: v1.13.4
  • Git provider: GitHub
  • Container registry provider: OpenShift Image Registry
@mvazquezc mvazquezc added blocked-needs-validation Issue is waiting to be validated before we can proceed bug labels Jun 20, 2019
@hiddeco
Copy link
Member

hiddeco commented Jun 24, 2019

What does the full image ref look like?

@hiddeco
Copy link
Member

hiddeco commented Jul 12, 2019

This should have been resolved by #2248

@hiddeco hiddeco closed this as completed Jul 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocked-needs-validation Issue is waiting to be validated before we can proceed bug
Projects
None yet
Development

No branches or pull requests

2 participants