The old LSC_CONFIGS guardian node, which was defunct but hadn't been properly destoryed, was briefly resurected after the h1guardian0 machine reboot.  It then tried to managed some nodes, which caused a bit of confusion.

I "destroyed" the node so it won't bother us anymore:

guardctrl destroy LSC_CONFIGS