Comment 5 for bug 1833157

Revision history for this message
Lin Shuicheng (shuicheng) wrote :

Both log show there is drbd configuration failure in puppet.log. And puppet configuration must be success in order to run sm service. This is why source command cannot be used.

It seems there is network/IP lose issue in both log. And the IP lose cause DRBD failed to init.
For the 1st log (controller-0_20190617.192835.tar) simplex system:
The error message in puppet log is below:
2019-06-17T15:22:12.763 ^[[mNotice: 2019-06-17 15:22:12 +0000 /Stage[main]/Platform::Drbd::Extension/Platform::Drbd::Filesystem[drbd-extension]/Drbd::Resource[drbd-extension]/Drbd::Resource::Enable[drbd-extension]/Drbd::Resource::Up[drbd-extension]/Exec[reuse existing DRBD resource drbd-extension]/returns: IP 192.168.204.3 not found on this host.^[[0m
2019-06-17T15:22:12.769 ^[[1;31mError: 2019-06-17 15:22:12 +0000 drbdadm adjust drbd-extension returned 10 instead of one of [0]

puppet.log also show this mmgt IP is configured successfully. So it is lost after configuration.

For 2nd log (controller-0_20190618.092729.tar) standard system:
The first error message in puppet log is as below:
2019-06-18T08:35:27.009 ^[[mNotice: 2019-06-18 08:35:26 +0000 /Stage[main]/Platform::Sm/Exec[Configure Cluster Host Interface]/returns: sm-configure interface: error: too few arguments^[[0m
2019-06-18T08:35:27.010 ^[[1;31mError: 2019-06-18 08:35:26 +0000 sm-configure interface controller cluster-host-interface 239.1.1.1 2222 2223 192.168.206.4 2222 2223 returned 2 instead of one of [0]

Need further check what cause the IP/network issue.