canonical / manual-tls-certificates-operator

A charmed operator for managing TLS certificates manually.
https://charmhub.io/manual-tls-certificates
Apache License 2.0
2 stars 11 forks source link

ca-common-name is not support in rev 50 from latest/edge #100

Closed jeffreychang911 closed 8 months ago

jeffreychang911 commented 8 months ago

Describe the bug

SolQA tried to deplot tls-certificates-operator rev 50 from latest/edge channel with kafka, but end up failed because "ca-common-name" is not supported.

To Reproduce

$ juju deploy tls-certificates-operator --channel edge --config generate-self-signed-certificates="true" --config ca-common-name="10" ERROR unknown option "ca-common-name" ERROR failed to deploy charm "tls-certificates-operator"

$ juju deploy tls-certificates-operator --channel stable --config generate-self-signed-certificates="true" --config ca-common-name="10" Deployed "tls-certificates-operator" from charm-hub charm "tls-certificates-operator", revision 22 in channel stable on ubuntu@22.04/stable

Expected behavior

This should work as stable channel.

Screenshots

Logs

2023-12-16-16:10:15 root DEBUG - upload charm tls-certificates-operator from charm-hub for base ubuntu@22.04/stable from channel latest/edge with architecture=amd64 2023-12-16-16:10:15 root DEBUG 16:10:15 INFO juju.cmd.juju.application.deployer baseselector.go:121 with the user specified base "ubuntu@22.04/stable" 2023-12-16-16:10:15 root DEBUG 16:10:15 INFO juju.cmd.juju.application.deployer baseselector.go:200 with the user specified base "ubuntu@22.04/stable" 2023-12-16-16:10:15 root DEBUG 16:10:15 DEBUG juju.cmd.juju.application.deployer bundlehandler.go:690 added charm ch:amd64/jammy/tls-certificates-operator-50 for channel latest/edge 2023-12-16-16:10:15 root DEBUG 16:10:15 DEBUG juju.cmd.juju.application.deployer bundlehandler.go:1662 resolve "$addCharm-6" from map[string]string{"addCharm-0":"ch:amd64/jammy/kafka-146", "addCharm-2":"ch:amd64/jammy/grafana-agent-28", "addCharm-4":"ch:amd64/jammy/ntp-50", "addCharm-6":"ch:amd64/jammy/tls-certificates-operator-50", "deploy-1":"kafka", "deploy-3":"kafka-agent", "deploy-5":"ntp"} 2023-12-16-16:10:15 root DEBUG - deploy application tls-certificates-operator from charm-hub on ubuntu@22.04/stable with latest/edge 2023-12-16-16:10:15 root DEBUG 16:10:15 DEBUG juju.api monitor.go:35 RPC connection died 2023-12-16-16:10:15 root DEBUG 16:10:15 DEBUG juju.api monitor.go:35 RPC connection died 2023-12-16-16:10:15 root DEBUG ERROR cannot deploy bundle: cannot deploy application "tls-certificates-operator": unknown option "ca-common-name" 2023-12-16-16:10:15 root DEBUG 16:10:15 DEBUG cmd supercommand.go:549 error stack: 2023-12-16-16:10:15 root DEBUG unknown option "ca-common-name" 2023-12-16-16:10:15 root DEBUG github.com/juju/juju/api/client/application.(Client).Deploy:178: 2023-12-16-16:10:15 root DEBUG github.com/juju/juju/cmd/juju/application.(deployAPIAdapter).Deploy:93: 2023-12-16-16:10:15 root DEBUG github.com/juju/juju/cmd/juju/application/deployer.(bundleHandler).addApplication:918: cannot deploy application "tls-certificates-operator" 2023-12-16-16:10:15 root DEBUG github.com/juju/juju/cmd/juju/application/deployer.(bundleHandler).handleChanges:561: 2023-12-16-16:10:15 root DEBUG github.com/juju/juju/cmd/juju/application/deployer.bundleDeploy:100: 2023-12-16-16:10:15 root DEBUG github.com/juju/juju/cmd/juju/application/deployer.(*deployBundle).deploy:117: cannot deploy bundle 2023-12-16-16:10:15 root ERROR [localhost] Command failed: juju deploy -m foundations-maas:kafka --debug /home/ubuntu/project/generated/kafka/bundle.yaml 2023-12-16-16:10:15 root ERROR 1[localhost] STDOUT follows: Executing changes:

Environment

Additional context

This is from SolQA test run - https://solutions.qa.canonical.com/testruns/b0bd64d2-b148-4e7c-a392-2e149dd6fe3a All artifacts can be found here - https://oil-jenkins.canonical.com/artifacts/b0bd64d2-b148-4e7c-a392-2e149dd6fe3a/index.html

gruyaume commented 8 months ago

Hello @jeffreychang911 , this is the intended behavior of manual-tls-certificates and not a bug. If you need self-signed certificates, please use the self-signed certificates charm. For more information about all the potential TLS integrations, there's this Security with X.509 certificates Charmhub topic