[Bug 1129566] New: ignition cannot write to /sysroot/etc with transactional-updates
http://bugzilla.suse.com/show_bug.cgi?id=1129566 Bug ID: 1129566 Summary: ignition cannot write to /sysroot/etc with transactional-updates Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: fvogt@suse.com Reporter: kukuk@suse.com QA Contact: qa-bugs@suse.de CC: iforster@suse.com Found By: --- Blocker: --- If I use our images with transactional-updates, like the ones for openSUSE MicroOS and Kubic, we have a problem: ignition runs at the first boot, but /sysroot/etc/fstab does not contain the overlayfs entries, they are only in /sysroot/etc/fstab.sys. So /sysroot/etc is not writeable and ignition will fail. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c1
Fabian Vogt
http://bugzilla.suse.com/show_bug.cgi?id=1129566
Fabian Vogt
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c2
Marcus Schaefer
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c3
Fabian Vogt
Issue #945 has been fixed. A submission to Factory will follow by Friday as soon as the integration build matrix is functional again, the obs problem from last weekend impacts those too
I added a comment: "Please reopen - fstab.patch does not actually fix this.". -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c4
--- Comment #4 from Marcus Schaefer
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c5
--- Comment #5 from Fabian Vogt
sorry that must felt off the radar,
why does it not fix it ?
I added a comment with further information for clarification. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c6
--- Comment #6 from Marcus Schaefer
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c7
Marcus Schaefer
http://bugzilla.suse.com/show_bug.cgi?id=1129566
Marcus Schaefer
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c8
Marcus Schaefer
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c9
Fabian Vogt
With regards to the conversation and agreement we had with Richard and you we extended the spare partition support such that the requested extra partition (/var in your case) including contents and fstab setup are part of the image build. The PR is open for reference here:
* https://github.com/SUSE/kiwi/pull/1101
Once added I assume the needed adaptions to the fstab regarding the special overlayfs setup you use can then be handled better
Can you provide an example which edits the /var entry in the /etc/fstab and works for multiple flavors with UUID mounting? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1129566
Fabian Vogt
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c13
Marcus Schaefer
From a partition perspective it looks like this
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT fd0 2:0 1 4K 0 disk sda 8:0 0 24G 0 disk ├─sda1 8:1 0 2M 0 part ├─sda2 8:2 0 20M 0 part /boot/efi ├─sda3 8:3 0 19G 0 part / └─sda4 8:4 0 5G 0 part /var sr0 11:0 1 1024M 0 rom So /var is at the end and growable If you are looking for code that could grow the partition. I wrote this code for the public cloud. It is designed to grow root but it can easily be adapted to just grow whatever is last https://github.com/SUSE-Enceladus/rootgrow/pulls Does this provide the desired layout ? One question from my side. The system is read-only on /etc and other parts of the rootfs. I guess this is by intention ? Thanks -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c14
--- Comment #14 from Fabian Vogt
I've setup an integration test based on your MicroOS description such that we have continuous testing of the feature set needed here. This image can be found here:
https://build.opensuse.org/package/show/Virtualization:Appliances:Images: Testing_x86/test-image-MicroOS
Based on that build I run a VM, and it comes up with the following layout:
--- UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /.snapshots btrfs defaults,subvol=@/.snapshots 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /home btrfs defaults,subvol=@/home 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /opt btrfs defaults,subvol=@/opt 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /root btrfs defaults,subvol=@/root 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /srv btrfs defaults,subvol=@/srv 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /tmp btrfs defaults,subvol=@/tmp 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /usr/local btrfs defaults,subvol=@/usr/local 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /boot/grub2/i386-pc btrfs defaults,subvol=@/boot/grub2/i386-pc 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /boot/grub2/x86_64-efi btrfs defaults,subvol=@/boot/grub2/x86_64-efi 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b / btrfs ro 0 0 UUID=1b6dcaba-3bc3-457a-939b-ca2e3da38c38 /var ext4 defaults 0 0 UUID=06CC-D762 /boot/efi vfat defaults 0 0 ---
From a partition perspective it looks like this
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT fd0 2:0 1 4K 0 disk sda 8:0 0 24G 0 disk ├─sda1 8:1 0 2M 0 part ├─sda2 8:2 0 20M 0 part /boot/efi ├─sda3 8:3 0 19G 0 part / └─sda4 8:4 0 5G 0 part /var sr0 11:0 1 1024M 0 rom
So /var is at the end and growable
If you are looking for code that could grow the partition. I wrote this code for the public cloud. It is designed to grow root but it can easily be adapted to just grow whatever is last
https://github.com/SUSE-Enceladus/rootgrow/pulls
Does this provide the desired layout ?
Yes, those two together should work for our use-case. BTW, config.sh generates the ssh host key, you don't want that...
One question from my side. The system is read-only on /etc and other parts of the rootfs. I guess this is by intention ?
No, you just ran into https://github.com/SUSE/kiwi/issues/945, the issue this bug report is about. You're missing the entries in /etc/fstab that the read-only-root-fs package takes care of.
Thanks
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c15
--- Comment #15 from Marcus Schaefer
BTW, config.sh generates the ssh host key, you don't want that...
just a temporary thing to be able to login until the read-only situation could be solved -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c16
--- Comment #16 from Marcus Schaefer
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c18
Marcus Schaefer
http://bugzilla.suse.com/show_bug.cgi?id=1129566
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c20
--- Comment #20 from Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1129566
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1129566
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1129566
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c22
--- Comment #22 from Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1129566
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1129566
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c26
--- Comment #26 from Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1129566
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1129566
http://bugzilla.suse.com/show_bug.cgi?id=1129566#c28
--- Comment #28 from Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1129566
Maintenance Robot
https://bugzilla.suse.com/show_bug.cgi?id=1129566
https://bugzilla.suse.com/show_bug.cgi?id=1129566#c30
--- Comment #30 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1129566
https://bugzilla.suse.com/show_bug.cgi?id=1129566#c42
--- Comment #42 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1129566
https://bugzilla.suse.com/show_bug.cgi?id=1129566#c44
--- Comment #44 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1129566
https://bugzilla.suse.com/show_bug.cgi?id=1129566#c46
--- Comment #46 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1129566
https://bugzilla.suse.com/show_bug.cgi?id=1129566#c47
--- Comment #47 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1129566
https://bugzilla.suse.com/show_bug.cgi?id=1129566#c48
--- Comment #48 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1129566
https://bugzilla.suse.com/show_bug.cgi?id=1129566#c45
--- Comment #45 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1129566
https://bugzilla.suse.com/show_bug.cgi?id=1129566#c43
--- Comment #43 from Swamp Workflow Management
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com