Hey Simon,

Hello,

 

I’m seeking clarity about Config channels. I’ve read the docs and been using them for a while, and whilst all the manual aspects work as I expect, the automation bits aren’t. I’ve read the documentation but still have some questions.

 

I’m not sure on whether this is a bug, or more likely, I’m misunderstanding or have misconfigured.

 

Problem:

I can see Uyuni regularly compares remote files to those in the config channels and reports versions, but even when a remote file is changed, it doesn’t replace the remote file.

 

Example:
I have a file in a Uyuni “managed config channel” called “/root/myfile.txt”.

I push this to a remote client and it appears there.  (Or a new vm is built and the file deployed when it’s bootstrapped to uyuni)

I then modify the file *on the remote client*

In Uyuni, if I manually run “Show differences between profiled config files and deployed config files” for that server (or let Uyuni do its periodic check) it does not replace the remote file.

 

Expectation:

That Uyuni would diff the remote file and if it was different, would re-push a copy from central configuration.

Because there is facility for

 

Note:
Uyuni is spotting the files have changed – on the System vm page:
“Last Uyuni and System Comparison: 9 hours ago 30 of 31 files on the system were successfully compared with Uyuni-Managed files. [View Details] 4 of 30 files on the system differed from the Uyuni-Managed files.”

 

I don’t have any State Channels configured – other than salt-minion as a remote client, I’m not doing anything Salty with Uyuni at all.

 

Can anyone help me understand what’s supposed to happen please, and how I can encourage Uyuni to force certain files?

 

Thank you

 

Simon

-- 
Abid Mehmood 
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nuremberg
Germany