<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1" class="" style="word-wrap:break-word">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Commented on the bug.<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF716742"><font face="Tahoma" color="#000000" size="2"><b>From:</b> Hung Chung Chih [lyanchih@gmail.com]<br>
<b>Sent:</b> Thursday, March 16, 2017 11:35 PM<br>
<b>To:</b> openstack-dev@lists.openstack.org<br>
<b>Subject:</b> [openstack-dev] [kolla][kolla-kubernetes][helm] global value inconsistent cause install result unpredicatable<br>
</font><br>
</div>
<div></div>
<div>Hi all,
<div class="">This is my first time to send mailing list, if I had made mistake please tell me, thank you.</div>
<div class=""><br class="">
</div>
<div class="">When I try to helm install keystone service, I found it can installed succeeded but sometimes will failed with unexpected nil value for field spec.externalIPs[0]. Then I report bug at launchpad [1].</div>
<div class=""><br class="">
</div>
<div class="">Then I found this issue was occurred because of there is one variable which exist at different micro service. For example, the global.kolla.keystone.all.port_external variable at keystone-itnernal-svc and keystone-public svc, one is true and the
other is false. Before helm install package, it will catch all chart’s values inside package. However later char’s value will overwrite previous chart’s value. This will cause the final value will become unpredictable. This issue will not happened in normal
helm use case. Because of usually subchart will have its own values and helm’s global value don’t support nesting yet [2].</div>
<div class=""><br class="">
</div>
<div class="">In my view, it is a critical issue. Because of the install result will possibly be inconsistent between different install. I just suggest maybe me can add one test validate, which will validate whether there is any one variable that is conflict
at different micro services in all_values.yaml</div>
<div class=""><br class="">
</div>
<div class="">[1] <a href="https://bugs.launchpad.net/kolla-kubernetes/+bug/1670979" class="" target="_blank">https://bugs.launchpad.net/kolla-kubernetes/+bug/1670979</a></div>
<div class="">[2] <a href="https://github.com/kubernetes/helm/blob/master/docs/charts.md" class="" target="_blank">https://github.com/kubernetes/helm/blob/master/docs/charts.md</a></div>
</div>
</div>
</div>
</body>
</html>