Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1688450 - RHEL8 image compatibility
Summary: RHEL8 image compatibility
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tempest
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Chandan Kumar
QA Contact: Martin Kopec
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-13 18:04 UTC by Attila Fazekas
Modified: 2019-04-04 04:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Attila Fazekas 2019-03-13 18:04:11 UTC
Description of problem:
In the previous cycle a change added to 
tempest which allows to use rhel7 image instead of very small test only image.
Unfortunately the change is not compatible with RHEL8,
first of all, the 'serivce network restart' Does not exists.

The change for RHEL7 in tempest:
https://github.com/openstack/tempest/commit/c5c7ba997e


tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet.* tests are failing.


Additional info:
RHEL guest image does not have the legacy part of the initscripts,
network-scripts was splinted out from initscripts (package build time) to a dedicated package since Jun 14 2018 9.83-1 .

Comment 1 Martin Kopec 2019-03-14 14:38:20 UTC
For the record steps how to reproduce:
generate tempest.conf using rhel8
$ discover-tempest-config --create --debug --image <path/to/rhel-8>

then use the generated tempest.conf to run tempest (either packaged or cloned from master):
$ tempest run --regex tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet


Note You need to log in before you can comment on or make changes to this bug.