mark_fixed should clear the osystem and distro_series fields

[Blake Rouse]

1. user acquires node
2. user changes the osystem and distro_series for the node
3. marks node broken,
4. marks node fixed

Now the node has a different osystem and distro_series instead of the default, and when it is acquired by another user it is not the default. "mark_fixed" should clear the osystem and distro_series fields.

[Newell Jensen (newell-jensen)]

I not able to reproduce this bug. After commissioning a node as the admin user and acquiring the node, I go in and change it to Ubuntu and Trusty for the osystem and distro series, respectively. I make sure to save the changes, and double verified they are there by going back in and checking again. After doing this, when I mark the node as broken and go into the node edit page, it has been changed back to the defaults already. Marking the node as fixed doesn't change anything at this point. Switching users also doesn't show what has been mentioned above.

[Christian Reis (kiko)]

What were the default OS and Release values?

[Blake Rouse (blake-rouse)]

The default OS and release values should just be "Default OS" and "Default Release". The actually values that are used when the node is set to this state is on the settings page.

Newell,

Can you test this with disk wiping, that is were I noticed it. Try the following to make sure it still doesn't occur, if it doesn't then great!

1. Deploy a node.
2. Release the node, with wiping on.
3. Abort the wipe operation after a moment.
4. Mark node broken.
5. Mark node fixed.
6. Check that OS/Release is default.