After upgrade from 8.0 to 9.0 can not edit network interfaces for new environment

Bug #1595210 reported by Dmitry Mescheryakov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
High
Arthur Svechnikov
Mitaka
Fix Released
High
Arthur Svechnikov
Newton
Fix Committed
High
Arthur Svechnikov

Bug Description

Version: 8.0 -> 9.0

Steps to reproduce:
1. Install 8.0 master node, make sure there are 6 discovered nodes
2. Install detach-rabbitmq plugin
3. Create a new environment consisting of 1 controller, 1 compute+cinder and 1 RabbitMQ node.
4. Upgrade master node to 9.0 using procedure described in http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/upgrade/upgrade-fuel.html
5. Restart 3 unallocated nodes so that they boot with the new 9.0 bootstrap image.
6. Try to create a new (the second) environment consisting of 1 controller, 1 compute+cinder and 1 RabbitMQ node.
7. Go to Nodes menu of the second env and try to configure interfaces here for any node. Make any change, for instance move some network from one interface to another.
8. Push 'Apply' button.

Expected result:
Changes to interfaces apply

Actual result:
A server error pop up appears

Details:
After enabling debug in Nailgun, Chrome's developer tools show the following stack trace from the server: http://paste.openstack.org/show/521182/

Workaround:
1. Remove all nodes from the second environment
2. Remove them from the Fuel DB with the following command:
      fuel node --node <node_id> --delete-from-db --force
3. Reboot the nodes
After that you can add these nodes back to the environment and you will be able to configure interfaces this time.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-web (master)

Fix proposed to branch: master
Review: https://review.openstack.org/333585

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-web (master)

Reviewed: https://review.openstack.org/333585
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=d8a409a6130cc0ec7362706b37bb51722b441d52
Submitter: Jenkins
Branch: master

commit d8a409a6130cc0ec7362706b37bb51722b441d52
Author: Artur Svechnikov <email address hidden>
Date: Thu Jun 23 23:49:34 2016 +0300

    Always fill interface properties with default values

    After upgrade of master node new interface properties
    may appears in new Fuel. However, there is no way default
    values to appear in the properties for nodes that were already
    discovered by old Fuel.

    Change-Id: I33a4d9b6303db581ea4fd6876a329e8b270da866
    Closes-Bug: #1595210

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-web (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/335080

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-web (stable/mitaka)

Reviewed: https://review.openstack.org/335080
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=6f3b56d7b115487b896cac24fbbb23172d513df6
Submitter: Jenkins
Branch: stable/mitaka

commit 6f3b56d7b115487b896cac24fbbb23172d513df6
Author: Artur Svechnikov <email address hidden>
Date: Thu Jun 23 23:49:34 2016 +0300

    Always fill interface properties with default values

    After upgrade of master node new interface properties
    may appears in new Fuel. However, there is no way default
    values to appear in the properties for nodes that were already
    discovered by old Fuel.

    Change-Id: I33a4d9b6303db581ea4fd6876a329e8b270da866
    Closes-Bug: #1595210
    (cherry picked from commit d8a409a6130cc0ec7362706b37bb51722b441d52)

Revision history for this message
Dmitry Belyaninov (dbelyaninov) wrote :

Verified on snapshot #255

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.