RE: Config channels - how do they work?
Thanks Stefan, it’s good to know that it can work! However, I’ve left the modified files in place on a target system and it hasn’t replaced them after three days, so it feels like it’s not going to. I wonder what’s not right on mine that is on yours? S From: Stefan Bluhm <stefan@bluhm-de.com> Sent: 13 May 2021 09:08 To: uyuni-users@opensuse.org; Simon Avery <Simon.Avery@atass-sports.co.uk> Subject: [EXTERNAL EMAIL] AW: Config channels - how do they work? Hey Simon, That is how it works for me. I see how many and what files changed including a diff per System. It does take some time to sync but you can force a refresh. Best wishes, Stefan Sent from a mobile device. ---- Simon Avery schrieb ---- 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<https://ata-oxy-uyuni01.atass.com/rhn/systems/details/history/Event.do?aid=49013&sid=1000010058>] 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
Hmm – quick update. If I force a Highstate on a machine with a changed config file, then Uyuni /will/ replace that file. If that’s how it’s supposed to work, it explains why mine isn’t as that’s only enforced during bootstrap here. Can someone confirm, please? Thanks S From: Simon Avery Sent: 14 May 2021 11:09 To: 'Stefan Bluhm' <stefan@bluhm-de.com>; uyuni-users@opensuse.org Subject: RE: Config channels - how do they work? Thanks Stefan, it’s good to know that it can work! However, I’ve left the modified files in place on a target system and it hasn’t replaced them after three days, so it feels like it’s not going to. I wonder what’s not right on mine that is on yours? S From: Stefan Bluhm <stefan@bluhm-de.com<mailto:stefan@bluhm-de.com>> Sent: 13 May 2021 09:08 To: uyuni-users@opensuse.org<mailto:uyuni-users@opensuse.org>; Simon Avery <Simon.Avery@atass-sports.co.uk<mailto:Simon.Avery@atass-sports.co.uk>> Subject: [EXTERNAL EMAIL] AW: Config channels - how do they work? Hey Simon, That is how it works for me. I see how many and what files changed including a diff per System. It does take some time to sync but you can force a refresh. Best wishes, Stefan Sent from a mobile device. ---- Simon Avery schrieb ---- 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<https://ata-oxy-uyuni01.atass.com/rhn/systems/details/history/Event.do?aid=49013&sid=1000010058>] 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
participants (1)
-
Simon Avery