| Summary: | PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found" | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jaroslav Škarvada <jskarvad> | ||||||||||||
| Component: | redhat-upgrade-tool | Assignee: | Michal Bocek <mbocek> | ||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 6.8 | CC: | jhornice, jskarvad, mganisin, ovasik, phracek, ttomecek | ||||||||||||
| Target Milestone: | rc | Keywords: | Extras | ||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | redhat-upgrade-tool-0.7.45-1.el6 | Doc Type: | No Doc Update | ||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2016-11-04 09:02:47 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Jaroslav Škarvada
2016-02-02 15:40:43 UTC
Please attach /var/log/redhat_upgrade_tool.log. The versions of the packages in the errors are from RHEL 7.1, so it looks like something went wrong in the repo setup. Created attachment 1120486 [details]
Log
Created attachment 1121125 [details]
/usr/bin/redhat-upgrade-tool with logging fix
There's a bug in the logging in the main script. I've attached a new version of the main redhat-upgrade-tool script. Can you replace the script in /usr/bin with the attachment, run redhat-upgrade-tool again, and attach the /var/log/redhat_upgrade_tool.log from that?
The diff is just this:
diff --git a/redhat-upgrade-tool.py b/redhat-upgrade-tool.py
index 0a614ee..28caef2 100755
--- a/redhat-upgrade-tool.py
+++ b/redhat-upgrade-tool.py
@@ -46,7 +46,7 @@ from preup import xccdf
from preup import settings
import logging
-log = logging.getLogger("redhat-upgrade-tool")
+log = logging.getLogger("redhat_upgrade_tool.main")
def message(m):
print m
log.info(m)
Ups, I have just returned the machine. I will take another, but it may take some time. Created attachment 1121424 [details]
Logs
Different machine, different error:
getting boot images...
.treeinfo | 2.2 kB 00:00
setting up update...
verify local files 100% [======================================================]
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
Importing GPG key 0xFD431D51:
Userid : Red Hat, Inc. (release key 2) <security>
Package: redhat-release-server-6Server-6.7.0.3.el6.x86_64 (@anaconda-RedHatEnterpriseLinux-201507020259.x86_64/6.7)
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
Importing GPG key 0x2FA658E0:
Userid : Red Hat, Inc. (auxiliary key) <security>
Package: redhat-release-server-6Server-6.7.0.3.el6.x86_64 (@anaconda-RedHatEnterpriseLinux-201507020259.x86_64/6.7)
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
Downloading failed: Didn't install any keys
The key error is normal. redhat-upgrade-tool attempts to check gpg signatures by default, and the packages on download.devel are not signed. You can add --nogpgcheck to the command line for that. Obviously this isn't the most friendly failure mode. I think there's a bug open to ask the user whether to add the keys, like yum does, instead of just failing. Thanks, it finished OK. I will retry on another machine and will try to exactly reproduce the steps that lead to the failure. Created attachment 1121453 [details] Logs I finally reproduced the problem by using the following steps (some may be redundant): # cd /etc/yum.repos.d # wget 'http://git.app.eng.bos.redhat.com/git/preupgrade-assistant.git/plain/repo-files/preupgrade-el6.repo' # cd # yum install redhat-upgrade-tool preupgrade-assistant-contents # redhat-upgrade-tool-cli --cleanup-post --addrepo optional=http://download.devel.redhat.com/released/RHEL-7/7.0/Server-optional/x86_64/os/ --instrepo=http://download.devel.redhat.com/released/RHEL-7/7.0/Server/x86_64/os --network 7.0 # preupg --force -s RHEL6_7 # redhat-upgrade-tool-cli --cleanup-post --addrepo optional=http://download.devel.redhat.com/released/RHEL-7/7.0/Server-optional/x86_64/os/ --instrepo=http://download.devel.redhat.com/released/RHEL-7/7.0/Server/x86_64/os --network 7.0 # redhat-upgrade-tool-cli --cleanup-post --addrepo optional=http://download.devel.redhat.com/released/RHEL-7/7.0/Server-optional/x86_64/os/ --instrepo=http://download.devel.redhat.com/released/RHEL-7/7.2/Server/x86_64/os --network 7.2 # redhat-upgrade-tool-cli --cleanup-post --addrepo optional=http://download.devel.redhat.com/released/RHEL-7/7.2/Server-optional/x86_64/os/ --instrepo=http://download.devel.redhat.com/released/RHEL-7/7.2/Server/x86_64/os --network 7.2 I think the last two steps are important. The cache/workdir is probably not cleared. I see. The quick fix is don't do that ;-) I'll add a check for whether there is an existing upgrade directory and print a message about it needing to be cleaned before another upgrade can be run. Fix prepared: https://github.com/upgrades-migrations/redhat-upgrade-tool/commit/d3968611e3b81bdc53e83d472bea813880898b53 This is a minor bug so it will be added to a next version of the tool. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-2619.html |