Add information for collection to the diagnostic snapshot

Bug #1618512 reported by Alexander Rubtsov
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Timmy Development Team
7.0.x
Won't Fix
Medium
MOS Maintenance
Mitaka
Fix Released
Medium
Timmy Development Team

Bug Description

Please change the default configuration of the diagnostic snapshot tool so that the following information to be collected:

1) System log files:
/var/log/syslog
/var/log/messages
/var/log/daemon.log

2) Status of Docker containers fron the Fuel master node:
dockerctl check all

3) Status of Galera cluster:
mysql ­e "SHOW status LIKE 'wsrep%';"

4) OCF scripts
The content of the following directory from the Controller nodes:
/usr/lib/ocf/resource.d/

5) Definition of VM used for reduced footprint
Libvirt XMLs of VMs which are OpenStack nodes:
virsh dumpxml <domain>

6) Network templates used for the deployment
fuel ­­env <ENV> network­template ­­download

Changed in fuel:
importance: Undecided → Medium
milestone: none → 9.1
Revision history for this message
Roman Prykhodchenko (romcheg) wrote :

IIRC the entire /var/log must be there so it's required to investigate why they aren't.

Changed in fuel:
status: New → Confirmed
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
Revision history for this message
Georgy Kibardin (gkibardin) wrote :

I think we need to recheck /var/log since we've switched to Timmy.

Revision history for this message
Maksim Malchuk (mmalchuk) wrote :

We need to think TWICE because the /var/log/atop/ (for example on production) could be several gigabytes/terabytes in size!

tags: added: area-python
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 9.1 → 10.0
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

We switched to timmy tool for logs gathering. Moving the bug to them.

Changed in fuel:
assignee: Fuel Sustaining (fuel-sustaining-team) → Timmy Development Team (timmy-core)
Revision history for this message
Georgy Kibardin (gkibardin) wrote :

My bad about atop, I've completely forgotten about its exclusion :(

Revision history for this message
Anton Chevychalov (achevychalov) wrote :

When we switch to timmy we loose all our code related to shotgun. So currently all we did last years are broken.

Revision history for this message
Dmitry Sutyagin (dsutyagin) wrote :

@Anton Chevychalov - if you have a specific issue you need a fix for - please create a bug. I understand that if your code relied on Shotgun's file structure then it won't work out of the box with timmy's data, but it sould be possible to remap your logic to read Timmy's output files, the content will be the same of the most part, only filenames and folders have changed. This issue is not relevant in scope of this bug.

Revision history for this message
Dmitry Sutyagin (dsutyagin) wrote :

If this bug is still relevant please update what the current needs are - I believe some of the items are now invalid, others do not look reasonable (like "dockerctl check all" which can take really long time)

Revision history for this message
Alexander Rubtsov (arubtsov) wrote :

The request is still relevant both for Shotgun (for 7.0) and Timmy (for 9.0)

I have only 1 clarification to the initial list:
2) "dockerctl check all" is relevant for MOS 7.0 only. The "fuel-utils check_all" command is used in MOS 9.0

Revision history for this message
Alexander Dobdin (sanek-dobdin) wrote :
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 10.0 → 10.1
Changed in fuel:
status: Confirmed → Fix Released
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.