Fetch pre_upgrade data based on node properties

[vsedmik]

Problem Statement

During TFA I've seen several post_upgrade failures for "rhel_contenthost-parametrized" upgrade scenario tests where the pre-data could not be fetched from the scenario_entities file:

failed on setup with "Failed: Invalid test parameter: rhel7. Test data not found."

The reason is that the pre-upgrade test names are now suffixed with -ipv4 or -ipv6 so the scenario_entities hold items like this:

{"tests/upgrades/test_repository.py::TestSimpleContentAccessOnly::test_pre_simple_content_access_only[rhel7-ipv4]": {...}}

while this piece of code requires the exact param, which is just rhel7, rhel8, rhel9.

Solution(?)

There are probably more than one solution and I'm not sure which one would be the best.

Initially I thought we could go regardless the ipvX suffix since I supposed the pipelines were separated (first commit).
That's probably not a good solution when we start decorating tests with ['ipv4', 'ipv6'] explicitly, so I took the network type from the settings.

Please let me know if there is a better place where to get that information from in scope of the pre_upgrade_data fixture.

[jyejare]

The network type is not always SatelliteNetworkType, it is first checked in tests param and if not then only in SatelliteNetworkType

[vsedmik]

The logic is that extracted_value can be anything like rhel7, rhel7-ipv4, rhel7-ipv6 and other rhel variants.
Also request.param can be anything like that - with or without ipvX. When it is decorated with ipvX, only that single value is added to the upgrade_data list due to the if on line 263. On the other hand, when request.param is not decorated with ipvX (i.e. just plain rhel7) the upgrade_data gets filled with everything that contains rhel7, like ['rhel7-ipv4', 'rhel7-ipv6']. Only in that case we read the SatelliteNetworkType to resolve which one should be picked from upgrade_data.

[jyejare]

@vsedmik We accept this as a half solution and we need to communicate to the team that, for now we are not supporting upgrade scenarios parametrization for network type.