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

User should be able to not specify rpm nor repo of ovirt #92

Open
StLuke opened this issue Dec 8, 2016 · 7 comments
Open

User should be able to not specify rpm nor repo of ovirt #92

StLuke opened this issue Dec 8, 2016 · 7 comments

Comments

@StLuke
Copy link
Collaborator

StLuke commented Dec 8, 2016

User should be able to not specify rpm nor repo of ovirt and rather do it manually with his custom repositories

@lukas-bednar
Copy link
Member

could you please elaborate on more details? thank you!

@StLuke
Copy link
Collaborator Author

StLuke commented Jan 3, 2017

Have preinstalled machine with correct repositories I want to use and install engine on it.

@lukas-bednar
Copy link
Member

you can still do it with current status of repo. just omit 'ovirt-common' role from your playbook.

@StLuke
Copy link
Collaborator Author

StLuke commented Jan 3, 2017

:) I would love to have that though withough remembering it

  • name: install libselinux-python for ansible
    yum:
    name: libselinux-python
    state: "present"

@lukas-bednar
Copy link
Member

hm, I don't know what to do with it, since ...

If you have SELinux enabled on remote nodes, you will also want to install libselinux-python on them before using any copy/file/template related functions in Ansible. You can of course still use the yum module in Ansible to install this package on remote systems that do not have it.

it looks like the role itself should be responsible for installation of this package when it is using above mentioned modules ... ok then you can not skip ovirt-common role ...

@lukas-bednar
Copy link
Member

we can consider it as part of #83

@KKoukiou
Copy link
Collaborator

@StLuke is this still relevant?

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

3 participants