Docker fails if using XFS and ftype=0

Bug #1765121 reported by Carlos Camacho on 2018-04-18
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tripleo
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.

Carlos Camacho (ccamacho) wrote :

There is no current fix rather than formatting again those volumes.

Changed in tripleo:
importance: Undecided → High
status: New → Triaged
assignee: nobody → Carlos Camacho (ccamacho)
tags: added: pike-backport-potential
Carlos Camacho (ccamacho) wrote :
tags: added: containers upgrade

Reviewed: https://review.openstack.org/562282
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=a5e63ee72531c85ee527ce721022fffce3cfcf75
Submitter: Zuul
Branch: master

commit a5e63ee72531c85ee527ce721022fffce3cfcf75
Author: Carlos Camacho <email address hidden>
Date: Wed Apr 18 15:41:58 2018 +0200

    Validate that there should not be XFS volumes with ftype=0

    If we have XFS partitions formatted with ftype=0,
    the upgrades will fail because ftype=0 is incompatible
    with the docker overlayfs driver.

    Related-Bug: 1765121
    Change-Id: I895fc83d148523c283664080b7b1bf75d53d9edb

Reviewed: https://review.openstack.org/564109
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=d54ae2d1e21245f7033107e1bae327621f54f82f
Submitter: Zuul
Branch: stable/queens

commit d54ae2d1e21245f7033107e1bae327621f54f82f
Author: Carlos Camacho <email address hidden>
Date: Wed Apr 18 15:41:58 2018 +0200

    Validate that there should not be XFS volumes with ftype=0

    If we have XFS partitions formatted with ftype=0,
    the upgrades will fail because ftype=0 is incompatible
    with the docker overlayfs driver.

    Related-Bug: 1765121
    Change-Id: I895fc83d148523c283664080b7b1bf75d53d9edb
    (cherry picked from commit a5e63ee72531c85ee527ce721022fffce3cfcf75)

tags: added: in-stable-queens

Change abandoned by Alex Schultz (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/564698
Reason: abandoning to clear gate for Bug 1770355. Will restore after fix lands.

Reviewed: https://review.openstack.org/564738
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=8e6ecb79ffdbe19578913b56b66eb6e68c106092
Submitter: Zuul
Branch: stable/ocata

commit 8e6ecb79ffdbe19578913b56b66eb6e68c106092
Author: Carlos Camacho <email address hidden>
Date: Wed Apr 18 15:41:58 2018 +0200

    Validate that there should not be XFS volumes with ftype=0

    If we have XFS partitions formatted with ftype=0,
    the upgrades will fail because ftype=0 is incompatible
    with the docker overlayfs driver.

    Related-Bug: 1765121
    Change-Id: I895fc83d148523c283664080b7b1bf75d53d9edb
    (cherry picked from commit a5e63ee72531c85ee527ce721022fffce3cfcf75)
    (cherry picked from commit d54ae2d1e21245f7033107e1bae327621f54f82f)

tags: added: in-stable-ocata

Reviewed: https://review.openstack.org/564698
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=578618e4c7598d3282c14c49cc341d14f4cb174f
Submitter: Zuul
Branch: stable/pike

commit 578618e4c7598d3282c14c49cc341d14f4cb174f
Author: Carlos Camacho <email address hidden>
Date: Wed Apr 18 15:41:58 2018 +0200

    Validate that there should not be XFS volumes with ftype=0

    If we have XFS partitions formatted with ftype=0,
    the upgrades will fail because ftype=0 is incompatible
    with the docker overlayfs driver.

    Related-Bug: 1765121
    Change-Id: I895fc83d148523c283664080b7b1bf75d53d9edb
    (cherry picked from commit a5e63ee72531c85ee527ce721022fffce3cfcf75)
    (cherry picked from commit d54ae2d1e21245f7033107e1bae327621f54f82f)

tags: added: in-stable-pike

Reviewed: https://review.openstack.org/564739
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=3130bc412917b7591b532ca792f6df909df21615
Submitter: Zuul
Branch: stable/newton

commit 3130bc412917b7591b532ca792f6df909df21615
Author: Carlos Camacho <email address hidden>
Date: Wed Apr 18 15:41:58 2018 +0200

    Validate that there should not be XFS volumes with ftype=0

    If we have XFS partitions formatted with ftype=0,
    the upgrades will fail because ftype=0 is incompatible
    with the docker overlayfs driver.

    Related-Bug: 1765121
    Change-Id: I895fc83d148523c283664080b7b1bf75d53d9edb
    (cherry picked from commit a5e63ee72531c85ee527ce721022fffce3cfcf75)
    (cherry picked from commit d54ae2d1e21245f7033107e1bae327621f54f82f)

tags: added: in-stable-newton
Changed in tripleo:
status: Triaged → Fix Released

Reviewed: https://review.openstack.org/613429
Committed: https://git.openstack.org/cgit/openstack/ansible-role-container-registry/commit/?id=5e1ba52f791835ff03aa8d6459354600b55db8fc
Submitter: Zuul
Branch: master

commit 5e1ba52f791835ff03aa8d6459354600b55db8fc
Author: Alex Schultz <email address hidden>
Date: Thu Oct 25 15:23:30 2018 -0600

    Add xfs ftype check during install

    Since we know xfs ftype=0 is incompatible with the container usage,
    let's fail hard with a message if the system has an improperly
    configured filesystem.

    Change-Id: I06f80003d7f3f6443f75f39973d4e68ac24673be
    Related-Bug: #1765121

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers