Alpha TC1 status
Hi, folks. Just to let everyone know - it didn't seem worth requesting a TC1 today. bcl and I have been building test images all day and have a decent handle on the current status. bcl's latest test boot.iso: https://alt.fedoraproject.org/pub/alt/anaconda/anaconda-19.12-1.boot.iso boots, and you can get through install config, but it gets stuck at the start of actual installation: https://bugzilla.redhat.com/show_bug.cgi?id=923459 we're looking into that. I've been building live images; the latest status is that I can get images that boot and can be installed, but gnome-initial-setup is busted on the installed system. If you work around that, you get something that more or less works. dgilmore was pretty tired so I thought not to bother him with a TC1 build; instead we'll do the blocker review meeting tomorrow AM, see if we can't fix the netinst bug, maybe get GNOME 3.7.92 in, and then probably fire TC1 tomorrow either way. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Gnome 3.8 Test Day
Tomorrow is the GNOME 3.8 Test Day. Unfortunately none of the recent nightly live images has succeeded to build. Also i tried to install F19 with the netboot image and using as source the https://dl.fedoraproject.org/pub/fedora/linux/development/19/x86_64/os/ . Nor this worked. I had problem with the infamous GRUB2 apostrophe bug. A lot of people who want to participate, ask me where they can find an image to install so they can participate to the test day. Is any other way to get a working F19 install image? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Gnome 3.8 Test Day
On Wed, 2013-03-20 at 10:50 +0200, Vasilis Keramidas wrote: Tomorrow is the GNOME 3.8 Test Day. Unfortunately none of the recent nightly live images has succeeded to build. Also i tried to install F19 with the netboot image and using as source the https://dl.fedoraproject.org/pub/fedora/linux/development/19/x86_64/os/ . Nor this worked. I had problem with the infamous GRUB2 apostrophe bug. A lot of people who want to participate, ask me where they can find an image to install so they can participate to the test day. Is any other way to get a working F19 install image? Don't worry, we'll have one by tomorrow. For now, try the one mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=923501#c2 , when it finishes uploading; it mostly works, but you have to nerf gnome-initial-setup from a console. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fedup network download
On 03/19/2013 05:30 PM, Michael Cronenworth wrote: Which component should I file the bug against? Fedup? Bug created: https://bugzilla.redhat.com/show_bug.cgi?id=923807 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Test Day kickstart update
Hello, I and Lukas Brabec have worked on our Test Day kickstart: * Lukas has created a welcome screen (based on LiveCD welcome screen) which should make super-easy to participate in the test day. It opens up the wiki page and the IRC chat in a browser. Behold: http://i.imgur.com/4ePuB1w.png * I have tried to strip all unimportant packages to make the image as small as possible. The reasoning is that bandwidth is important for many people and we should keep just the most important stuff in the kickstart. If the Test Day host team needs additional packages, they will simply adjust the kickstart and add what they need, overriding the defaults. Currently we are at 680 MB (the default LiveCD is now at 1.2 GB). * I have changed some system defaults to a more reliable state, namely disabled firewall and set SELinux into permissive mode. My thinking is that we should keep most obstacles away to let people test the stuff they are asked to test. The firewall sometimes makes the life harder and the cause is hard to discover (why my ssh doesn't work?). The SELinux, if in permissive mode, still reports issues and the user can easily file them into bugzilla, but doesn't prevent the programs from functioning. It's easier to ask users to report any SELinux popups than to instruct them how to turn it off if the program behaves weirdly. Again, Test Day maintainers can override this if they see fit. * I have removed Anaconda. Partly to save space, but not just because of it. Because the image is heavily modified (half of the packages are missing, some system defaults are changed), I don't think this is a good candidate for installation. I think TCs/RCs serve this purpose much better, they are the default offering. Of course Test Day maintainers can add Anaconda back, if they want, but I don't think we should have it there by default. The new kickstart is temporarily stored here: http://git.fedorahosted.org/cgit/fedora-qa.git/tree/?h=testday And a sample Test Day image is here: http://kparal.fedorapeople.org/testdays/testday-f19-sample.iso sha256sum: 82d0791e00cd3fc3d4c96d5af43853ef7618079fb9db72cd05f9c0f5af01f6b9 Before I request committing it to spin-kickstarts, I'd like to ask if you have some concerns or suggestions about the new kickstart. Do you think some of the system changes are not appropriate? Do you think that some of the packages I removed should stay? Or some more packages should be removed? Tell me. Once this is done, I'll update our wiki guide: https://fedoraproject.org/wiki/QA/Test_Days/Live_Image Thanks. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Test Day kickstart update
On Wed, 2013-03-20 at 13:48 -0400, Kamil Paral wrote: Hello, I and Lukas Brabec have worked on our Test Day kickstart: * Lukas has created a welcome screen (based on LiveCD welcome screen) which should make super-easy to participate in the test day. It opens up the wiki page and the IRC chat in a browser. Behold: http://i.imgur.com/4ePuB1w.png * I have tried to strip all unimportant packages to make the image as small as possible. The reasoning is that bandwidth is important for many people and we should keep just the most important stuff in the kickstart. If the Test Day host team needs additional packages, they will simply adjust the kickstart and add what they need, overriding the defaults. Currently we are at 680 MB (the default LiveCD is now at 1.2 GB). * I have changed some system defaults to a more reliable state, namely disabled firewall and set SELinux into permissive mode. My thinking is that we should keep most obstacles away to let people test the stuff they are asked to test. The firewall sometimes makes the life harder and the cause is hard to discover (why my ssh doesn't work?). The SELinux, if in permissive mode, still reports issues and the user can easily file them into bugzilla, but doesn't prevent the programs from functioning. It's easier to ask users to report any SELinux popups than to instruct them how to turn it off if the program behaves weirdly. Again, Test Day maintainers can override this if they see fit. * I have removed Anaconda. Partly to save space, but not just because of it. Because the image is heavily modified (half of the packages are missing, some system defaults are changed), I don't think this is a good candidate for installation. I think TCs/RCs serve this purpose much better, they are the default offering. Of course Test Day maintainers can add Anaconda back, if they want, but I don't think we should have it there by default. The new kickstart is temporarily stored here: http://git.fedorahosted.org/cgit/fedora-qa.git/tree/?h=testday And a sample Test Day image is here: http://kparal.fedorapeople.org/testdays/testday-f19-sample.iso sha256sum: 82d0791e00cd3fc3d4c96d5af43853ef7618079fb9db72cd05f9c0f5af01f6b9 Before I request committing it to spin-kickstarts, I'd like to ask if you have some concerns or suggestions about the new kickstart. Do you think some of the system changes are not appropriate? Do you think that some of the packages I removed should stay? Or some more packages should be removed? Tell me. Once this is done, I'll update our wiki guide: https://fedoraproject.org/wiki/QA/Test_Days/Live_Image Thanks for this! It's worth noting I haven't used the kickstart for many images lately, as it was so crufty - a lot of the stuff in there just doesn't work, as it was designed for GNOME 2. Did you look at / fix any of that? It's my experience that SELinux doesn't necessarily give you all the denials in enforcing=0 that you get in enforcing=1, but I don't care hugely either way, as it can be toggled either way easily enough. Still, if we're going to make test day images with two of our major security features disabled, we should communicate this very clearly on Test Day pages. A note on the size - current F19 images are significantly larger than expected, I think due to a) debugging code and b) some apparent bugs in dependency resolution during live image creation. They should not be coming in as huge as they are. So your Test Day image will likely be rather smaller, once those bugs get squished. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F19 Alpha Blocker Bug Review #2 Minutes
= #fedora-blocker-review: f19alpha-blocker-review-2 = Minutes: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-20/f19alpha-blocker-review-2.2013-03-20-16.00.html Minutes (text): http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-20/f19alpha-blocker-review-2.2013-03-20-16.00.txt Log: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-20/f19alpha-blocker-review-2.2013-03-20-16.00.log.html Meeting summary --- * Roll Call (tflink, 16:00:13) * Introduction (tflink, 16:06:52) * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (tflink, 16:07:47) * LINK: http://qa.fedoraproject.org/blockerbugs/current (tflink, 16:08:18) * LINK: https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria (tflink, 16:08:36) * 11 Proposed Blockers (tflink, 16:08:59) * 1 Accepted Blockers (tflink, 16:08:59) * 2 Proposed Freeze Exceptions (tflink, 16:08:59) * 1 Accepted Freeze Exceptions (tflink, 16:08:59) * (922988) virtio modules (and possibly others?) missing from installed system's initramfs after a Fedora 19 live (pre-Alpha TC1) install (tflink, 16:10:34) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922988 (tflink, 16:10:37) * Proposed Blocker, anaconda, NEW (tflink, 16:10:40) * AGREED: 922988 - We're not 100% clear on the impact of this bug. Once we have more data on its impact, we can make a decision WRT its impact (tflink, 16:22:33) * (923459) F19 pre-Alpha TC1 network installs stop at Starting package installation process (anaconda is stuck in a loop between writev and recvfrom) (tflink, 16:23:56) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=923459 (tflink, 16:23:59) * Proposed Blocker, anaconda, NEW (tflink, 16:24:02) * AGREED: 923459 - AcceptedBlocker - Violates the following F19 alpha release criteria for network sources When using the dedicated installer images, the installer must be able to use either HTTP or FTP repositories (or both) as package sources. (tflink, 16:27:42) * (922991) dracut hook pre-pivot runs before mount hook (tflink, 16:27:54) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922991 (tflink, 16:27:54) * Proposed Blocker, dracut, MODIFIED (tflink, 16:27:54) * AGREED: 922991 - AcceptedBlocker - Violates the following F19 alpha release criterion: The installer must be able to download and use an installer update image from an HTTP server. (tflink, 16:31:41) * (921896) Single quote in f19 release name breaks grub2, probably other stuff (tflink, 16:32:04) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=921896 (tflink, 16:32:07) * Proposed Blocker, fedora-release, NEW (tflink, 16:32:09) * AGREED: 921896 - AcceptedBlocker - Violates the following F19 alpha release criteria as soon as the kernel is updated post-install After firstboot is completed and on subsequent boots, a graphical install must boot to a log in screen where it is possible to log in to a working desktop as the user created during firstboot. (tflink, 16:38:42) * (919374) /var/run not created with var_run_t leading to many boot avc's (tflink, 16:39:19) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=919374 (tflink, 16:39:22) * Proposed Blocker, filesystem, ASSIGNED (tflink, 16:39:25) * AGREED: 919374 - While this sounds like it could be a blocker, we want to wait until it has been reproduced by at least one other person before accepting it as a blocker for F19 alpha (tflink, 16:45:50) * (923501) gnome-initial-setup is not visible on first boot after install (tflink, 16:46:18) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=923501 (tflink, 16:46:21) * Proposed Blocker, gdm, NEW (tflink, 16:46:23) * the criteria need to be updated to cover both firstboot and gnome-initial-experience (tflink, 16:53:08) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922951 covers the other fail. (adamw, 16:53:55) * AGREED: 923501 - AcceptedBlocker - Violates the following F19 alpha release criterion (substituting gnome-initial-experience for firstboot) A system installed with a graphical package set must boot to the 'firstboot' utility on the first boot after installation. (tflink, 16:56:51) * (922951) gnome-initial-setup is enabled by default (and presently crashes) (tflink, 16:57:23) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922951 (tflink, 16:57:26) * Proposed Blocker, gnome-initial-setup, NEW (tflink, 16:57:28) * AGREED: 922951 - While this seems as it it would be a blocker, we suspect that it has been fixed. If it isn't fixed already, will revisit at the next meeting (tflink, 17:03:55) * (922885) make sure gnome-initial-setup.service doesn't start on LiveCD (tflink, 17:04:14) *
Password not entered by the enter key on rawhide
I just noticed that on my rawhide test machine, when I go to enter in my password on either the login screen or the lock screen, i cannot just press the enter key when i'm done. I have to press the blue login button with my mouse. is anyone else seeing this issue? cheers, ryanlerch -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Password not entered by the enter key on rawhide
On Wed, 2013-03-20 at 16:28 -0400, Ryan Lerch wrote: I just noticed that on my rawhide test machine, when I go to enter in my password on either the login screen or the lock screen, i cannot just press the enter key when i'm done. I have to press the blue login button with my mouse. is anyone else seeing this issue? It's already fixed in very current F19/Rawhide packages. It was broken for the last week or two indeed. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F19 abrt report uploader confusion
I download this: https://alt.fedoraproject.org/pub/alt/anaconda/anaconda-19.12-1.boot.iso Short version: How do I submit crashes using the bug reporter? It doesn't work at all like F18. Some of the screens look the same as F18, most do not. The UI is so tragically hideous I'm, for the moment, assuming it's incomplete. The main thing I want to know is if it should function, and if so how. Superfluous, ignorable, long version of my experience: 1. I get an anaconda crash. 2. Unknown error has occurred dialog; click on Report Bug button. 2. Upload the problem data to a server (?) button, I click that and it says the wrong settings are detected, if I click on Configure Reporter uploader it wants a URL. 3. Back to 1, Report Bug. This time click on Preferences button, I see three workflows and two events. Report to Fedora and Bugzilla are two such options, both have bugzilla configuration dialogs. Confusing. Filling out either one, there is no way forward, only close buttons all of which take me back to dialog 1 with the Report Bug button. And then the whole UI froze on me. Attempt 2, I'm able to get to the bug submission window, totally inadvertently, but the processing failed and the log shows: No processing for event 'report_Uploader' is defined. *shrug* Chris Murphy-- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 abrt report uploader confusion
On Wed, 2013-03-20 at 14:47 -0600, Chris Murphy wrote: I download this: https://alt.fedoraproject.org/pub/alt/anaconda/anaconda-19.12-1.boot.iso Short version: How do I submit crashes using the bug reporter? It doesn't work at all like F18. Some of the screens look the same as F18, most do not. The UI is so tragically hideous I'm, for the moment, assuming it's incomplete. The main thing I want to know is if it should function, and if so how. Superfluous, ignorable, long version of my experience: 1. I get an anaconda crash. 2. Unknown error has occurred dialog; click on Report Bug button. 2. Upload the problem data to a server (?) button, I click that and it says the wrong settings are detected, if I click on Configure Reporter uploader it wants a URL. 3. Back to 1, Report Bug. This time click on Preferences button, I see three workflows and two events. Report to Fedora and Bugzilla are two such options, both have bugzilla configuration dialogs. Confusing. Filling out either one, there is no way forward, only close buttons all of which take me back to dialog 1 with the Report Bug button. And then the whole UI froze on me. Attempt 2, I'm able to get to the bug submission window, totally inadvertently, but the processing failed and the log shows: No processing for event 'report_Uploader' is defined. It may have too old a libreport. I don't think anyone's looked at this much, as we have a showstopper that everyone's hitting that we need to fix; we're not really poking the rest of the install UI much right now. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 abrt report uploader confusion
On Mar 20, 2013, at 3:07 PM, Adam Williamson awill...@redhat.com wrote: It may have too old a libreport. If it's from Feb 7, possibly. Current one was built yesterday. Same for abrt. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Fedora QA] #344: Fedora 19 i18n Test Day
#344: Fedora 19 i18n Test Day ---+--- Reporter: aalam | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 19 Component: Test Day |Version: Resolution:| Keywords: Blocked By:| Blocking: ---+--- Changes (by tagoh): * cc: test@… (added) Comment: Can we propose renaming the page to Test_Day:2013-05-02_Internationalization instead of Localization_(i18n) ? because that name gives us confusion. -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/344#comment:3 Fedora QA http://fedorahosted.org/fedora-qa Fedora Quality Assurance -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Test Day kickstart update
On Wed, 2013-03-20 at 13:48 -0400, Kamil Paral wrote: Hello, I and Lukas Brabec have worked on our Test Day kickstart: Oh, one more thing - you might want to base off of the fedora-live-desktop.ks rather than fedora-livecd-desktop.ks , as I don't think anyone really cares about maintaining fedora-livecd-desktop.ks any more. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Fedora QA] #344: Fedora 19 i18n Test Day
#344: Fedora 19 i18n Test Day ---+--- Reporter: aalam | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 19 Component: Test Day |Version: Resolution:| Keywords: Blocked By:| Blocking: ---+--- Comment (by anipeter): Replying to [comment:3 tagoh]: Can we propose renaming the page to Test_Day:2013-05-02_Internationalization instead of Localization_(i18n) ? because that name gives us confusion. I too agree. Its better to rename to i18n. Thanks Ani -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/344#comment:4 Fedora QA http://fedorahosted.org/fedora-qa Fedora Quality Assurance -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
