Revision as of 16:49, 29 May 2018

Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#Remote_logging 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 article is incomplete. Remote logging happens when the operating system logs events and errors to a different machine (server) over the network. This test case shows whether remote logging can be set up in a Fedora Server environment using system packages available after the installation.

How to test

Run the default installation of Fedora Server on two different machines, either bare metal or virtual.
When the systems are installed, check the following steps (3 and 4) on both machines.
Check that rsyslog is installed on both machines.
```
rpm -qi rsyslog
```
Check that the rsyslog.service is up and running.
```
systemctl status rsyslog.service
```

If not, enable the service and start it.

systemctl enable rsyslog.service

systemctl start rsyslog.service

On the server, edit the /etc/rsyslog.conf file.
```
vi /etc/rsyslog.conf
```

In the file, uncomment the following lines:

module(load="imudp")

input(type="imudp" port="514")

On the server, open the UDP port 514 for incoming traffic.

firewall-cmd --permanent --add-port=514/udp

firewall-cmd --reload

On the server, restart the rsyslog.service.
```
systemctl restart rsyslog.service
```
On the server, display the /var/log/messages so that it continues in the console.
```
tail -f /var/log/messages
```

Expected Results

The following must be true to consider this a successful test run. Be brief ... but explicit.

Step #1 completes without error
The system boots into runlevel 5
Program completes with exit code 0

Optional

Optionally provide hints for exploratory testing.

@@ Line 4: / Line 4: @@
 |description=This article is '''incomplete'''. Remote logging happens when the operating system logs events and errors to a different machine (server) over the network. This test case shows whether remote logging can be set up in a Fedora Server environment using system packages available after the installation.
 |actions=
-Be as specific as required for the target audience.
+# Run the default installation of Fedora Server on two different machines, either bare metal or virtual.
-# Start here ...
+# When the systems are installed, check the following steps (3 and 4) on both machines.
-# Next do this ...
+# Check that <code>rsyslog</code> is installed on both machines. <pre>rpm -qi rsyslog</pre>
-# Finally click that
+# Check that the <code>rsyslog.service</code> is up and running. <pre>systemctl status rsyslog.service</pre>
+# If not, enable the service and start it. <pre>systemctl enable rsyslog.service</pre><pre>systemctl start rsyslog.service</pre>
+# On the server, edit the <code>/etc/rsyslog.conf</code> file. <pre>vi /etc/rsyslog.conf</pre>
+# In the file, uncomment the following lines: <pre>module(load="imudp")</pre><pre>input(type="imudp" port="514")</pre>
+# On the server,  open the '''UDP port 514''' for incoming traffic. <pre>firewall-cmd --permanent --add-port=514/udp</pre><pre>firewall-cmd --reload</pre>
+# On the server, restart the <code>rsyslog.service</code>. <pre>systemctl restart rsyslog.service</pre>
+# On the server, display the <code>/var/log/messages</code> so that it continues in the console. <pre>tail -f /var/log/messages</pre>
 |results=
 The following must be true to consider this a successful test run. Be brief ... but explicit.

Search

QA:Testcase Remote Logging: Difference between revisions

Revision as of 16:49, 29 May 2018

Contents

Description

How to test

Expected Results

Optional