[uyuni-users] Channel subscription after registering
Hello, we are on a process to migrate our old spacewalk installation to uyuni or foreman. At the moment we are evaluating uyuni against foreman/katello. Till now a lot of things are working fine, but I found one thing, I don't understand. I configured all Centos 7 and Centos 8 channels and they are updated daily, this part is working fine. Now I want to subscribe a Centos test system. I do so by editing a salt config file in this way: master: <our uyuni server name> server_id_use_src: adler32 enable_legacy_startup_events: False enable_fqdns_grains: False grains: susemanager: activation-key: "1-centos8-x86_64" After starting salt-minion, a key is generated and I can see the key under Software => Keys. My expectation is that the server will be added by accepting the key. This works fine, but the server has no base channel and no child channels.. When I look at the activation key (1-centos8-x86_64) I see a base channel and a lot of child channels activated for this key. Why are these channels not activated after registering a new server? Thank you, Peter
Hi Peter, If I understand correctly what you are doing, you want to add channels to an already onboarded server, and you want to do it from the salt minion itself. Is that right? I don't understand what do you mean with a "key under Software => Keys". The keys are at "Systems => Activation Keys". Is that what you mean? The key is generated on the Uyuni server, not from the minion. In other words, the workflow is: 1. You add the channels for the OS you want, and sync them on the server. 2. You create an activation key on the server, and you assing the channels you want to the activation key 3. You start bootstrapping clients, from either WebUI, bootstrap scripts or API. You don't really need to touch the salt configuration on the client. I am not aware the doc says you need to manually add grains with the activation key to the client. But if it is there: can you tell me where it is? Maybe we need a fix there. On lunes, 6 de julio de 2020 11:08:42 (CEST) Huber, Peter wrote:
Hello,
we are on a process to migrate our old spacewalk installation to uyuni or foreman. At the moment we are evaluating uyuni against foreman/katello. Till now a lot of things are working fine, but I found one thing, I don't understand. I configured all Centos 7 and Centos 8 channels and they are updated daily, this part is working fine. Now I want to subscribe a Centos test system. I do so by editing a salt config file in this way:
master: <our uyuni server name>
server_id_use_src: adler32
enable_legacy_startup_events: False
enable_fqdns_grains: False
grains:
susemanager:
activation-key: "1-centos8-x86_64"
After starting salt-minion, a key is generated and I can see the key under Software => Keys. My expectation is that the server will be added by accepting the key. This works fine, but the server has no base channel and no child channels.. When I look at the activation key (1-centos8-x86_64) I see a base channel and a lot of child channels activated for this key. Why are these channels not activated after registering a new server?
Thank you, Peter
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
Hi,
sorry for confusing you. I want to onboard a client and this client should be added to a base channel and child channels automatically. With spacewalk this is done via the activation key. After registering the client to the spacewalk server via rhnreg_ks --activationkey=1-centos7-x86_64, the client has a base channel and some child channels (e.g. epel).
The client I am using for testing uyuni, is not added via bootstrap but on command line via minion, see https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/registra...
After editing /etc/salt/minion.d/NAME.conf and starting minion on the client (systemctl restart salt-minion) the is a new salt key for this client iand I can see the key under Salt => Keys.
When I accept this key, the client can be found under systems, but without any channel subscription.
-----Ursprüngliche Nachricht-----
Von: Julio González Gil
Hello,
we are on a process to migrate our old spacewalk installation to uyuni or foreman. At the moment we are evaluating uyuni against foreman/katello. Till now a lot of things are working fine, but I found one thing, I don't understand. I configured all Centos 7 and Centos 8 channels and they are updated daily, this part is working fine. Now I want to subscribe a Centos test system. I do so by editing a salt config file in this way:
master: <our uyuni server name>
server_id_use_src: adler32
enable_legacy_startup_events: False
enable_fqdns_grains: False
grains:
susemanager:
activation-key: "1-centos8-x86_64"
After starting salt-minion, a key is generated and I can see the key under Software => Keys. My expectation is that the server will be added by accepting the key. This works fine, but the server has no base channel and no child channels.. When I look at the activation key (1-centos8-x86_64) I see a base channel and a lot of child channels activated for this key. Why are these channels not activated after registering a new server?
Thank you, Peter
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
On 06/07/2020 11.54, Huber, Peter wrote:
When I accept this key, the client can be found under systems, but without any channel subscription.
With the "plain" Salt onboarding mode you can use grains to set activation keys. Edit /etc/salt/grains on the minion to be registered and add: susemanager: - management_key: "1-myactivationkeylabel" The 1-myactivationkeylabel activation key will be applied at onboarding time and any channels will be added. Lana: this seems to be something that should be in the docs but I could not really find it there. Do you need an issue opened? Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Hi Am Montag, 6. Juli 2020, 14:23:18 CEST schrieb Silvio Moioli:
On 06/07/2020 11.54, Huber, Peter wrote:
When I accept this key, the client can be found under systems, but without any channel subscription. With the "plain" Salt onboarding mode you can use grains to set activation keys. Edit /etc/salt/grains on the minion to be registered and add:
susemanager: - management_key: "1-myactivationkeylabel"
uhhh, be carefull: not "management_key" please. - activation_key: for a normal activation key. - management_key: for a re-registration key or a key generated during an autoinstallation
The 1-myactivationkeylabel activation key will be applied at onboarding time and any channels will be added.
Lana: this seems to be something that should be in the docs but I could not really find it there. Do you need an issue opened?
-- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
On 06/07/2020 14.32, Michael Calmer wrote:
uhhh, be carefull: not "management_key" please.
- activation_key:
for a normal activation key.
- management_key:
for a re-registration key or a key generated during an autoinstallation
Sorry, you are right, I got that wrong! Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Hi Am Montag, 6. Juli 2020, 11:08:42 CEST schrieb Huber, Peter:
Hello,
[...]
After starting salt-minion, a key is generated and I can see the key under Software => Keys. My expectation is that the server will be added by accepting the key. This works fine, but the server has no base channel and no child channels.. When I look at the activation key (1-centos8-x86_64) I see a base channel and a lot of child channels activated for this key. Why are these channels not activated after registering a new server?
The activation key "1-centos8-x86_64" what is set as the "Base Channel"? Ist "SUSE Manager Default" (Could also be "Uyuni Default" not sure how far we are with the branding :-) or is it the centos8-x86_64 base channel directly? In the first case the system try to find out what could be the best channel, but this may fail. So it is better to specify it directly and say what you want. If it is already the second case it could be, that you were running into a bug we had where assigning of channels from the activation key did not work as it should. This was fixed, but I am not sure if we have this already released or not. -- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
I have configured 4 activation keys
1-centos7-x86_64 (Base Channel: CentOS 7 (x86_64), Child Channels: CentOS 7 (x86_64), Uyuni Client Tools..... EPEL7...)
1-centos8-x86_64 (Base Channel: CentOS 8 (x86_64) , Child Channels: CentOS 8 (x86_64), Uyuni Client Tools..... EPEL8...)
1-opensuse_leap15_1-x86_64 (Base Channel: openSUSE Leap 15.1 (x86_64), Child Channels: OpenSUSE Leap 15.1 (x86_64), Uyuni Client Tools..)
1-oraclelinux7-x86_64 (Base Channel: Oracle Linux 7 (x86_64), Child Channels: no child channels at this time.)
None of them is configured as an "universal default channel", because I have to move existing CentOS 7 / Oracle OS 7 and CentOS 8 machines and every machine needs a different Base Channel.
As written before, on the client machine I have set the activation key:
grains:
susemanager:
activation-key: "1-centos7-x86_64"
Does this help you? Is this a bug?
Kind regards,
Peter
-----Ursprüngliche Nachricht-----
Von: Michael Calmer
Hello,
[...]
After starting salt-minion, a key is generated and I can see the key under Software => Keys. My expectation is that the server will be added by accepting the key. This works fine, but the server has no base channel and no child channels.. When I look at the activation key (1-centos8-x86_64) I see a base channel and a lot of child channels activated for this key. Why are these channels not activated after registering a new server?
The activation key "1-centos8-x86_64" what is set as the "Base Channel"? Ist "SUSE Manager Default" (Could also be "Uyuni Default" not sure how far we are with the branding :-) or is it the centos8-x86_64 base channel directly? In the first case the system try to find out what could be the best channel, but this may fail. So it is better to specify it directly and say what you want. If it is already the second case it could be, that you were running into a bug we had where assigning of channels from the activation key did not work as it should. This was fixed, but I am not sure if we have this already released or not. -- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
On 06/07/2020 15.07, Huber, Peter wrote:
grains: susemanager: activation-key: "1-centos7-x86_64"
Is this the exact content of your /etc/salt/grains file? Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
There is no /etc/salt/grains file, but a subdir called minion.d with a file <clientname>.conf, like mentioned here:
https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/registra...
The content if this file:
master: <uyuni-sever>.uni-wh.de
server_id_use_src: adler32
enable_legacy_startup_events: False
enable_fqdns_grains: False
grains:
susemanager:
activation-key: "1-centos7-x86_64"
Regards,
Peter
-----Ursprüngliche Nachricht-----
Von: Silvio Moioli
grains: susemanager: activation-key: "1-centos7-x86_64"
Is this the exact content of your /etc/salt/grains file? Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Am Montag, 6. Juli 2020, 15:37:03 CEST schrieb Huber, Peter:
There is no /etc/salt/grains file, but a subdir called minion.d with a file <clientname>.conf, like mentioned here: https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/registr ation-cli.html The content if this file:
master: <uyuni-sever>.uni-wh.de server_id_use_src: adler32 enable_legacy_startup_events: False enable_fqdns_grains: False grains: susemanager: activation-key: "1-centos7-x86_64" ^^^^^^^^^^^
Use underscore (_) not dash (-). activation_key: "1-centos7-x86_64"
Regards,
Peter
-----Ursprüngliche Nachricht----- Von: Silvio Moioli
Gesendet: Montag, 6. Juli 2020 15:19 An: uyuni-users@opensuse.org Betreff: Re: AW: [uyuni-users] Channel subscription after registering On 06/07/2020 15.07, Huber, Peter wrote:
grains:
susemanager:
activation-key: "1-centos7-x86_64"
Is this the exact content of your /etc/salt/grains file?
Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
-- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Perfect ;-) please correct your online documentation, there is no underline in the config...
https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/registra...
master: SERVER.EXAMPLE.COM
server_id_use_src: adler32
enable_legacy_startup_events: False
enable_fqdns_grains: False
grains:
susemanager:
activation-key: "
There is no /etc/salt/grains file, but a subdir called minion.d with a file <clientname>.conf, like mentioned here: https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/registr ation-cli.html The content if this file:
master: <uyuni-sever>.uni-wh.de server_id_use_src: adler32 enable_legacy_startup_events: False enable_fqdns_grains: False grains: susemanager: activation-key: "1-centos7-x86_64" ^^^^^^^^^^^
Use underscore (_) not dash (-). activation_key: "1-centos7-x86_64"
Regards,
Peter
-----Ursprüngliche Nachricht----- Von: Silvio Moioli
Gesendet: Montag, 6. Juli 2020 15:19 An: uyuni-users@opensuse.org Betreff: Re: AW: [uyuni-users] Channel subscription after registering On 06/07/2020 15.07, Huber, Peter wrote:
grains:
susemanager:
activation-key: "1-centos7-x86_64"
Is this the exact content of your /etc/salt/grains file?
Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
-- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
On 7/6/20 4:25 PM, Huber, Peter wrote:
Perfect ;-) please correct your online documentation, there is no underline in the config... https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/registra...
master: SERVER.EXAMPLE.COM server_id_use_src: adler32 enable_legacy_startup_events: False enable_fqdns_grains: False grains: susemanager: activation-key: "
" ^^^^^^^^^^^^^^ Thank you, it is working now :-)
Fix prepared here https://github.com/uyuni-project/uyuni-docs/pull/362 . It will be reflected in the online documentation once it's merged btw. Thank you for pointing that out. Feel also free to contribute if you would like to as long as you find other doc issues Thanks again :)
-----Ursprüngliche Nachricht----- Von: Michael Calmer
Gesendet: Montag, 6. Juli 2020 16:14 An: uyuni-users@opensuse.org Betreff: Re: AW: AW: [uyuni-users] Channel subscription after registering Am Montag, 6. Juli 2020, 15:37:03 CEST schrieb Huber, Peter:
There is no /etc/salt/grains file, but a subdir called minion.d with a file <clientname>.conf, like mentioned here: https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/registr ation-cli.html The content if this file:
master: <uyuni-sever>.uni-wh.de server_id_use_src: adler32 enable_legacy_startup_events: False enable_fqdns_grains: False grains: susemanager: activation-key: "1-centos7-x86_64" ^^^^^^^^^^^
Use underscore (_) not dash (-).
activation_key: "1-centos7-x86_64"
Regards,
Peter
-----Ursprüngliche Nachricht----- Von: Silvio Moioli
Gesendet: Montag, 6. Juli 2020 15:19 An: uyuni-users@opensuse.org Betreff: Re: AW: [uyuni-users] Channel subscription after registering On 06/07/2020 15.07, Huber, Peter wrote:
grains:
susemanager:
activation-key: "1-centos7-x86_64"
Is this the exact content of your /etc/salt/grains file?
Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Cheers, -- Dario Leidi SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Funny enough, I was unable to locate that part of the doc by typing "grains" on the searchbox (see attached screenshot) @doc team, is the search engine considering the boxes with "code"? On lunes, 6 de julio de 2020 16:51:01 (CEST) Dario Leidi wrote:
On 7/6/20 4:25 PM, Huber, Peter wrote:
Perfect ;-) please correct your online documentation, there is no underline in the config... https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/regis tration-cli.html
master: SERVER.EXAMPLE.COM server_id_use_src: adler32 enable_legacy_startup_events: False enable_fqdns_grains: False
grains: susemanager: activation-key: "
" ^^^^^^^^^^^^^^
Thank you, it is working now :-)
Fix prepared here https://github.com/uyuni-project/uyuni-docs/pull/362 . It will be reflected in the online documentation once it's merged btw.
Thank you for pointing that out.
Feel also free to contribute if you would like to as long as you find other doc issues
Thanks again :)
-----Ursprüngliche Nachricht----- Von: Michael Calmer
Gesendet: Montag, 6. Juli 2020 16:14 An: uyuni-users@opensuse.org Betreff: Re: AW: AW: [uyuni-users] Channel subscription after registering Am Montag, 6. Juli 2020, 15:37:03 CEST schrieb Huber, Peter:
There is no /etc/salt/grains file, but a subdir called minion.d with a file <clientname>.conf, like mentioned here: https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/regis tr ation-cli.html The content if this file:
master: <uyuni-sever>.uni-wh.de server_id_use_src: adler32 enable_legacy_startup_events: False enable_fqdns_grains: False
grains: susemanager: activation-key: "1-centos7-x86_64"
^^^^^^^^^^^
Use underscore (_) not dash (-).
activation_key: "1-centos7-x86_64"
Regards,
Peter
-----Ursprüngliche Nachricht----- Von: Silvio Moioli
Gesendet: Montag, 6. Juli 2020 15:19 An: uyuni-users@opensuse.org Betreff: Re: AW: [uyuni-users] Channel subscription after registering On 06/07/2020 15.07, Huber, Peter wrote:
grains: susemanager: activation-key: "1-centos7-x86_64"
Is this the exact content of your /etc/salt/grains file?
Regards, -- Silvio Moioli SUSE Manager Development Team
Cheers,
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
participants (5)
-
Dario Leidi
-
Huber, Peter
-
Julio González Gil
-
Michael Calmer
-
Silvio Moioli