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

packages required for ssh_key configuration #234

Closed
GowthamShanmugam opened this issue Mar 2, 2017 · 6 comments
Closed

packages required for ssh_key configuration #234

GowthamShanmugam opened this issue Mar 2, 2017 · 6 comments

Comments

@GowthamShanmugam
Copy link
Contributor

For ssh-key configuration needs two different packages called psutil and libselinux-python

psutil used to find sshd service status and port using process id (pip package)
libselinux-python gives support at the time of copying authorize key (yum package)

But these two packages names are differ in cent os and rhel
in rhel package name is python-psutil, libselinux

@GowthamShanmugam
Copy link
Contributor Author

@mbukatov
Copy link
Contributor

mbukatov commented Mar 6, 2017

I wonder how psutil is actually used. When I grep sources of tendrl-node-agent for it, I don't find anything.

@r0h4n
Copy link
Contributor

r0h4n commented Mar 6, 2017

@mbukatov you are correct, psutil is used here Tendrl/commons#175

and the requirement for psutil should be on tendrl-commons and not on tendrl-node-agent. This a newly introduced issue. I will fix it

@GowthamShanmugam
Copy link
Contributor Author

@r0h4n Tendrl/commons#175 this is job_class patch here psutil not used

@r0h4n
Copy link
Contributor

r0h4n commented Mar 6, 2017

Sorry, the correct PR is Tendrl/commons#176

@GowthamShanmugam
Copy link
Contributor Author

@mbukatov @r0h4n i have raised this issue wrongly

both centos and rhel yum package have same name psutil only i am confused with pip and yum package.

Now wen no need to worry about libselinux-python, because i have mentioned in spec selinux should be disable for ssh_util config patch.

We can close this bug i feel, yours suggestion please

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