ironic template doesn't work if fixed network has two subnet

Bug #1472938 reported by yuanying
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Medium
Spyros Trigazis

Bug Description

At magnum/templates/heat-kubernetes/kubecluster-fedora-ironic.yaml
floating_ip is not created if fixed network has two subnet.

It should be changed to creating floating ip from fixed ip address (not port).

See more information: https://review.openstack.org/#/c/198596/4/magnum/templates/heat-kubernetes/kubecluster-fedora-ironic.yaml

Adrian Otto (aotto)
Changed in magnum:
status: New → Triaged
importance: Undecided → Medium
Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
Eli Qiao (taget-9)
Changed in magnum:
assignee: nobody → Eli Qiao (taget-9)
Changed in magnum:
assignee: Eli Qiao (taget-9) → Spyros Trigazis (strigazi)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/320968
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=08531c170293bf13ec0c77bc396c1150998d39eb
Submitter: Jenkins
Branch: master

commit 08531c170293bf13ec0c77bc396c1150998d39eb
Author: OTSUKA, Yuanying <email address hidden>
Date: Thu Jul 14 21:07:06 2016 +0200

    Fix ironic template

    This is workaround fix to support baremetal.
    Following items are remained to support.
    * Documents
    * Functional test

    To test this template, there are some requirements and problem as below.

    Requirements:
    * `ephemeral_disk` on ironic baremetal flavor
      `ephemeral_disk` is used for docker storage instead of cinder volume.

    * `fixed_subnet` must be setup with dns_nameservers like following.
        * `neutron subnet-update private-subnet --dns-nameserver 8.8.8.8`

    * `fixed_subnet` must be IP version 4.
      if you use devstack, please add following configuration.
        * `IP_VERSION=4`

    * Fedora 23 image including kubernetes, etcd, flannel.

    Problem:
    Ironic stores `instance_info` about nova instance.
    `instance_info` contains config_drive data, but this data can be
    too large to store ironic.nodes table.
    Magnum uses large config drive data to setup k8s.
    It means, we can not start ironic instance by Magnum.

    Workaround fix is changing column type of ironic.nodes.instance_info.
    Following sql will help you.

      `alter table ironic.nodes modify instance_info LONGTEXT;`

    Partial-Implements: blueprint magnum-baremetal-full-support
    Change-Id: Ica87610b9114bff4277b492de8fe528fe2860108
    Closes-Bug: #1454895
    Closes-Bug: #1472938
    Co-Authored-By: Spyros Trigazis <email address hidden>

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 3.0.0

This issue was fixed in the openstack/magnum 3.0.0 release.

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.