[uyuni-users] Bootstrap repo question
Hi, I'm trying to figure out why my bootstrap repo for os150 seems to be wanting to install older rpms. Any thoughts how I should go about trouble-shooting this? The channels were sync'd by: # spacewalk-common-channels -u <myuser> -p <mypassword> -a x86_64 'opensuse_leap42_3*' # spacewalk-common-channels -u <myuser> -p <mypassword> -a x86_64 'opensuse_leap15* ..after sync's finished about 2 days later :-) The bootstrap repo's were created with: #mgr-create-bootstrap-repo -c openSUSE-Leap-15-x86_64 #mgr-create-bootstrap-repo -c openSUSE-Leap-42.3-x86_64 # mgr-create-bootstrap-repo -l 1. openSUSE-Leap-15-x86_64 2. openSUSE-Leap-42.3-x86_64 The bootstrap_os150.sh file has the key defined, that key has the os150 base channel set, and has: openSUSE 15.0 non oss (x86_64) openSUSE Leap 15.0 non oss Updates (x86_64) openSUSE Leap 15.0 Updates (x86_64) Bootstrap output... uyuni:~ # cat /srv/www/htdocs/pub/bootstrap/bootstrap_os150.sh | ssh r oot@os150test /bin/bash The authenticity of host 'os150test (192.168.5.23)' can't be established. ECDSA key fingerprint is SHA256:EELiWSn3F8JABjdagE2OuHxCDWNGZQNf7R7Fiv12o8o. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'os150test,192.168.5.23' (ECDSA) to the list of known hosts. Password: Uyuni Server Client bootstrap script v4.0 MINOR MANUAL EDITING OF THIS FILE MAY BE REQUIRED! If this bootstrap script was created during the initial installation of a Uyuni Server, the ACTIVATION_KEYS, and ORG_GPG_KEY values will probably *not* be set (see below). If this is the case, please do the following: - copy this file to a name specific to its use. (e.g., to bootstrap-SOME_NAME.sh - like bootstrap-web-servers.sh.) - on the website create an activation key or keys for the system(s) to be registered. - edit the values of the VARIABLES below (in this script) as appropriate: - ACTIVATION_KEYS needs to reflect the activation key(s) value(s) from the website. XKEY or XKEY,YKEY Please note that if you are using this script to boostrap minions, only the FIRST activation key will be used. Multiple activation keys are not supported with salt - ORG_GPG_KEY needs to be set to the name(s) of the corporate public GPG key filename(s) (residing in /srv/www/htdocs/pub) if appropriate. XKEY or XKEY,YKEY Verify that the script variable settings are correct: - CLIENT_OVERRIDES should be only set differently if a customized client-config-overrides-VER.txt file was created with a different name. - ensure the value of HOSTNAME is correct. - ensure the value of ORG_CA_CERT is correct. Enable this script: comment (with #'s) this block (or, at least just the exit below, if present) UPDATING RHN_REGISTER/UP2DATE CONFIGURATION FILES ------------------------------------------------- * downloading necessary files client_config_update.py... WARNING: cannot verify uyuni.mydomain.site's certificate, issued by ‘CN=uyuni.mydomain.site,OU=services,O=mydomain,L=Fort Wayne,ST=IN,C=US’: Unable to locally verify the issuer's authority. 2019-03-14 11:55:34 URL:https://uyuni.mydomain.site/pub/bootstrap/clie nt_config_update.py [6478/6478] -> "client_config_update.py" [1] FINISHED --2019-03-14 11:55:34-- Total wall clock time: 0.04s Downloaded: 1 files, 6.3K in 0s (167 MB/s) client-config-overrides.txt... WARNING: cannot verify uyuni.mydomain.site's certificate, issued by ‘CN=uyuni.mydomain.site,OU=services,O=mydomain,L=Fort Wayne,ST=IN,C=US’: Unable to locally verify the issuer's authority. 2019-03-14 11:55:34 URL:https://uyuni.mydomain.site/pub/bootstrap/clie nt-config-overrides.txt [641/641] -> "client-config-overrides.txt" [1] FINISHED --2019-03-14 11:55:34-- Total wall clock time: 0.04s Downloaded: 1 files, 641 in 0s (65.1 MB/s) PREPARE GPG KEYS AND CORPORATE PUBLIC CA CERT ------------------------------------------------- * no organizational GPG keys to import * attempting to install corporate public CA cert WARNING: cannot verify uyuni.mydomain.site's certificate, issued by ‘CN=uyuni.mydomain.site,OU=services,O=mydomain,L=Fort Wayne,ST=IN,C=US’: Unable to locally verify the issuer's authority. 2019-03-14 11:55:34 URL:https://uyuni.mydomain.site/pub/rhn-org-truste d-ssl-cert-1.0-1.noarch.rpm [9416/9416] -> "rhn-org-trusted-ssl-cert- 1.0-1.noarch.rpm" [1] FINISHED --2019-03-14 11:55:34-- Total wall clock time: 0.04s Downloaded: 1 files, 9.2K in 0s (101 MB/s) Preparing... ################################ ######## Updating / installing... rhn-org-trusted-ssl-cert-1.0- 1 ######################################## CLEANING UP OLD SUSE MANAGER REPOSITORIES ------------------------------------------------- CHECKING THE REGISTRATION STACK ------------------------------------------------- * check for necessary packages being installed... * client codebase is opensuse-15-sp0 package salt is not installed package salt-minion is not installed 2019-03-14 11:55:35 URL:https://uyuni.mydomain.site/pub/repositories/o pensuse/15/0/bootstrap/repodata/repomd.xml [1279/1279] -> "repomd.xml" [1] FINISHED --2019-03-14 11:55:35-- Total wall clock time: 0.04s Downloaded: 1 files, 1.2K in 0s (130 MB/s) * going to install missing packages... 2019-03-14 11:55:35 URL:https://uyuni.mydomain.site/pub/repositories/o pensuse/15/0/bootstrap/repodata/repomd.xml [1279/1279] -> "repomd.xml" [1] FINISHED --2019-03-14 11:55:35-- Total wall clock time: 0.04s Downloaded: 1 files, 1.2K in 0s (95.1 MB/s) adding client software repository at https://uyuni.mydomain.site/pub/ repositories/opensuse/15/0/bootstrap Retrieving repository 'susemanager:bootstrap' metadata [.done] Building repository 'susemanager:bootstrap' cache [....done] Specified repositories have been refreshed. Loading repository data... Reading installed packages... Resolving package dependencies... 2 Problems: Problem: nothing provides python2-salt = 2018.3.0-33.2 needed by salt- 2018.3.0-33.2.x86_64 Problem: nothing provides python2-salt = 2018.3.0-33.2 needed by salt- 2018.3.0-33.2.x86_64 Problem: nothing provides python2-salt = 2018.3.0-33.2 needed by salt- 2018.3.0-33.2.x86_64 Solution 1: do not install salt-2018.3.0-33.2.x86_64 Solution 2: break salt-2018.3.0-33.2.x86_64 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): c no package provides salt ERROR: Failed to install all missing packages. Thanks, -Steve -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
On jueves, 14 de marzo de 2019 17:23:28 (CET) Steve Moring wrote:
Hi,
I'm trying to figure out why my bootstrap repo for os150 seems to be wanting to install older rpms.
Any thoughts how I should go about trouble-shooting this?
The channels were sync'd by: # spacewalk-common-channels -u <myuser> -p <mypassword> -a x86_64 'opensuse_leap42_3*' # spacewalk-common-channels -u <myuser> -p <mypassword> -a x86_64 'opensuse_leap15*
..after sync's finished about 2 days later :-)
Syncing is not a fast operation, but two days seems to be just too much. I guess the instance is low on CPU/RAM or using magnetic disks, right? As for the problem itself, why do you think the bootstrap repo is trying to install old rpms? It seems to me that salt package is not from openSUSE. Current one at Leap 15.0 is: salt2018.3.0-lp150.3.20.1 Yours is: salt-2018.3.0-33.2 (without the "lp150). Please check at what repository and channel you have "salt-2018.3.0-33.2" (you can do that at the WebUI), and also check from where it was synced (/var/log/ rhn/reposync/*). Maybe that will provide some hints.
The bootstrap repo's were created with: #mgr-create-bootstrap-repo -c openSUSE-Leap-15-x86_64 #mgr-create-bootstrap-repo -c openSUSE-Leap-42.3-x86_64
# mgr-create-bootstrap-repo -l 1. openSUSE-Leap-15-x86_64 2. openSUSE-Leap-42.3-x86_64
The bootstrap_os150.sh file has the key defined, that key has the os150 base channel set, and has: openSUSE 15.0 non oss (x86_64) openSUSE Leap 15.0 non oss Updates (x86_64) openSUSE Leap 15.0 Updates (x86_64)
Bootstrap output...
uyuni:~ # cat /srv/www/htdocs/pub/bootstrap/bootstrap_os150.sh | ssh r oot@os150test /bin/bash The authenticity of host 'os150test (192.168.5.23)' can't be established. ECDSA key fingerprint is SHA256:EELiWSn3F8JABjdagE2OuHxCDWNGZQNf7R7Fiv12o8o. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'os150test,192.168.5.23' (ECDSA) to the list of known hosts. Password: Uyuni Server Client bootstrap script v4.0
MINOR MANUAL EDITING OF THIS FILE MAY BE REQUIRED!
If this bootstrap script was created during the initial installation of a Uyuni Server, the ACTIVATION_KEYS, and ORG_GPG_KEY values will probably *not* be set (see below). If this is the case, please do the following: - copy this file to a name specific to its use. (e.g., to bootstrap-SOME_NAME.sh - like bootstrap-web-servers.sh.) - on the website create an activation key or keys for the system(s) to be registered. - edit the values of the VARIABLES below (in this script) as appropriate: - ACTIVATION_KEYS needs to reflect the activation key(s) value(s) from the website. XKEY or XKEY,YKEY Please note that if you are using this script to boostrap minions, only the FIRST activation key will be used. Multiple activation keys are not supported with salt - ORG_GPG_KEY needs to be set to the name(s) of the corporate public GPG key filename(s) (residing in /srv/www/htdocs/pub) if appropriate. XKEY or XKEY,YKEY
Verify that the script variable settings are correct: - CLIENT_OVERRIDES should be only set differently if a customized client-config-overrides-VER.txt file was created with a different name. - ensure the value of HOSTNAME is correct. - ensure the value of ORG_CA_CERT is correct.
Enable this script: comment (with #'s) this block (or, at least just the exit below, if present)
UPDATING RHN_REGISTER/UP2DATE CONFIGURATION FILES ------------------------------------------------- * downloading necessary files client_config_update.py... WARNING: cannot verify uyuni.mydomain.site's certificate, issued by ‘CN=uyuni.mydomain.site,OU=services,O=mydomain,L=Fort Wayne,ST=IN,C=US’: Unable to locally verify the issuer's authority. 2019-03-14 11:55:34 URL:https://uyuni.mydomain.site/pub/bootstrap/clie nt_config_update.py [6478/6478] -> "client_config_update.py" [1] FINISHED --2019-03-14 11:55:34-- Total wall clock time: 0.04s Downloaded: 1 files, 6.3K in 0s (167 MB/s) client-config-overrides.txt... WARNING: cannot verify uyuni.mydomain.site's certificate, issued by ‘CN=uyuni.mydomain.site,OU=services,O=mydomain,L=Fort Wayne,ST=IN,C=US’: Unable to locally verify the issuer's authority. 2019-03-14 11:55:34 URL:https://uyuni.mydomain.site/pub/bootstrap/clie nt-config-overrides.txt [641/641] -> "client-config-overrides.txt" [1] FINISHED --2019-03-14 11:55:34-- Total wall clock time: 0.04s Downloaded: 1 files, 641 in 0s (65.1 MB/s)
PREPARE GPG KEYS AND CORPORATE PUBLIC CA CERT ------------------------------------------------- * no organizational GPG keys to import
* attempting to install corporate public CA cert WARNING: cannot verify uyuni.mydomain.site's certificate, issued by ‘CN=uyuni.mydomain.site,OU=services,O=mydomain,L=Fort Wayne,ST=IN,C=US’: Unable to locally verify the issuer's authority. 2019-03-14 11:55:34 URL:https://uyuni.mydomain.site/pub/rhn-org-truste d-ssl-cert-1.0-1.noarch.rpm [9416/9416] -> "rhn-org-trusted-ssl-cert- 1.0-1.noarch.rpm" [1] FINISHED --2019-03-14 11:55:34-- Total wall clock time: 0.04s Downloaded: 1 files, 9.2K in 0s (101 MB/s) Preparing... ################################ ######## Updating / installing... rhn-org-trusted-ssl-cert-1.0- 1 ########################################
CLEANING UP OLD SUSE MANAGER REPOSITORIES -------------------------------------------------
CHECKING THE REGISTRATION STACK ------------------------------------------------- * check for necessary packages being installed... * client codebase is opensuse-15-sp0 package salt is not installed package salt-minion is not installed 2019-03-14 11:55:35 URL:https://uyuni.mydomain.site/pub/repositories/o pensuse/15/0/bootstrap/repodata/repomd.xml [1279/1279] -> "repomd.xml" [1] FINISHED --2019-03-14 11:55:35-- Total wall clock time: 0.04s Downloaded: 1 files, 1.2K in 0s (130 MB/s) * going to install missing packages... 2019-03-14 11:55:35 URL:https://uyuni.mydomain.site/pub/repositories/o pensuse/15/0/bootstrap/repodata/repomd.xml [1279/1279] -> "repomd.xml" [1] FINISHED --2019-03-14 11:55:35-- Total wall clock time: 0.04s Downloaded: 1 files, 1.2K in 0s (95.1 MB/s) adding client software repository at https://uyuni.mydomain.site/pub/ repositories/opensuse/15/0/bootstrap Retrieving repository 'susemanager:bootstrap' metadata [.done] Building repository 'susemanager:bootstrap' cache [....done] Specified repositories have been refreshed. Loading repository data... Reading installed packages... Resolving package dependencies... 2 Problems: Problem: nothing provides python2-salt = 2018.3.0-33.2 needed by salt- 2018.3.0-33.2.x86_64 Problem: nothing provides python2-salt = 2018.3.0-33.2 needed by salt- 2018.3.0-33.2.x86_64
Problem: nothing provides python2-salt = 2018.3.0-33.2 needed by salt- 2018.3.0-33.2.x86_64 Solution 1: do not install salt-2018.3.0-33.2.x86_64 Solution 2: break salt-2018.3.0-33.2.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): c no package provides salt ERROR: Failed to install all missing packages.
Thanks, -Steve
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
Julio, On Thu, 2019-03-21 at 11:48 +0100, Julio González Gil wrote:
As for the problem itself, why do you think the bootstrap repo is trying to install old rpms?
It seems to me that salt package is not from openSUSE.
Current one at Leap 15.0 is: salt2018.3.0-lp150.3.20.1 Yours is: salt-2018.3.0-33.2 (without the "lp150).
Please check at what repository and channel you have "salt-2018.3.0- 33.2" (you can do that at the WebUI), and also check from where it was synced (/var/log/ rhn/reposync/*).
Maybe that will provide some hints.
Looking here: /pub/repositories/opensuse/15/0/bootstrap/x86_64/ It shows both in the bootstrap repo: salt-2018.3.0-33.2.x86_64.rpm 2018-12-22 16:56 137K salt-2018.3.0-lp150.3.20.1.x86_64.rpm 2019-02-21 03:39 145K In the UI, it does not show them: salt-2018.3.0-lp150.2.1.x86_64 openSUSE Leap 15.0 (x86_64) salt-2018.3.0-lp150.3.20.1.x86_64 openSUSE Leap 15.0 Updates (x86_64) salt-2018.3.0-lp150.3.17.1.x86_64 openSUSE Leap 15.0 Updates (x86_64) salt-2018.3.0-lp150.3.14.1.x86_64 openSUSE Leap 15.0 Updates (x86_64) salt-2018.3.0-lp150.3.9.1.x86_64 openSUSE Leap 15.0 Updates (x86_64) salt-2018.3.0-lp150.3.6.1.x86_64 openSUSE Leap 15.0 Updates (x86_64) Is there a way to clear the bootstrap repo and recreate it? mgr-create-bootstrap-repo -c openSUSE-Leap-15-x86_64 Doesn't seem to remove then recreate the repo. -Steve -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Julio, On Thu, 2019-03-21 at 10:40 -0400, Steve Moring wrote:
Is there a way to clear the bootstrap repo and recreate it?
Clearing the contents of: uyuni:/srv/www/htdocs/pub/repositories/opensuse/15/0/bootstrap then re-running the mgr-create-bootstrap-repo -c openSUSE-Leap-15- x86_64 Fixed it! Question now, I have no idea how this happened, perhaps I added the repo for os423 to these channels before creating the bootstrap repo, is it a problem going forward leaving older packages in the repo when rebuilding them? Will this burn someone when we rename a package? Thanks, -Steve -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
You don't really need to clear the repo. If you check mgr-create-bootstrap-repo: -f, --flush when used in conjuction with --create, deletes the target repository before creating it I am not 100% sure, but I think that without it, the repository is created, but any previous content is not removed. On jueves, 21 de marzo de 2019 15:48:48 (CET) Steve Moring wrote:
Julio,
On Thu, 2019-03-21 at 10:40 -0400, Steve Moring wrote:
Is there a way to clear the bootstrap repo and recreate it?
Clearing the contents of:
uyuni:/srv/www/htdocs/pub/repositories/opensuse/15/0/bootstrap
then re-running the mgr-create-bootstrap-repo -c openSUSE-Leap-15- x86_64
Fixed it!
Question now, I have no idea how this happened, perhaps I added the repo for os423 to these channels before creating the bootstrap repo, is it a problem going forward leaving older packages in the repo when rebuilding them? Will this burn someone when we rename a package?
Thanks, -Steve
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
Julio, On Thu, 2019-03-21 at 16:13 +0100, Julio González Gil wrote:
You don't really need to clear the repo.
If you check mgr-create-bootstrap-repo:
-f, --flush when used in conjuction with --create, deletes the target repository before creating it
I am not 100% sure, but I think that without it, the repository is created, but any previous content is not removed.
Excellent, there's no man page for mgr-create-bootstrap-repo, so how would one know how to check these options? -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
On jueves, 21 de marzo de 2019 17:02:17 (CET) Steve Moring wrote:
Julio,
On Thu, 2019-03-21 at 16:13 +0100, Julio González Gil wrote:
You don't really need to clear the repo.
If you check mgr-create-bootstrap-repo: -f, --flush when used in conjuction with --create,
deletes the
target repository before creating it
I am not 100% sure, but I think that without it, the repository is created, but any previous content is not removed.
Excellent, there's no man page for mgr-create-bootstrap-repo, so how would one know how to check these options?
"mgr-create-bootstrap-repo -h" :-) But I agree that a man page could be useful as well. Maybe you can send us a Pull Request? It should be fairly simple. The script and the spec are at: https://github.com/uyuni-project/uyuni/tree/master/susemanager -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
participants (2)
-
Julio González Gil -
Steve Moring