open-port for sidecar charms: placeholder port remains

Bug #2003782 reported by Jon Seager
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
High
Unassigned

Bug Description

When using the (newly supported!) open-port hook tool with a sidecar charm, the placeholder port (65535/tcp) remains configured, as well as the specified port.

I'm invoking the tool here: https://github.com/jnsgruk/zinc-k8s-operator/commit/2076f30311ce915aae7b982de33b03e0b4bb15ce#diff-b9ed39bbc9c0387bd3e07da31d13373745534a1cd723d3e292c73496b12e307cR79

The port is opened correctly, but if you inspect the service with kubectl, you see the following:

❯ k -n zinc get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
modeloperator ClusterIP 10.152.183.142 <none> 17071/TCP 17m
zinc-k8s-endpoints ClusterIP None <none> <none> 2m5s
zinc-k8s ClusterIP 10.152.183.247 <none> 65535/TCP,4080/TCP 2m5s

Note that 65536/TCP is still configured, where only 4080/TCP should be.

Harry Pidcock (hpidcock)
Changed in juju:
importance: Undecided → High
milestone: none → 3.1.1
status: New → Triaged
Changed in juju:
milestone: 3.1.1 → 3.1.2
Changed in juju:
milestone: 3.1.2 → 3.1.3
Changed in juju:
milestone: 3.1.3 → 3.1.4
Changed in juju:
milestone: 3.1.4 → 3.1.5
Changed in juju:
milestone: 3.1.5 → 3.1.6
Changed in juju:
milestone: 3.1.6 → 3.1.7
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.