Amazing, Angie! I succeed install panko with this command now.

helm install starlingx/panko --values aa.yaml -n osh-openstack-panko --namespace openstack

controller-0:/var/lib/kubelet$ kubectl get jobs -n openstack | grep panko

panko-db-init                          1/1           50s        100s

panko-db-sync                          1/1           67s        100s

panko-ks-endpoints                     1/1           67s        100s

panko-ks-service                       1/1           48s        100s

panko-ks-user                          1/1           56s        100s

I create aa.yaml with excerpt value in armada manifest file and generated override file for chart panko, and add this field.

  conf:

    panko:

      database:

        event_time_to_live: "24568998"

So for LP1828056 fix solution, currently system helm-override-update has only –set <overrides>. I will add –set-string option.

https://bugs.launchpad.net/starlingx/+bug/1828056

Thanks

Martin, Chen

SSP, Software Engineer

021-61164330

From: Wang, Jing (Angie) [mailto:Angie.Wang@windriver.com]
Sent: Wednesday, July 17, 2019 7:24 AM
To: Chen, Haochuan Z <haochuan.z.chen@intel.com>; starlingx-discuss@lists.starlingx.io
Subject: RE: question about LP1828056

Hi Marin,

In the helm chart values.yaml , if the value has only numbers(at least 8), helm will cast it to float64. We need to add single/double quotes to the overrided value(if it contains only numbers) to force it to be a string, then helm would be able to parse it correctly.

Ie…

system helm-override-update –value panko.yaml

cat panko.yaml

conf:

  panko:

    database:

      event_time_to_live: "555555555555"

But I cannot override it with quotes added via system helm-override-update with --set option.

The openstack-helm LP you created https://bugs.launchpad.net/openstack-helm/+bug/1836744 is invalid. This is not related to openstack-helm.

There had couples of helm issues regarding to the float number, it fixed in commit https://github.com/helm/helm/pull/3599

So if you need to use –set-string option to override the value(if it contains only numbers and at least 8)

Ie. helm install panko –set-string conf.panko.database.event_time_to_live=24828899

Thanks,

-Angie

From: Chen, Haochuan Z [mailto:haochuan.z.chen@intel.com]
Sent: July-15-19 10:53 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] question about LP1828056

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