Hi Am Dienstag, 29. Dezember 2020, 21:44:57 CET schrieb Stefan Bluhm:
- The setup routine does not complete successfully. [...] Ahhh, check spacewalk-java.spec. There is an %if which should do the trick. I think it just check for "is_opensuse".
This is where I need some direction on. I am running SUSE Manager which is looking for js scripts that do not exist. That explains the empty dash board or the empty login page.
I rebuild spacewalk-java.spec with the "is_opensuse" logic and re-installed spacewalk-java-*.rpm. I also took the Uyuni Master spacewalk-java-libs.rpm directly and re-installed it. The interface did not jump to Uyuni. Any hint what needs to be replaced (quick and dirty... And yes, I did restart Tomcat and mgr-setup)? It should only be the rhn.jar, right?
Ideally, I would like to avoid rebuilding my current dev system from scratch until I have the changes recorded. (too many dirty workarounds everywhere atm).
It would be great to send you all a screenshot of Uyuni on a C8 box before the end of the year :)
In the end it is just a configuration thingy. uyuni-master-srv:/usr/share/rhn/config-defaults # grep -i uyuni * rhn.conf:product_name = Uyuni rhn_java.conf:java.product_tree_tag = Uyuni rhn_web.conf:web.theme_default = uyuni The first one where we set "product_name" is mostly used in the UI and code when we want to diffentiate between SUSE Manager and Uyuni. The second one is important for product syncing in case you have SCC access but no SUSE Manager Subscription. The last one is only the default theme . Best wishes Michael