| Summary: | lorax / livemedia-creator / anaconda : iso creation fails with 'No protocol specified' error message | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | xvr <smith93_28> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 25 | CC: | anaconda-maint-list, bcl, g.kaviyarasu, jdieter, jonathan, mkolman, smith93_28, vanmeeuwen+fedora, vponcova | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-12-12 10:41:57 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
xvr
2016-12-13 07:37:30 UTC
No protocol specified' - 'Unable to init server: cannot connect : connection refused is from python-meh (IIRC) the actual error should be logged in the ./anaconda/*log files someplace. There are/were 2 issues: 1. My internet connection was much, much too slow, and this confused anaconda... This issue is now corrected. 2. I can now create a live image with the following kickstart file (I keep only the %package section, as the problem seems to arise in that section - it's a bit rough, but my only concern for now is getting livemedia-creator to work): %packages @anaconda-tools @base-x @core @dial-up @firefox @fonts @guest-desktop-agents @hardware-support # @kde-apps # @kde-desktop # @kde-media # @kde-office # @kde-telepathy @multimedia @networkmanager-submodules @printing @standard aajohan-comfortaa-fonts anaconda dracut-live fuse glibc-all-langpacks grub2-efi # k3b # kde-l10n # kdegames-minimal kernel kernel-modules kernel-modules-extra mariadb-embedded mariadb-libs mariadb-server #mediawriter memtest86+ # qupzilla syslinux system-config-language wqy-microhei-fonts #-@input-methods #-adobe-source-han-sans-cn-fonts #-adobe-source-han-sans-tw-fonts #-autofs #-coolkey #-desktop-backgrounds-basic #-digikam #-gnome-disk-utility #-hplip #-ibus* #-iok #-isdn4k-utils #-kdeaccessibility* #-kdegames #-kipi-plugins #-m17n* #-make #-mpage #-naver-nanum-gothic-fonts #-numactl #-paratype-pt-sans-fonts #-sane-backends #-scim* #-sox #-system-config-printer #-system-config-services #-system-config-users #-vlgothic-fonts #-wget #-xsane #-xsane-gimp xterm twm %end The next kickstart file (again the %packages section) does not work : %packages @anaconda-tools @base-x @core @dial-up @firefox @fonts @guest-desktop-agents @hardware-support @kde-apps @kde-desktop @kde-media @kde-office @kde-telepathy @multimedia @networkmanager-submodules @printing @standard aajohan-comfortaa-fonts anaconda dracut-live fuse glibc-all-langpacks grub2-efi k3b kde-l10n kdegames-minimal kernel kernel-modules kernel-modules-extra mariadb-embedded mariadb-libs mariadb-server mediawriter memtest86+ qupzilla syslinux system-config-language wqy-microhei-fonts -@input-methods -adobe-source-han-sans-cn-fonts -adobe-source-han-sans-tw-fonts -autofs -coolkey -desktop-backgrounds-basic -digikam -gnome-disk-utility -hplip -ibus* -iok -isdn4k-utils -kdeaccessibility* -kdegames -kipi-plugins -m17n* -make -mpage -naver-nanum-gothic-fonts -numactl -paratype-pt-sans-fonts -sane-backends -scim* -sox -system-config-printer -system-config-services -system-config-users -vlgothic-fonts -wget -xsane -xsane-gimp %end Please note that the only real difference with the working .ks file is the presence of the @kde... group specifications. I'm struggling with that problem. Maybe I missed something ? Are you seeing the same error, or a new one? Packaging problems are either anaconda, dnf, or repository issues so attaching (not pasting) the logs as individual text/plain attachments would help. Created attachment 1231865 [details]
anaconda error log (software selection error)
I ran into this same bug when trying to create a gold install image for our school. I downgraded device-mapper and lvm2 to the following, and that fixed it: device-mapper x86_64 1.02.131-3.fc25 fedora device-mapper-event x86_64 1.02.131-3.fc25 fedora device-mapper-event-libs x86_64 1.02.131-3.fc25 fedora device-mapper-libs x86_64 1.02.131-3.fc25 fedora lvm2 x86_64 2.02.161-3.fc25 fedora lvm2-libs x86_64 2.02.161-3.fc25 fedora This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |