[Ironic] fix import of missing translation markers

Bug #1549868 reported by Vasyl Saienko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
In Progress
High
Vasyl Saienko
8.0.x
In Progress
High
Vasyl Saienko
9.x
Won't Fix
High
MOS Ironic

Bug Description

Due to missing import of translation markers ironicclient failed.
It can land that nova mark instance build as ERROR.

https://paste.mirantis.net/show/1911/

Vasyl Saienko (vsaienko)
Changed in mos:
milestone: none → 8.0
tags: added: area-ironic
Revision history for this message
Vasyl Saienko (vsaienko) wrote :
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix proposed to openstack/python-ironicclient (openstack-ci/fuel-8.0/liberty)

Fix proposed to branch: openstack-ci/fuel-8.0/liberty
Change author: Vasyl Saienko <email address hidden>
Review: https://review.fuel-infra.org/17567

Revision history for this message
Vasyl Saienko (vsaienko) wrote :

This issue is reproduced on scale when booting 50 Nova instances simultaneously with 100-150 active nova instances.

tags: added: scale
Changed in mos:
status: Confirmed → In Progress
Revision history for this message
Pavlo Shchelokovskyy (pshchelo) wrote :

The error happens mostly when API is unresponsive and when ironicclient is used from some automation scripts/code, like rally.

to reproduce on MOS8:

1) deploy cluster with ironic
2) stop all ironic-api services on controllers to simulate non-responsive API
3) get Ironic API endpoint
   $ openstack catalog show baremetal
4) get Keystone token
   $ openstack token issue
5) issue following command
   $ ironic --ironic-url <public-ironic-endpoint-from-step-3> --os-auth-token <token-id-from-step-4> node-list

Expected:
meaningful HTTP-related error after some timeout

Actual:
almost immediate "global name '_' is not defined"

one can also prepend --debug to ironic command to see the actual request/response interchange

Changed in mos:
assignee: MOS Ironic (mos-ironic) → Vasyl Saienko (vsaienko)
no longer affects: mos/7.0.x
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.