Thanks for supplying further details - I’ve worked out exactly what is going wrong and there are two aspects to the problem.
The latest version of connman that we are using (1.29) does not seem to like leading zeros on the IP address field. It logs the following error in the log:
Jun 19 12:17:03 rpi2 connmand[255]: connman_inet_set_address: Operation not permitted
Jun 19 12:17:03 rpi2 connmand[255]: connman_inet_clear_address: Operation not permitted
Strangely, it doesn’t seem to mind if the netmask, gateway or DNS have leading zeros…
Furthermore, this was not the case in connman 1.22 which we were using in earlier releases, (I forget when we switched, but it was back around Alpha 4 or RC1) as I’m pretty sure I remember testing leading zeros when the preseed script was originally written, and they worked at that time.
Nothing has changed in that part of the preseed script since then but apparently connman is now more fussy, so I will strip off any leading zeros before passing them to connman. Easy fix.
However this testing revealed another bug which is an interaction between connman and our current GUI design. When the incorrectly formatted IP address is passed to connman it ends up in a strange limbo state where it is stuck forever in “connecting” state, (Ac in connmanctl) and is not configured to use either DHCP or Static IP. (no settings file under the ethernet interface in /var/lib)
Our Networking GUI interprets this as the network being down (unknown state) and therefore does not display the controls that would allow you to enter a static IP configuration to get yourself out of this limbo state.
(Rebooting however does revert connman back to DHCP and make it possible to edit settings again)
So the fix for this will be to still display the Configure Network Manually control provided the link layer connection is up. This has the added advantage that on a network with no DHCP server you don’t have to wait a minute before you can configure a static configuration.
Our networking GUI guy is going away on holiday for a bit but we will hopefully have both these issues fixed in time for the final release.