Newton scheduler clients should keep trying to report
Bug #1655494 reported by
Dan Smith
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Dan Smith | ||
Newton |
Fix Committed
|
Undecided
|
Matt Riedemann |
Bug Description
Newton scheduler clients will stop reporting any time they encounter a setup-related error, which isn't very operator-friendly for the ocata upgrade process.
Changed in nova: | |
assignee: | nobody → Dan Smith (danms) |
status: | New → In Progress |
Changed in nova: | |
status: | In Progress → Confirmed |
importance: | Undecided → Medium |
tags: | added: newton-backport-potential |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/418590 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=bbf9b431ee2 6e4064278e58bf9 c177de48e8719a
Committed: https:/
Submitter: Jenkins
Branch: master
commit bbf9b431ee26e40 64278e58bf9c177 de48e8719a
Author: Dan Smith <email address hidden>
Date: Tue Jan 10 13:49:19 2017 -0800
Make placement client keep trying to connect
In Newton, placement is optional and computes will stop even trying
to connect to placement when they encounter an error or missing
configuration. We really want them to keep trying so that enabling
the service pre-upgrade does not require restarting all computes
to start filling data.
This patch removes the auto-disable logic and replaces it with a
limited, but persistent warning to the logs about the required
nature of placement for the upgrade. If we had messaged the upcoming
requirement better, I think we could have been less chatty here.
However, we know that it's not been received, so this patch periodically
re-emits the warning and mentions the upgrade specifically.
Closes-Bug: #1655494 0d39c00f519e828 8f3b3a5e9cb
Change-Id: Ie6387afeb239a2