Description of problem: On page /rhn/channels/software/Search.do (Channels->Package Search), these errors occur, shown in catalina.out : 2017-04-04 11:51:19,307 [TP-Processor5] ERROR com.redhat.rhn.common.localization.LocalizationService - *** ERROR: Message with id: [Sparc Solaris] not found.*** called by com.redhat.rhn.frontend.action.BaseSearchAction.addOption(BaseSearchAction.java:246) 2017-04-04 11:51:19,307 [TP-Processor5] ERROR com.redhat.rhn.common.localization.LocalizationService - *** ERROR: Message with id: [Sparc Solaris] not found.*** called by com.redhat.rhn.frontend.action.BaseSearchAction.addOption(BaseSearchAction.java:246) 2017-04-04 11:51:19,307 [TP-Processor5] ERROR com.redhat.rhn.common.localization.LocalizationService - *** ERROR: Message with id: [i386 Solaris] not found.*** called by com.redhat.rhn.frontend.action.BaseSearchAction.addOption(BaseSearchAction.java:246) 2017-04-04 11:51:19,307 [TP-Processor5] ERROR com.redhat.rhn.common.localization.LocalizationService - *** ERROR: Message with id: [i386 Solaris] not found.*** called by com.redhat.rhn.frontend.action.BaseSearchAction.addOption(BaseSearchAction.java:246) Furthermore, there is Solaris architecture mentioned which is not supported anymore. How reproducible: Deterministic Steps to Reproduce: 1. Go to <sat_url>/rhn/channels/software/Search.do 2. Notice mention of Solaris in architecture options 3. See the errors in catalina.out Actual results: Errors + Solaris mentioned Expected results: No errors, no Solaris mentions
I can't recreate this on a fresh 5.8 install. That happens only if rhnPackageArch still contains the 'sparc-solaris' entry. Part of the 5.7-to-5.8 upgrade finds and removes that reference: spacewalk/upgrade/spacewalk-schema-2.5-to-spacewalk-schema-2.6/007-remove-solaris-arch.sql.postgresql:delete from rhnPackage where package_arch_id = (select id from rhnPackageArch where label = 'sparc-solaris'); Currently I don't see any way to make this happen. Lukas, can you give me some more details on the history of the system you see this on?
I tried again on current compose and indeed, I can't reproduce the bug. Maybe it got fixed somewhere on the way. I advise closing this bugzilla.
(In reply to Lukáš Hellebrandt from comment #2) > I tried again on current compose and indeed, I can't reproduce the bug. > Maybe it got fixed somewhere on the way. I advise closing this bugzilla. Sounds like a plan to me :)