Actions
Issue #5846
closedWhen Travis CI fails to see the operator's services come up, insufficient debug is outputted
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:
Description
plugin-template has pulp-operator.git be checked out, and it checks/waits for the containers & operators to be fully running by running pulp-operator.git/pulp-operator-check-and-wait.sh .
If say the operator cannot be downloaded, there is insufficient debug info why:
ERROR 2: 1 or more external services never came up
SERVICES:
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.43.0.1 <none> 443/TCP 2m50s
VOLUMES:
No resources found in default namespace.
No resources found in default namespace.
Filesystem Size Used Avail Use% Mounted on
udev 3.7G 0 3.7G 0% /dev
tmpfs 748M 8.8M 739M 2% /run
/dev/sda1 68G 13G 56G 19% /
tmpfs 3.7G 8.0K 3.7G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.7G 0 3.7G 0% /sys/fs/cgroup
none 768M 44M 725M 6% /var/ramfs
tmpfs 748M 0 748M 0% /run/user/2000
NAME READY STATUS RESTARTS AGE
local-path-provisioner-56db8cbdb5-qg4sc 1/1 Running 0 2m36s
error: expected 'logs [-f] [-p] (POD | TYPE/NAME) [-c CONTAINER]'.
POD or TYPE/NAME is a required argument for the logs command
See 'kubectl logs -h' for help and examples
The command ".travis/install.sh" failed and exited with 2 during .
Your build has been stopped.
Where as if it failed with ERROR 3 (checking that the pods have transitioned to the running state), you would see enough debug info.
Added by Mike DePaulo over 4 years ago
Updated by mdepaulo@redhat.com over 4 years ago
- Subject changed from When Travis CI fails to see the operator's services some up, insufficient debug is outputted to When Travis CI fails to see the operator's services come up, insufficient debug is outputted
Updated by mdepaulo@redhat.com over 4 years ago
- Status changed from NEW to 5
Waiting to see it in action when a travis build randomly fails.
Updated by mdepaulo@redhat.com about 4 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Actions
Problem: When Travis CI fails to see the operator's services come up, insufficient debug is outputted
Solution: Output the running pods and the docker image cache at that
stage of pulp-operator-check-and-wait.sh
Fixes: #5846