-
Notifications
You must be signed in to change notification settings - Fork 27
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
NPE panic in the inventory #495
Comments
@bennyz I just caught this today , is there a fix or workaround? Is it supposed to be informational error?
|
@jsakil14 this looks like a different issue, it is definitely not intentional (we shouldn't hit NPEs), it seems to be coming from: so I'd check the VirtualMachineExport instance you have to figure out why is it missing the certificate (or perhaps a different field is not set for some reason) |
@bennyz thanks - I still cant wrap my head around this...Would you mind taking a look at this? pvc has some issues , but am trying to find relevant logs
adding @ahadas Should I open this as a new issue? controller logs with main container crashing,.,.
|
@jsakil14 yes, this is separate issue. It seems the issue is, based on your VirtualMachineExport yaml is that it is missing the https://kubevirt.io/user-guide/storage/export_api/#external-link-certificates |
Looks like I need to setup ingress to make this work. documentation to perform migration between openshift clusters would be helpful... |
There were no additional steps required when tested with openshift and we have never seen this issue before, are you using plain k8s or some other k8s distribution? |
This is kubevirt running on k8s physical 3 node cluster. Still I am stuck,
unsure on this approach.
…On Wed, 21 Aug, 2024, 4:39 pm Benny Zlotnik, ***@***.***> wrote:
Looks like I need to setup ingress to make this work. documentation to
perform migration between openshift clusters would be helpful...
There were no additional steps required when tested with openshift and we
have never seen this issue before, are you using plain k8s or some other
k8s distribution?
perhaps in these cases there is another step required which we weren't
aware of
—
Reply to this email directly, view it on GitHub
<#495 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APS2FWGQTKKNDMLY6UZKJD3ZSRYPJAVCNFSM6AAAAABMXHZYQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBRG44DSMZUHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I suggest asking in a kubevirt slack channel or mailing list, I don't have access to a k8s env right now |
Seems to happen when the access to the provider is slow
Happened during the development of 2.5.0
The text was updated successfully, but these errors were encountered: