[atomic-wg] Issue #299: Concerns related to enabling Atomic Host CloudImages compose in Rawhide for multi-arches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


sinnykumari reported a new issue against the project: `atomic-wg` that you are following:
I am working on enabling Atomic Host CloudImages in Fedora 27 onward for multi-arches which includes aarch64 and ppc64le. Required changes has been made in Fedora config to enable qcow2 and raw images [Link - https://pagure.io/pungi-fedora/blob/master/f/fedora.conf#_361] .

It seems making above changes is not sufficient because we are seeing all related builds failing for both arches. One of the failed koji build link - https://koji.fedoraproject.org/koji/taskinfo?taskID=20304853

After debugging cause of failure (started with ppc64le), I see following two issues:
1. kickstart file used for building Atomic CloudImage has arch specific content at line https://pagure.io/fedora-kickstarts/blob/master/f/fedora-atomic.ks#_35 .

Possible solution
We can remove x86_64 mention with something generic like:
basearch=$(uname -i)
and replacing x86_64 with $basearch should fix this.

2. I see that in kickstart fedora-atomic.ks [ https://pagure.io/fedora-kickstarts/blob/master/f/fedora-atomic.ks#_27 ], we don't use autopart (used by all other variants' kickstart) to create partition. Instead of autopart, we create partitions manually by using part. This leads to anaconda text based installation failure with error message "storage configuration failed: failed to find a suitable stage1 device." on ppc64le [ https://kojipkgs.fedoraproject.org//work/tasks/4883/20304883/screenshot.ppm ]
It seems required PReP partition is not getting created for ppc64le arch.
If I add into kickstart file "part prepboot --fstype "PPC PReP Boot" --size=10" to create PReP partition on ppc64le, I get successful running AH CloudImage on ppc64le (tried locally) . But, this would again add-up arch-specific changes in kickstart file.

I would like to know your thoughts on getting them fixed in proper way.

Note: Debugging issue on aarch64 is still pending which might bring-up some additional concern.

To reply, visit the link below or just reply to this email
cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Big List of Linux Books]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux