Skip to content
This repository has been archived by the owner on Feb 9, 2024. It is now read-only.

Disk checker kicks in even if requirements are not specified #1748

Closed
a-palchikov opened this issue Jun 22, 2020 · 2 comments
Closed

Disk checker kicks in even if requirements are not specified #1748

a-palchikov opened this issue Jun 22, 2020 · 2 comments
Assignees
Labels
gravity-cli kind/bug Something isn't working priority/0 High priority regression Something that worked in a previous version no longer works.

Comments

@a-palchikov
Copy link
Contributor

Reported from a 7.0.9 installation:

[  129.608996] cloud-init[1120]: [×] disk capacity at /proc is 0 (failed to validate storage requirements)
@a-palchikov a-palchikov added kind/bug Something isn't working gravity-cli regression Something that worked in a previous version no longer works. labels Jun 22, 2020
@burdzwastaken
Copy link
Contributor

we are also seeing this behaviour in 7.0.9:

[  118.100276] cloud-init[1123]: �[31m[ERROR]: The following pre-flight checks failed:
[  118.104108] cloud-init[1123]: [×] disk capacity at /proc is 0 (failed to validate storage requirements)

@r0mant r0mant added the priority/0 High priority label Jun 24, 2020
@r0mant r0mant changed the title [satellite] do not consider virtual file systems for storage evaluation Disk checker kicks in even if requirements are not specified Jun 25, 2020
@r0mant r0mant mentioned this issue Jun 25, 2020
14 tasks
@r0mant
Copy link
Contributor

r0mant commented Jun 25, 2020

Released in 7.0.11, ports are tracked in #1740.

@r0mant r0mant closed this as completed Jun 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
gravity-cli kind/bug Something isn't working priority/0 High priority regression Something that worked in a previous version no longer works.
Projects
None yet
Development

No branches or pull requests

5 participants