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

pve (proxmox) agent not included in spec file #456

Open
tuesdaycodes opened this issue Dec 5, 2021 · 5 comments
Open

pve (proxmox) agent not included in spec file #456

tuesdaycodes opened this issue Dec 5, 2021 · 5 comments

Comments

@tuesdaycodes
Copy link

https://github.com/ClusterLabs/fence-agents/blob/master/fence-agents.spec.in#L33

unclear why not included but would be helpful if it was. if unable to package how would someone use it with a pacemaker install otherwise? just copy the .py to some directory?

can these agents also be packaged in epel for easier consumption? looks like only a few are.

@tuesdaycodes tuesdaycodes changed the title pve agent not included in spec file pve (proxmox) agent not included in spec file Dec 5, 2021
@oalbrigt
Copy link
Collaborator

oalbrigt commented Dec 8, 2021

Usually it's either because of dependency we dont want to pull in, or simply that we havent considered if it should be dependency from the -all subpackage yet.

In this case it seems like it has the same dependencies as multiple other agents that are included, so we can add it.

@oalbrigt
Copy link
Collaborator

oalbrigt commented Dec 8, 2021

If you run:

./autogen.sh
./configure
make

It'll generate a version without .py (with Python binary and other replacements done if necessary).

To get it into EPEL someone needs to volunteer to maintain it.

I see there's a bz about it: https://bugzilla.redhat.com/show_bug.cgi?id=2029251

@ghost
Copy link

ghost commented Dec 14, 2021

@oalbrigt i have same issue. is being fix by clusterlabs for spec in repo even if not in epel? or require comm pr?

@oalbrigt
Copy link
Collaborator

oalbrigt commented Jan 4, 2022

It needs to be fixed in EPEL, since the CentOS package only provides the subpackages from the RHEL package.

@ghost
Copy link

ghost commented Jan 18, 2022

i see on bugzilla they blame rhel there, wont fix epel. if rhel use repo here needs fix here for rhel to fix = fix in epel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants