Add Instruction to downgrade kernel correctly about cortx-re HOT 16 CLOSED

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @shailesh-vaidya for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

from cortx-re.

Hi @shailesh-vaidya is this issue still relevant since we are using k8s?

from cortx-re.

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @shailesh-vaidya for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

from cortx-re.

Hi @hessio - Motr has removed kernel dependency now. We need to modify cortx-build docker image to fix this one.

from cortx-re.

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @shailesh-vaidya for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

from cortx-re.

Ok no worries, I am trying to clear out the backlog, and label issue for tracking internally, would you say this is on the backlog? or is there a scheduled fix for this issue?

from cortx-re.

@hessio We have removed kernel dependency in cortx-build docker image now. Let me validate it once and then we can close this one.

from cortx-re.

Ok thank you @shailesh-vaidya :)

from cortx-re.

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @shailesh-vaidya for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

from cortx-re.

For the convenience of the Seagate development team, this issue has been mirrored in a private Seagate Jira Server: https://jts.seagate.com/browse/EOS-28336. Note that community members will not be able to access that Jira server but that is not a problem since all activity in that Jira mirror will be copied into this GitHub issue.

from cortx-re.

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @shailesh-vaidya for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

from cortx-re.

Hi @shailesh-vaidya did you get a chance to check this issue?

from cortx-re.

Shailesh Vaidya commented in Jira Server:

We have moved to Kubernetes based deployment and hence CORTX is no more tied up with Kernel Version. We can use any OS (CentOS/Ubuntu) for K8s setup and Deploy CORTX on it. Host OS and Application image OS need not be the same as the Kubernetes layer.

from cortx-re.

Shailesh Vaidya commented in Jira Server:

This bug is no more valid with CORTX deployed on Kubernetes cluster

from cortx-re.

Shailesh Vaidya commented in Jira Server:

This bug is no more valid with CORTX deployed on Kubernetes cluster

from cortx-re.

Mukul Malhotra commented in Jira Server:

.

from cortx-re.