[Starlingx-discuss] question about LP1828056

[Chen, Haochuan Z]

Hi folks

I work on LP1828056, https://bugs.launchpad.net/starlingx/+bug/1828056

Issue description:
After system deployed, begin to deploy openstack application
$ system application-upload <openstack application tarball>
$ system helm-override-update --set conf.panko.database.event_time_to_live=24828899 stx-openstack panko openstack
$ system application-apply stx-openstack

When deploy chart for osh-openstack-panko, it will deploy fail, with job panko-db-sync.
controller-0:~$ kubectl get jobs -n openstack | grep panko
panko-db-init                          1/1           37s        107m
panko-db-sync                          0/1           107m       107m
panko-events-cleaner-1563196200        0/1           90m        90m
panko-ks-endpoints                     1/1           67s        107m
panko-ks-service                       1/1           39s        107m
panko-ks-user                          1/1           62s        107m

check pod log, you will find in panko.con, "event_time_to_live = 2.4828899e+07", but it request a integer for db-sync.
/var/lib/kubelet/pods/73b84006-a6ff-11e9-ae87-525400d66765/volumes/kubernetes.io~secret/db-sync-conf/..2019_07_15_12_52_54.229165405/panko.conf
event_time_to_live = 2.4828899e+07

In /opt/platform/helm/19.01/stx-openstack/1.0-17/openstack-panko.yaml
  values:
    conf:
      panko:
        database:
          event_time_to_live: 24828899

So this is maybe tiller's issue. I find if set event_time_to_live to more than 6 digit value, it will generate a float value in panko.conf. Any idea about how to fix this issue?

Thanks!

Martin, Chen
SSP, Software Engineer
021-61164330

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190715/10257fbe/attachment-0001.html>