controller-1 in failed state due to puppet cfg for firewall failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Don Penney |
Bug Description
Brief Description
-----------------
Controller-1 came up in failed state after lock/unlock due to puppet firewall cfg failed
Severity
--------
Major
Steps to Reproduce
------------------
1. Bring up the system and lock/unlock controller-1
Expected Behavior
------------------
controller-1 to be in enabled/available state
Actual Behavior
----------------
controller-1 is in enabled/failed state
Reproducibility
---------------
intermittent
System Configuration
-------
2+2 system
Branch/Pull Time/Commit
-------
JOB="STX_
<email address hidden>"
BUILD_NUMBER="42"
BUILD_HOST=
BUILD_DATE=
Timestamp/Logs
--------------
2019-02-
2019-
2019-
2019-
2019-
2019-
2019-
2019-
2019-
tags: | added: stx.containers |
tags: |
added: stx.2.0 removed: stx.2019.05 |
Marking as release gating; related to container env
- For now, using this bug, the plan is to disable the Puppet firewall configuration
- Longer term, a task will be created to move the firewall configuration to calico CI