Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Hello Waldemar Znoinski,
I'm ovs-qe and doing the bug verification. Could you please give an instruction or script to reproduce the issue?
Thanks
Qijun
Comment 4Waldemar Znoinski
2018-09-17 09:04:51 UTC
hi Qijun,
I'm getting this problem in a TripleO environment. If you want to use the same method of installation of OVS + ODL as mine you'd have a quite beefy machine, i.e.: 64GB RAM server and I can give you the commands to test. Other option is to install OVS + ODL on its own (not sure whether the issue exists there - probably yes but never checked it) or using a machine I dpeloy with OSP14 + OVS + ODL that shows the problem. You can then install patched version of OVS and verify fix.
Which way you want to go?
(In reply to Waldemar Znoinski from comment #4)
> hi Qijun,
>
> I'm getting this problem in a TripleO environment. If you want to use the
> same method of installation of OVS + ODL as mine you'd have a quite beefy
> machine, i.e.: 64GB RAM server and I can give you the commands to test.
> Other option is to install OVS + ODL on its own (not sure whether the issue
> exists there - probably yes but never checked it) or using a machine I
> dpeloy with OSP14 + OVS + ODL that shows the problem. You can then install
> patched version of OVS and verify fix.
>
> Which way you want to go?
We have no problem to get a server with 64G RAM, so prefer the option OVS+ODL, the same one as yours because with the chance we want to extend it to a test case so that we can have a basic verification for this combination in our regular test. As we don't know much on ODL, it would be appreciated if you can give us a much detail instruction. Thank you very much.
Qijun
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2018:2735