Comment 14 for bug 2015870

Hi Sriramu,

I haven't been able to reproduce the issue you are seeing on your environment. I would like to ask you to capture some extra logs to understand.

1. Enable magnum in debugging mode and wait until the config-changed hook completes:

    juju config magnum debug=True

2. Create a new cluster template with the settings you've tested so far.
3. Create a new cluster using the template created previously.
4. Wait until the cluster has fully deployed.
5. Capture the following logs:
    - in magnum units /var/log/magnum and /var/log/apache2 directories.
    - juju config magnum/leader date # this allow us to get a reference of the time window we need to analyze.
    - "kubectl logs -n kube-system cluster-autoscaler-XXXX" (replacing XXXX with suffix of the deployment).

Thanks in advance.