need logs for agent time
Bug #1439511 reported by
John George
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-ci-tools |
Fix Released
|
High
|
Martin Packman | ||
Bug Description
Many jobs across substrates fail due to hitting a timeout waiting for deployed services to complete.
An example console log:
http://
Note that the status lists an IP address for the pending agents. juju-ci log collection needs to ssh in and capture cloud-init and any juju logs. With logs as supporting evidence juju-qa may need to open a bug against core to solve this as a overall reliability issue; in a recent sample this issues caused 17% of the test jobs to fail.
Related branches
lp:~gz/ci-director/archive_artifact_subdirs
- Curtis Hovey (community): Approve (code)
-
Diff: 140 lines (+67/-3)3 files modifiedcidirector/storage.py (+7/-3)
cidirector/tests/test_storage.py (+49/-0)
cidirector/utility.py (+11/-0)
| Changed in juju-ci-tools: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
Revision history for this message
| Martin Packman (gz) wrote | #1 |
| Changed in juju-ci-tools: | |
| importance: | Critical → High |
| Changed in juju-ci-tools: | |
| assignee: | nobody → Martin Packman (gz) |
| status: | Triaged → In Progress |
| Changed in juju-ci-tools: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
I filed bug 1451104 against juju-core for this.
The issue seems to be we're not archiving sub-directory artifacts from jenkins to s3, or showing them on juju-reports. The jenkins jobs do have the cloud-init logs from the machines that came up but got no agents.