From: Luis Chamberlain <mcgrof@kernel.org>
To: Swarna Prabhu <sw.prabhu6@gmail.com>
Cc: kdevops@lists.linux.dev, da.gomez@samsung.com,
Swarna Prabhu <s.prabhu@samsung.com>
Subject: Re: [PATCH] gen_node: add debugger support for guestfs libvirt guests
Date: Thu, 24 Apr 2025 10:28:51 -0700 [thread overview]
Message-ID: <aAp0011D-hjMDRaJ@bombadil.infradead.org> (raw)
In-Reply-To: <20250424165809.2576146-1-s.prabhu@samsung.com>
Nice!
On Thu, Apr 24, 2025 at 04:58:09PM +0000, Swarna Prabhu wrote:
> +config LIBVIRT_ENABLE_GDB
> + bool "Enable GDB debugging for the guest"
> + output yaml
> +- name: Find if port conflict occur
> + ansible.builtin.shell: "ss -ltn | grep ':{{ (libvirt_gdb_baseport | int) + (idx | int) }} '"
> + register: gdb_port_reg
> + failed_when: false
> + changed_when: false
> + loop: "{{ guestfs_nodes }}"
> + loop_control:
> + index_var: idx
> + when:
> + - kdevops_enable_guestfs|bool
This needs to be:
when:
- libvirt_enable_gdb|bool
- kdevops_enable_guestfs|bool
> +
> +- name: Set the conflict flag on if conflict occur
> + set_fact:
> + gdb_port_conflict: True
> + when: >
> + gdb_port_reg.results is defined and
> + gdb_port_reg.results | selectattr('rc', 'equalto', 0) | list | length > 0
Same here and we need to use a flat entry per line so
when:
- libvirt_enable_gdb|bool
- gdb_port_reg.results is defined
- gdb_port_reg.results | selectattr('rc', 'equalto', 0) | list | length > 0
> +- name: Fail bringup if gdb port conflict occur
> + fail:
> + msg: "GDB port conflict occur, please check the base port number {{ libvirt_gdb_baseport }} and try with another"
> + when: gdb_port_conflict|bool
And here.
I made those small changes to your patch and pushed to the test throw
away kdevops tree, kdevops-kpd, which let's us trigger tests on both
containers and bare metal. The results are ephemeral, in that we can
ignore these tests for production. The test has been scheduled:
https://github.com/linux-kdevops/kdevops-kpd/actions/runs/14647807925
If that passes then I'll merge this! Thanks!
Luis
prev parent reply other threads:[~2025-04-24 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 16:58 [PATCH] gen_node: add debugger support for guestfs libvirt guests Swarna Prabhu
2025-04-24 17:28 ` Luis Chamberlain [this message]
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=aAp0011D-hjMDRaJ@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=da.gomez@samsung.com \
--cc=kdevops@lists.linux.dev \
--cc=s.prabhu@samsung.com \
--cc=sw.prabhu6@gmail.com \
/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