Bug 2223289

Summary: iot-installer issue booting BIOS image Failed to pull from repository: g-io-error-quark
Product: [Fedora] Fedora Reporter: Mario Cattamo <mcattamo>
Component: osbuild-composerAssignee: Ondřej Budai <obudai>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 39CC: akoutsou, anaconda-maint-list, go-sig, jkonecny, obudai, osbuilders, ssteinbe, tgunders
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mario Cattamo 2023-07-17 09:02:21 UTC
In iot-installer, virt-install is not able to boot BIOS VM with installer blueprint.

Fedora rawhide compose Fedora-Rawhide-20230716.n.0
osbuild-89-2.fc39.noarch.rpm
osbuild-composer-85-1.fc39.x86_64.rpm
weldr-client-35.11-1.fc39.x86_64.rpm

BIOS VM issue log:

================================================================================

================================================================================
Installation

1) [x] Language settings                 2) [x] Time settings
       (English (United States))                (America/New_York timezone)
3) [x] Installation Destination          4) [x] Network configuration
       (Automatic partitioning                  (Connected: enp1s0)
       selected)
5) [ ] Root password
       (Root account is disabled)

================================================================================
================================================================================
Progress

Setting up the installation environment
.
Configuring storage
Creating disklabel on /dev/vda
Creating ext4 on /dev/vda2
Creating ext4 on /dev/vda1
.
Running pre-installation scripts
.
Running pre-installation tasks
.
Installing the software
Starting pull of fedora/39/x86_64/iot from fedora
================================================================================
================================================================================
Error

The following error occurred while installing the payload. This is a fatal error
and installation will be aborted.

Failed to pull from repository: g-io-error-quark: opening repo:
opendir(/run/install/repo/ostree/repo): No such file or directory (1)

Press ENTER to exit: 

Reproducible: Always

Steps to Reproduce:
1. Create Fedora Rawhide VM in Openstack
2. git clone https://github.com/virt-s1/rhel-edge.git
3. cd rhel-edge
4. DOWNLOAD_NODE="hello-world.com" OCP4_TOKEN=abcdefg QUAY_USERNAME=rhel-edge QUAY_PASSWORD=123456 ./ostree-ng.sh
Actual Results:  
BIOS VM installation aborted.

Expected Results:  
BIOS VM installation successful.

Continue VM installation without any issues.

Comment 1 Achilleas Koutsou 2023-07-18 10:00:08 UTC
@anaconda-maint-list Is there a change or known issue with Anaconda?  We haven't changed anything in our build and it seems that, when booting the ISO, /run/install/repo isn't mounted.

@mcattamo tells me the last compose that works is Fedora-Rawhide-20230715.n.0

Comment 2 Achilleas Koutsou 2023-07-19 14:25:37 UTC
Potential duplicate: Bug 2223795 - Since systemd 254 landed in Rawhide, installs from DVD no longer mount or use the DVD repo

Comment 3 Jiri Konecny 2023-07-25 09:39:38 UTC
We were facing some issues with the rpm-ostree support in the installer recently. See here:

https://pagure.io/fedora-infrastructure/issue/11317


It might be the same issues. However, I also discovered that Anaconda ostree functionality doesn't support mirrorlists (never did) which is now default for IoT. However, hard to say what is in the repository here without longs and custom repository.

The first issue was already resolved, for the second one I would need more data to be able to tell. Could we please get /tmp/*log files and information what is in the repository. When I'm looking on the error I guess it's broken repository but hard to say this way.

Comment 4 Fedora Release Engineering 2023-08-16 08:13:03 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.