Charm configs don't get updated in database

[Alvaro Uria]

Some charm configurations don't get updated in the database after the initial deployment. Namely setting the following after a successful deploy:

* juju model-config http-proxy=http://my-little-proxy:8080/ https-proxy=http://my-little-proxy:8080/
* juju config landscape-server root-url=https://myscape/

Values appear in configuration files, but not in the database (system_configuration) and thus web UI.

[Andreas Hasenack (ahasenack)]

Related, if not a duplicate: https://bugs.launchpad.net/landscape/+bug/1523950

Even when not deploying via the charm this issue is present.

[Andrea Ieri (aieri)]

Also to be considered: proxy variables can be set in either the legacy http-proxy / https-proxy variables or the charm-specific juju-http-proxy / juju-https-proxy. (at least) The latter set should be supported.
The workaround is to manually hack proxy variables in /opt/canonical/landscape/scripts/landscape-env.sh

[Andrea Ieri (aieri)]

Er... the workaround should be to manually edit /etc/environment, not /opt/canonical/landscape/scripts/landscape-env.sh

[Andrea Ieri (aieri)]

Another workaround is to set the proxy in the web GUI, under Settings -> Proxy for HTTP and HTTPS traffic (and restart)

[semidark (nthomaier)]

I edited the /etc/enviroment and added the Proxy entries as I need them.
also I added the Proxy Information in the Web GUI. Restarted everything...

But the update_security_db.sh is still failing.

When trying to download the Database File via wget on the console, everything is working fine.

So none of the Workarounds is working for me.

[Simon Poirier (simpoir)]

Setting in the GUI is most definitely not a workaround to the script errors, due to #1523950 .

Additionally, the current charms does honor http-proxy,https-proxy,no-proxy model settings on install. Setting prior to the deploy

  juju model-config http-proxy=http://my-little-proxy:8080/ https-proxy=http://my-little-proxy:8080/
  juju deploy landscape-scalable

I did get those values set correctly in the web UI without doing anything.

So the way I see it, what's missing is:

1) fixing the scripts through #1523950
2) adding a hook for config changes to possibly override values, although we don't currently do that for any config post-bootstrap

I'd flag this as duplicate if it were not for 2)

[Arif Ali (arif-ali)]

We tried to the same thing with root-url today, as we had issues with SSL certs and such.

And this was resolved by updating the Root URL on the UI. However, we then tried to sort it out via the root-url configuration from he charm, it did not update it in the UI.

Looking through the code, it updates /etc/landscape/service.conf when root-url is changed, but doesn't update the Root URL on the UI. We were expecting that to change for us, rather than having to do it manually