Docker fails if using XFS and ftype=0
Bug #1765121 reported by
Carlos Camacho
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Carlos Camacho |
Bug Description
We need to be sure that we don't have volumes formatted with XFS and ftype=0.
Deployments from OpenStack Kilo or Liberty have XFS
partitions formatted with ftype=0, which is incompatible
with the docker overlayfs driver.
From OpenStack Newton, we have support for XFS ftype=1
by default.
There is the need of checking this for deployments coming
back from Kilo or Liberty
having XFS partitions with ftype=0.
tags: | added: containers upgrade |
Changed in tripleo: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
There is no current fix rather than formatting again those volumes.