-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible regression - there is no tailed log from a failed unit #531
Comments
zaza/zaza/charm_lifecycle/func_test_runner.py Lines 82 to 87 in 60ea801
|
That 'stdout' should now be 'Stdout'; I'm guessing that when zaza went fully async this was further harmonised across the whole code-base. Originally, juju used to respond with 'Stdout', and then this changed, but by then zaza was locked into 'Stdout', so it was that used everywhere. There's code that automatically adjusts 'stdout' to 'Stdout' and I guess it was finally enforced here. |
I guess stdout should work still. Lines 499 to 510 in bb59dfc
This can be from the whole libjuju drama so it can go away as it's pinned by now. |
When #518 was merged, I'm pretty sure we were able to see the unit log from a failed unit (
zaza.model.run_on_unit and tail
).However, I've realized that there is no tailed log from recent CI jobs. For example, the following one has
[ERROR] Juju log for octavia/2
as expected but there is no following lines of the actual log. But we see trace back from zaza instead.https://openstack-ci-reports.ubuntu.com/artifacts/22c/848297/1/check/focal-xena-ha/22cd3cb/job-output.txt
The text was updated successfully, but these errors were encountered: