Bug 623067
Summary: | Failed to install using an FTP installation resource | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | MingtaoNiu <mniu> | ||||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | low | ||||||||||
Version: | rawhide | CC: | anaconda-maint-list, awilliam, jonathan, jskala, kdudka, lili, rhe, vanmeeuwen+fedora | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | All | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2010-10-06 19:49:03 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
MingtaoNiu
2010-08-11 08:58:40 UTC
Version-Release: anaconda14.15 F14-alpha-rc3 How reproducible: 100% :1,$/s/NFS/FTP/g sorry for the mistakes... Note that ftp install only failed by running this test: https://fedoraproject.org/wiki/QA:Testcase_Additional_Ftp_Repository Repo=ftp:// and askmethod(using ftp source) work as expected. Could it have been a transient mirror error? Did you try the test more than once? Seems like it's unlikely that the *installer* would cause a repo problem... I see "Detail info is in the attachment", but there isn't an attachment :) -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers The release criterion related to this bug is: "The installer must be able to use at least one of the HTTP or FTP remote package source options " We actually meant that to be about the *main installation source* - so doing an install from boot.iso using FTP or HTTP repositories, not adding FTP or HTTP repositories to a DVD install. Doing an install that way works. Also, adding an HTTP source to a DVD install works - it has a green tick from Liam in the table. So either way you can interpret the criterion, it's satisfied. Hence this bug does not block the Alpha. (Just adding this for clarification before go/no-go meeting). -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Created attachment 438322 [details]
pic of err when installing using an FTP installation resource
This is the pic of err when installing using an FTP installation resource
Hi, could you provide logs using Ctrl+Alt_F2 then /tmp/anaconda.log, ... Thanks, Jiri Created attachment 438572 [details]
anaconda.log for FTP error
anaconda.log for FTP error
This would not happen when the repo version is the same as boot media, like all are rc4. But if boot media is rc3, but repo version is rc4, may cause this issue. But I think anaconda should read correctly, no matter what version of repo(like rc1, rc2, rc3, etc..). Interestingly, if I add a nfs or http repo in advance at the repository selection step, then the same ftp repo can be retrieved successfully. So in my case, this issue happens when I firstly add a ftp repo. HTTP links work fine. The issue is generated using FTP links. Unfortunately this issue has nothing to do with ftp package. Therefore I'm going to set needinfo flag and ask for some ideas from maintainers of curl/libcurl and yum. Oops, one of intended addresses was not saved by BZ. Right, anaconda uses libcurl as the FTP client. How can I repeat the issue with a public ftp server? 10.66.65.86 is not accessible from my network, so that I am getting the same result: $ curl -v ftp://10.66.65.86/pub/iso/repodata/repomd.xml * About to connect() to 10.66.65.86 port 21 (#0) * Trying 10.66.65.86... Connection timed out * couldn't connect to host * Closing connection #0 curl: (7) couldn't connect to host Please also attach /tmp/syslog to this bug report. It looks to me like the network simply isn't active. Created attachment 438885 [details]
file "syslog" for the err when installing using a FTP resource
I am unable to reproduce this problem locally. |