Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
qubes-staging molecule scenario fails at create step #3936
qubes-staging molecule action fails to create (clone sd-$ROLE-base) in the adminvm:
manually running qvm-clone results in the same error (and the VMs are not cloned):
Steps to Reproduce
molecule scenario should succeed and a SecureDrop staging environment should be created
Molecule scenario fails at the Create step
qvm-clone automatically uses the class of the source of the copy (
Workaround is to qvm-clone the base VMs in dom0, and then run the molecule converge step in the adminVM. In dom0:
Came across this issue the other day. And it quite obnoxious. After a little digging, it seems that the problem is with qubes, particularly some part that does not seem to be yet implemented. They even have a
A quick temporary fix to comment out all those lines like so:
""" try: # FIXME: convert to qrexec calls to dom0/GUI VM appmenus_cmd = \ ['qvm-appmenus', '--init', '--update', '--source', src_vm.name, dst_vm.name] subprocess.check_output(appmenus_cmd, stderr=subprocess.STDOUT) except OSError: # this file needs to be python 2.7 compatible,so no FileNotFoundError self.log.error('Failed to clone appmenus, qvm-appmenus missing') if not ignore_errors: raise qubesadmin.exc.QubesException( 'Failed to clone appmenus') except subprocess.CalledProcessError as e: self.log.error('Failed to clone appmenus: %s', e.output.decode()) if not ignore_errors: raise qubesadmin.exc.QubesException( 'Failed to clone appmenus') """
Maybe this problem should be mentioned in the docs so people at least know it's not only happening to them.
I use this script locally to work around the problem in the meantime:
Run that in dom0, then