stx4.0 openstack application apply stuck

Bug #1892830 reported by Austin Sun
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
High
Austin Sun

Bug Description

Brief Description
-----------------
When openstack application apply, the apply is stucking as sysinv crash
Severity
--------
Provide the severity of the defect.
<Critical: System/Feature is not usable due to the defect>
<Major: System/Feature is usable but degraded>
<Minor: System/Feature is usable with minor issue>

Steps to Reproduce
------------------

application apply get stuck as sysinv crash.

Expected Behavior
------------------
The application apply successfully

Actual Behavior
----------------
get stuck and apply failed

Reproducibility
---------------
<Reproducible/Intermittent/Seen once>
State if the issue is 100% reproducible, intermittent or seen once. If it is intermittent, state the frequency of occurrence

System Configuration
--------------------
<One node system, Two node system, Multi-node system, Dedicated storage, https, IPv4, IPv6 etc.>

Branch/Pull Time/Commit
-----------------------
Branch and the time when code was pulled or git commit or cengn load info
Stx.4.0 and master
Last Pass
---------
Customer
Timestamp/Logs
--------------
Test Activity
-------------
Other

Workaround
----------

Revision history for this message
Austin Sun (sunausti) wrote :
Changed in starlingx:
importance: Undecided → High
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/747859

Changed in starlingx:
status: New → In Progress
Ghada Khalil (gkhalil)
tags: added: not-yet-in-r-stx40 stx.4.0 stx.5.0 stx.distro.openstack
Revision history for this message
Ghada Khalil (gkhalil) wrote :

stx.4.0 as Austin created this as a high priority bug

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

Reviewed: https://review.opendev.org/747859
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=552b4e01716011ae35b6364716b84f66551adacc
Submitter: Zuul
Branch: master

commit 552b4e01716011ae35b6364716b84f66551adacc
Author: Austin Sun <email address hidden>
Date: Tue Aug 25 23:10:43 2020 +0800

    Application applied failed due to wrong attribute 'id'

    Fault Class/Object only has alarm_id, not id which cause sysinv crash
    like "AttributeError: 'Fault' object has no attribute 'id'"

    Change-Id: I4aaefc764f5fa13842cd60ee99752e497a3fd439
    Closes-bug: 1892830
    Signed-off-by: Austin Sun <email address hidden>

Changed in starlingx:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (r/stx.4.0)

Fix proposed to branch: r/stx.4.0
Review: https://review.opendev.org/749428

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (r/stx.4.0)

Reviewed: https://review.opendev.org/749428
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=b8cf1c2a2e032fa82ba9e51139d7cb124a3f741c
Submitter: Zuul
Branch: r/stx.4.0

commit b8cf1c2a2e032fa82ba9e51139d7cb124a3f741c
Author: Austin Sun <email address hidden>
Date: Tue Aug 25 23:10:43 2020 +0800

    Application applied failed due to wrong attribute 'id'

    Fault Class/Object only has alarm_id, not id which cause sysinv crash
    like "AttributeError: 'Fault' object has no attribute 'id'"

    Change-Id: I4aaefc764f5fa13842cd60ee99752e497a3fd439
    Closes-bug: 1892830
    Signed-off-by: Austin Sun <email address hidden>
    (cherry picked from commit 552b4e01716011ae35b6364716b84f66551adacc)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on config (r/stx.4.0)

Change abandoned by "Al Bailey <email address hidden>" on branch: r/stx.4.0
Review: https://review.opendev.org/c/starlingx/config/+/774182
Reason: Abandoning since no activity in over 6 months

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.