Kubernetes: empty configuration for etcd slave node
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
murano-apps |
Fix Released
|
High
|
Alexander Tivelkov | ||
Kilo |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
A "etcdctl member add" command which adds slave etcd nodes to the cluster may fail if the cluster is busy when it is run;
if it happens the command has to be repeated. The code which is doing that contains a bug: it attempts to repeat the command only 5 times with a 2-second intervals between attempts.
So, if after 5 tries the execution still had not been successful, the code is just returning an empty string as a configuration setting of the newly added node. This string, beeing passed to other cluster nodes, may cause them to malfunction at some later point of environment lifecycle.
The script needs to be rewritten to do more attempts (10 second is not enough), if if none of them succeed, the job should fail at this point, without passing incorrect config any further.
Changed in murano-apps: | |
assignee: | nobody → Alexander Tivelkov (ativelkov) |
Changed in murano-apps: | |
importance: | Undecided → High |
status: | New → Confirmed |
milestone: | none → liberty-rc1 |
status: | Confirmed → Fix Committed |
Changed in murano-apps: | |
status: | Fix Committed → Fix Released |
Changed in murano-apps: | |
milestone: | liberty-rc1 → 1.0.0 |
Changed in murano-apps: | |
milestone: | 1.0.0 → 1.0.1 |
Fixed by https:/ /review. openstack. org/222832 in Liberty