kdevops.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: "kdevops@lists.linux.dev" <kdevops@lists.linux.dev>
Subject: "make" on a pristine aarch64 system
Date: Mon, 5 Feb 2024 16:15:59 +0000	[thread overview]
Message-ID: <A0D58F46-8A97-43FB-A719-AD9C657D6761@oracle.com> (raw)

This is my first libvirt / guestfs bringup as well as being a fresh
install on an Ampere Altra system.

I'm thinking I'm missing some python module, but really, I have no clue.


TASK [gen_nodes : Generate XML files for the libvirt guests] ***********************************************************************************
task path: /home/cel/kdevops/playbooks/roles/gen_nodes/tasks/main.yml:388
The full traceback is:
Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/ansible/plugins/action/template.py", line 94, in run
    source = self._find_needle('templates', source)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/ansible/plugins/action/__init__.py", line 1429, in _find_needle
    return self._loader.path_dwim_relative_stack(path_stack, dirname, needle)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/ansible/parsing/dataloader.py", line 341, in path_dwim_relative_stack
    raise AnsibleFileNotFound(file_name=source, paths=[to_native(p) for p in search])
ansible.errors.AnsibleFileNotFound: Could not find or access 'guestfs_pc.j2.xml'
Searched in:
/home/cel/kdevops/playbooks/roles/gen_nodes/templates/guestfs_pc.j2.xml
/home/cel/kdevops/playbooks/roles/gen_nodes/guestfs_pc.j2.xml
/home/cel/kdevops/playbooks/roles/gen_nodes/tasks/templates/guestfs_pc.j2.xml
/home/cel/kdevops/playbooks/roles/gen_nodes/tasks/guestfs_pc.j2.xml
/home/cel/kdevops/playbooks/templates/guestfs_pc.j2.xml
/home/cel/kdevops/playbooks/guestfs_pc.j2.xml on the Ansible Controller.
If you are using a module and expect the file to exist on the remote, see the remote_src option
failed: [localhost] (item={'name': 'testing64-btrfs-fspace'}) => {
    "ansible_loop_var": "item",
    "changed": false,
    "item": {
        "name": "testing64-btrfs-fspace"
    },
    "msg": "Could not find or access 'guestfs_pc.j2.xml'\nSearched in:\n\t/home/cel/kdevops/playbooks/roles/gen_nodes/templates/guestfs_pc.j2.xml\n\t/home/cel/kdevops/playbooks/roles/gen_nodes/guestfs_pc.j2.xml\n\t/home/cel/kdevops/playbooks/roles/gen_nodes/tasks/templates/guestfs_pc.j2.xml\n\t/home/cel/kdevops/playbooks/roles/gen_nodes/tasks/guestfs_pc.j2.xml\n\t/home/cel/kdevops/playbooks/templates/guestfs_pc.j2.xml\n\t/home/cel/kdevops/playbooks/guestfs_pc.j2.xml on the Ansible Controller.\nIf you are using a module and expect the file to exist on the remote, see the remote_src option"
}

--
Chuck Lever



             reply	other threads:[~2024-02-05 16:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 16:15 Chuck Lever III [this message]
2024-02-05 16:43 ` "make" on a pristine aarch64 system Chuck Lever III
2024-02-06 20:38   ` Luis Chamberlain
2024-02-06 22:46     ` Chuck Lever
2024-02-06 23:32       ` Luis Chamberlain
2024-02-06 23:44         ` Chuck Lever
2024-02-15 14:09           ` Chuck Lever III

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A0D58F46-8A97-43FB-A719-AD9C657D6761@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=kdevops@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).