core.collectd dump generated during lock/unlock controller-0

Bug #1901039 reported by Peng Peng
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Triaged
Low
Eric MacDonald

Bug Description

Brief Description
-----------------
During controller-0 lock-unlock, core.collected dump file was generated.

Severity
--------
Major

Steps to Reproduce
------------------
in SX system,
lock/unlock controller-0

TC-name: TestCoreDumpsAndCrashes::test_system_coredumps_and_crashes[core_dumps]

Expected Behavior
------------------
no core dump file generated

Actual Behavior
----------------
core dump file was generated

Reproducibility
---------------
3/3 in 3 runs

System Configuration
--------------------
One node system

Lab-name: SM-3

Branch/Pull Time/Commit
-----------------------
2020-10-22_00-00-10

Last Pass
---------
unknown

Timestamp/Logs
--------------
[2020-10-22 09:57:54,578] 314 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://[abcd:204::1]:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-endpoint-type internalURL --os-region-name RegionOne host-unlock controller-0'

[2020-10-22 10:00:38,707] 288 INFO MainThread ssh.wait_for_disconnect:: ssh session to 2620:10a:a001:a103::81 disconnected
[2020-10-22 10:03:38,737] 314 DEBUG MainThread ssh.send :: Send ''
[2020-10-22 10:03:38,838] 436 DEBUG MainThread ssh.expect :: Output: packet_write_wait: Connection to 2620:10a:a001:a103::81 port 22: Broken pipe
svc-cgcsauto@yow-tuxlab2:~$
[2020-10-22 10:03:38,839] 1298 INFO MainThread ssh.connect :: Attempt to connect to 2620:10a:a001:a103::81 from 128.224.151.254...
[2020-10-22 10:03:38,839] 314 DEBUG MainThread ssh.send :: Send '/usr/bin/ssh -o RSAAuthentication=no -o PubkeyAuthentication=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null sysadmin@2620:10a:a001:a103::81'
[2020-10-22 10:03:39,447] 436 DEBUG MainThread ssh.expect :: Output:
svc-cgcsauto@yow-tuxlab2:~$ /usr/bin/ssh -o RSAAuthentication=no -o PubkeyAuthentication=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null sysadmin@2620:10a:a001:a103::81
command-line line 0: Unsupported option "rsaauthentication"
Warning: Permanently added '2620:10a:a001:a103::81' (ECDSA) to the list of known hosts.
Release 20.12

post_coredumps_and_crash_reports = {'controller-0': [['-rw-r----- 1 root root 6000416 2020-10-22_10-02-02 core.collectd.0.54a9ec163a3b4565b919036a6f87d9c...root root 6005368 2020-10-22_10-41-26 core.collectd.0.df42fd8e418847b19e891625d9897c8e.1674.1603363260000000.xz'], []]}

Test Activity
-------------
Regression Testing

Peng Peng (ppeng)
tags: added: stx.retestneeded
Revision history for this message
Peng Peng (ppeng) wrote :

collect log and core dump file uploaded at
https://files.starlingx.kube.cengn.ca/launchpad/1901039

Revision history for this message
Peng Peng (ppeng) wrote :

Issue was reproduced on WP_3-7
on 2020-10-22_20-00-09

core.collected dump generated during system initial and host boot up.
core dump file attached
collect log loaded at

Ghada Khalil (gkhalil)
summary: - core.collected dump generated during lock/unlock controller-0
+ core.collectd dump generated during lock/unlock controller-0
Revision history for this message
Ghada Khalil (gkhalil) wrote :
Revision history for this message
Ghada Khalil (gkhalil) wrote :

Marking as a duplicate. This has no system impact.

Changed in starlingx:
importance: Undecided → Low
status: New → Triaged
tags: added: stx.metal
Changed in starlingx:
assignee: nobody → Eric MacDonald (rocksolidmtce)
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.