Il giorno lun 13 dic 2021 alle ore 17:25 Sandro Bonazzola <
sbonazzo(a)redhat.com> ha scritto:
Il giorno lun 13 dic 2021 alle ore 17:16 Sandro Bonazzola <
sbonazzo(a)redhat.com> ha scritto:
>
>
> Il giorno lun 13 dic 2021 alle ore 16:43 Sandro Bonazzola <
> sbonazzo(a)redhat.com> ha scritto:
>
>>
>>
>> Il giorno lun 13 dic 2021 alle ore 16:31 <federico.fiordoliva(a)inaf.it>
>> ha scritto:
>>
>>> Hi all,
>>> i have 3 Dell server r740. All have the same hardware configurations.
>>> When i try to install the 2 last images; 4.4.9-2021120923, and
>>> 4.4.9-2021120714 the installation process fail during boot installation.
>>> At this linkt he bug report generated by anaconda.
>>>
>>>
https://www.dropbox.com/s/5vkymurf8pyiuip/bug.tar.gz?dl=0
>>>
>>> When i install the image 4.4.9-2021102623 all works great.
>>> Thank all
>>> bye
>>>
>>
>> thanks for the report!
>> Error seems to be:
>> ERROR:anaconda.modules.common.task.task:Thread
>> AnaTaskThread-InstallBootloaderTask-1 has failed: Traceback (most recent
>> call last):
>> File "/usr/lib64/python3.6/site-packages/pyanaconda/threading.py",
>> line 280, in run
>> threading.Thread.run(self)
>> File "/usr/lib64/python3.6/threading.py", line 885, in run
>> self._target(*self._args, **self._kwargs)
>> File
>>
"/usr/lib64/python3.6/site-packages/pyanaconda/modules/common/task/task.py",
>> line 97, in _task_run_callback
>> self._set_result(self.run())
>> File
>>
"/usr/lib64/python3.6/site-packages/pyanaconda/modules/storage/bootloader/installation.py",
>> line 103, in run
>> install_boot_loader(storage=self._storage)
>> File
>>
"/usr/lib64/python3.6/site-packages/pyanaconda/modules/storage/bootloader/utils.py",
>> line 166, in install_boot_loader
>> storage.bootloader.write()
>> File
>>
"/usr/lib64/python3.6/site-packages/pyanaconda/modules/storage/bootloader/efi.py",
>> line 113, in write
>> self.install()
>> File
>>
"/usr/lib64/python3.6/site-packages/pyanaconda/modules/storage/bootloader/efi.py",
>> line 122, in install
>> self.remove_efi_boot_target()
>> File
>>
"/usr/lib64/python3.6/site-packages/pyanaconda/modules/storage/bootloader/efi.py",
>> line 86, in remove_efi_boot_target
>> buf = self.efibootmgr(capture=True)
>> File
>>
"/usr/lib64/python3.6/site-packages/pyanaconda/modules/storage/bootloader/efi.py",
>> line 57, in efibootmgr
>> return exec_func("efibootmgr", list(args), **kwargs)
>> File "/usr/lib64/python3.6/site-packages/pyanaconda/core/util.py",
>> line 413, in execWithCapture
>> filter_stderr=filter_stderr)[1]
>> File "/usr/lib64/python3.6/site-packages/pyanaconda/core/util.py",
>> line 321, in _run_program
>> env_prune=env_prune)
>> File "/usr/lib64/python3.6/site-packages/pyanaconda/core/util.py",
>> line 202, in startProgram
>> preexec_fn=preexec, cwd=root, env=env, **kwargs)
>> File "/usr/lib64/python3.6/subprocess.py", line 729, in __init__
>> restore_signals, start_new_session)
>> File "/usr/lib64/python3.6/subprocess.py", line 1364, in
_execute_child
>> raise child_exception_type(errno_num, err_msg, err_filename)
>> FileNotFoundError: [Errno 2] No such file or directory: 'efibootmgr':
>> 'efibootmgr'
>>
>> And indeed between 4.4.9 and 4.4.9.1 build the following packages
>> disappeared from the manifest:
>>
>> efi-filesystem-3-3.el8.noarch
>> efibootmgr-16-1.el8.x86_64
>> efivar-libs-37-4.el8.x86_64
>> grub2-efi-x64-2.02-99.el8_4.1.x86_64
>>
>> I also see there's a regression in ovirt-host package:
>> in 4.4.9 the ISO contained ovirt-host-4.4.9-2.el8.x86_64 while in
>> 4.4.9.1 it contains ovirt-host-4.4.8-1.el8.x86_64
>>
>> I'm digging into the root cause of this issue. I fear some packages got
>> lost with the migration of the main server out of the Phoenix datacenter.
>>
>> I guess we missed this because we tested the ISO on a non-efi system.
>>
>> +Lev Veyde <lveyde(a)redhat.com> +Sanja Bonic <sbonic(a)redhat.com>
+Michal
>> Skrivanek <mskrivan(a)redhat.com> for awareness.
>>
>>
>
> The above missing packages are required from ovirt-release-host-node
> package on x86_64 architecture.
>
> Looks like the jenkins job building the iso is not able to detect it's an
> x86_64 host anymore and it's taking packages from some proxy which or
> mirror with outdated content.
>
> I'm going to try rebuilding by enforcing the use of the master mirror and
> enforcing the x86_64 architecture there.
>
Apparently we are already enforcing master mirror:
https://github.com/oVirt/ovirt-node-ng-image/blob/ovirt-4.4/data/ovirt-no...
So the master mirror may be broken.
The 4.4.9-2 package is there:
https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/x86_64/ovirt-host-4.4.9...
so it's not missing.
I'm going to re-generate the repodata and retry the build.
>
>
>
>>
>>
>>
>>>
>>> Federico
>>>
>>> _______________________________________________
>>> Users mailing list -- users(a)ovirt.org
>>> To unsubscribe send an email to users-leave(a)ovirt.org
>>> Privacy Statement:
https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct:
>>>
https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/K5EVL2TPWGQ...
>>>
>>
>>
>> --
>>
>> Sandro Bonazzola
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>>
>> Red Hat EMEA <
https://www.redhat.com/>
>>
>> sbonazzo(a)redhat.com
>> <
https://www.redhat.com/>
>>
>> *Red Hat respects your work life balance. Therefore there is no need to
>> answer this email out of your office hours.*
>>
>>
>>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat EMEA <
https://www.redhat.com/>
>
> sbonazzo(a)redhat.com
> <
https://www.redhat.com/>
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.*
>
>
>
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <
https://www.redhat.com/>
sbonazzo(a)redhat.com
<
https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*