- 
    
Bug
 - 
    Resolution: Unresolved
 - 
    
Critical
 - 
    4.20, 4.21
 
- 
        Quality / Stability / Reliability
 - 
        False
 - 
        
 - 
        None
 - 
        None
 - 
        None
 
- 
        None
 - 
        Rejected
 - 
        None
 
- 
        In Progress
 - 
        Release Note Not Required
 - 
        None
 
- 
        None
 - 
        None
 - 
        None
 - 
        None
 
Description of problem:
A cold boot test where both nodes are shut down in an ungraceful manner. Once the virsh list command verifies the VMs are no longer running, I start the VMs. [core@master-1 ~]$ sudo pcs resource status * Clone Set: kubelet-clone [kubelet]: * Started: [ master-0 master-1 ] * Clone Set: etcd-clone [etcd]: * Stopped: [ master-0 master-1 ]
Version-Release number of selected component (if applicable):
    
How reproducible:
80%
Steps to Reproduce:
 1. Deploy a TNF cluster using TNT
 2. Power each node using virsh destroy <node name>
 3. Wait for the nodes to no longer be un running state 
       (virsh list --all)
 4. Start each node
 5. Check the running state of pcs
    
Actual results:
    the etcd-podman does not seem to start, so etcd does not start
Expected results:
    The cluster should be recreated, and should be in working order.
Additional info:
    
- blocks
 - 
                    
OCPBUGS-63249 cold boot test both nodes ungraceful shutdown results in unresponsive cluster
-         
 - Closed
 
 -         
 
- is cloned by
 - 
                    
OCPBUGS-63249 cold boot test both nodes ungraceful shutdown results in unresponsive cluster
-         
 - Closed
 
 -         
 
- is duplicated by
 - 
                    
OCPBUGS-60533 cold boot test one node ungraceful, other graceful results in unresponsive cluster
-         
 - Closed
 
 -         
 
- links to