User application pod stuck in Container Creating state after upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Andre Kantek |
Bug Description
Brief Description
Customer had to delete a POD manually that was stuck in the "container creating" state after platform upgrade
The issue was seen BEFORE any K8s upgrade was attempted.
Severity
Major - Manual intervention is required to delete the POD so the deployment can create a new one.
Steps to Reproduce
POD is running on previous version as AIO_SX_Subcloud requesting a single SRIOV interface.
Operator upgraded the subcloud and Found the POD stuck in container creating state. After 2.5 hours of system left in the same state, customer deleted the POD and a new POD was created.
Expected Behavior
PODs controlled by deployment/
labels:
app: adpf29991502555
nename: adpf29991502555
release: samsungadpf-
Actual Behavior
2022-11-
Followed by non-stop error messages:
2022-11-
Reproducibility
Although the POD went to a container-creating state during the Upgrade (with the same error message, VF pci addr is required). The Pod was recreated by the deployment as expected.
System Configuration
AIO_SX_Subcloud
Changed in starlingx: | |
assignee: | nobody → Andre Kantek (akantek) |
summary: |
- Customer application pod stuck in Container Creating state after upgrade + User application pod stuck in Container Creating state after upgrade |
tags: | added: stx.8.0 stx.networking |
Changed in starlingx: | |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. opendev. org/c/starlingx /integ/ +/866878
Review: https:/