Revision as of 13:38, 18 September 2014

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.

Description

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

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.
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

Ideally, connect to the Cockpit port on the test system from another system with a web browser; the Cockpit management interface should show up

As far as you can reasonably test, Cockpit should be enabled and accessible on the test system after installation.

@@ Line 6: / Line 6: @@
 # 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.
 # Boot the installed system, and check that Cockpit is running and accessible:
-#: {{command|sudo systemctl status cockpit.service}} should show the service as enabled and running without errors
+#: {{command|sudo systemctl status cockpit.socket}} should show the service as enabled and running without errors
 #: {{command|sudo firewall-cmd --list-all}} should show the cockpit service
 #: Ideally, connect to the Cockpit port on the test system from another system with a web browser; the Cockpit management interface should show up