Cannot deploy Centos7 with xfs when using Focal as commissioning image
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Mauricio Faria de Oliveira | ||
2.8 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.9 |
Fix Released
|
Medium
|
Unassigned | ||
3.0 |
Fix Released
|
Medium
|
Mauricio Faria de Oliveira | ||
3.1 |
Fix Released
|
Undecided
|
Unassigned | ||
curtin |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When setting Focal as commissioning image and try to deploy Centos7 with xfs the machine keeps rebooting.
The reboots happen because the root partition is mounted as read-only and cannot be re-mounted as rw :
[ 1.627587] XFS (sda2): Superblock has unknown read-only compatible features (0x4) enabled.
[ 3.115579] XFS (sda2): ro->rw transition prohibited on unknown (0x4) ro-compat filesystem
If use Bionic as commissioning image Centos7+xfs is deployed without problems.
The root cause of this is xfs being incompatible between older and newer versions.
To confirm this I passed "reflink=0" to mkfs.xfs command with following hack :
diff --git a/curtin/
index ea5f09dd..abfefdb1 100644
--- a/curtin/
+++ b/curtin/
@@ -84,7 +84,7 @@ family_
- "xfs": ("-m", "uuid={uuid}")},
+ "xfs": ("-m", "uuid={
}
release_
With this hack I was able to deploy Centos7+xfs using focal as commissioning image.
However this quick hack is only to confirm the root cause and not a good fix.
I open this bug to investigate a more appropriate solution.
Related branches
- Alexsander de Souza: Approve
- MAAS Lander: Approve
-
Diff: 13 lines (+3/-0)1 file modifiedcontrib/preseeds_v2/curtin_userdata_centos (+3/-0)
- Alexsander de Souza: Approve
- MAAS Lander: Approve
-
Diff: 13 lines (+3/-0)1 file modifiedcontrib/preseeds_v2/curtin_userdata_centos (+3/-0)
- Alexsander de Souza: Approve
- MAAS Lander: Approve
-
Diff: 13 lines (+3/-0)1 file modifiedcontrib/preseeds_v2/curtin_userdata_centos (+3/-0)
- Alexsander de Souza: Approve
- MAAS Lander: Approve
-
Diff: 13 lines (+3/-0)1 file modifiedcontrib/preseeds_v2/curtin_userdata_centos (+3/-0)
Changed in maas: | |
status: | New → Confirmed |
Changed in curtin: | |
status: | New → Confirmed |
Changed in maas: | |
status: | Confirmed → New |
Changed in curtin: | |
status: | Confirmed → Incomplete |
status: | Incomplete → New |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → next |
Changed in curtin: | |
status: | New → Invalid |
Changed in maas: | |
status: | Triaged → Confirmed |
Changed in maas: | |
status: | Confirmed → In Progress |
assignee: | nobody → Mauricio Faria de Oliveira (mfo) |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | next → 3.2.0 |
milestone: | 3.2.0 → next |
Changed in maas: | |
milestone: | next → 3.2.0 |
Changed in maas: | |
milestone: | 3.2.0 → 3.2.0-beta5 |
status: | Fix Committed → Fix Released |
tags: | added: sts |
A solution could also be to use a higher kernel version.
You can download the CentOS 7 cloud image, edit it and add kernel-lt (or kernel-ml) to it from elrepo-kernel (https:/ /elrepo. org/tiki/ HomePage).
After that, during deployment you will have to regenerate the initramfs with dracut and uninstall the "normal" kernel package (then it will use kernel-lt) using curtin commands. This is necessary because MaaS is only set up to regenerate the initramfs of the "kernel" package.