OpenStack-Gate

internap doesn't support the same cpu flags as other providers

Bug #1535799 reported by Sean Dague
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Gate
Invalid
Undecided
Unassigned
devstack
Fix Released
Undecided
Unassigned

Bug Description

Internap doesnt support ssse3 and vme cpu flags, which means our gate64 devstack definition is wrong.

Revision history for this message
Matt Riedemann (mriedem) wrote :

Fix is here in devstack: https://review.openstack.org/#/c/269743/

Changed in openstack-gate:
status: New → Invalid
Changed in devstack:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (stable/kilo)

Reviewed: https://review.openstack.org/269742
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=40d0fb91d85a23c4af028291db7d09db7fd7974e
Submitter: Jenkins
Branch: stable/kilo

commit 40d0fb91d85a23c4af028291db7d09db7fd7974e
Author: Clark Boylan <email address hidden>
Date: Tue Jan 19 08:15:36 2016 -0800

    Remove vme and ssse3 from gate64 cpu mapping

    It turns out that we need to be even more restrictive on the cpu flags
    we expose as some clouds don't expose vme or ssse3.

    Fixes-Bug: 1535799
    Change-Id: I6c8c1101771d1c5496884be7a405285472ae803a
    (cherry picked from commit e62a5e1df872e332062f4d4efd6c9ef2ee4db1dd)

tags: added: in-stable-kilo
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (stable/liberty)

Reviewed: https://review.openstack.org/269743
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=6b757821fb8731caca56fd4ccacb2579cb600e0a
Submitter: Jenkins
Branch: stable/liberty

commit 6b757821fb8731caca56fd4ccacb2579cb600e0a
Author: Clark Boylan <email address hidden>
Date: Tue Jan 19 08:15:36 2016 -0800

    Remove vme and ssse3 from gate64 cpu mapping

    It turns out that we need to be even more restrictive on the cpu flags
    we expose as some clouds don't expose vme or ssse3.

    Fixes-Bug: 1535799
    Change-Id: I6c8c1101771d1c5496884be7a405285472ae803a
    (cherry picked from commit e62a5e1df872e332062f4d4efd6c9ef2ee4db1dd)

tags: added: in-stable-liberty
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (master)

Reviewed: https://review.openstack.org/269739
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=ba6fb27bc874b940a2a8a34e24a6c34ecabb3ba8
Submitter: Jenkins
Branch: master

commit ba6fb27bc874b940a2a8a34e24a6c34ecabb3ba8
Author: Clark Boylan <email address hidden>
Date: Tue Jan 19 08:15:36 2016 -0800

    Remove vme and ssse3 from gate64 cpu mapping

    It turns out that we need to be even more restrictive on the cpu flags
    we expose as some clouds don't expose vme or ssse3.

    Fixes-Bug: 1535799
    Change-Id: I6c8c1101771d1c5496884be7a405285472ae803a

Changed in devstack:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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