Network Interface is not connected and configured with DHCP in SUT #2

Closed
opened 2021-08-15 20:59:51 +00:00 by tcooper · 1 comment
tcooper commented 2021-08-15 20:59:51 +00:00 (Migrated from github.com)

Describe the bug

When POSTing tests without specifying grub commandline parameters that will activate the network interface in the SUT (eg. GRUB="ip=dhcp bootdev=52:54:00:12:34:56 inst.waitfornet=300") the network interface is not CONNECTED and tests requiring network access will fail.

Currently the test fails because it matches the needle rocky-network_configure-20210813 before it matches the needle rocky-anaconda_network_connected-20210813 and, instead of simply toggling the ON/OFF state of the interface. The test tries to Configure the interface with a static IP, as per the intention of matching the rocky-network_configure-20210813. That needles is designed for a different test and intended to be triggered along with proper POST variables to provide IP information to use for the static network configuration.


To Reproduce

Steps to reproduce the behavior:

  1. Configure a Rocky openQA development system per the instruction in this repo.
  2. Complete the default configuration and POST the example test.
  3. Wait for the example test to complete successfully. If it doesn't complete successfully STOP HERE and get it working.
  4. POST another test using the command line... sudo openqa-cli api -X POST isos ISO=Rocky-8.4-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.4 PACKAGE_SET=server and DO NOT provide the GRUB variable.
  5. Wait for test to fail in the _anaconda_network_enable.pm test.

Expected behavior

The test suite will not fail in the _anaconda_network_enable.pm test, the SUT will have a CONNECTED network interface configured with DHCP and the test suite will continue to the next test in the test suite, _anaconda_kdump_disable.pm.


System / Environment (please complete the following information):

**Describe the bug** When `POST`ing tests without specifying grub commandline parameters that will activate the network interface in the SUT (eg. `GRUB="ip=dhcp bootdev=52:54:00:12:34:56 inst.waitfornet=300"`) the network interface is not `CONNECTED` and tests requiring network access will fail. Currently the test fails because it matches the needle `rocky-network_configure-20210813` before it matches the needle `rocky-anaconda_network_connected-20210813` and, instead of simply toggling the `ON/OFF` state of the interface. The test tries to `Configure` the interface with a static IP, as per the intention of matching the `rocky-network_configure-20210813`. That needles is designed for a different test and intended to be triggered along with proper `POST` variables to provide IP information to use for the static network configuration. --- **To Reproduce** Steps to reproduce the behavior: 1. Configure a Rocky openQA development system per the instruction in [this repo](https://github.com/tcooper/OpenQA-Fedora-Installation). 2. Complete the default configuration and `POST` the example test. 3. Wait for the example test to complete successfully. If it doesn't complete successfully **STOP HERE** and get it working. 4. `POST` another test using the command line... `sudo openqa-cli api -X POST isos ISO=Rocky-8.4-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.4 PACKAGE_SET=server` and **DO NOT** provide the `GRUB` variable. 5. Wait for test to fail in the `_anaconda_network_enable.pm` test. --- **Expected behavior** The test suite will not fail in the `_anaconda_network_enable.pm` test, the SUT will have a `CONNECTED` network interface configured with DHCP and the test suite will continue to the next test in the test suite, `_anaconda_kdump_disable.pm`. --- **System / Environment (please complete the following information):** - OS: Fedora 34 Server - OS Version: 34 - Testing Repository - Branch: develop (waiting merge of PR #1) - Hash: [e698d7207d45cc56ef5ffc24f0198a5048aaffc5](https://github.com/rocky-linux/os-autoinst-distri-rocky/pull/1/commits/e698d7207d45cc56ef5ffc24f0198a5048aaffc5) (or later)
tcooper commented 2021-08-20 03:04:48 +00:00 (Migrated from github.com)

Resolved in #3

Resolved in #3
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: testing/os-autoinst-distri-rocky-migrated#2
No description provided.