We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Scenario:
KMM version in use: 2.3.0(have observed similar issue with 2.2.0 as well).
Attaching logs of KMM Controller before and after node reboot.
Before Node Reboot: kmm-operator-controller-564dc74655-b2gxc-manager.log
After Node Reboot: kmm-operator-controller-564dc74655-b2gxc-manager (1).log
Recovery steps: I had to delete/create the module instance to recover.
The text was updated successfully, but these errors were encountered:
Thank you for this issue @quic-vmellemp
Can you please share the following information:
oc get node/<node name> -o yaml
describe
logs
oc get module/<modulename> -n <namespace> -o yaml
oc get nmc/<name> -n <namespace> -o yaml
oc get moduleimagesconfig/<module-name> -n <namespace> -o yaml
oc get modulebuildsignconfig/<module-name> -n <namespace> -o yaml
Sorry, something went wrong.
ybettan
No branches or pull requests
Scenario:
Issue: When I login to the node's terminal and try lsmod, I don't see the modules on the host kernel.
KMM version in use: 2.3.0(have observed similar issue with 2.2.0 as well).
Attaching logs of KMM Controller before and after node reboot.
Before Node Reboot: kmm-operator-controller-564dc74655-b2gxc-manager.log
After Node Reboot: kmm-operator-controller-564dc74655-b2gxc-manager (1).log
Recovery steps: I had to delete/create the module instance to recover.
The text was updated successfully, but these errors were encountered: