Amphora image requires explicit --property hw_architecture='x86_64 in multi-arch clouds

Bug #1818563 reported by Nir Magnezi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Undecided
Nir Magnezi

Bug Description

Initially reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1677064

Description of problem:
In our multi-architecture cloud, creating a load balancer occasionally fails because it's being spun up on ppc64le compute nodes (the octavia-amphora image is x86_64 only).

Version-Release number of selected component (if applicable):
octavia-amphora-13.0-20190109.1.x86_64

How reproducible:
If no hw_architecture property is specific and the image attempts to be deployed onto ppc64le nodes, it will fail.

Steps to Reproduce:
1. Leave out hw_architecture='86_64' property from the image
2. Try to deploy image. If it tries to schedule on a ppc64le node it will fail
3.

Actual results:
Failure without explicit hw_architecture

Expected results:
If this can only be created on x86_64 nodes, can we default to x86_64 for this image?

Additional info:
If it's not possible to default to x86_64, we can move this to a Docs issue and we can update the documentation to inform customers they need to set this property for the image.

Nir Magnezi (nmagnezi)
summary: - mphora image requires explicit --property hw_architecture='x86_64 in
+ Amphora image requires explicit --property hw_architecture='x86_64 in
multi-arch clouds
Changed in tripleo:
assignee: nobody → Nir Magnezi (nmagnezi)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (stable/rocky)

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/640921

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (stable/queens)

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/640922

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (master)

Reviewed: https://review.openstack.org/639973
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=2f1c0b89ee15ad95e23e23995aa3340d8db59966
Submitter: Zuul
Branch: master

commit 2f1c0b89ee15ad95e23e23995aa3340d8db59966
Author: Nir Magnezi <email address hidden>
Date: Thu Feb 28 11:57:00 2019 +0200

    Specify Octavia amphora image hw_architecture property in Glance

    In the case of a multi-architecture cloud, Nova will try to schedule an
    Amphora to a non-x86_64 architecture compute node, which will fail the
    load balancer creation in Octavia.

    This patch explicitly specifies the Amphora image hw_architecture
    property when the image is being uploaded to Glance. By doing so, it
    hints the Nova scheduler which compute nodes to take into
    account when it schedules an Amphora instance.

    The default for hw_architecture is x86_64, which resembles the current
    behavior since this is the only image type that we ship.

    Closes-Bug: #1818563

    Change-Id: Ia7be6503a40e08d0d1f7f4d89132c9e9b5bd6704

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (stable/rocky)

Reviewed: https://review.openstack.org/640921
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=ef5bf9deb83a81364cea39b12de0ba799aa8b8ee
Submitter: Zuul
Branch: stable/rocky

commit ef5bf9deb83a81364cea39b12de0ba799aa8b8ee
Author: Nir Magnezi <email address hidden>
Date: Thu Feb 28 11:57:00 2019 +0200

    Specify Octavia amphora image hw_architecture property in Glance

    In the case of a multi-architecture cloud, Nova will try to schedule an
    Amphora to a non-x86_64 architecture compute node, which will fail the
    load balancer creation in Octavia.

    This patch explicitly specifies the Amphora image hw_architecture
    property when the image is being uploaded to Glance. By doing so, it
    hints the Nova scheduler which compute nodes to take into
    account when it schedules an Amphora instance.

    The default for hw_architecture is x86_64, which resembles the current
    behavior since this is the only image type that we ship.

    Closes-Bug: #1818563

    Change-Id: Ia7be6503a40e08d0d1f7f4d89132c9e9b5bd6704
    (cherry picked from commit 2f1c0b89ee15ad95e23e23995aa3340d8db59966)

tags: added: in-stable-rocky
tags: added: in-stable-queens
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (stable/queens)

Reviewed: https://review.openstack.org/640922
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=17a050f13e836a1022e640f2e8a1c6f682c2a7b0
Submitter: Zuul
Branch: stable/queens

commit 17a050f13e836a1022e640f2e8a1c6f682c2a7b0
Author: Nir Magnezi <email address hidden>
Date: Thu Feb 28 11:57:00 2019 +0200

    Specify Octavia amphora image hw_architecture property in Glance

    In the case of a multi-architecture cloud, Nova will try to schedule an
    Amphora to a non-x86_64 architecture compute node, which will fail the
    load balancer creation in Octavia.

    This patch explicitly specifies the Amphora image hw_architecture
    property when the image is being uploaded to Glance. By doing so, it
    hints the Nova scheduler which compute nodes to take into
    account when it schedules an Amphora instance.

    The default for hw_architecture is x86_64, which resembles the current
    behavior since this is the only image type that we ship.

    Closes-Bug: #1818563

    Change-Id: Ia7be6503a40e08d0d1f7f4d89132c9e9b5bd6704
    (cherry picked from commit 2f1c0b89ee15ad95e23e23995aa3340d8db59966)
    (cherry picked from commit ef5bf9deb83a81364cea39b12de0ba799aa8b8ee)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 10.5.0

This issue was fixed in the openstack/tripleo-common 10.5.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 9.6.0

This issue was fixed in the openstack/tripleo-common 9.6.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 8.7.0

This issue was fixed in the openstack/tripleo-common 8.7.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.