svc:/network/ipmp maintenance in shared IP zone
In a shared IP zone, the
network/ipmp services goes into maintenance, and it should not.
[ Apr 4 13:10:47 Enabled. ] [ Apr 4 13:10:49 Executing start method ("/lib/svc/method/net-ipmp"). ] [ Apr 4 13:10:49 Method "start" exited with status 95. ]
The problem here is that the method script for the
network/ipmp service contains this line:
smf_configure_ip || exit $SMF_EXIT_ERR_FATAL
# smf_configure_ip # # Returns zero (success) if this zone needs IP to be configured i.e. # the global zone or has an exclusive stack. 1 otherwise. #
The logic here is wrong, if the zone IP does not need to be configured, then the IPMP daemon (in.mpathd) does not need to run in this zone. The service should not exit with a fatal error, leaving it in a maintenance state. The
SMF_EXIT_NODAEMON status was made for this type of case - smf_method(7) describes it as:
Method exited successfully but purposefully leaves no processes remaining in the contract; it should be treated as if it had a transient service model.
Updated by Electric Monk 4 months ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
commit 57cf819efa50a6a3b3a478c25a098c29722eb358 Author: Andy Fiddaman <email@example.com> Date: 2022-04-05T19:32:01.000Z 14617 svc:/network/ipmp maintenance in shared IP zone Reviewed by: Marco van Wieringen <firstname.lastname@example.org> Reviewed by: Yuri Pankov <email@example.com> Reviewed by: Garrett D'Amore <firstname.lastname@example.org> Approved by: Robert Mustacchi <email@example.com>