Yesterday I got in a bit of a pickle with Uyuni and through my own fault, managed - in
relatively few clicks - to add some new files to an existing Configuration channel and set
them as "Locally managed" on almost 200 machines.
Once I understood my mistake (I wanted to push a new version of existing files), I tried
to revert this mistake but I could not find a way to do so globally.
The only way I could see to do this was to visit each machine in Uyuni, select the three
files one at a time and delete the record for that machine. I did actually try to do
this, but Uyuni becomes unresponsive when you have over a hundred browser tabs open to
Deleting the files from the channel didn't remove the association on the machines,
which I expected.
Re-adding the files caused the new record to assume the same, and they immediately set as
Locally managed, suggesting the link is the file+path on the machines.
I searched for some time to find a way to remove this globally but was unsuccessful.
Eventually, as I as pressed for time, I restored a backup of Uyuni and re-added the files
as centrally managed which worked fine.
So my question: Was I being dim and there is a way to globally change what Uyuni records
as "Locally managed" configuration files - if so, how? Or is this a "We
didn't think users could be so silly so we didn't allow for it" situation?
Show replies by date