Error when adding Leap 15.4 and 15.5: child channel names already in use
Hi all, I successfully added the openSUSE Leap 15.5 base channel and child channels to my Uyuni server last week. Today I wanted to add 15.4 in addition, which left out two child channels:
WARNING: opensuse_leap15_4-x86_64-backports-updates: redstone.xmlrpc.XmlRpcFault: The channel name 'Update repository of openSUSE Backports (x86_64)' is already in use, please enter a different name WARNING: opensuse_leap15_4-x86_64-sle-updates: redstone.xmlrpc.XmlRpcFault: The channel name 'Update repository with updates from SUSE Linux Enterprise 15 (x86_64)' is already in use, please enter a different name
The command I used was from the docs: spacewalk-common-channels -a x86_64 opensuse_leap15_4 \ opensuse_leap15_4-uyuni-client \ opensuse_leap15_4-updates \ opensuse_leap15_4-non-oss \ opensuse_leap15_4-non-oss-updates \ opensuse_leap15_4-backports-updates \ opensuse_leap15_4-sle-updates How to solve this? 1. Can I influence the "internal" naming those channels get? The child channels names I gave on the command line included 15_4 or 15_5, but this does not seem to be reflected in the "internal" name (wherever that comes from). 2. Can I add the existing child channels (from 15.5 to the 15.4 base channel? Not sure if this is a good idea, as those are service pack (or Leap minor version dependent) IIRC. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
El jueves, 6 de abril de 2023 10:30:45 (CEST) Johannes Kastl escribió:
Hi all,
I successfully added the openSUSE Leap 15.5 base channel and child channels to my Uyuni server last week.
Today I wanted to add 15.4 in addition, which left out two child channels:
WARNING: opensuse_leap15_4-x86_64-backports-updates: redstone.xmlrpc.XmlRpcFault: The channel name 'Update repository of openSUSE Backports (x86_64)' is already in use, please enter a different name WARNING: opensuse_leap15_4-x86_64-sle-updates: redstone.xmlrpc.XmlRpcFault: The channel name 'Update repository with updates from SUSE Linux Enterprise 15 (x86_64)' is already in use, please enter a different name
Looks to me we'll need to adjust the naming at spacewalk-common-channels.ini I just created a PR for this: https://github.com/uyuni-project/uyuni/pull/6830, but I'd appreciate if you can run a couple of tests for me.
The command I used was from the docs: spacewalk-common-channels -a x86_64 opensuse_leap15_4 \ opensuse_leap15_4-uyuni-client \ opensuse_leap15_4-updates \ opensuse_leap15_4-non-oss \ opensuse_leap15_4-non-oss-updates \ opensuse_leap15_4-backports-updates \ opensuse_leap15_4-sle-updates
How to solve this?
1. Can I influence the "internal" naming those channels get? The child channels names I gave on the command line included 15_4 or 15_5, but this does not seem to be reflected in the "internal" name (wherever that comes from).
You can adjust the naming at https://<server_hostname>/rhn/channels/manage/Manage.do For opensuse_leap15_5-x86_64-backports-updates the current name should be now: Update repository of openSUSE Backports (x86_64) Change it to: Update repository of openSUSE Leap 15.5 Backports (x86_64) For opensuse_leap15_5-x86_64-sle-updates the current name should be now: Update repository with updates from SUSE Linux Enterprise 15 (x86_64) Change it to: Update repository with updates from SUSE Linux Enterprise 15 for openSUSE Leap 15.5 (x86_64) Then finally, get `spacewalk-common-channels.ini from my PR by running this on your Uyuni Server: curl https://raw.githubusercontent.com/uyuni-project/uyuni/33bdfae201f20c967d9599... -o /etc/rhn/spacewalk-common-channels.ini Then, finally, try to add the Leap 15.4 channels again, and please report the result.
2. Can I add the existing child channels (from 15.5 to the 15.4 base channel? Not sure if this is a good idea, as those are service pack (or Leap minor version dependent) IIRC.
Do not. The content of the channels is different.
Kind Regards, Johannes
-- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de
B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
Hi Julio, On 11.04.23 at 10:14 Julio Gonzalez via Uyuni Users wrote:
Looks to me we'll need to adjust the naming at spacewalk-common-channels.ini
I just created a PR for this: https://github.com/uyuni-project/uyuni/pull/6830, but I'd appreciate if you can run a couple of tests for me.
Sure.
You can adjust the naming at https://<server_hostname>/rhn/channels/manage/Manage.do
For opensuse_leap15_5-x86_64-backports-updates the current name should be now: Update repository of openSUSE Backports (x86_64) Change it to: Update repository of openSUSE Leap 15.5 Backports (x86_64)
Done.
For opensuse_leap15_5-x86_64-sle-updates the current name should be now: Update repository with updates from SUSE Linux Enterprise 15 (x86_64) Change it to: Update repository with updates from SUSE Linux Enterprise 15 for openSUSE Leap 15.5 (x86_64)
Done.
Then finally, get `spacewalk-common-channels.ini from my PR by running this on your Uyuni Server:
curl https://raw.githubusercontent.com/uyuni-project/uyuni/33bdfae201f20c967d9599... -o /etc/rhn/spacewalk-common-channels.ini
Done, sha256sum of the file was 90a4544b3ba1aa3f32f658e2990978360bf971bea5c614d251c33b75127d7678
Then, finally, try to add the Leap 15.4 channels again, and please report the result.
I got errors for the channels that were already existing, but the two "problematic channels" were added properly:
# spacewalk-common-channels -a x86_64 opensuse_leap15_4 opensuse_leap15_4-uyuni-client opensuse_leap15_4-updates opensuse_leap15_4-non-oss opensuse_leap15_4-non-oss-updates opensuse_leap15_4-backports-updates opensuse_leap15_4-sle-updates [...] INFO: opensuse_leap15_4-x86_64 exists WARNING: opensuse_leap15_4-uyuni-client-x86_64: redstone.xmlrpc.XmlRpcFault: The channel name 'Uyuni Client Tools for openSUSE Leap 15.4 (x86_64)' is already in use, please enter a different name WARNING: opensuse_leap15_4-x86_64-non-oss: redstone.xmlrpc.XmlRpcFault: The channel name 'openSUSE 15.4 non oss (x86_64)' is already in use, please enter a different name WARNING: opensuse_leap15_4-x86_64-non-oss-updates: redstone.xmlrpc.XmlRpcFault: The channel name 'openSUSE Leap 15.4 non oss Updates (x86_64)' is already in use, please enter a different name WARNING: opensuse_leap15_4-x86_64-updates: redstone.xmlrpc.XmlRpcFault: The channel name 'openSUSE Leap 15.4 Updates (x86_64)' is already in use, please enter a different name
Channel names for the newly created channels: Update repository of openSUSE Leap 15.4 Backports (x86_64) Update repository with updates from SUSE Linux Enterprise 15 for openSUSE Leap 15.4 (x86_64)
2. Can I add the existing child channels (from 15.5 to the 15.4 base channel? Not sure if this is a good idea, as those are service pack (or Leap minor version dependent) IIRC.
Do not. The content of the channels is different.
Thanks for the confirmation. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
El viernes, 14 de abril de 2023 12:16:17 (CEST) Johannes Kastl escribió:
On 11.04.23 at 10:14 Julio Gonzalez via Uyuni Users wrote:
Then finally, get `spacewalk-common-channels.ini from my PR by running this on your Uyuni Server:
curl https://raw.githubusercontent.com/uyuni-project/uyuni/33bdfae201f20c967d9 5995fb52eb663e28affb5/utils/spacewalk-common-channels.ini -o /etc/rhn/spacewalk-common-channels.ini
Done, sha256sum of the file was 90a4544b3ba1aa3f32f658e2990978360bf971bea5c614d251c33b75127d7678
Right, that's because in the end we merged the PR without waiting more, and the rebase changed the hash. Sorry about it :-)
Then, finally, try to add the Leap 15.4 channels again, and please report the result.
I got errors for the channels that were already existing, but the two "problematic channels" were added properly:
Good! :-)
Channel names for the newly created channels:
Update repository of openSUSE Leap 15.4 Backports (x86_64) Update repository with updates from SUSE Linux Enterprise 15 for openSUSE Leap 15.4 (x86_64)
Yeah, looks good. Thanks a lot for the report and the tests. The fix will be part of 2023.04 :-)
2. Can I add the existing child channels (from 15.5 to the 15.4 base channel? Not sure if this is a good idea, as those are service pack (or Leap minor version dependent) IIRC.
Do not. The content of the channels is different.
Thanks for the confirmation.
Kind Regards, Johannes
-- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de
B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
participants (2)
-
Johannes Kastl -
Julio Gonzalez