Well, it’s a definite improvement. I’ve rolled that into the template customization scripts and I can now see more than 1 system registered. Thank you.

I’m now seeing a different problem.

W: Failed to fetch https://myuniserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-main-security-uyuni/InRelease  Undetermined Error [IP: AA.BB.CC.DD 443]

If I try to go to that URL from a browser, I get

You need a token to access /manager/download/ubuntu-2004-amd64-main-security-uyuni/repodata/InRelease

The only reference I’ve found in google for that appears to be in Spanish and CentOS related on a capa9.net forum.

 

From: Pau Garcia <pau.garcia@suse.com>
Sent: Tuesday, January 26, 2021 1:18 AM
To: Paul-Andre Panon <paul-andre.panon@avigilon.com>; users@lists.uyuni-project.org
Subject: Re: Registration problems with Ubuntu 20.04 and Uyuni

 

Hello

 

Have you checked this?

 

https://www.uyuni-project.org/uyuni-docs/uyuni/administration/tshoot-registerclones.html

If you are using Uyuni to manage virtual machines, you might find it useful to create clones of your VMs. A clone is a VM that uses a primary disk that is an exact copy of an existing disk.

 

 

 

Thank you

 

Pau Garcia Quiles

SUSE Manager Product Owner & Technical Project Manager

SUSE Software Solutions Spain

 

 


From: Paul-Andre Panon <paul-andre.panon@avigilon.com>
Sent: Tuesday, January 26, 2021 8:30 AM
To: users@lists.uyuni-project.org <users@lists.uyuni-project.org>
Subject: Registration problems with Ubuntu 20.04 and Uyuni

 

Hi,

 

I’m trying to set up an Uyuni server to replace a Spacewalk server, starting with setting up support for Ubuntu 20.04. Ideally we would like to be able to use a vSphere VM template that we can use to generate/clone new VMs, and then run a script on that new VM to customize it with the specific desired hostname, AD domain registration, and Uyuni registration. For the Uyuni registration, I started with the generated bootstrap script and customized it with an Activation Key and the Ubuntu GPG keys (ubuntu-gpg-pubkey-871920D1991BC93C.key,uyuni-gpg-pubkey-0d20833e.key) .

 

The registration script appears to work. If I look in Uyuni’s Salt->Keys page, I see the key, can approve it and the system shows up in the system list…. the first time.
On subsequent VMs however, I see the key in the Salt->Keys page, can approve them, and then after some time I only see one of the two VMs in the system list, usually the last one added.

 

While setting up the Uyuni server and VM template, it took me a while to figure out I was supposed to use the modified bootstrap script, so I had first tried to install salt packages on the template and thought that might be the problem. I took a hint from the bootstrap script and tried to run
  apt-get purge salt-minion

  apt-get purge salt-common

  rm -rf /etc/salt/minion.d/
on the template to clear any salt state, cleared systems and keys on the Uyuni server, and started over creating new VMs,… with the same result.

Any suggestions on what could be going wrong?

 

Thanks,

Paul-Andre Panon, B.Sc.

Senior Systems Administrator

Video Security & Analytics

 

o: +1.604.629.5182 ext 2190

m: +1.604.787.4547

 

 

For more information on how and why we collect your personal information, please visit our Privacy Policy.


For more information on how and why we collect your personal information, please visit our Privacy Policy.