B&R Optimized restore, calico cni aren't brought up
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Joshua Kraitberg |
Bug Description
Brief Description
-----------------
During optimized restore, while attempting to bring up kubernetes calico cni fails to come up.
kubectl describe -n armada pod armada-
...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 6m16s default-scheduler Successfully assigned armada/
Warning FailedCreatePod
...
Warning FailedCreatePod
Severity
--------
Critical
Steps to Reproduce
------------------
Run optimized restore
Expected Behavior
------------------
Pass
Actual Behavior
----------------
Fail
Reproducibility
---------------
100% on certain system configurations
System Configuration
-------
AIO-SX
Branch/Pull Time/Commit
-------
master branch. BUILD_ID=
Last Pass
---------
Yes, it still passes except on certain systems.
Timestamp/Logs
--------------
See above.
Test Activity
-------------
Developer Testing
Workaround
----------
Run:
sudo systemctl restart networking kubelet
Do this after networking is restore but before kubernetes is brought up.
Changed in starlingx: | |
assignee: | nobody → Joshua Kraitberg (jkraitbe-wr) |
Changed in starlingx: | |
importance: | Undecided → Medium |
description: | updated |
tags: | added: stx.8.0 stx.update |
Fix proposed to branch: master /review. opendev. org/c/starlingx /ansible- playbooks/ +/868251
Review: https:/