Bug 1326843 - rhel-osp-director: after undercloud upgrade 7.3->8.0 the vips are down. The upgrade finishes successfully.
Summary: rhel-osp-director: after undercloud upgrade 7.3->8.0 the vips are down. The u...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Angus Thomas
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-13 13:59 UTC by Alexander Chuzhoy
Modified: 2018-05-02 10:49 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-03 12:58:25 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Alexander Chuzhoy 2016-04-13 13:59:46 UTC
rhel-osp-director: after undercloud upgrade 7.3->8.0 the vips are down. The upgrade finishes successfully.

Environment:
instack-undercloud.noarch


Steps to reproduce:
1. Deploy 7.3 (no SSL)
2. Yum update the undercloud
3. Check that the VIPs are still alive.
4. run "openstack undercloud upgrade" and wait until it completes successfully.
5. Check the VIPs 

Result:
The VIPs are not reachable.


Expected result:
The VIPs should be reachable.


Restarting the keepalived service restores them.

Comment 2 Marios Andreou 2017-05-10 11:15:06 UTC
is this still a bug? looks like something filed during OSP8 testing - can we close it?

marking it triaged for now and adding needinfo on sasha though I doubt he can answer the question now if he isn't testing this?

I assume if it was something that came up during OSP8 testing and wasn't already fixed we would have heard more about it by now.

Proposing to close for now.

Comment 3 Amit Ugol 2017-07-03 12:58:25 UTC
This have been fixed ages ago. I would assume any new bug with the same symptoms will have a different root cause.

Comment 4 Amit Ugol 2018-05-02 10:49:29 UTC
closed, no need for needinfo.


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