Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1536142 - OSP10 -> OSP13 FFU upgrade: after running upgrade_steps_playbook instance connectivity via a floating ip no longer works
OSP10 -> OSP13 FFU upgrade: after running upgrade_steps_playbook instance con...
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates (Show other bugs)
13.0 (Queens)
Unspecified Unspecified
high Severity urgent
: beta
: 13.0 (Queens)
Assigned To: Emilien Macchi
Marius Cornea
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-18 12:01 EST by Marius Cornea
Modified: 2018-06-27 09:43 EDT (History)
9 users (show)

See Also:
Fixed In Version: openstack-tripleo-heat-templates-8.0.0-0.20180304031149.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-06-27 09:42:33 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1744126 None None None 2018-01-18 12:01 EST
OpenStack gerrit 542796 None master: MERGED tripleo-heat-templates: [Upgrade] Reuse OVS workaround in docker neutron ovs agent (If3a63cad754a875f56b604033c1aff49824... 2018-03-22 12:56 EDT
Red Hat Product Errata RHEA-2018:2086 None None None 2018-06-27 09:43 EDT

  None (edit)
Description Marius Cornea 2018-01-18 12:01:35 EST
Description of problem:
OSP10 -> OSP13 FFU upgrade: after running upgrade_steps_playbook instance connectivity via a floating ip no longer works.

I can reach the l3 router external interface(where the fip is set) but I cannot reach the instance via the assigned floating ip.
Comment 10 errata-xmlrpc 2018-06-27 09:42:33 EDT
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:2086

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