issue 1954 negative usecase example

log

20:35:35 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n namespace-test-61e4539a41ec40768a4b0ec8d7716c31 --kubeconfig /home/ocsqe/data/mbukatov-dc2-cluster_20200226T131741/auth/kubeconfig get Pod fio-qk5hj -n namespace-test-61e4539a41ec40768a4b0ec8d7716c31
20:35:36 - MainThread - ocs_ci.ocs.ocp - ERROR - Waiting for Pod resource  at column STATUS to reach desired condition Completed was aborted because at least one is in unexpected Error state.
20:35:36 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n namespace-test-61e4539a41ec40768a4b0ec8d7716c31 --kubeconfig /home/ocsqe/data/mbukatov-dc2-cluster_20200226T131741/auth/kubeconfig describe Pod 
20:35:38 - MainThread - ocs_ci.ocs.ocp - WARNING - Description of the resource(s) we were waiting for:
Name:               fio-d42xz
Namespace:          namespace-test-61e4539a41ec40768a4b0ec8d7716c31
Priority:           0
PriorityClassName:  <none>
Node:               compute-1/10.70.60.58
Start Time:         Thu, 30 Apr 2020 20:35:35 +0200
Labels:             controller-uid=4d9c5cb9-8b11-11ea-a0bb-005056bee634
                    job-name=fio
Annotations:        openshift.io/scc: restricted
Status:             Pending
IP:                 
Controlled By:      Job/fio
Containers:
  fio:
    Container ID:  
    Image:         quay.io/johnstrunk/fs-performance:latest
    Image ID:      
    Port:          <none>
    Host Port:     <none>
    Command:
      /usr/bin/fio
      --output-format=json
      /etc/fio/workload.foo
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /etc/fio from fio-config-volume (rw)
      /mnt/target from fio-target (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-q696v (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  fio-target:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  fio-target
    ReadOnly:   false
  fio-config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      fio-config
    Optional:  false
  default-token-q696v:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-q696v
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Start Time:         Thu, 30 Apr 2020 20:35:04 +0200
Labels:             controller-uid=4d9c5cb9-8b11-11ea-a0bb-005056bee634
                    job-name=fio
Annotations:        k8s.v1.cni.cncf.io/networks-status: 
                    openshift.io/scc: restricted
Status:             Failed
IP:                 10.128.1.87
Controlled By:      Job/fio
Containers:
  fio:
    Container ID:  cri-o://89cab4920728a8f8326a7511abd9cf7d3d8b884f7d36428cb1098b5603b16cd2
    Image:         quay.io/johnstrunk/fs-performance:latest
    Image ID:      quay.io/johnstrunk/fs-performance@sha256:a4dc2e4531a25fffda52e3b0a814a523004e449e8ab543ea7a6d1eb0ff9dc050
    Port:          <none>
    Host Port:     <none>
    Command:
      /usr/bin/fio
      --output-format=json
      /etc/fio/workload.foo
    State:          Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Thu, 30 Apr 2020 20:35:34 +0200
      Finished:     Thu, 30 Apr 2020 20:35:34 +0200
    Ready:          False
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /etc/fio from fio-config-volume (rw)
      /mnt/target from fio-target (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-q696v (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  fio-target:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  fio-target
    ReadOnly:   false
  fio-config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      fio-config
    Optional:  false
  default-token-q696v:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-q696v
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason                  Age                From                     Message
  ----     ------                  ----               ----                     -------
  Warning  FailedScheduling        36s (x2 over 36s)  default-scheduler        pod has unbound immediate PersistentVolumeClaims (repeated 3 times)
  Normal   Scheduled               34s                default-scheduler        Successfully assigned namespace-test-61e4539a41ec40768a4b0ec8d7716c31/fio-qk5hj to compute-1
  Normal   SuccessfulAttachVolume  34s                attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-4d59a975-8b11-11ea-a0bb-005056bee634"
  Normal   Pulling                 8s                 kubelet, compute-1       Pulling image "quay.io/johnstrunk/fs-performance:latest"
  Normal   Pulled                  5s                 kubelet, compute-1       Successfully pulled image "quay.io/johnstrunk/fs-performance:latest"
  Normal   Created                 4s                 kubelet, compute-1       Created container fio
  Normal   Started                 4s                 kubelet, compute-1       Started container fio

20:35:38 - MainThread - ocs_ci.utility.workloadfixture - ERROR - exception raised during measured operation: Status of 'fio-qk5hj'  at column STATUS is Error.
20:35:42 - Thread-1 - ocs_ci.utility.workloadfixture - INFO - Logging of all prometheus alerts stopped