Comment 5 for bug 1802322

Why is this still including set-name calls? I thought we had established this was very wrong to do?

Regardless, there's clearly an error, but it's one that could be easily avoided in this particular if the config generated by cloud-init was "correct".