Skip to content
This repository has been archived by the owner on Jun 28, 2024. It is now read-only.

CI failure: no tracing span status #1735

Closed
bergwolf opened this issue Jun 19, 2019 · 2 comments
Closed

CI failure: no tracing span status #1735

bergwolf opened this issue Jun 19, 2019 · 2 comments
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team.

Comments

@bergwolf
Copy link
Member

Description of problem

Saw at http://jenkins.katacontainers.io/job/kata-containers-runtime-fedora-PR/2276/console

15:02:59 INFO: Enabling kata tracing on /usr/share/defaults/kata-containers/configuration.toml
15:02:59 INFO: Checking runtime spans
15:03:04 ERROR: no span status
15:03:05 jaeger
15:03:05 jaeger
15:03:05 INFO: Disabling kata tracing on /usr/share/defaults/kata-containers/configuration.toml
15:03:06 make: *** [Makefile:150: tracing] Error 1
15:03:06 Build step 'Execute shell' marked build as failure
15:03:13 Performing Post build task...
15:03:13 Match found for :.* : True
15:03:13 Logical operation result is TRUE
15:03:13 Running script  : #!/bin/bash

Is it because jaeger not configured? /cc @jodh-intel

@jodh-intel
Copy link
Contributor

Hi @bergwolf - difficult to tell as we're not yet capturing the logfile from the tracing test (see kata-containers/ci#182).. I'll try to recreate locally but I suspect this might be a transitory issue.

@GabyCT
Copy link
Contributor

GabyCT commented Nov 4, 2019

Closing this issue as this 39d862c is already merged

@GabyCT GabyCT closed this as completed Nov 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team.
Projects
None yet
Development

No branches or pull requests

3 participants