Bug 1212959

Summary:	SelfInstall Image - Failed to create partition table
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Malcolm Lewis <malcolmlewis>
Component:	MicroOS	Assignee:	Forgotten User u0-bnvADNc <forgotten_u0-bnvADNc>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	forgotten_u0-bnvADNc, greylinux, khanich.opensource, marcus.schaefer, thomas
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Malcolm Lewis 2023-07-03 19:33:16 UTC

Hi
The latest SelfInstall Image 20230701; (607aaefe2caf487834659f95e59ee7c2adff4f4c6ae69906c5b2746d3f359dd0 openSUSE-MicroOS.x86_64-SelfInstall.raw.xz)

Install fails with the following error with Combustion;

dracut [676]: Created symlink /etc/systemd/system/systemd-fsck-root.service -> /dev/null
dracut-pre-mount[1070]: Warning! Unable to generate a proper UUID! Creating an improper one as a last
dracut-pre-mount[1070]: resort! Windows 7 may crash if you save this partition table!
dracut-pre-mount(1073]: /lib/kiwi-partitions-lib.sh: line 25: partprobe: command not found
dracut: FATAL: Failed to create partition table
dracut: Refusing to continue
dracut-pre-mount[1079]: Failed to get properties: Transport endpoint is not connected

Screen blanks, no signal!

Force power off, then Power On.

Install completes, system reboots and arrive at login prompt.

Login as root user and / is only 1.3GB and almost full, run transactional-update shell, then run btrfs fi resize max / exit and reboot.

All is fine, the combustion scripts have run and everything populated as expected. However due to this I cannot install my Combustion additional packages, this has to be done after the NVMe is resized.

Comment 1 Tim Harrison 2023-07-09 21:45:04 UTC

I ran into this bug today whilst trying microOS self install image and my combustion script. Running the mentioned commands does fix the issue but its a shame to have to install the additional packages after first boot.

Comment 2 Kilian Hanich 2023-07-19 20:40:07 UTC

After digging a bit, it seems like an update of KIWI should solve that (if blockdev is available).

Am I correct about that assumption, considering that this https://github.com/OSInside/kiwi/pull/2318 isn't yet in the package in OBS (it's still on 9.24.61)?

Comment 3 Kilian Hanich 2023-07-19 20:43:30 UTC

PS: There is still have the .de address in the specfile of the python-wiki package.

Comment 4 Marcus Schäfer 2023-07-28 07:08:02 UTC

Hi, I cannot tell much about the combustion errors but the missing partprobe issue was fixed in this PR upstream:

* https://github.com/OSInside/kiwi/pull/2318

> There is still have the .de address in the specfile 

That issue was also fixed upstream :) Thanks

Regarding the PR from above, an updated kiwi package in Factory/TW is
still pending but on its way

Hope this helps

Comment 5 Malcolm Lewis 2023-07-28 11:56:41 UTC

@All, thanks for fixing this issue, will wait for the next snapshot release and re-test to confirm.

Comment 6 Malcolm Lewis 2023-08-14 13:58:29 UTC

(In reply to Malcolm Lewis from comment #5)
> @All, thanks for fixing this issue, will wait for the next snapshot release
> and re-test to confirm.

@Marcus Schäfer
 
I've not seen an update for python-kiwi appear as it's still on version v9.24.61?

From the PR you indicated it should have appeared in version v9.25.3?

<https://build.opensuse.org/package/show/Virtualization:Appliances:Builder/python-kiwi>

Or is the updated version coming from a different build repository?

Comment 7 Marcus Schäfer 2023-08-15 07:23:59 UTC

Hi

> I've not seen an update for python-kiwi appear as it's still on version v9.24.61?


yep, on the list for today. Virt:App:Builder now has the Staging version which completed all integration test successfully, fingers crossed

The submission to Factory was done in SR:

    1103984

Comment 8 Malcolm Lewis 2023-08-17 15:49:35 UTC

Hi All, just tested today's snapshot (20230816) and this issue is now resolved.

Install completes and btrfs file system is using the whole disk as expected.

Many thanks to all involved.