Bugzilla – Bug 1211970
Product appears as registered when de-registered
Last modified: 2023-07-14 15:54:41 UTC
Created attachment 867382 [details] scc log ## Observation Looks pretty similar to https://bugzilla.suse.com/show_bug.cgi?id=1119512. System appears as still registered and returns error code after running "SUSEConnect --de-register" on sle 15 sp3 with the following products activated sle-module-development-tools sle-module-desktop-applications sle-module-server-applications sle-module-basesystem However,if we run SUSEConnect --cleanup, then it appears as de-registered after all. See openqa run here (if still available) https://openqa.suse.de/tests/11229121#step/scc_deregistration/21 Note, it appears as maintenance product, but the test uses normal repos.
On the server side I can see that the system also activated the products [0] "Development Tools Module 15 SP3 s390x", [1] "Desktop Applications Module 15 SP3 s390x", [2] "Basesystem Module 15 SP3 s390x", [3] "SUSE Linux Enterprise Server 15 SP3 s390x" but it seems they're not seen as activated on the client side, that why de-register fails with: Error: Registration server returned 'Cannot deactivate the product "Basesystem Module". Other activated products depend upon it.' (422) Can you also share the logs of the initial registration? My suspicion is that the -release.rpm packages of those products did not install correctly.
(In reply to Thomas Schmidt from comment #1) > On the server side I can see that the system also activated the products > > [0] "Development Tools Module 15 SP3 s390x", > [1] "Desktop Applications Module 15 SP3 s390x", > [2] "Basesystem Module 15 SP3 s390x", > [3] "SUSE Linux Enterprise Server 15 SP3 s390x" > > but it seems they're not seen as activated on the client side, that why > de-register fails with: > > Error: Registration server returned 'Cannot deactivate the product > "Basesystem Module". Other activated products depend upon it.' (422) > > Can you also share the logs of the initial registration? My suspicion is > that the -release.rpm packages of those products did not install correctly. Hi, it looks like it's indeed because of this, as in bsc#1202234. I don't have the logs of registration, but if I explicitely add the -release file in the autoyast profile, then this does not happen.
Can we close this as a duplicate then?
Closing as duplicate. *** This bug has been marked as a duplicate of bug 1202234 ***