Bug 2024505 - python38-jsonschema-3.2.0-7.el8pc installation failed
Summary: python38-jsonschema-3.2.0-7.el8pc installation failed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: Unspecified
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-18 08:36 UTC by Yuxin Sun
Modified: 2023-08-01 17:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-01 17:29:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19277 0 None None None 2023-07-31 17:58:31 UTC

Description Yuxin Sun 2021-11-18 08:36:01 UTC
Description of problem:
Failed to install python38-jsonschema-3.2.0-7.el8pc.noarch.rpm in RHEL-8.6 because nothing provides dependencies.

Version-Release number of selected component (if applicable):
RHEL-8.6
python38-jsonschema-3.2.0-7.el8pc.noarch.rpm 

How reproducible:
100%

Steps to Reproduce:
1. Boot up a RHEL-8.6. Try to yum install python38-jsonschema-3.2.0-7.el8pc.noarch.rpm package.

Actual results:
# yum install ./python38-jsonschema-3.2.0-7.el8pc.noarch.rpm 
Last metadata expiration check: 3:04:03 ago on Thu 18 Nov 2021 12:25:21 AM EST.
Error: 
 Problem: conflicting requests
  - nothing provides python38-pyrsistent >= 0.14.0 needed by python38-jsonschema-3.2.0-7.el8pc.noarch
  - nothing provides python38-importlib-metadata needed by python38-jsonschema-3.2.0-7.el8pc.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Expected results:
Can install this package successfully.

Additional info:
If uninstall python36 and install python38 then try to install python38-jsonschema-3.2.0-7.el8pc.noarch.rpm, also hit this issue.

Comment 1 Eduardo Otubo 2021-11-23 12:59:07 UTC
(In reply to Yuxin Sun from comment #0)
> Description of problem:
> Failed to install python38-jsonschema-3.2.0-7.el8pc.noarch.rpm in RHEL-8.6
> because nothing provides dependencies.
> 
> Version-Release number of selected component (if applicable):
> RHEL-8.6
> python38-jsonschema-3.2.0-7.el8pc.noarch.rpm 
> 
> How reproducible:
> 100%
> 
> Steps to Reproduce:
> 1. Boot up a RHEL-8.6. Try to yum install
> python38-jsonschema-3.2.0-7.el8pc.noarch.rpm package.
> 
> Actual results:
> # yum install ./python38-jsonschema-3.2.0-7.el8pc.noarch.rpm 
> Last metadata expiration check: 3:04:03 ago on Thu 18 Nov 2021 12:25:21 AM
> EST.
> Error: 
>  Problem: conflicting requests
>   - nothing provides python38-pyrsistent >= 0.14.0 needed by
> python38-jsonschema-3.2.0-7.el8pc.noarch
>   - nothing provides python38-importlib-metadata needed by
> python38-jsonschema-3.2.0-7.el8pc.noarch
> (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to
> use not only best candidate packages)
> 
> Expected results:
> Can install this package successfully.
> 
> Additional info:
> If uninstall python36 and install python38 then try to install
> python38-jsonschema-3.2.0-7.el8pc.noarch.rpm, also hit this issue.

@ymankad all the package removal we did was only for rhel-9, right? Can you double check if there's anything weird about those for rhel-8.6?

Comment 2 Yash Mankad 2021-11-26 21:37:28 UTC
(In reply to Eduardo Otubo from comment #1)
> (In reply to Yuxin Sun from comment #0)

> > Error: 
> >  Problem: conflicting requests
> >   - nothing provides python38-pyrsistent >= 0.14.0 needed by
> > python38-jsonschema-3.2.0-7.el8pc.noarch
> >   - nothing provides python38-importlib-metadata needed by
> > python38-jsonschema-3.2.0-7.el8pc.noarch
> > (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to
> > use not only best candidate packages)
> > 

> 
> @ymankad all the package removal we did was only for rhel-9,
> right? Can you double check if there's anything weird about those for
> rhel-8.6?

Yes, while the removal of the python dependencies were only from RHEL-9,
one related action as part of the removal process was that these packages
were deprecated in RHEL-8. So, they would not get updated after RHEL-8.5.

And I don't see the python38-jsonschema in RHEL-8.5, or 8.6.

Moving the needinfo to Tomas Orsava, Python PO, who might be able to
provide better insight into what happened to the python38-pyrsistent,
and -jsconschema packages in 8.5 and 8.6.

Comment 6 Jeff Nelson 2023-01-23 18:59:46 UTC
I believe this is NOTABUG as far as RHEL is concerned. The package appears to have originated from a Satellite build, not RHEL, so I am redirecting the BZ to the Satellite team for their analysis.

If the reporter wishes to return this back to RHEL, I would ask for additional information, like: why are you attempting to install this package? What are you trying to do with it once it is installed? It appears that RHEL no longer provides the package

Comment 7 Jeff Nelson 2023-01-23 19:07:58 UTC
I changed the Pool ID to one of the ones in satellite. It's probably wrong, but better than sst_virtualization_cloud, which was even more wrong.

Comment 8 Brad Buckingham 2023-01-26 15:47:55 UTC
Patrick,

Can you take a quick look to confirm if this bugzilla should be on Satellite?  Thanks!

Comment 10 Patrick Creech 2023-08-01 17:29:49 UTC
Reviewing the comments on this bug, it's unclear what repo python-jsonschema is being pulled in from.  If the initial comment is to be believed, it appears it has been downloaded and being installed directly:

    # yum install ./python38-jsonschema-3.2.0-7.el8pc.noarch.rpm

notice the './' part of the above command.

This package is shipped in repos for ansible automation platform and for satellite, and it does have other python dependencies that will need to be installed alongside.

Closing as not-a-bug based on initial content, feel free to re-open with more specific information if my assumptions on install method are incorrect.


Note You need to log in before you can comment on or make changes to this bug.