[upgrade] Fuel upgrade 8-9 with multirack does not backups dhcp ranges

Bug #1628529 reported by Vladimir Khlyunev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Unassigned

Bug Description

https://review.openstack.org/#/c/365903/
https://review.openstack.org/#/c/374241/

These patches were merged into mitaka but not into staable/8.0

Changed in fuel:
status: New → Confirmed
description: updated
Changed in fuel:
milestone: 9.2 → 8.0-updates
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-octane (stable/8.0)

Fix proposed to branch: stable/8.0
Review: https://review.openstack.org/378652

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-octane (stable/7.0)

Fix proposed to branch: stable/7.0
Review: https://review.openstack.org/379308

Revision history for this message
Ilya Kharin (akscram) wrote :

These patches will not help there because in 8.0 there is only manual way how dhcp ranges can be configured and it means that nothing to back up. It have to be fixed in fuel-qa and mentioned in documentationn.

Changed in fuel:
status: Confirmed → Invalid
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-octane (stable/8.0)

Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: stable/8.0
Review: https://review.openstack.org/378652
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-octane (stable/7.0)

Change abandoned by Sergey Abramov (<email address hidden>) on branch: stable/7.0
Review: https://review.openstack.org/379308

Curtis Hovey (sinzui)
Changed in fuel:
assignee: Registry Administrators (registry) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.