Anaconda Error Downloading Treeinfo

com Subject: [PATCH] Errors downloading .treeinfo files should not be logged as errors. Date: Thu, 28 Oct 2010 14:05:10 -0400 At least in Fedora, there won't be a .treeinfo file at the mirror manager URL. So when we attempt to fetch the addon list, it'll look like there is a real problem when it's an expected situation. Log appropriately. --- pyanaconda/yuminstall.py | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/pyanaconda/yuminstall.py b/pyanaconda/yuminstall.py index 54afb10..4ceafcc 100644 --- a/pyanaconda/yuminstall.py +++ b/pyanaconda/yuminstall.py @@ -729,7 +729,7 @@ class AnacondaYum(YumSorter): copy_local=1, proxies=proxies) return "/tmp/.treeinfo" except Exception as e: - log.error("Error downloading %s/.treeinfo: %s" % (baseurl, e)) + log.info("Error downloading %s/.treeinfo: %s" % (baseurl, e)) return None def _getReleasever(self): -- 1.7.1.1 [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]

Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by Red Hat Cloud Computing Back Red Hat CloudForms Red Hat OpenStack Platform Red Hat Cloud Infrastructure Red Hat Cloud Suite Red Hat OpenShift Container Platform Red Hat OpenShift Online Red Hat OpenShift Dedicated Storage Back Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application Platform Red Hat JBoss Data Grid Red Hat JBoss Web Server Red Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and https://www.redhat.com/archives/anaconda-devel-list/2010-October/msg00321.html Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back Red Hat Mobile Application Platform Services Back Consulting Technical Account Management Training & Certifications Red Hat Enterprise Linux Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified https://access.redhat.com/solutions/710323 Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log Out Language Back English español Deutsch italiano 한국어 français 日本語 português 中文 (中国) русский Customer Portal Search Products & Services Back View All Products Infrastructure and Management Back Red Hat Enterprise Linux Red Hat Virtualization Red Hat Identity Management Red Hat Directory Server Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrast

Documentation EPEL Infrastructure Internationalization Localization Marketing Magazine Package Maintainers Quality Assurance Websites All projects Search Tools What links here Related changes Special pages Printable version Permanent link How to debug installation problems From FedoraProject Jump to: navigation, search Contents 1 Narrowing it Down 2 Types of Bugs 2.1 Loader Bugs 2.2 Kernel Bugs 2.3 X Bugs 2.4 Tracebacks 2.5 Hardware Errors 3 Other Potentially Useful Information 3.1 Log Files 3.2 Hardware 4 Kickstart File 4.1 Anaconda Stage 4.2 Previous Steps 4.3 Attached Devices 4.4 Encryption 4.5 Partitioning Layout 5 Writing the Report 5.1 To Form or Not to Form? 5.2 Specificity 5.3 Tone 6 What Happens Next? Narrowing it Down Before doing anything else, please try to figure out if you're testing the latest version of anaconda - this goes for all software products. If you're running into a problem in F10 while we're developing F12, a bug report will not be very helpful and the problem may even be fixed already. If you ever encounter a bug that is not in the latest anaconda, please locate the newest one and try that. To check which version of anaconda you're running, you need only watch the screen when anaconda starts up. It will print something like Greetings. anaconda installer init version 11.5.0.47 starting And that's your version of anaconda! The other useful number is the tree. If you're using an official release, all we need is which Fedora you're installing. If, on the other hand, you're using the development tree (Rawhide), there are two ways to discover which tree you're using. Often the installation source will have a date in the path, which will tell us which build to look at. If your install source does not have a date, its .treeinfo file should contain a timestamp and a version number. If you cannot remember what yo