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

ps: Handle error when the backend storage is uninitialized #778

Merged
merged 1 commit into from
Feb 8, 2021

Conversation

darkowlzz
Copy link
Contributor

Running ignite ps for the first time on a new machine fails with:

FATA[0000] open /var/lib/firecracker/vm: no such file or directory

This change handles the error returned when the backend storage is
uninitialized. NewPsOptions() returns an empty list of VMs and allows
the ps execution to continue without any error.

Running ignite ps for the first time on a new machine fails with:
```
FATA[0000] open /var/lib/firecracker/vm: no such file or directory
```

This change handles the error returned when the backend storage is
uninitialized. NewPsOptions() returns an empty list of VMs and allows
the ps execution to continue without any error.
@darkowlzz darkowlzz added the kind/enhancement Categorizes issue or PR as related to improving an existing feature. label Feb 6, 2021
@darkowlzz darkowlzz added the area/UX Let's make Ignite's UX great! label Feb 6, 2021
@stealthybox stealthybox merged commit 05698d4 into weaveworks:master Feb 8, 2021
@darkowlzz darkowlzz deleted the no-storage-ps-fail branch February 8, 2021 16:21
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/UX Let's make Ignite's UX great! 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