Comment 3 for bug 1185518

I'm not at all opposed to whatever discussion this may bring up -- but this specific bug just seems to be a simple, small oversight in the update_subnet implementation. Thought I would submit a similarly trivial fix!