Skip to content
This repository was archived by the owner on May 6, 2020. It is now read-only.

Conversation

@jodh-intel
Copy link

Display the shim log messages at the end of the CI Run.

Fixes #605.

Signed-off-by: James O. D. Hunt james.o.hunt@intel.com

Display the shim log messages at the end of the CI Run.

Fixes clearcontainers#605.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
@clearcontainersbot
Copy link

kubernetes qa-passed 👍

Copy link
Contributor

@grahamwhaley grahamwhaley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

echo "Clear Containers Proxy Log:"
sudo journalctl --no-pager -u cc-proxy
echo "Clear Containers Shim Log:"
sudo journalctl --no-pager -t cc-shim
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a query/note...
I guess this will show all of the shim log for all of its lifetime - which, my gut tells me we may not want it that contains info from (many) previous runs.... but, then my head tells me that this code is currently specifically run in one-shot VMs, so the only log it should have is from this specific test run...
Just noting like - and considering if in the future we might need to take note of the start time of the test run, and then trim the log to include only data from this run, iyswim.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. We probably need @chavafg to comment. I personally wipe the journal before running tests locally. Atleast once clearcontainers/shim#90 lands this dump from the beginning-of-time will allow us to atleast link the shim entries with the other pieces.

It's worth noting that once #590 lands, we could be a little cleverer and have the CI call the cc-log-parser tool as described on its README on teardown so that you'd atleast have a time-ordered dump of the run.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can wait until #590 lands and see if that makes debugging easier, if not we can start looking other ideas.

@grahamwhaley
Copy link
Contributor

You have a Fedora CI fail - huge log. I found this, which I suspect may not actually be the problem, but will post anyhow...

Oct 12 12:56:20 jenkins-azure-vm-fedora-26-7a1ef0.localdomain cc-proxy[16593]: time="2017-10-12T12:56:20.439583771Z" level=debug msg="         Starting Journal Service..." source=qemu vm=gKg6SwRaGEld94HqooJs
Oct 12 12:56:20 jenkins-azure-vm-fedora-26-7a1ef0.localdomain cc-proxy[16593]: time="2017-10-12T12:56:20.445137532Z" level=debug msg="         Starting Create Static Device Nodes in /dev..." source=qemu vm=gKg6SwRaGEld94HqooJs
Oct 12 12:56:20 jenkins-azure-vm-fedora-26-7a1ef0.localdomain cc-proxy[16593]: time="2017-10-12T12:56:20.453490372Z" level=debug msg="         Starting Apply Kernel Variables..." source=qemu vm=gKg6SwRaGEld94HqooJs
Oct 12 12:56:20 jenkins-azure-vm-fedora-26-7a1ef0.localdomain cc-proxy[16593]: time="2017-10-12T12:56:20.462636207Z" level=debug msg="         Starting Load/Save Random Seed..." source=qemu vm=gKg6SwRaGEld94HqooJs
Oct 12 12:56:20 jenkins-azure-vm-fedora-26-7a1ef0.localdomain cc-proxy[16593]: time="2017-10-12T12:56:20.471396845Z" level=debug msg="         Mounting Temporary Directory (/tmp)..." source=qemu vm=gKg6SwRaGEld94HqooJs
Oct 12 12:56:20 jenkins-azure-vm-fedora-26-7a1ef0.localdomain cc-proxy[16593]: time="2017-10-12T12:56:20.475204818Z" level=debug msg="[\x1b[0;32m  OK  \x1b[0m] Set up automount Arbitrary Executab…rmats File System Automount Point." source=qemu vm=gKg6SwRaGEld94HqooJs
Oct 12 12:56:20 jenkins-azure-vm-fedora-26-7a1ef0.localdomain cc-proxy[16593]: time="2017-10-12T12:56:20.51282755Z" level=debug msg="[\x1b[0;32m  OK  \x1b[0m] Started Apply Kernel Variables." source=qemu vm=gKg6SwRaGEld94HqooJs
Oct 12 12:56:20 jenkins-azure-vm-fedora-26-7a1ef0.localdomain cc-proxy[16593]: time="2017-10-12T12:56:20.517735515Z" level=debug msg="[    1.116473] systemd-journald[116]: Failed to open configuration file '/etc/systemd/journald.conf': No such file or directory" source=qemu vm=gKg6SwRaGEld94HqooJs

@jodh-intel jodh-intel merged commit 82466eb into clearcontainers:master Oct 13, 2017
mcastelino pushed a commit to mcastelino/tests that referenced this pull request Jan 23, 2019
This tells what is doing this test.

Fixes clearcontainers#606

Signed-off-by: Gabriela Cervantes <gabriela.cervantes.tellez@intel.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants