Closed baycarbone closed 4 months ago
Hi @baycarbone ,
The mainfest.yaml
you have provided has a commented out line which shouldn't be commented out: # charms:
.
I tried with the following manifest.yaml:
deployment:
bootstrap:
management_cidr: 10.20.0.0/24
haproxy:
virtual_ip: 10.20.0.80
postgres:
max_connections: 110
software:
charms:
postgresql:
config:
experimental_max_connections: 120
pgbouncer:
channel: 1/stable
config:
pool_mode: transaction
Which is overriding many things, including the final max_connections value that will be used for postgresql. After a successful bootstrap, I was able to observer that instead of default pool_mode: session
and experimental_max_connections: 110
that Anvil typically sets, the overridden values where chosen:
ubuntu@maas-1:~$ juju config pgbouncer pool_mode
transaction
ubuntu@maas-1:~$ juju config postgresql experimental_max_connections
120
ubuntu@maas-1:~$ vim .config/anvil/manifest.yaml
Full logs are available here: https://paste.ubuntu.com/p/tCWyqN4hNX/
I would suggest to try again with a proper manifest.yaml
, if you still have the need for explicitly overriding Anvil values.
Thank you for your time to report this issue.
Versions:
When running the bootstrap command and specifying a manifest file (e.g. to change some charm config options), it looks like the manifest file is ignored.
Manifest file:
Command:
maas-anvil -v cluster bootstrap --manifest /home/ubuntu/.config/anvil/config.yaml --role database --role region --role agent --role haproxy
Log output: (full log: https://pastebin.canonical.com/p/K4t3TYQjgS/)