There is no diagnostic snapshot for most failed 5.0 CI jobs

Bug #1433355 reported by Ryan Moe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel QA Team
5.0.x
Won't Fix
High
Fuel QA Team
5.1.x
Invalid
Undecided
Fuel QA Team
6.0.x
Invalid
Undecided
Fuel QA Team

Bug Description

Both 5.0.fuel-library.centos.deploy_neutron_gre and 5.0.fuel-library.ubuntu.deploy_ha_vlan fail to generate snapshots for most failed jobs. It happens more with Ubuntu because that job fails much more frequently than the CentOS job. This makes it impossible to debug these failures.

Ryan Moe (rmoe)
Changed in fuel:
importance: Undecided → High
assignee: nobody → Fuel DevOps (fuel-devops)
milestone: none → 5.0.3
status: New → Confirmed
tags: added: fuel-ci jenkins
Revision history for this message
Sergey Kulanov (skulanov) wrote :

It should be fixed for now, there was some misconfiguration in job regarding archiving correct artefacts:

https://review.fuel-infra.org/#/c/4545/

I'll put bug in Fix Committed, in case if the issue is still exists for your let's back to this bug again

Changed in fuel:
status: Confirmed → Fix Committed
tags: added: non-release
Revision history for this message
Ryan Moe (rmoe) wrote :

I'm still not seeing any diagnostic snapshots. See here: https://fuel-jenkins.mirantis.com/job/5.0.fuel-library.ubuntu.deploy_ha_vlan/. It looks like the dump command is exceeding the 300 second timeout.

Changed in fuel:
status: Fix Committed → Confirmed
Revision history for this message
Igor Belikov (ibelikov) wrote :

Looks like pull_out_logs_via_ssh is not implemented in stable/5.0, forwarding to QA.

Changed in fuel:
assignee: Fuel DevOps (fuel-devops) → Fuel QA Team (fuel-qa)
Changed in fuel:
milestone: 5.0.3 → 6.1
status: Confirmed → New
Revision history for this message
Nastya Urlapova (aurlapova) wrote :

This issue is invalid for 6.1 milestone.

Changed in fuel:
status: New → Invalid
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

Ditto 5.1

Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

MOS5.0 is no longer supported, moving to Won't Fix.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.