Did anyone succeed in virt-install'ing F24 beta using kickstart
(on CentOS 6 host, if that matters)?
I see lots of warnings (dracut-initqueue), then the console goes
into a slowly filling bar at the bottom (plymouthd!?), then I see
lots of "No space left on device" errors, then a dracut emergency
shell is started.
The generated rdsosreport.txt contains 34284 lines...
FWIW, when *not* using kickstart I can install F24 beta on the
same system with virt-install fine.
-- Jos Vos <jos(a)xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204
Per https://fedorahosted.org/fedora-qa/ticket/471 and
https://bugzilla.redhat.com/show_bug.cgi?id=1221920 , it seems we no
longer want to require release notes to be present on all media. For
simplicity's sake, I suggest we simply remove the media section of the
We could I suppose require that media include some kind of pointer to
the release notes, but this seems difficult in the case of e.g. cloud
Anyone have comments, alternative proposals? Thanks!
For the record, the criterion is https://fedoraproject.org/wiki/Fedora_
"The final branded release notes must be present on release-blocking
images and the appropriately versioned generic release notes must be
available in the release repository."
I propose amending it to:
"The final branded and generic release notes must be present in the
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
Sumantro and me were working upon the possibility of shifting QA
tickets to some other platform like pagure. Thanks Justin(jflory7) for
Following are the points:-
1. Shifting to Pagure will be easy and efficient.
2. Wiki -----> overview
2. In the Pagure repo, priorities can be set for tickets based on
ranking, e.g. 10=urgent,20=high,30=normal, etc.(we can have custom
3. Milestones----> Pagure milestones(has been improved)
*All the ticket with the tag roadmap will show up on the roadmap page.
*For each milestones defined in the settings of the project, the
roadmap will group tickets with the corresponding tag.
*Tickets with the tag roadmap that are not associated with any of the
milestones defined in the settings are group in an unplanned section.
5. All of the fields in both ticket type and ticket component are
likely best implemented in tags for tickets. That would allow for the
categorization and grouping of the tickets based on their keywords.
6. The blocked by and blocking feature is available in Pagure as metadata.
7. All other things can be easily implemented using tags.
8. As discussed in the last meeting, https://pagure.io/pagure-importer
can be used to import tickets.
I am putting this as a mail because, I wont be able to attend the meeting today.
Thanks and Regards
currently this problem seems to be only mine.
PC: Acer Laptop, 2 years old, Aspire E15 E5-571G
Installation of F25 Beta workstation EFI mode on a Sandisk Ultra USB 3.0 32GB flash medium ok (as it was for F22 - F24)
Installation on an Sandisk Ultra 65GB -- Dracut Error, as I have tested now, the same error occurs for F22 to F25
Installation in legacy mode on 32Gb and 65GB for F24 and F25 ok.
Now I had a live Chat with Acer Support (Acer says always we make Windows PCs, linux is not our beer),
but in the Chat today I got:
"Grundsätzlich ist nur zu beachten, dass Legacy bei derInstallation von Linux aktiviert ist und nach der Installation jenach Linux Version auf UEFI umgestellt wird."
I try to translate: Legacy is in the installing process of Linux activated. And will be repositioned depending on the Linux version to UEFI.
"Es gibt Linux Version, die lassen sich nur im Legacy installieren,nach der Installation hat Linux aber grafische Fehler, weswegen manauf UEFI umstellen muss. Das hat an sich mit der Treiberanbindung zutun."
Translation: There are Linux versions, which can only be installed in Legacy mode, after installation Linux has grafical errors, therefore it has to transferred to UEFI. The reason is driver connection.
So far what I got from Acer.
Therefore this problem seems to be at least partly in the interworking of Acer Bios (EFI) and F25 ?Anaconda?
So far that's all what I currently know about.
Is it possible to transfer a Lecacy installation to EFI? In the Acer language by "changing", adding or patching drivers?
I would just like to kindly ask someone to check if my account (zdenek) works correctly on bodhi. Even if I added some karma these days, my bodhi profile page still says "Last bodhi-related activity: 2 years ago".
Maybe this "last activity" is not related to karma activity but to some other. But if someone could confirm, I would appreciate.
Last but not least, does badge appraisal works properly please? I just realized I'm behind 20 karma evaluations but badge for 20 karma didn't arrive.
Thanks a lot for your feedback in advance.
Missing expected images:
Cloud_base qcow2 x86_64
Server boot x86_64
Atomic qcow2 x86_64
Server dvd i386
Server dvd x86_64
Cloud_base raw-xz x86_64
Server boot i386
Atomic raw-xz x86_64
Failed openQA tests: 1/2 (arm)
Old failures (same test failed in 25-20161030.n.0):
ID: 45129 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload
Passed openQA tests: 22/22 (x86_64), 2/2 (i386)
New passes (same test did not pass in 25-20161030.n.0):
ID: 45117 Test: x86_64 KDE-live-iso desktop_update_graphical
Skipped openQA tests: 1 of 26
Mail generated by check-compose:
I'm running F25 inside a wayland session, and for curiosity i tried to
restart gnome-shell with Alt+F2 / r.
This is rejected by a popup "Restart is not available on Wayland".
Fedora release 25 (Twenty Five)
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>