QA:Testcase Server cockpit default

Associated release criterion
This test case is associated with the Basic_Release_Criteria#cockpit-management-interface release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.

Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#cockpit-management-interface release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.

Description

This test case checks that Cockpit is enabled, accessible and functional after a Fedora Server installation, as required in the Server/Technical_Specification.

How to test

1. Install the Fedora Server release you wish to test, in graphical or text mode, making as few choices as possible and making the most simple and obvious choices where a choice is required.
2. Boot the installed system, and check that Cockpit is running and accessible:

   sudo systemctl status cockpit.socket should show the service as enabled and running without errors

   sudo firewall-cmd --list-all should show the cockpit service

3. Connect to the Cockpit port on the test system from another system with a web browser; the Cockpit management interface should show up
4. Log in to Cockpit with the root account or an administrative user account, and select the system from the host list
5. Click 'Journal' and check you can browse the journal and open individual entries
6. Click 'Services' and check you can see services with their statuses

Expected Results

1. As far as you can reasonably test, Cockpit must be enabled and accessible on the test system after installation
2. It must be possible to view the journal and service status from Cockpit