------- Comment From <email address hidden> 2018-03-21 09:04 EDT-------
(In reply to comment #31)
> Could you please comment as to whether the workaround resolved the issue?
Yes, the workaround resolves the issue. But could we have a udev rule added in kdump-tools
to trigger kdump-tools.service restart after a DLPAR memory/CPU add/remove operation
instead of manually restarting kdump-tools service after a DLPAR operation..
------- Comment From <email address hidden> 2018-03-21 09:04 EDT-------
(In reply to comment #31)
> Could you please comment as to whether the workaround resolved the issue?
Yes, the workaround resolves the issue. But could we have a udev rule added in kdump-tools
to trigger kdump-tools.service restart after a DLPAR memory/CPU add/remove operation
instead of manually restarting kdump-tools service after a DLPAR operation..
Thanks
Hari