Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2137312 - F38FailsToInstall: votca-libs
Summary: F38FailsToInstall: votca-libs
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: libfabric
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F38FailsToInstall
TreeView+ depends on / blocked
 
Reported: 2022-10-24 12:22 UTC by Miro Hrončok
Modified: 2022-11-11 23:33 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-11 23:33:49 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ofiwg libfabric pull 8227 0 None Merged prov/net: fix error path in xnet_enable_rdm 2022-11-09 17:13:37 UTC

Internal Links: 2142192

Description Miro Hrončok 2022-10-24 12:22:34 UTC 
Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

Your package (votca) Fails To Install in Fedora 38:

can't install votca-libs:
  - nothing provides libxc.so.9()(64bit) needed by votca-libs-2022-8.fc37.x86_64
  
If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.


If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.


P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock:

    $ mock -r fedora-38-x86_64 --config-opts mirrored=False install votca-libs


P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages

Thanks!
Comment 1 Miro Hrončok 2022-10-31 12:40:27 UTC 
Hello,

This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs).

If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.
Comment 2 Christoph Junghans 2022-10-31 20:44:11 UTC 
@mhroncok https://koji.fedoraproject.org/koji/taskinfo?taskID=93493562, but no idea why it is hanging...
Comment 3 Miro Hrončok 2022-11-04 09:22:00 UTC 
No idea what info is required form me here.
Comment 4 Christoph Junghans 2022-11-07 21:28:24 UTC 
Let's do a fresh rebuild: https://koji.fedoraproject.org/koji/taskinfo?taskID=93920373
Comment 5 Christoph Junghans 2022-11-08 20:18:05 UTC 
Ok, got it, CMaake is hanging when detecting espresso-openmpi.

I was able to reproduce this by running 'python -c "import espressomd"' in mock --shell.

@jgrad.de any ideas.
Comment 6 Jean-Noël Grad 2022-11-09 14:21:24 UTC 
From my side, I can run `fedpkg prep` without any issue for x86_64 in a Docker image using the fedora:rawhide base image. VOTCA builds and all tests pass. There is however a recurring non-fatal Open MPI warning, which I am not familiar with:
```
$ PYTHONPATH=/usr/lib64/python3.11/site-packages/openmpi python3 -c 'import espressomd.version;print(espressomd.version.friendly())'
70937f55f601:pid156.python3: Failed to get eth0 (unit 0) cpu set
70937f55f601:pid156: PSM3 can't open nic unit: 0 (err=23)
PMIx Log Report:[156]: (nic/PSM)[156]: PSM3 can't open nic unit: 0 (err=23)
70937f55f601:pid156.python3: Failed to get eth0 (unit 0) cpu set
70937f55f601:pid156: PSM3 can't open nic unit: 0 (err=23)
PMIx Log Report:[156]: (nic/PSM)[156]: PSM3 can't open nic unit: 0 (err=23)
70937f55f601:pid156.python3: Failed to get eth0 (unit 0) cpu set
70937f55f601:pid156: PSM3 can't open nic unit: 0 (err=23)
PMIx Log Report:[156]: (nic/PSM)[156]: PSM3 can't open nic unit: 0 (err=23)
70937f55f601:pid156.python3: Failed to get eth0 (unit 0) cpu set
70937f55f601:pid156: PSM3 can't open nic unit: 0 (err=23)
PMIx Log Report:[156]: (nic/PSM)[156]: PSM3 can't open nic unit: 0 (err=23)
--------------------------------------------------------------------------
Open MPI failed an OFI Libfabric library call (fi_endpoint).  This is highly
unusual; your job may behave unpredictably (and/or abort) after this.

  Local host: 70937f55f601
  Location: mtl_ofi_component.c:512
  Error: Invalid argument (22)
--------------------------------------------------------------------------
4.2
```
Looking at the Koji build, it seems to hang at the CMake stage where espressomd is being detected. From my side, when CMake reaches that stage, it doesn't hang but produces the same Open MPI warning. During the testsuite execution, this warning is emitted when the `regression_spce_ibi_espresso` test starts.
Comment 7 Christoph Junghans 2022-11-09 17:13:38 UTC 
I think this might the same issue I saw on openSUSE https://bugzilla.suse.com/show_bug.cgi?id=1205139 and https://github.com/ofiwg/libfabric/pull/8227
Comment 8 Miro Hrončok 2022-11-11 23:33:49 UTC 
Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

All subpackages of a package against which this bug was filled are now installable or removed from Fedora 38.

Thanks for taking care of it!
Note You need to log in before you can comment on or make changes to this bug.