placement could not be started

Bug #1833497 reported by zhipeng liu
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
High
zhipeng liu

Bug Description

Brief Description
-----------------
placement pod will not be started
Root cause is in patch merged in Jun. 13th
https://review.opendev.org/#/c/653932/
It override below
openstack-compute-kit',
                    },
                    'data': {
                        'chart_group': [
                            'openstack-libvirt',
                            'openstack-openvswitch',
                            'openstack-nova',
                            'openstack-nova-api-proxy',
                            'openstack-neutron',
                        ]

Need add placement back to this chart_group, otherwise placement pod could not be restarted

zhipeng liu (zhipengs)
Changed in starlingx:
assignee: nobody → zhipeng liu (zhipengs)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (master)

Fix proposed to branch: master
Review: https://review.opendev.org/666491

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

Reviewed: https://review.opendev.org/666491
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=62165b4a2945236d38713856c4fc440a57c15779
Submitter: Zuul
Branch: master

commit 62165b4a2945236d38713856c4fc440a57c15779
Author: zhipengl <email address hidden>
Date: Thu Jun 20 22:32:37 2019 +0800

    Fix placement PO could not be started issue

    placement po will not be started
    Root cause is in below patch
    https://review.opendev.org/#/c/653932/
    It overrides openstack-compute-kit group which do not include
    openstack-placement.

    Below basic test pass
    1) Deploy simplex setup
    2) Create VM

    Change-Id: I668561955cc7c84c87a0cfd3178be5a5ffeed883
    Closes-Bug: #1833497
    Signed-off-by: zhipengl <email address hidden>

Changed in starlingx:
status: In Progress → Fix Released
Ghada Khalil (gkhalil)
Changed in starlingx:
importance: Undecided → Critical
tags: added: stx.2.0 stx.containers
description: updated
Revision history for this message
Ghada Khalil (gkhalil) wrote :

Marking as release gating; this would cause the stx-openstack application apply to fail if the vswitch_type = none (ex: in virtual environments).

Changed in starlingx:
importance: Critical → High
Revision history for this message
Ghada Khalil (gkhalil) wrote :

Correction: It appears that the application apply will succeed, but VM operations will fail as the placement service pod is not running

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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