Closed gustavosr98 closed 5 months ago
This issue was fixed with https://github.com/canonical/opensearch-operator/pull/249:
$ juju deploy opensearch --channel 2/edge
Located charm "opensearch" in charm-hub, revision 64
Deploying "opensearch" from charm-hub charm "opensearch", revision 64 in channel 2/edge on ubuntu@22.04/stable
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
opensearch aws-opensearch aws/eu-central-1 3.1.8 unsupported 08:36:28Z
App Version Status Scale Charm Channel Rev Exposed Message
opensearch active 1 opensearch 2/edge 64 no
tls-certificates-operator active 1 tls-certificates-operator stable 22 no
Unit Workload Agent Machine Public address Ports Message
opensearch/2* active idle 4 3.123.39.212 9200/tcp
tls-certificates-operator/1* active idle 2 3.79.185.201
[...]
Steps to reproduce
Expected behavior
I would expect to see the workload open ports under the column ports when running
juju status
Actual behavior
Versions
Operating system: Ubuntu Jammy Juju CLI: 2.9.44-ubuntu-amd64 Juju Controller: 2.9.44 Charm revision: 2/edge (rev 2) Cloud Substrate: GCP
Additional context
Workaround