juju upgrade-controller with custom caas-image-repo failed

Bug #1935953 reported by Tu Pham
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju
High
Yang Kelvin Liu

Bug Description

Setting caas-image-repo=192.168.1.1:8000 causes juju upgrade-controller failed with error:

```
ERROR Get "https://registry.hub.docker.com/v1/repositories/192.168.1.1:8000/jujusolutions/jujud-operator/tags": dial tcp: lookup registry.hub.docker.com on 127.0.0.53:53: read udp 127.0.0.1:49299->127.0.0.53:53: i/o timeout.
```

This bug is caused by malformed registry URL generated by the ListOperatorImages function in the docker package.

Tags: k8s Edit Tag help
Tu Pham (tupm)
description: updated
Ian Booth (wallyworld)
Changed in juju:
milestone: none → 2.9.10
importance: Undecided → High
status: New → Triaged
Changed in juju:
assignee: nobody → Yang Kelvin Liu (kelvin.liu)
status: Triaged → In Progress
Changed in juju:
milestone: 2.9.10 → 2.9.11
Changed in juju:
milestone: 2.9.11 → 2.9.12
Changed in juju:
milestone: 2.9.12 → 2.9.13
tags: added: k8s
Changed in juju:
milestone: 2.9.13 → 2.9.14
Revision history for this message
John A Meinel (jameinel) wrote :

I know Kelvin was working on this earlier, but I thought it actually landed. Which version was this fixed in? Is it part of the other authentication work, so would all be part of 2.9.13?

Revision history for this message
Yang Kelvin Liu (kelvin.liu) wrote :

This should be part of the authentication work. You know, the whole authentication work is still work in process. The dockerhub is done, but we are still integrating other providers. So I keep these related bugs open for now.

Changed in juju:
milestone: 2.9.14 → 2.9.15
Changed in juju:
milestone: 2.9.15 → 2.9.16
Changed in juju:
milestone: 2.9.16 → 2.9.17
Revision history for this message
Yang Kelvin Liu (kelvin.liu) wrote :
Changed in juju:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers