kubernetes-nat rule not applied on controller following DOR
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Andy |
Bug Description
Brief Description
-----------------
Following a Dead Office Recovery (DOR), where both controllers are restarted at the same time, the first controller does not apply the controller Puppet manifest, therefore is not fully configured, including missing the kubernetes-nat rule that permits worker hosts to access external registries for pulling images.
Severity
--------
Major
Steps to Reproduce
------------------
1) Restart both controllers simultaneously and wait for recovery.
2) Check for the existence of the iptables/ip6tables entry, it will be missing on the first controller to have recovered.
- iptables -nvL -t nat | grep kubernetes-nat
Expected Behavior
------------------
The iptables rule needs to be reapplied under all restart conditions.
Actual Behavior
----------------
The iptables rules is only applied if one of the controllers remains inservice.
Reproducibility
---------------
100% Reproducible
System Configuration
-------
Standard and AIO-DX deployments
Branch/Pull Time/Commit
-------
Present in all loads since stx3.0
Last Pass
---------
No.
Timestamp/Logs
--------------
Not applicable.
Test Activity
-------------
Normal Use.
Workaround
----------
Manually re-apply the iptables rule.
CVE References
tags: | added: stx.5.0 stx.containers stx.networking |
stx.5.0 / medium priority - issue after fault scenario (DOR); workaround exists.
TBD whether this gets ported to stx.4.0