Thank you for taking the time to report this issue. Unfortunately I
couldn't reproduce the coredump following the steps you provided. What I
did is the following:
1. Started an amd64 Xenial virtual machine using multipass
2. Installed pacemaker and pcs
3. Created /usr/local/bin/new.sh identical to yours, and
marked it as executable
4. Ran: pcs resource create newRes ClusterMon user="root" \
extra_options="-E /usr/local/bin/new.sh "
5. Ran: pcs resource create newRes ocf:pacemaker:ClusterMon \
user="root" extra_options="-E /usr/local/bin/new.sh"
6. Checked the kernel messages.
In both cases no coredumps happened. Without a reproducer where isn't
enough information for a developer to confirm this issue is a bug, or to
begin working on it. Is it possible for you to provide up complete steps
to reproduce from scratch from a clean system? You could use multipass
to conveniently start a VM, or LXD to start a container (the *host*
kernel is used in this case.)
I'm marking this report as Incomplete for the moment; please change its
status back to New after providing more information. Thanks!
** Changed in: pacemaker (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848834
Title:
ClusterMon resource creation core-dumps while created with
extra_option -E
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1848834/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
