| Latest revision |
Your text |
| Line 24: |
Line 24: |
|
| |
|
| * '''The extra wallpapers included by default with Fedora 36''' - these also did not make the meta media. There is a set of 12 installed-by-default but not set as default wallpapers that will ship with Fedora 36. 6 of these are abstract wallpapers provided by GNOME upstream, and 6 are Fedora community submitted photographic wallpapers. All of this set of 12 wallpapers supports the new dark mode in Fedora Workstation / GNOME. we'd also like folks to test these backgrounds and note their monitor(s) and resolution(s) and desktop environments(s) to ensure it looks acceptable. | | * '''The extra wallpapers included by default with Fedora 36''' - these also did not make the meta media. There is a set of 12 installed-by-default but not set as default wallpapers that will ship with Fedora 36. 6 of these are abstract wallpapers provided by GNOME upstream, and 6 are Fedora community submitted photographic wallpapers. All of this set of 12 wallpapers supports the new dark mode in Fedora Workstation / GNOME. we'd also like folks to test these backgrounds and note their monitor(s) and resolution(s) and desktop environments(s) to ensure it looks acceptable. |
| | | [[File:F36_extra_wallpapers.png]] |
| [[File:F36 photographic wallpapers.png]] | |
| [[File:F36 abstract backgrounds.png]]
| |
|
| |
|
| == Who's available == | | == Who's available == |
| Line 37: |
Line 35: |
|
| |
|
| You can chat with us on the Fedora Design channel on fedora.im https://matrix.to/#/#design:fedoraproject.org. See the infobox on top of the page to learn the right IRC channel. | | You can chat with us on the Fedora Design channel on fedora.im https://matrix.to/#/#design:fedoraproject.org. See the infobox on top of the page to learn the right IRC channel. |
|
| |
| [[User:duffy|Máirín Duffy]] (mizmo) and [[User:madelinepeck|Madeline Peck]] (madelinepeck) will have live office hours from 1700-1800 UTC (1-2 PM US Eastern Time) during this test day in the Fedora Design Matrix channel accessible via this link https://matrix.to/#/#design:fedoraproject.org or via the IRC link at the top of this page.
| |
|
| |
|
| == Prerequisite for Test Day == | | == Prerequisite for Test Day == |
|
| |
|
| * A virtual machine or a bare metal machine | | * A virtual machine or a bare metal machine |
| * An installation of a recent Fedora 36 Nightly (any Edition or Spin). Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest [https://openqa.fedoraproject.org/nightlies.html nightly image]. The nightly images *should* have all of the updated wallpapers in needed of testing by the test day - the March 28, 2022 nightly was tested and did indeed have them. | | * An installation of Fedora 35 (any Edition or Spin). Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest [https://www.happyassassin.net/nightlies.html nightly image]. The nightly images *should* have all of the updated wallpapers in needed of testing by the test day. |
|
| |
|
| == How to test? == | | == How to test? == |
|
| |
|
| This isn't too intensive a test process. We need your help trying out these wallpapers using your desktop environment of choice with your monitor / resolution to simply make sure they look OK. For those using GNOME, we'd like you to test both the light and dark modes of the wallpapers.
| | <!-- |
| | High level details on how a contributor can get involved. This can include (but not limited to): |
| | * Areas to target with exploratory testing |
| | * Areas to put special focus on |
| | * Links to documentation, if relevant |
| | * How to report the results |
| | Example: https://fedoraproject.org/wiki/Test_Day:2020-02-20_Gnome_3.36_Test_Day#How_to_test.3F |
|
| |
|
| Please note your monitor resolution and the desktop environment you are testing the wallpapers under.
| | If not using the TestDays app, provide a list of test areas or test cases that you'd like contributors to execute. For examples, see https://fedoraproject.org/wiki/Category:Test_Cases . If possible, always include https://fedoraproject.org/wiki/QA:Testcase_Exploratory_Testing among test cases. If using the TestDays app, link the test cases in it. |
| | --> |
|
| |
|
| Log your results on our event's page on the test days app: '''https://testdays.fedoraproject.org/events/130'''
| | Visit the '''[http://testdays.fedorainfracloud.org/events/NUMBER results page]''' and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test. |
|
| |
|
| Things to look for depending on the wallpaper you're viewing:
| | Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases. |
| | |
| === The default Fedora 36 background ===
| |
| | |
| [[File:F36 default wallpaper.png]]
| |
| | |
| * The "fedora" text logo in the lower right corner (under GNOME) should be visible and readable.
| |
| * Users of the GNOME desktop should be able to enable "dark mode" and "light mode" on this wallpaper and test both versions.
| |
| * When set as the active wallpaper, the wallpaper should not hurt your eyes or be overly distracting as you engage with the desktop.
| |
| | |
| | |
| | |
| === The extra wallpapers included by default with Fedora 36 ===
| |
| | |
| [[File:F36 photographic wallpapers.png]]
| |
| [[File:F36 abstract backgrounds.png]]
| |
| | |
| * Users of the GNOME desktop should be able to enable "dark mode" and "light mode" each of these 12 wallpapers and test both versions.
| |
| * When set as the active wallpaper, the wallpaper should not hurt your eyes or be overly distracting as you engage with the desktop.
| |
| | |
| Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases. If anything stands out to you as something that appears wrong or broken about the wallpapers, please report it. | |
|
| |
|
| == Reporting bugs == | | == Reporting bugs == |
|
| |
|
| === Bugs with the Default Wallpaper ===
| | <!-- |
| [[File:F36 default wallpaper.png]]
| | If there are multiple places where to report bugs (e.g. general GNOME bugs go into upstream GNOME GitLab, and only packaging issues or non-GNOME bugs go to Red Hat Bugzilla), mention it and advise users where to file which issues. |
| Bugs related to the default wallpaper should be reported into '''[https://bugzilla.redhat.com Bugzilla]''', in most cases against the <code>f36-backgrounds</code> component.
| | --> |
| | |
| === Bugs with the Fedora 6 photographic extra backgrounds ===
| |
| [[File:F36 photographic wallpapers.png]]
| |
| Bugs related to the photographic extra wallpapers should be reported into '''[https://bugzilla.redhat.com Bugzilla]''', in most cases against the <code>fedora-workstation-backgrounds</code> component.
| |
| | |
| === Bugs with the GNOME 6 abstract extra backgrounds ===
| |
| [[File:F36 abstract backgrounds.png]]
| |
| Bugs related to the abstract extra wallpapers should be reported into '''[https://bugzilla.redhat.com Bugzilla]''', in most cases against the <code>gnome-backgrounds</code> component.
| |
|
| |
|
| If you are unsure about exactly how to file the report or what other information to include, just ask us on IRC / Matrix (see instructions above). | | All bugs should be reported into '''[https://bugzilla.redhat.com Bugzilla]''', in most cases against the <code>FIXME</code> component. If you are unsure about exactly how to file the report or what other information to include, just ask us on IRC (see instructions above). |
|
| |
|
| == Test Results == | | == Test Results == |
| Line 95: |
Line 70: |
| Test results will be exported here once the test day is over. See [[#How_to_test?|How to test?]] section for information how to submit results and see the live results. | | Test results will be exported here once the test day is over. See [[#How_to_test?|How to test?]] section for information how to submit results and see the live results. |
|
| |
|
| === Notes ===
| | <!-- |
| | | If you're not using TestDays app for submitting test results, and want to let users input results directly into wiki, here's an example results table: |
| For some reason I can't load these into the test days app right now so -
| | {| |
| | |
| * https://bugzilla.redhat.com/show_bug.cgi?id=2069451 - Bug 2069451 - No logo on default background in dark mode
| |
| * https://bugzilla.redhat.com/show_bug.cgi?id=2066878 - Bug 2066878 - awaita is incorrectly set as default background in XML for fedora
| |
| | |
| | |
| === Installation ===
| |
| {| class="wikitable" width=100%
| |
| ! User
| |
| ! Profile
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_virtual_install Virtual install]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_baremetal_install Bare Metal install] | |
| ! References
| |
| |-
| |
| | [[User:Daniels|Daniels]]
| |
| | QEMU - KVM (fedora-coreos-36.20220410.1.1-live.x86_64.iso) Host: Gnome 41.5 Intel® Pentium(R) CPU 4415U @ 2.30GHz × 4 Lenovo 2in1 14
| |
| | {{result|pass}}<ref>ssh ((port (core@localhost) access denied to 127.0.0.1:2222. coreos 410))
| |
| Earlier versions of Coreos : 2022313.325. 327: Virtual Install. (No Pass)
| |
| librvirt test Installs (OS: fedora-coreos-next, not recognized ) Smooth testing otherwise.
| |
| </ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:Nemric|Nemric]]
| |
| | PXE installation
| |
| |
| |
| | {{result|pass}}<ref>Configured swap on Zram with default settings</ref>{{result|pass}}<ref>Running : 1) docker.io/grafana/promtail:latest instance 2) quay.io/prometheus/node-exporter:latest instance 3) docker.io/library/registry:latest and docker.io/library/redis:latest in a pod </ref>
| |
| | <references/>
| |
| |-
| |
| | [[User:andilinux|andilinux]]
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| | <references/>
| |
| |-
| |
| | [[User:andilinux|andilinux]]
| |
| | GNOME BOXES
| |
| | {{result|pass}}<ref>Fedora CoreOS next
| |
| all worked fine for me</ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:bittin|bittin]]
| |
| | FCOS next image
| |
| |
| |
| | {{result|pass}}
| |
| | <references/>
| |
| |-
| |
| | [[User:bittin|bittin]]
| |
| | FCOS next image in Virtualbox
| |
| | {{result|pass}}{{result|fail}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:checking|checking]]
| |
| | FCOS next image
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:danniel|danniel]]
| |
| | FCOS next image
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:donaldsebleung|donaldsebleung]]
| |
| | FCOS next image with QEMU; arch: x86_64; custom Ignition file with password-based SSH access; launching with QEMU
| |
| | {{result|warn}}<ref>Can confirm that IP address of VM is printed in FCOS stable but not FCOS next, using identical configuration. Does not seem to affect usability of system though</ref>{{result|pass}}<ref>Using ignition file: https://github.com/DonaldKellett/fcos-test-day-cloud-launch/blob/main/fcos-test-day.ign ; following documentation "launching with QEMU": https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-qemu/ ; did not see IP address of VM printed to console possibly because password-based SSH was configured instead of SSH key(s) ; both local and SSH password login worked as expected, did not find any system issues</ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:dustymabe|dustymabe]]
| |
| | Installed FCOS `next` on Intel NUC
| |
| |
| |
| | {{result|pass}}
| |
| | <references/>
| |
| |-
| |
| | [[User:ersen|ersen]]
| |
| | virt-manager
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:geraldosimiao|geraldosimiao]]
| |
| | FCOS next image
| |
| | {{result|pass}}<ref>tested qemu qcow and iso image too</ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:kisk|kisk]]
| |
| | fedora-coreos-36.20220325.1.0-qemu.x86_64.qcow2.xz - libvirt
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:lnie|lnie]]
| |
| | fcos next image,x86_64,VM created by testcloud
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:lruzicka|lruzicka]]
| |
| | QEMU
| |
| | {{result|pass}}<ref>I was able to install using the approach described in https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-qemu/, however the approach described here https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-libvirt/ did not work and the command was complaining about no permission to read the ignition file which was the same (with same permissions) in both attempts.</ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:millerthegorilla|millerthegorilla]]
| |
| |
| |
| | {{result|warn}}<ref>these were both the x86_64 image</ref>{{result|fail}}<ref>mounted virtual image as per https://gist.github.com/shamil/62935d9b456a6f9877b5 (Mount qcow image), and installed using https://docs.fedoraproject.org/en-US/fedora-coreos/bare-metal/#_installing_from_the_container. Installer ran fine, sshd in, and no ip address was reported on screen. got the ip address from virt-manager and ssh'd in. Seems to be working, tried machinectl shell to open standard user from ignition file, worked fine.</ref>{{result|fail}}<ref>started live cd install using virt-manager. Started ok, to prompt, but when trying to run coreos-installer picking up config.ign from the local network, the install failed with 'error checking whether /dev/sda is an ibm dasd disk.' Output of lsblk is garbled, with disk listed as '^%\xef\x9aaU'. Perhaps related to this (https://discussion.fedoraproject.org/t/coreos-pxeboot-coreos-installer-cant-format-dev-vda-or-dev-sda/25680)</ref>
| |
| | {{result|fail}}<ref>edk2 install failed to present a network address to the internet, wired connection not recognised by router.</ref>{{result|warn}}<ref>Docs for uboot at (https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-raspberry-pi4/#_installing_fcos_and_booting_via_u_boot) assume a non rpm-ostree install on the host machine. Ie there is no dnf available on my silverblue laptop, and I couldn't figure how to install using toolbox (perhaps I should have used a --privileged flag to podman).
| |
| The docs for EDK (https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-raspberry-pi4/#_edk2_combined_fedora_coreos_edk2_firmware_disk), should probably invite the user to expand their xfs partition before mounting. In my experience, only gparted has the capacity to do this correctly without too much hassle.</ref>{{result|fail}}<ref>install on pi4b following instructions for edk2 at [fedora-docs](https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-raspberry-pi4/#_edk2_combined_disk_mode_alternate_machine_disk_preparation) - boot loads, after very long pause at grub boot screen 'booting coreos-vernum' , No IP address is shown, and SSH host key is displayed, 3 times, one for ecdsa, one for ed25519 and one for RSA. What are these host keys, and why are they displayed?</ref>
| |
| | <references/>
| |
| |-
| |
| | [[User:pnemade|pnemade]]
| |
| | FCOS next image
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:sayaksarkar|sayaksarkar]]
| |
| | GNOME Boxes
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:sumantrom|sumantrom]]
| |
| | QEMU
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| | |
| |-
| |
| |}
| |
| | |
| === Cloud launch ===
| |
| {| class="wikitable" width=100%
| |
| ! User
| |
| ! Profile
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_AWS AWS]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Azure Azure]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_GCP GCP]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_DigitalOcean DigitalOcean]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_VMware VMWare]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Exoscale Exoscale]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_IBM_Cloud IBM Cloud]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Provisioning_on_VirtualBox VirtualBox]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Provisioning_on_Vultr Vultr]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_OpenStack OpenStack]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Alibaba Alibaba]
| |
| ! References
| |
| |-
| |
| | [[User:alciregi|alciregi]]
| |
| | DigitalOcean droplet
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>ok, works (in the documentation: in doctl compute image create the "--wait" option thorws an error)</ref>{{result|warn}}<ref>Droplet creation successfully. Can't ssh: I don't know if it is a problem on my side (ssh key, ignition file) or what else. Will try again later</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:danniel|danniel]]
| |
| | FCOS next image
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:donaldsebleung|donaldsebleung]]
| |
| | Fedora CoreOS 36 Next stream (arch: x86_64; ami: ami-066680d6ebe90fce1) on AWS
| |
| | {{result|pass}}<ref>Using https://github.com/DonaldKellett/fcos-test-day-cloud-launch#aws</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:donaldsebleung|donaldsebleung]]
| |
| | Fedora CoreOS 36 Next stream (arch: x86_64; instance type: e2-micro) on GCP
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>Using https://github.com/DonaldKellett/fcos-test-day-cloud-launch#gcp</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:dustymabe|dustymabe]]
| |
| | 36.20220410.1.1 on s-2vcpu-2gb droplet in nyc3
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:dustymabe|dustymabe]]
| |
| | exoscale
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|fail}}<ref>Failed to provisiion https://github.com/coreos/fedora-coreos-tracker/issues/1160</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:dustymabe|dustymabe]]
| |
| | ibmcloud bx2-2x8 instance
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:fifofonix|fifofonix]]
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>Successfully created and ssh'd into a fedora:36 next machine on vSphere 6.7 using govc following instructions linked from the test case. Some issues following govc instructions and suggested documentation improvements here:
| |
| https://github.com/coreos/fedora-coreos-tracker/issues/1158</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:jdoss|jdoss]]
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>Fedora CoreOS 36.20220325.1.0 launched just fine on GCP with a e2-medium instance in us-central1-a</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:miabbott|miabbott]]
| |
| | FCOS 36 on Aliyun
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>Used fedora-coreos-36.20220325.1.0-aliyun.x86_64.qcow2</ref>
| |
| | <references/>
| |
| |-
| |
| | [[User:mnguyen|mnguyen]]
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>Booted FCOS 36.20220325.1.0 on Azure in centralus following https://fedoraproject.org/wiki/QA:Testcase_CoreOS_Azure</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>Provisioned FCOS 36.20220325.1.0 on OpenStack following https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-openstack/. I did not need to assign floating IP for my OpenStack instance so those steps were not followed.</ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:ravanelli|ravanelli]]
| |
| | Fedora CoreOS 36 Next stream (arch: x86_64) on VirtualBox
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>1. Successfully booted fedora-coreos-36.20220325.1.0-live.x86_64.iso on VirtualBox using these instructions: https://fedoraproject.org/wiki/QA:Testcase_CoreOS_Provisioning_on_VirtualBox</ref>
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:sayaksarkar|sayaksarkar]]
| |
| | fedora-coreos-36.20220325.1.0-live.x86_64.iso
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:sohank2602|sohank2602]]
| |
| | Fedora CoreOS 36 Next stream (arch: x86_64) on Vultr
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>Successfully booted fedora-coreos-36.20220325.1.0-vultr.x86_64 on Vultr using these instructions: https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-vultr/ </ref>
| |
| |
| |
| |
| |
| | <references/>
| |
| | |
| |-
| |
| |}
| |
| | |
| === aarch64 ===
| |
| {| class="wikitable" width=100%
| |
| ! User
| |
| ! Profile
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_AWS AWS]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_virtual_install Virtual install]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_baremetal_install Bare Metal install]
| |
| ! References
| |
| |-
| |
| | [[User:Daniels|Daniels]]
| |
| | QEMU - KVM (fedora-coreos-36.20220410.1.1-live.x86_64.iso) Host: Gnome 41.5 Intel® Pentium(R) CPU 4415U @ 2.30GHz × 4 Lenovo 2in1 14
| |
| |
| |
| | {{result|pass}}<ref>ssh ((port (core@localhost) access denied to 127.0.0.1:2222. coreos 410))
| |
| Earlier versions of Coreos : 2022313.325. 327: Virtual Install. (No Pass)
| |
| librvirt test Installs (OS: fedora-coreos-next, not recognized ) Smooth testing otherwise.
| |
| </ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:Nemric|Nemric]]
| |
| | PXE installation
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>Configured swap on Zram with default settings</ref>{{result|pass}}<ref>Running : 1) docker.io/grafana/promtail:latest instance 2) quay.io/prometheus/node-exporter:latest instance 3) docker.io/library/registry:latest and docker.io/library/redis:latest in a pod </ref>
| |
| | <references/>
| |
| |-
| |
| | [[User:andilinux|andilinux]]
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| | <references/>
| |
| |-
| |
| | [[User:andilinux|andilinux]]
| |
| | GNOME BOXES
| |
| |
| |
| | {{result|pass}}<ref>Fedora CoreOS next
| |
| all worked fine for me</ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:bittin|bittin]]
| |
| | FCOS next image
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| | <references/>
| |
| |-
| |
| | [[User:bittin|bittin]]
| |
| | FCOS next image in Virtualbox
| |
| |
| |
| | {{result|pass}}{{result|fail}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:checking|checking]]
| |
| | FCOS next image
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:danniel|danniel]]
| |
| | FCOS next image
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:donaldsebleung|donaldsebleung]]
| |
| | FCOS next image with QEMU; arch: x86_64; custom Ignition file with password-based SSH access; launching with QEMU
| |
| |
| |
| | {{result|warn}}<ref>Can confirm that IP address of VM is printed in FCOS stable but not FCOS next, using identical configuration. Does not seem to affect usability of system though</ref>{{result|pass}}<ref>Using ignition file: https://github.com/DonaldKellett/fcos-test-day-cloud-launch/blob/main/fcos-test-day.ign ; following documentation "launching with QEMU": https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-qemu/ ; did not see IP address of VM printed to console possibly because password-based SSH was configured instead of SSH key(s) ; both local and SSH password login worked as expected, did not find any system issues</ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:donaldsebleung|donaldsebleung]]
| |
| | Fedora CoreOS 36 Next stream (arch: x86_64; ami: ami-066680d6ebe90fce1) on AWS
| |
| | {{result|pass}}<ref>Using https://github.com/DonaldKellett/fcos-test-day-cloud-launch#aws</ref>
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:dustymabe|dustymabe]]
| |
| | Installed FCOS `next` on Intel NUC
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| | <references/>
| |
| |-
| |
| | [[User:ersen|ersen]]
| |
| | virt-manager
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:geraldosimiao|geraldosimiao]]
| |
| | FCOS next image
| |
| |
| |
| | {{result|pass}}<ref>tested qemu qcow and iso image too</ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:kisk|kisk]]
| |
| | fedora-coreos-36.20220325.1.0-qemu.x86_64.qcow2.xz - libvirt
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:lnie|lnie]]
| |
| | fcos next image,x86_64,VM created by testcloud
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:lruzicka|lruzicka]]
| |
| | QEMU
| |
| |
| |
| | {{result|pass}}<ref>I was able to install using the approach described in https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-qemu/, however the approach described here https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-libvirt/ did not work and the command was complaining about no permission to read the ignition file which was the same (with same permissions) in both attempts.</ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:millerthegorilla|millerthegorilla]]
| |
| |
| |
| |
| |
| | {{result|warn}}<ref>these were both the x86_64 image</ref>{{result|fail}}<ref>mounted virtual image as per https://gist.github.com/shamil/62935d9b456a6f9877b5 (Mount qcow image), and installed using https://docs.fedoraproject.org/en-US/fedora-coreos/bare-metal/#_installing_from_the_container. Installer ran fine, sshd in, and no ip address was reported on screen. got the ip address from virt-manager and ssh'd in. Seems to be working, tried machinectl shell to open standard user from ignition file, worked fine.</ref>{{result|fail}}<ref>started live cd install using virt-manager. Started ok, to prompt, but when trying to run coreos-installer picking up config.ign from the local network, the install failed with 'error checking whether /dev/sda is an ibm dasd disk.' Output of lsblk is garbled, with disk listed as '^%\xef\x9aaU'. Perhaps related to this (https://discussion.fedoraproject.org/t/coreos-pxeboot-coreos-installer-cant-format-dev-vda-or-dev-sda/25680)</ref>
| |
| | {{result|fail}}<ref>edk2 install failed to present a network address to the internet, wired connection not recognised by router.</ref>{{result|warn}}<ref>Docs for uboot at (https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-raspberry-pi4/#_installing_fcos_and_booting_via_u_boot) assume a non rpm-ostree install on the host machine. Ie there is no dnf available on my silverblue laptop, and I couldn't figure how to install using toolbox (perhaps I should have used a --privileged flag to podman).
| |
| The docs for EDK (https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-raspberry-pi4/#_edk2_combined_fedora_coreos_edk2_firmware_disk), should probably invite the user to expand their xfs partition before mounting. In my experience, only gparted has the capacity to do this correctly without too much hassle.</ref>{{result|fail}}<ref>install on pi4b following instructions for edk2 at [fedora-docs](https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-raspberry-pi4/#_edk2_combined_disk_mode_alternate_machine_disk_preparation) - boot loads, after very long pause at grub boot screen 'booting coreos-vernum' , No IP address is shown, and SSH host key is displayed, 3 times, one for ecdsa, one for ed25519 and one for RSA. What are these host keys, and why are they displayed?</ref>
| |
| | <references/>
| |
| |-
| |
| | [[User:pnemade|pnemade]]
| |
| | FCOS next image
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:sayaksarkar|sayaksarkar]]
| |
| | GNOME Boxes
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:sumantrom|sumantrom]]
| |
| | QEMU
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| | |
| |-
| |
| |}
| |
| | |
| === Advanced configuration ===
| |
| {| class="wikitable" width=100%
| |
| ! User
| |
| ! Profile
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_static_networking Static networking]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_complex_partitioning Complex partitioning]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_build_container Building containers]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_containerized_service Containerized service]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_kernel_tuning_sysctl Kernel Tuning (sysctl)]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_modifying_kernel_arguments Modifying Kernel Arguments]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_OS_extensions OS extensions]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_swap_on_zram Configuring SwapOnZRAM]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_time_zone Configuring Time Zone]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_debugging_toolbox Debugging with Toolbox]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_NIC_Name Customizing NIC name]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Alternatives Setting alternatives]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Counting Node counting]
| |
| ! References
| |
| |-
| |
| | [[User:Nemric|Nemric]]
| |
| | FCOS updated from "next 35" to "next 36" on baremetal
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>Running :
| |
| - docker.io/grafana/promtail:latest instance
| |
| - quay.io/prometheus/node-exporter:latest instance
| |
| - docker.io/library/registry:latest and docker.io/library/redis:latest in a pod
| |
| | |
| Services were running well before and after running 'podman system reset' -> https://docs.fedoraproject.org/en-US/fedora-coreos/major-changes/#_podman_v4_0
| |
| | |
| </ref>
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:Nemric|Nemric]]
| |
| | PXE installation
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:aaradhak|aaradhak]]
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>Executed some debugging commands using toolbox version : registry.fedoraproject.org/fedora-toolbox:35</ref>{{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:aaradhak|aaradhak]]
| |
| | FCOS 36 next stream
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>Debugged toolbox with strace command and it was succcessful</ref>
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:alciregi|alciregi]]
| |
| | DigitalOcean droplet
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| |
| |
| | {{result|fail}}<ref>Apr 10 09:27:49 my-fcos-droplet rpm-ostree[1434]: Problem: conflicting requests
| |
| Apr 10 09:27:49 my-fcos-droplet rpm-ostree[1434]: - package vim-enhanced-2:8.2.4701-1.fc36.x86_64 requires vim-common = 2:8.2.4701-1.fc36, but none of the providers can>
| |
| Apr 10 09:27:49 my-fcos-droplet rpm-ostree[1434]: - package vim-enhanced-2:8.2.4621-1.fc36.x86_64 requires vim-common = 2:8.2.4621-1.fc36, but none of the providers can>
| |
| Apr 10 09:27:49 my-fcos-droplet rpm-ostree[1434]: - package vim-common-2:8.2.4701-1.fc36.x86_64 requires vim-data = 2:8.2.4701-1.fc36, but none of the providers can be >
| |
| Apr 10 09:27:49 my-fcos-droplet rpm-ostree[1434]: - package vim-common-2:8.2.4621-1.fc36.x86_64 requires vim-data = 2:8.2.4621-1.fc36, but none of the providers can be >
| |
| Apr 10 09:27:49 my-fcos-droplet rpm-ostree[1434]: - cannot install both vim-data-2:8.2.4701-1.fc36.noarch and vim-data-2:8.2.4579-1.fc36.noarch
| |
| Apr 10 09:27:49 my-fcos-droplet rpm-ostree[1434]: - cannot install both vim-data-2:8.2.4621-1.fc36.noarch and vim-data-2:8.2.4579-1.fc36.noarch
| |
| Apr 10 09:27:49 my-fcos-droplet systemd[1]: rpm-ostree-install-vim.service: Main process exited, code=exited, status=1/FAILURE
| |
| </ref>
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| | <references/>
| |
| |-
| |
| | [[User:checking|checking]]
| |
| | FCOS next image
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:donaldsebleung|donaldsebleung]]
| |
| | FCOS 36.20220325.1.0 on QEMU/KVM
| |
| | {{result|warn}}<ref>Did not see IP address of VM printed to console after boot (prints when using "stable" stream), but does not affect usability of system</ref>{{result|pass}}<ref>Static networking worked as expected. Configured IP address and netmask 10.0.2.10/24, gateway 10.0.2.2. `ip addr show` gives correct IP, pinging the VM, host and external websites all work as expected</ref>
| |
| | {{result|pass}}<ref>Test case "Adding /var/log from a secondary disk" works as expected: second disk is detected, partition created and formatted with xfs filesystem as specified, filesystem mounted on /var/log as specified</ref>
| |
| | {{result|pass}}<ref>Rootless podman, privileged podman, privileged docker all passed</ref>
| |
| | {{result|pass}}<ref>Busybox hello.service works as expected</ref>
| |
| | {{result|pass}}<ref>kernel.sysrq test works as expected, custom value of 0 remains after a reboot</ref>
| |
| | {{result|pass}}<ref>Setting systemd.unified_cgroup_hierarchy=0 in the Ignition config worked as expected: got a visible warning message on SSH login, /proc/cmdline indicates the kernel argument has been set. Rebooted the VM, settings persisted. Used `rpm-ostree kargs` to (1) update systemd.unified_cgroup_hierarchy to 1; (2) remove systemd.unified_cgroup_hierarchy; (3) add systemd.unified_cgroup_hierarchy=0. All changes were correctly registered after a reboot.</ref>
| |
| | {{result|fail}}<ref>Following the example "Layering vim and setting it as the default editor" in the docs results in a failed service with the following messages: Problem: conflicting requests - package vim-enhanced-2:8.2.4621-1.fc36.x86_64 requires vim-common = 2:8.2.4621-1.fc36, but none of the providers can be installed - package vim-common-2:8.2.4621-1.fc36.x86_64 requires vim-data = 2:8.2.4621-1.fc36, but none of the providers can be installed - cannot install both vim-data-2:8.2.4621-1.fc36.noarch and vim-data-2:8.2.4579-1.fc36.noarch . EDITOR is set correctly to vim though. Also the docs should mention that this service might take a while to run before the reboot.</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:hricky|hricky]]
| |
| | Intel® Core™ i7-4790 CPU, 32 GB RAM, Bare Metal
| |
| |
| |
| |
| |
| | {{result|warn}}<ref>Building and running container using podman in rootless mode failed. Others passed.</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:lnie|lnie]]
| |
| | fcos next image,x86_64,VM created by testcloud
| |
| |
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:lnie|lnie]]
| |
| | fcos next image,x86_64,VM created with virt-install
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:lruzicka|lruzicka]]
| |
| | QEMU
| |
| | {{result|pass}}
| |
| |
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|pass}}<ref>The `vim` package cannot be installed because there is a conflict of versions, as far as I can tell from the output in journalctl when attempting to install it. However, the mechanism does work normally when trying to install a different editor, such as `e3`.</ref>
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| |
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | <references/>
| |
| |-
| |
| | [[User:sohank2602|sohank2602]]
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>After discussing with Dusty on IRC, followed the first three steps from https://fedoraproject.org/wiki/QA:Testcase_CoreOS_swap_on_zram to verify this test case</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| | |
| |-
| |
| |}
| |
| | |
| === Upgrade ===
| |
| {| class="wikitable" width=100% | |
| ! User | | ! User |
| ! Profile | | ! [[QA:Testcase_example_1|Example test 1]] |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_switch_stream Switch stream] | | ! [[QA:Testcase_example_2|Example test 2]] |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_bootupd Bootloader updates] | | ! [[QA:Testcase_example_3|Example test 3]] |
| | ! [[QA:Testcase_example_4|Example test 4]] |
| ! References | | ! References |
| |- | | |- |
| | [[User:alciregi|alciregi]] | | | [[User:ExampleUser|Example User]] |
| | DigitalOcean droplet
| | | {{result|none}} |
| | {{result|pass}} | |
| | {{result|pass}} | | | {{result|pass}} |
| | | {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref> |
| | | {{result|fail}} <ref>{{bz|12345}}</ref> |
| | <references/> | | | <references/> |
| |-
| |
| | [[User:donaldsebleung|donaldsebleung]]
| |
| | FCOS stable image with QEMU; arch: x86_64; custom Ignition file with password-based SSH access; launching with QEMU
| |
| | {{result|warn}}<ref>FCOS stable prints IP address of VM to console but FCOS next does not after a switch stream. No other issues found with FCOS next</ref>{{result|pass}}<ref>Switch stream stable -> next successful. Did not test rollback.</ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:donaldsebleung|donaldsebleung]]
| |
| | FCOS stable image with QEMU; arch: x86_64; custom Ignition file with password-based SSH access; launching with QEMU
| |
| |
| |
| | {{result|pass}}<ref>Bootloader updates behaved as expected. Did not test automatic bootloader updates with systemd service</ref>
| |
| | <references/>
| |
| |-
| |
| | [[User:dustymabe|dustymabe]]
| |
| | FCOS stable image with qemu - rebased to next.
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | <references/>
| |
| |-
| |
| | [[User:hricky|hricky]]
| |
| | Intel® Core™ i7-4790 CPU, 32 GB RAM, Bare Metal
| |
| | {{result|pass}}<ref>next → testing → stable</ref>
| |
| | {{result|pass}}
| |
| | <references/>
| |
| |-
| |
| | [[User:lruzicka|lruzicka]]
| |
| | QEMU
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | <references/>
| |
|
| |
| |-
| |
| |}
| |
|
| |
| === Tutorials ===
| |
| {| class="wikitable" width=100%
| |
| ! User
| |
| ! Profile
| |
| ! References
| |
|
| |
| |-
| |
| |}
| |
|
| |
| === Miscellaneous ===
| |
| {| class="wikitable" width=100%
| |
| ! User
| |
| ! Profile
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_documentation Documentation]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_exploratory_testing Exploratory testing]
| |
| ! References
| |
| |-
| |
| | [[User:Nemric|Nemric]]
| |
| | PXE installation
| |
| |
| |
| | {{result|pass}}<ref>Setting up journald to run in RAM (since promtail send logs to grafana/loki) with :
| |
| ```yaml
| |
| systemd:
| |
| units:
| |
| - name: systemd-journald.service
| |
| dropins:
| |
| - name: 11-storage_volatile.conf
| |
| contents: |
| |
| [Journal]
| |
| Storage=volatile
| |
| RuntimeMaxUse=16M
| |
| RuntimeMaxFileSize=16M
| |
| RuntimeMaxFiles=1
| |
|
| |
| - name: systemd-journal-flush.service
| |
| mask: true```</ref>{{result|pass}}<ref>Trying the rewritten fscahe that landed on kernel 5.17
| |
| -> sudo rpm-ostree install --apply-live cachefilesd && sudo systemctl enable --now cachefilesd
| |
| Seems to be more reliable : it worked at first attempt and still alive (cat /proc/fs/nfsfs/* : fsc = yes) after nfs server reboot and/or host reboot
| |
| </ref>
| |
| | <references/>
| |
| |-
| |
| | [[User:hricky|hricky]]
| |
| | Intel® Core™ i7-4790 CPU, 32 GB RAM, Bare Metal
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:lruzicka|lruzicka]]
| |
| | QEMU
| |
| | {{result|fail}}<ref>The approach in this procedure does not work https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-libvirt/. Any attempt fails with "ERROR internal error: qemu ended monitor unexpectedly: 2022-04-11T11:17:53.116624Z qemu-system-x86_64: -fw_cfg name=opt/com.coreos/config,file=/home/lruzicka/todelete/coreos_yaml.ign: can't load /home/lruzicka/todelete/coreos.ign: Failed to open file “/home/lruzicka/todelete/coreos_yaml.ign”: Permission denied.
| |
| "</ref>
| |
| |
| |
| | <references/>
| |
|
| |
| |- | | |- |
| |} | | |} |
| | --> |
|
| |
|
|
| |
|
| |
|
| [[Category:Fedora 36 Test Days]] | | [[Category:Fedora 36 Test Days]] |
