Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

Handle error when the backend storage is uninitialized #807

Merged
merged 1 commit into from
Mar 15, 2021

Conversation

darkowlzz
Copy link
Contributor

VM, image and kernel list return error when the backend storage is
uninitialized (/var/lib/firecracker/{vm,image,kernel} don't exist).

FATA[0000] open /var/lib/firecracker/kernel: no such file or directory
...
FATA[0000] open /var/lib/firecracker/image: no such file or directory

This was fixed for VM in #778. This change improves the error check.

VM, image and kernel list return error when the backend storage is
uninitialized (/var/lib/firecracker/{vm,image,kernel} don't exist).

```
FATA[0000] open /var/lib/firecracker/kernel: no such file or directory
...
FATA[0000] open /var/lib/firecracker/image: no such file or directory
```

This was fixed for VM. This change improves the error check.
@darkowlzz darkowlzz added the kind/enhancement Categorizes issue or PR as related to improving an existing feature. label Mar 13, 2021
@stealthybox stealthybox merged commit 2269681 into weaveworks:master Mar 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/enhancement Categorizes issue or PR as related to improving an existing feature.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants