Re: [qubes-users] Management of salt configs: Syncing from dom0 to a git-repository harboring vm?
I see. that seems straight forward then ... how time consuming is such a move? Sincerely, Joh On Saturday, April 3, 2021 at 7:36:02 PM UTC+2 unman wrote: > On Sat, Apr 03, 2021 at 09:42:49AM -0700, balin wrote: > > Hi, > > I urgently need to backup (and version control) my by now relative > > elaborate salt config. > > > > The plan is to manage it in a `git` repo in a dedicated Vm (whether I > push > > it to some private online repo still needs some contemplation). > > A shell script will > > a) copy/sync the salt dir to the `git` vm > > b) execute git add/commit(and possibly push) there > > > > >From this proposition the need arises to sync an entire directory from > > `dom0` to the `git` vm. I found > > `https://www.qubes-os.org/doc/copy-from-dom0/` > <https://www.qubes-os.org/doc/copy-from-dom0/> and consequently > `qvm-copy-to-vm > > ` ... > > I can see a workflow of packing the salt dir to a *.zip or some such, > > copying that, unpacking it on the `git` vm through `qrexec` and > preoceeding > > with git operations ... somewhat inelegant. > > Is there any other means of syncing an entire directory tree from `dom0` > to > > a vm? > > > > Thanks for any pointers. > > > > Sincerely, Joh > > > > qvm-copy-to-vm will take a directory as an argument. > You will have to then sync the files from QubesIncoming/dom0 to your git > repo, but that is trivial. > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/172b16bc-992b-4551-a9ec-4ff1e875f5aen%40googlegroups.com.
[qubes-users] Management of salt configs: Syncing from dom0 to a git-repository harboring vm?
Hi, I urgently need to backup (and version control) my by now relative elaborate salt config. The plan is to manage it in a `git` repo in a dedicated Vm (whether I push it to some private online repo still needs some contemplation). A shell script will a) copy/sync the salt dir to the `git` vm b) execute git add/commit(and possibly push) there >From this proposition the need arises to sync an entire directory from `dom0` to the `git` vm. I found `https://www.qubes-os.org/doc/copy-from-dom0/` and consequently `qvm-copy-to-vm ` ... I can see a workflow of packing the salt dir to a *.zip or some such, copying that, unpacking it on the `git` vm through `qrexec` and preoceeding with git operations ... somewhat inelegant. Is there any other means of syncing an entire directory tree from `dom0` to a vm? Thanks for any pointers. Sincerely, Joh -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6b20e3be-4238-4c0a-9d0c-aaf592b824ben%40googlegroups.com.
Re: [qubes-users] Re: salt management issues since last qubes (dom0?) upgrade
Thank you for pointing this out. the one liner solution in https://github.com/QubesOS/qubes-issues/issues/6188#issuecomment-726373728 (as applied to the default management template) fixed things for me. On Friday, November 13, 2020 at 9:10:54 PM UTC+1 Ludovic Bellier wrote: > > Le 13/11/2020 à 19:33, balin a écrit : > > Ok. More detail: > > > > When calling (as root and in dom0): > > qubesctl --target=fedora-32 state.highstate, > > I get > > fedora-32: ERROR (exit code 20, details in > > /var/log/qubes/mgmt-fedora-32.log) > > > > The relevant part in the referenced log reads: > > ... > > 2020-11-13 19:28:13,125 output: Traceback (most recent > > call last): > > 2020-11-13 19:28:13,125 output: File > > "/usr/lib/qubes-vm-connector/ssh-wrapper/ssh", line 101, in > > ... > > > > > > What is going on here? why did this stop working? > > > Hi Balin, > > it's a known temporary issue, read this: > > > https://qubes-os.discourse.group/t/updating-vms-throwing-an-ssh-error-any-ideas/1397 > > > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/36476358-d51e-47c4-9be0-70b39ac55034n%40googlegroups.com.
[qubes-users] Re: salt management issues since last qubes (dom0?) upgrade
Ok. More detail: When calling (as root and in dom0): qubesctl --target=fedora-32 state.highstate, I get fedora-32: ERROR (exit code 20, details in /var/log/qubes/mgmt-fedora-32.log) The relevant part in the referenced log reads: 2020-11-13 19:27:51,237 calling 'state.highstate'... 2020-11-13 19:28:13,123 output: fedora-32: 2020-11-13 19:28:13,125 output: -- 2020-11-13 19:28:13,125 output: _error: 2020-11-13 19:28:13,125 output: Failed to return clean data 2020-11-13 19:28:13,125 output: retcode: 2020-11-13 19:28:13,125 output: 1 2020-11-13 19:28:13,125 output: stderr: 2020-11-13 19:28:13,125 output: Traceback (most recent call last): 2020-11-13 19:28:13,125 output: File "/usr/lib/qubes-vm-connector/ssh-wrapper/ssh", line 101, in 2020-11-13 19:28:13,125 output: sys.exit(main()) 2020-11-13 19:28:13,125 output: File "/usr/lib/qubes-vm-connector/ssh-wrapper/ssh", line 94, in main 2020-11-13 19:28:13,125 output: return ssh(args) 2020-11-13 19:28:13,125 output: File "/usr/lib/qubes-vm-connector/ssh-wrapper/ssh", line 29, in ssh 2020-11-13 19:28:13,126 output: assert args[1] == '/bin/sh' 2020-11-13 19:28:13,126 output: AssertionError 2020-11-13 19:28:13,126 output: stdout: 2020-11-13 19:28:13,126 exit code: 20 What is going on here? why did this stop working? On Friday, November 13, 2020 at 2:59:12 PM UTC+1 balin wrote: > > I'm managing my fleet of templates and VMs using the salt stack. Since the > most recent qubes upgrade this no longer works. > I'm not at the machine in question right now, but the error that shows up > is one of "unclean data returned" and according to the logs related to an > ssh wrapper component. > > Does anyone have insight into this? What info does it take to figure this > out? > > > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1452461a-76a6-4769-97e9-f9dc952ddd0cn%40googlegroups.com.
[qubes-users] salt management issues since last qubes (dom0?) upgrade
I'm managing my fleet of templates and VMs using the salt stack. Since the most recent qubes upgrade this no longer works. I'm not at the machine in question right now, but the error that shows up is one of "unclean data returned" and according to the logs related to an ssh wrapper component. Does anyone have insight into this? What info does it take to figure this out? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/17746d2b-15a9-4111-b503-bf8b06ba18aan%40googlegroups.com.
