In a Virtual Chassis for the EX4300 Series switch, the "Unable to commit the configuration error: Check-out failed for Chassis control process (/usr/sbin/chassisd) without details" error might be seen during commit followed by commit failure.

This article provides a workaround to resolve the error while indicating the possible reason for its occurrence.

Primarily, two symptoms are seen for this issue:

1. Error during commit

Unable to commit the configuration error: Check-out failed for Chassis control process (/usr/sbin/chassisd) without details

2. The following errors in the logs:

Aug 1 <time>  ex4300 chassisd[1449]: %DAEMON-3: mojito_pseudo_cb_periodic error reading iic_get_max6581_temp 0xffffffff
Aug 1 <time>  ex4300 /kernel: %KERN-7:  Failed read to device 0x4d
Aug 1 <time>  ex4300 /kernel: %KERN-7:  i2c_write_addr: EIO: addr = 0x70
Aug 1 <time>  ex4300 chassisd[1449]: %DAEMON-3: mojito_pseudo_cb_periodic error reading iic_get_max6581_temp 0xffffffff
Aug 1 <time>  ex4300 last message repeated 3 times
Aug 1 <time>  ex4300 /kernel: %KERN-7:  Failed read to device 0x4d

This issue is caused when i2c and hence the Flexible PIC Concentrator (FPC) is unable to read the hardware device for some interface, and multiple FPCs are preventing the commit.

As a workaround to resolve the error, re-seat the optics/sfp (usually the uplink interfaces).

If the error persists even after re-seating the optics/sfp, contact Support for further investigation.