Bug 1417425

Summary: Release note script is not handling well "No Doc Update" category
Product: [oVirt] ovirt-distribution Reporter: Sandro Bonazzola <sbonazzo>
Component: GeneralAssignee: Rafael Martins <rmartins>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: bugs
Target Milestone: ovirt-4.1.1Flags: rule-engine: ovirt-4.1+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-12 16:10:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sandro Bonazzola 2017-01-29 05:59:47 UTC
Example from 4.1.0 release notes:

No Doc Update
oVirt Engine
Team: SLA

    BZ 1346669 Can't start a VM (NPE around scheduling.SchedulingManager.selectBestHost(SchedulingManager.java:434) )
    undefined

The line with "undefined" shouldn't be added: just the list of BZs is enough there.

Comment 1 Yaniv Kaul 2017-02-12 16:10:02 UTC
I think I've fixed it with https://gerrit.ovirt.org/#/c/72048/ .

Comment 2 Rafael Martins 2017-02-13 11:40:14 UTC
(In reply to Yaniv Kaul from comment #1)
> I think I've fixed it with https://gerrit.ovirt.org/#/c/72048/ .

Hi Yaniv,

I think that this bug is related to the release_notes_git.py script. At least I was able to reproduce the issue with it. Not sure if we are using the release_notes.py script yet.

I'm looking at consolidating the scripts we have and port the functionality you implemented to the git based script.

Thanks.
Rafael

Comment 3 Rafael Martins 2017-02-13 11:48:01 UTC
(In reply to Rafael Martins from comment #2)
> (In reply to Yaniv Kaul from comment #1)
> > I think I've fixed it with https://gerrit.ovirt.org/#/c/72048/ .
> 
> Hi Yaniv,
> 
> I think that this bug is related to the release_notes_git.py script. At
> least I was able to reproduce the issue with it. Not sure if we are using
> the release_notes.py script yet.

I meant: Not sure if we are still using the release_notes.py script.

> I'm looking at consolidating the scripts we have and port the functionality
> you implemented to the git based script.
> 
> Thanks.
> Rafael