besawn
besawn
Moving this PR to the next release until we can better understand which versions of OpenSSH require private keys with 0640 vs 0600 permissions.
@nealep The current behavior was due to this issue: https://github.com/xcat2/xcat-core/issues/2617 which references this issue: https://bugzilla.redhat.com/show_bug.cgi?id=819896 Given that different versions of OpenSSH require different ownership and permissions, a more reliable approach...
This is a good feature request. Enhancing xCAT to take better advantage of `dnf` features has been desirable since `dnf` replaced `yum`; this issue will give us a good way...
@bviviano Thank you for the suggestion to improve xCAT support for FIPS. Contributions like this will improve xCAT's ability to function correctly with FIPS enabled. 1.) Would you be willing...
xCAT does not provide a built in feature to do this, but I think it should be possible to implement this manually. I have not attempted to do this myself....
Closing this issue due to lack of activity.
This document describes a process that is similar to what you are trying to achieve: https://xcat-docs.readthedocs.io/en/stable/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms/discovery_using_defined.html I think you can modify the process slightly to meet your needs. I don't...
Please provide the following information and perhaps another CentOS user with a similar hardware configuration will be able to assist you: - Manufacturer and model of blade server. - Collect...
The xCAT core team does our internal x86 testing using an ethernet provisioning network rather than Infiniband. The problem you are having might be due to the RHEL 8 initrd...
@ocfmatt IPv6 support in xCAT does not work due to limitations in xCAT. There are attempts in parts of the code to address IPv6, but it is not officially supported...