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 2077856 - package sssd-idp-2.7.0-1.fc35.x86_64 requires sssd-common = 2.7.0-1.fc35, but none of the providers can be installed
Summary: package sssd-idp-2.7.0-1.fc35.x86_64 requires sssd-common = 2.7.0-1.fc35, but...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: sssd
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: sssd-maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F36FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2022-04-22 12:51 UTC by Kamil Páral
Modified: 2022-05-02 19:43 UTC (History)
15 users (show)

Fixed In Version: sssd-2.7.0-1.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-02 19:43:06 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Kamil Páral 2022-04-22 12:51:39 UTC 
Description of problem:
When trying to upgrade from F35 to F36:

Error: 
 Problem: package sssd-idp-2.7.0-1.fc35.x86_64 requires sssd-common = 2.7.0-1.fc35, but none of the providers can be installed
  - sssd-common-2.7.0-1.fc35.x86_64 does not belong to a distupgrade repository
  - problem with installed package sssd-idp-2.7.0-1.fc35.x86_64

I believe that is resolved by pushing this update stable:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-cdc3365ffc

Requesting for a Freeze Exception.
Comment 1 Pavel Březina 2022-04-22 14:04:22 UTC 
Thank you. This is unfortunate. It will indeed be fixed by the update which is already submitted to stable.
Comment 2 Adam Williamson 2022-04-22 18:49:10 UTC 
+3 in https://pagure.io/fedora-qa/blocker-review/issue/773 , marking accepted. However, as the first RC has been built, this will not be pushed stable unless we're sure a new RC is needed.
Comment 3 Uncle No.5 2022-04-24 02:11:09 UTC 
Is there any way to ignore this error and update to fedora 36?
```
sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-cdc3365ffc
```
I tried this as suggested but doesn't seem to work for me :-(
Comment 4 Geraldo Simião 2022-04-25 02:51:54 UTC 
And now we have this other bug related to the same package 
https://bugzilla.redhat.com/show_bug.cgi?id=2078243
Comment 5 Pavel Březina 2022-04-25 08:56:02 UTC 
(In reply to Adam Williamson from comment #2)
> +3 in https://pagure.io/fedora-qa/blocker-review/issue/773 , marking
> accepted. However, as the first RC has been built, this will not be pushed
> stable unless we're sure a new RC is needed.

sssd-idp is a new package which is already included in Fedora 35. This package is required by sssd-ipa which is likely to be installed. It is currently not available in Fedora 36 stable therefore this update needs to go to Fedora stable in order to allow transition from F35 to F36.

I think as a workaround, users can uninstall sssd-ipa,sssd-idp -> upgrade to F36 -> install sssd-ipa.
Comment 6 Kamil Páral 2022-04-25 10:54:01 UTC 
(In reply to Uncle No.5 from comment #3)
> Is there any way to ignore this error and update to fedora 36?

The workaround is to use --allowerasing, e.g.:
$ sudo dnf system-upgrade download --releasever=36 --allowerasing

Make sure to read the transaction output carefully before confirming.
Comment 7 Pavel Březina 2022-04-29 14:03:06 UTC 
Kamil, what does VERIFIED mean in the context of this BZ? When will the update be pushed to stable?
Comment 8 Adam Williamson 2022-04-29 17:44:23 UTC 
It would have been pushed stable yesterday if anyone actually linked the update to the bug :(

It's very important for the update that needs to be pushed to be marked as fixing the bug that's marked as FE. The blockerbugs tool we use to generate the push requests won't show the update in the request unless this link is present.

I'll edit the update and it'll go in the next push request.
Comment 9 Fedora Update System 2022-04-29 17:44:40 UTC 
FEDORA-2022-cdc3365ffc has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-cdc3365ffc
Comment 10 Kamil Páral 2022-05-02 08:07:43 UTC 
(In reply to Adam Williamson from comment #8)
> It's very important for the update that needs to be pushed to be marked as
> fixing the bug that's marked as FE. The blockerbugs tool we use to generate
> the push requests won't show the update in the request unless this link is
> present.

Yes, but that's why I set it to VERIFIED, to make it clear for you that the bug has a verified fix ready, even if it's not linked :-)

> I'll edit the update and it'll go in the next push request.

Thank you.
Comment 11 Adam Williamson 2022-05-02 15:34:26 UTC 
kamil: unfortunately that's not how I read VERIFIED...I usually read VERIFIED as meaning "the fix is in updates-testing and has been confirmed to work", i.e. I can more or less stop worrying about that bug :|
Comment 12 Fedora Update System 2022-05-02 19:43:06 UTC 
FEDORA-2022-cdc3365ffc has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.