Bug 1619419
| Summary: | mock fails when creating custom iso | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | donatom <donatom.martino> | ||||
| Component: | mock | Assignee: | Miroslav Suchý <msuchy> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 28 | CC: | Jasper.Hartline, jdisnard, jkeating, mebrown, msimacek, msuchy, praiskup, williams | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-05-28 22:14:32 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: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Two days ago I used livemedia-creator outside of mock (in a qemu VM). No errors were thrown and livemedia-creator produced a customized live fedora iso. For the past two years mock has been problematic, having several different bugs. Perhaps this is still a bug in livemedia-creator though like building under SELinux enforcing used to be problematic. Perhaps this is still a bug in livemedia-creator though like building under SELinux enforcing used to be problematic. I tried building an ISO in mock chroot and it failed also. It said somen spokes were not met Software Selection in my ks config file. Jasper, as I said above, livemedia-creator seems to be working fine. As far as missing spokes, you are probably adding programs that no longer exist in the repos or there is a typo in one or more of the programs you are adding. It could also be that you are missing a repo or one or more of your repos are not valid (test them by pasting them in Firefox to see if you can reach the repo). This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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. This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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. |
Created attachment 1477365 [details] Final output of mock terminal, starting from right before traceback Description of problem: I have tried 4 times recently to create a custom iso; each time livemedia-creator (in mock) downloads the programs, installs them and tries to create the iso, but each time an error arises and the process stops Version-Release number of selected component (if applicable): mock 1.4.13 How reproducible: happens every time Steps to Reproduce: 1.I enter mock 2.I start livemedia-creator 3.Livemedia-creator successfully completes steps but at the very end of the process it throws and error ( '--show', '/var/tmp/lmc-work-l6d73rlq/images/efiboot.img']' returned non-zero exit status 1.) Actual results: mock fails Expected results: mock creates the custom iso Additional info: I am now going to run the process (livemedia-creator) without using mock (I intend to run livemedia-creator directly -- in a qemu VM which is what I had to do last year due to another mock bug).