Hello all There is one thing I don't really understand about channels. I created a channel called "opensuse_leap_15.1" with all repositories connected to a normal openSuSE Leap 15.1 system (openSUSE-Leap-15.1-1, openSUSE-Leap-15.1-Non-Oss, openSUSE-Leap-15.1-Update, openSUSE-Leap-15.1-Update-Non-Oss). Then I created a child channel called "opensuse_leap_15.1_uyuni" with the uyuni repository (uyuni-server-stable). After all channels are synced, I create an Activation Key "openSuSE LEAP 15.1 Uyuni Server" with base channel "opensuse_leap_15.1" and Child Channel "opensuse_leap_15.1_uyuni". After that I use "Bootstrapping" to add my uyuni Server to the system list. The uyuni Server is now displayed in System overview. The connected repositories are: uyuni:/var/spacewalk # zypper lr -E Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Name | Enabled | GPG Check | Refresh ---+--------------------------------------+--------------------------+---------+-----------+-------- 12 | susemanager:opensuse_leap_15.1 | openSuSE LEAP 15.1 | Yes | ( p) Yes | Yes 13 | susemanager:opensuse_leap_15.1_uyuni | openSuSE LEAP 15.1 Uyuni | Yes | ( p) Yes | Yes Seems to be ok in my eyes - but now I've discovered an unpleasant side effect. In zypper.log I see this messages: 2020-04-25 15:01:34 <1> uyuni(31866) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_o(829)patterns-uyuni_server-2020.04-1.1.uyuni.x86_64(@System) 2020-04-25 15:01:34 <1> uyuni(31866) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_ou(1162)python3-suseRegisterInfo-4.1.1-1.1.uyuni.noarch(@System) 2020-04-25 15:01:34 <1> uyuni(31866) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_o(1254)spacewalk-backend-tools-4.1.7-1.3.uyuni.noarch(@System) 2020-04-25 15:01:34 <1> uyuni(31866) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_o(1263)spacewalk-common-4.1.3-1.1.uyuni.noarch(@System) 2020-04-25 15:01:34 <1> uyuni(31866) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_o(1270)spacewalk-postgresql-4.1.3-1.1.uyuni.noarch(@System) 2020-04-25 15:01:34 <1> uyuni(31866) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_o(1273)spacewalk-setup-4.1.4-4.1.uyuni.noarch(@System) 2020-04-25 15:01:34 <1> uyuni(31866) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_o(1287)supportutils-plugin-susemanager-4.1.2-1.1.uyuni.noarch(@System) 2020-04-25 15:01:34 <1> uyuni(31866) [zypper++] Summary.cc(readPool):144 <uninstall> I_Tu_ou(1289)suseRegisterInfo-4.1.1-1.1.uyuni.noarch(@System) 2020-04-25 15:01:34 <1> uyuni(31866) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_o(1290)susemanager-4.1.10-1.1.uyuni.x86_64(@System) 2020-04-25 15:01:34 <1> uyuni(31866) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_o(1296)susemanager-tools-4.1.10-1.1.uyuni.x86_64(@System) 2020-04-25 15:01:34 <1> uyuni(31866) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_u(1494)pattern:uyuni_server-2020.04-1.1.uyuni.x86_64(@System) 2020-04-25 15:02:12 <1> uyuni(1545) [libsolv++] PoolImpl.cc(logSat):123 allowuninstall=1, allowdowngrade=0, allownamechange=1, allowarchchange=0, allowvendorchange=0 2020-04-25 15:02:12 <1> uyuni(1545) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_ou(764)mgr-push-4.1.1-1.1.uyuni.noarch(@System) 2020-04-25 15:02:12 <1> uyuni(1545) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_ou(1103)python3-mgr-push-4.1.1-1.1.uyuni.noarch(@System) 2020-04-25 15:02:12 <1> uyuni(1545) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_ou(1159)python3-spacewalk-certs-tools-4.1.7-1.1.uyuni.noarch(@System) 2020-04-25 15:02:12 <1> uyuni(1545) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_o(1160)python3-spacewalk-client-tools-4.1.5-1.1.uyuni.noarch(@System) 2020-04-25 15:02:12 <1> uyuni(1545) [zypper++] Summary.cc(readPool):144 <uninstall> I_Ts_ou(1258)spacewalk-certs-tools-4.1.7-1.1.uyuni.noarch(@System) 2020-04-25 15:02:12 <1> uyuni(1545) [zypper++] Summary.cc(readPool):144 <uninstall> I_Tu_o(1259)spacewalk-client-tools-4.1.5-1.1.uyuni.noarch(@System) And in yes the uyuni_server was uninstalled: yuni:/var/spacewalk # zypper in patterns-uyuni_server Loading repository data... Reading installed packages... Resolving package dependencies... The following 16 NEW packages are going to be installed: mgr-push patterns-uyuni_server python3-mgr-push python3-spacewalk-certs-tools python3-spacewalk-client-tools python3-suseRegisterInfo spacewalk-backend-tools spacewalk-certs-tools spacewalk-client-tools spacewalk-common spacewalk-postgresql spacewalk-setup supportutils-plugin-susemanager suseRegisterInfo susemanager susemanager-tools The following NEW pattern is going to be installed: uyuni_server 16 new packages to install. Overall download size: 1.2 MiB. Already cached: 0 B. After the operation, additional 4.7 MiB will be used. Continue? [y/n/v/...? shows all options] (y): n I can reinstall the pattern, but the rpm's will be uninstalled again later. Did I miss something - or is it not possible to add the Uyuni server to the system itself? Best regards, Martin -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org