On martes, 27 de agosto de 2019 21:10:38 (CEST) Strahil Nikolov wrote:
On August 27, 2019 8:16:26 PM GMT+03:00, Steve Moring <smoring@dgsllc.biz> wrote:
Spoke a bit too soon. Re-created bootstrap repo (even with -f) but still receiving errors on some items and there are no enabled repo's.
Going to try to attach the zypper.log here.
error: curl error: 22: The requested URL returned error: 404 404, temp file size 0 bytes.
Exception.cc(log):166 MediaCurl.cc(evaluateCurlCode):1146 THROW: File '/media.1/media' not found on medium 'https://uyuni.exa mple.com/pub/repositories/opensuse/15/1/bootstrap'
Any thoughts?
-Steve
On Tue, 2019-08-27 at 11:07 -0400, Steve Moring wrote:
Indeed, this did resolve the problem for me also.
Thank you.
On Tue, 2019-08-27 at 09:26 +0200, Silvio Moioli wrote:
On 8/26/19 8:33 PM, Steve Moring wrote:
So, how will this be handled?
[sending in behalf of Julio]
This is not the definitive fix, but...
Could you please backup /usr/lib/python3.6/site- packages/spacewalk/server/importlib/packageImport.py
And then apply the diff from: https://gist.github.com/juliogonzalez/fc0cc3c78fc6ba6b3a61dceb48b1 c5 f1
i.e.: curl https://gist.githubusercontent.com/juliogonzalez/fc0cc3 c7 8fc6ba6b3a61dceb48b1c5f1/raw/87eb1764a3a8fab542f05751cc8dd699795d1 ce 0/gistfile1.txt|patch -d/ -p0
Restart services: spacewalk-service restart
And finally retry the reposync.
This is part of https://github.com/uyuni-project/uyuni/pull/1315
NOTE: I was on holidays when this was develop, and the developer that did the fix is on holidays now, but he tested so it should work for you as well.
Worst case, you can just rollback /usr/lib/python3.6/site- packages/spacewalk/server/importlib/packageImport.py
HTH
Regards, -- Silvio Moioli SUSE Manager Development Team
I've got the latest version of packageImport.py from git and it synced all packages, but creating the bootstrap repo looks strange:
uyuni:/var/log/rhn/reposync # mgr-create-bootstrap-repo 1. openSUSE-Leap-15.1-x86_64 Enter a number of a product label: 1 Creating bootstrap repo for openSUSE-Leap-15.1-x86_64
copy 'libgudev-1_0-0-232-lp151.2.3.x86_64' copy 'libnewt0_52-0.52.20-lp151.6.4.x86_64' copy 'libslang2-2.3.1a-lp151.4.3.x86_64' copy 'newt-0.52.20-lp151.6.4.x86_64' copy 'python3-asn1crypto-0.24.0-lp151.2.3.noarch' copy 'python3-cffi-1.11.2-lp151.4.3.x86_64' copy 'python3-cryptography-2.1.4-lp151.4.2.x86_64' copy 'python-dmidecode-3.12.2-lp150.4.6.x86_64' copy 'python-dmidecode-3.12.2-lp150.4.6.x86_64' copy 'python3-dmidecode-3.12.2-lp150.4.6.x86_64' copy 'python3-dmidecode-3.12.2-lp150.4.6.x86_64' copy 'python3-idna-2.6-lp151.2.2.noarch' copy 'python3-libxml2-python-2.9.7-lp151.5.3.1.i586' copy 'python3-libxml2-python-2.9.7-lp151.5.3.1.x86_64' copy 'python3-netifaces-0.10.6-lp151.2.4.x86_64' copy 'python3-newt-0.52.20-lp151.6.4.x86_64' copy 'python3-pyasn1-0.4.2-lp151.2.2.noarch' copy 'python3-pycparser-2.17-lp151.2.1.noarch' copy 'python3-pyOpenSSL-17.5.0-lp151.3.3.noarch' copy 'python3-pyudev-0.21.0-lp151.4.2.noarch' copy 'python3-rpm-4.14.1-lp151.13.10.x86_64' copy 'python3-packaging-16.8-lp151.2.1.noarch' copy 'python3-setuptools-40.5.0-lp151.1.1.noarch' copy 'python3-appdirs-1.4.3-lp151.2.1.noarch' copy 'python3-pyparsing-2.2.0-lp151.2.1.noarch' copy 'hwdata-0.320-lp151.1.1.noarch' copy 'python3-hwdata-2.3.5-lp150.2.1.noarch' copy 'python3-hwdata-2.3.5-lp150.2.1.noarch' copy 'python3-rhnlib-4.0.8-lp150.4.1.noarch' copy 'spacewalk-check-4.0.9-lp150.3.1.noarch' copy 'spacewalk-client-setup-4.0.9-lp150.3.1.noarch' copy 'spacewalk-client-tools-4.0.9-lp150.3.1.noarch' copy 'python3-spacewalk-check-4.0.9-lp150.3.1.noarch' copy 'python3-spacewalk-client-setup-4.0.9-lp150.3.1.noarch' copy 'python3-spacewalk-client-tools-4.0.9-lp150.3.1.noarch' copy 'python3-spacewalk-usix-4.0.9-lp150.3.1.noarch' copy 'python3-spacewalk-usix-4.0.9-lp150.3.1.noarch' copy 'mgr-daemon-4.0.6-lp150.2.1.noarch' copy 'mgr-daemon-4.0.6-lp150.2.1.noarch' copy 'suseRegisterInfo-4.0.4-lp150.2.1.noarch' copy 'suseRegisterInfo-4.0.4-lp150.2.1.noarch' copy 'python3-suseRegisterInfo-4.0.4-lp150.2.1.noarch' copy 'python3-suseRegisterInfo-4.0.4-lp150.2.1.noarch' copy 'zypp-plugin-spacewalk-1.0.5-lp150.3.1.noarch' copy 'zypp-plugin-spacewalk-1.0.5-lp150.3.1.noarch' copy 'python3-zypp-plugin-0.6.3-lp151.2.1.noarch' copy 'python3-zypp-plugin-spacewalk-1.0.5-lp150.3.1.noarch' copy 'python3-zypp-plugin-spacewalk-1.0.5-lp150.3.1.noarch' copy 'libpgm-5_2-0-5.2.122-lp151.3.3.x86_64' copy 'libsodium23-1.0.16-lp151.4.3.x86_64' copy 'libzmq5-4.2.3-lp151.5.3.1.x86_64' copy 'python3-Babel-2.5.1-lp151.2.2.noarch' copy 'python3-certifi-2018.1.18-lp151.2.2.noarch' copy 'python3-chardet-3.0.4-lp151.3.2.noarch' copy 'python3-Jinja2-2.10.1-lp151.1.1.noarch' copy 'python3-MarkupSafe-1.0-lp151.2.5.x86_64' copy 'python3-msgpack-0.5.6-lp151.1.1.x86_64' copy 'python3-psutil-5.4.8-lp151.1.1.x86_64' copy 'python3-py-1.5.2-lp151.2.2.noarch' copy 'python3-pycrypto-2.6.1-lp151.2.4.x86_64' copy 'python3-pytz-2018.5-lp151.1.1.noarch' copy 'python3-PyYAML-3.13-lp151.1.1.x86_64' copy 'python3-pyzmq-17.0.0-lp151.2.3.x86_64' copy 'python3-requests-2.20.1-lp151.2.3.1.noarch' copy 'python3-simplejson-3.13.2-lp151.2.4.x86_64' copy 'python3-six-1.11.0-lp151.3.1.noarch' copy 'python3-tornado-4.5.3-lp151.2.4.x86_64' copy 'python3-urllib3-1.24-lp151.1.3.noarch' copy 'timezone-2019b-lp151.2.3.1.i586' copy 'timezone-2019b-lp151.2.3.1.x86_64' copy 'salt-2019.2.0-lp151.5.3.1.x86_64' copy 'python3-salt-2019.2.0-lp151.5.3.1.x86_64' copy 'salt-minion-2019.2.0-lp151.5.3.1.x86_64' copy 'dmidecode-3.2-lp151.3.1.x86_64' copy 'libunwind-1.2.1-lp151.3.3.x86_64' Directory walk started Directory walk done - 66 packages Temporary output repo path: /srv/www/htdocs/pub/repositories/opensuse/15/1/bootstrap/.repodata/ Preparing sqlite DBs Pool started (with 5 workers) Pool finished
Do you think it is related to the issue ? Based on the output , it looks harmless .
I guess you mean that it's strange there are some packages mentioned two times, such as:
copy 'python3-spacewalk-usix-4.0.9-lp150.3.1.noarch' copy 'python3-spacewalk-usix-4.0.9-lp150.3.1.noarch'
Right? I think it's harmless, but still it would be good to understand why it is happening. Can you try to run with -d and attach the output as a txt file, or paste it to https://paste.opensuse.org/ ?
Best Regards, Strahil Nikolov
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com