Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

or does not work well for hostname in Beaker XML #3274

Open
skycastlelily opened this issue Oct 10, 2024 · 2 comments
Open

or does not work well for hostname in Beaker XML #3274

skycastlelily opened this issue Oct 10, 2024 · 2 comments
Labels
area | hardware Implementation of hardware requirements plugin | mrack The beaker provision plugin step | provision Stuff related to the provision step

Comments

@skycastlelily
Copy link
Collaborator

Here is the or part of the plan,with which I try to provision a server from a certain list:

        or:
          - hostname: dummy1.redhat.com
          - hostname: dummy2.redhat.com

Here is the hostname part of the plan file:

        <and>
          <hostname op="==" value="dummy1.redhat.com"/>
        </and>

which means the job will only try to reserve dummy1.redhat.com

@happz happz changed the title or does not work well or does not work well for hostname in Beaker XML Oct 10, 2024
@happz happz added step | provision Stuff related to the provision step area | hardware Implementation of hardware requirements plugin | mrack The beaker provision plugin labels Oct 10, 2024
@happz
Copy link
Collaborator

happz commented Oct 10, 2024

The specification looks correct, there might be a problem in how or - and possibly and as well, they are very similar - is handled by the mrack plugin.

@skycastlelily
Copy link
Collaborator Author

Yeah, this only affects mrack, not hostname specific, cpu.model,etc :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area | hardware Implementation of hardware requirements plugin | mrack The beaker provision plugin step | provision Stuff related to the provision step
Projects
None yet
Development

No branches or pull requests

2 participants