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
[BACKPORT][v1.5.5][BUG][v1.6.0-rc1] Failed to run instance-manager in storage network environment #8305
Comments
Pre Ready-For-Testing Checklist
To reproduce in v1.5.x before fix:
To test the backported fix in v1.5.x:
|
@ejweber I've tested it on v1.5.x-head, but the behavior is a little different from #8305 (comment). If the storage-network setting is set to a |
@yangchiu, this is not the behavior I observe in my cluster, but it may make sense. My cluster does not have Multus or the NetworkAttachmentDefinition CRD installed. So, Longhorn sets the annotation on the instance-manager pod, but no component in the cluster actually attempts to set up a secondary network.
This is fine for testing, as I only want to verify whether setting the Longhorn storage-network setting causes instance-manager pods to be continuously restarted. Do you have Multus installed in your test cluster? If so, I think it is likely that the container fails to start because there is no If you DO have Multus installed, can we test by EITHER:
If you DON'T have Multus installed, can you please send a support bundle for evaluation? |
Yes, I tested with Multus installed in my cluster. Instance mangers get stuck in
So it's expected. Thank you for the clarification!
Yes, changed the storage-network setting to an existent crd, instance managers work without problem. |
Verified passed on v1.5.x-head (longhorn-manager 63ba2f7) following the test plan. And Longhorn runs without problem on the storage network pipeline: https://ci.longhorn.io/job/private/job/longhorn-storage-network-test/15/ |
backport #7640
The text was updated successfully, but these errors were encountered: