We have a weird behavior of the lpassigner.py script

Bug #1498015 reported by Andrey Nikitin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Alexander Lomski

Bug Description

Hello!

We have a weird behavior of lpassigner.py script which implemented on Custom scripts infrastructure. For example, we have a list with bugs not assigned correctly (https://custom-scripts.infra.mirantis.net/job/lp-assigner/104/console):

https://bugs.launchpad.net/bugs/1497965
https://bugs.launchpad.net/bugs/1497608.

So, this situation should be investigated and script should be updated (if it's needed) to fix the problem.

Andrey Nikitin (heos)
summary: - We have a weird behavior if the lpassigner.py script
+ We have a weird behavior of the lpassigner.py script
Changed in fuel:
status: New → Triaged
Dmitry Pyzhov (dpyzhov)
tags: added: area-devops
Igor Shishkin (teran)
tags: added: area-tools
removed: area-devops
tags: added: area-infra-apps
removed: area-tools
Changed in fuel:
assignee: Fuel DevOps (fuel-devops) → Aleh Malafei (marfx000)
information type: Private → Public
Changed in fuel:
importance: High → Medium
Changed in fuel:
assignee: Aleh Malafei (marfx000) → Alexander Lomski (aliaksandr-lomski)
Revision history for this message
Alexander Lomski (aliaksandr-lomski) wrote :

Unfortunately, the referenced console log has expired long ago - is there a more recent example or a description of script's abnormal behaviour?

Revision history for this message
Andrey Nikitin (heos) wrote :

Unfortunately, I have no more debug information. I think, we can investigate it, when that job will be run again. So, current bug can be marked as Incomplete and assigned on Fuel Devops team to get more information.

Revision history for this message
Alexander Lomski (aliaksandr-lomski) wrote :

Can you change the bug then? I do not have permissions to assign it to devops team.

Revision history for this message
Andrey Nikitin (heos) wrote :

I have additional information about the script from the mail thread with the subject "FYI Fuel McRobotson script is now active":

1. First of all, this script shouldn't use 'future' branche to target the bugs - We must attempt to fix all bugs in 9.0, and not making a decision now that some of the bugs should wait for a bright "future".
2. Many bugs that were fix committed or fix released are now proposed to Next release as New. That's not going to be the case. QA should be the only group to drop a bug out of fix committed or fix released state (or if we find a very obvious regression through another bug report)
3. Priority should remain the same as 8.0 as it does in 9.0/mitaka, not "undecided".

Changed in fuel:
status: Triaged → In Progress
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

Moving to High because we need the script running for 8.0 on regular basis. And this bug blocks it.

Changed in fuel:
importance: Medium → High
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix merged to tools/custom-scripts (master)

Reviewed: https://review.fuel-infra.org/15976
Submitter: Alexander Charykov <email address hidden>
Branch: master

Commit: 80cfcc9d9cb59a39e9c9edee8e2e104e8134f260
Author: Alexander Lomski <email address hidden>
Date: Thu Jan 21 14:53:52 2016

Improved milestone/series version comparison.

Bugs with "Fix Committed" and "Fix Released" status will not change status
when targeting to a new series/milestone.

Bugs will retain their importance.

Version sorting for milestones/series has been exported to a new library which
correctly compares versions for Launchpad `MOS` and `Fuel` projects (including
Fuel new version names like "mitaka" etc). This should also get resolve any
issues with "future" being targeted.

Change-Id: Id1a592a4821ea39cb0b32fc3c80d6a1b5dc15ce6
Closes-Bug: #1498015

Changed in fuel:
status: In Progress → Fix Committed
Andrey Nikitin (heos)
Changed in fuel:
status: Fix Committed → Fix Released
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.