release notes are not taken into account during TOX

Bug #1781239 reported by Shilpa Devharakar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
masakari-monitors
Fix Released
Undecided
Shilpa Devharakar

Bug Description

Description
===========

Release notes documentation seems to be broken.

After running 'tox -ereleasenotes', TOX gets succeeded but release note/s for
previous releases are not taken into account.

Steps to reproduce
==================
1. Pull current master for masakari-monitors
2. Run 'tox -ereleasenotes'

Expected result
===============
After running 'tox -ereleasenotes', previous release notes should be taken
into account, and below entry should be there on console.

[reno.scanner] 081e74dfaf78fe99: adding releasenotes/notes/pythonize-monitors-081e74dfaf78fe99.yaml from 3.0.1

Actual result
=============
After running 'tox -ereleasenotes', TOX gets succeeded but below release not is not considered for [reno] scanning
https://github.com/openstack/masakari-monitors/blob/master/releasenotes/notes/pythonize-monitors-081e74dfaf78fe99.yaml

Logs
=====
openstack@openstack-VirtualBox:/opt/stack/masakari-monitors$ tox -e releasenotes
releasenotes create: /opt/stack/masakari-monitors/.tox/releasenotes
releasenotes installdeps: -r/opt/stack/masakari-monitors/test-requirements.txt
releasenotes develop-inst: /opt/stack/masakari-monitors
releasenotes installed: alabaster==0.7.11,appdirs==1.4.3,asn1crypto==0.24.0,Babel==2.6.0,certifi==2018.4.16,cffi==1.11.5,chardet==3.0.4,cliff==2.13.0,cmd2==0.8.8,contextlib2==0.5.5,coverage==4.5.1,cryptography==2.2.2,debtcollector==1.19.0,decorator==4.3.0,deprecation==2.0.5,docutils==0.14,dogpile.cache==0.6.6,dulwich==0.19.5,enum-compat==0.0.2,enum34==1.1.6,eventlet==0.20.0,extras==1.0.0,fasteners==0.14.1,fixtures==3.0.0,flake8==2.5.5,funcsigs==1.0.2,functools32==3.2.3.post2,future==0.16.0,futures==3.2.0,greenlet==0.4.13,hacking==0.11.0,idna==2.7,imagesize==1.0.0,ipaddress==1.0.22,iso8601==0.1.12,Jinja2==2.10,jmespath==0.9.3,jsonpatch==1.23,jsonpointer==2.0,jsonschema==2.6.0,keystoneauth1==3.9.0,libvirt-python==4.4.0,linecache2==1.0.0,MarkupSafe==1.0,-e git+https://github.com/openstack/masakari-monitors.git@26d558333d9731ca06da09b26fe6592c49c0ac8a#egg=masakari_monitors,mccabe==0.2.1,mock==2.0.0,monotonic==1.5,mox3==0.25.0,msgpack==0.5.6,munch==2.3.2,netaddr==0.7.19,netifaces==0.10.7,openstacksdk==0.15.0,os-client-config==1.31.2,os-service-types==1.2.0,os-testr==1.0.0,osc-lib==1.10.0,oslo.concurrency==3.27.0,oslo.config==6.3.0,oslo.context==2.21.0,oslo.i18n==3.20.0,oslo.log==3.39.0,oslo.middleware==3.35.0,oslo.privsep==1.29.0,oslo.serialization==2.27.0,oslo.service==1.31.2,oslo.utils==3.36.3,oslosphinx==4.18.0,oslotest==3.6.0,packaging==17.1,Paste==2.0.3,PasteDeploy==1.5.2,pbr==4.1.0,pep8==1.5.7,prettytable==0.7.2,pycparser==2.18,pyflakes==0.8.1,Pygments==2.2.0,pyinotify==0.9.6,pyOpenSSL==18.0.0,pyparsing==2.2.0,pyperclip==1.6.2,python-cinderclient==3.6.1,python-dateutil==2.7.3,python-glanceclient==2.11.1,python-keystoneclient==3.17.0,python-mimeparse==1.6.0,python-novaclient==10.3.0,python-openstackclient==3.15.0,python-subunit==1.3.0,pytz==2018.5,PyYAML==3.13,reno==2.9.2,repoze.lru==0.7,requests==2.19.1,requestsexceptions==1.4.0,rfc3986==1.1.0,Routes==2.4.1,simplejson==3.16.0,six==1.11.0,snowballstemmer==1.2.1,Sphinx==1.7.5,sphinxcontrib-websupport==1.1.0,statsd==3.2.2,stestr==2.1.0,stevedore==1.28.0,subprocess32==3.5.2,testrepository==0.0.20,testscenarios==0.5.0,testtools==2.3.0,traceback2==1.4.0,typing==3.6.4,unicodecsv==0.14.1,unittest2==1.1.0,urllib3==1.23,voluptuous==0.11.1,warlock==1.3.0,wcwidth==0.1.7,WebOb==1.8.2,wrapt==1.10.11
releasenotes runtests: PYTHONHASHSEED='1198691960'
releasenotes runtests: commands[0] | sphinx-build -a -E -W -d releasenotes/build/doctrees -b html releasenotes/source releasenotes/build/html
Running Sphinx v1.7.5
making output directory...
Using openstack theme from /opt/stack/masakari-monitors/.tox/releasenotes/local/lib/python2.7/site-packages/oslosphinx/theme
building [mo]: all of 0 po files
building [html]: all source files
updating environment: 2 added, 0 changed, 0 removed
reading sources... [ 50%] index
reading sources... [100%] unreleased
[reno.config] no configuration file in: /opt/stack/masakari-monitors/releasenotes/config.yaml, /opt/stack/masakari-monitors/reno.yaml
[reno] scanning /opt/stack/masakari-monitors/releasenotes/notes for current branch release notes
[reno.scanner] scanning /opt/stack/masakari-monitors/releasenotes/notes (branch=*current* earliest_version=None collapse_pre_releases=True)
[reno.scanner] found ref 'master' as 'refs/heads/master' at 26d558333d9731ca06da09b26fe6592c49c0ac8a
[reno.scanner] found ref u'stable/queens' as u'refs/remotes/origin/stable/queens' at e6ecb5623214d88bbe36e038f2a398743b436726
[reno.scanner] looking at 5.0.0 at base of stable/queens to stop scanning the current branch
[reno.scanner] earliest version to include is 4.0.0.0rc1
[reno.scanner] stopping scan at 5.0.0
[reno.scanner] 000001 26d558333d9731ca06da09b26fe6592c49c0ac8a updating current version to 6.0.0.0b2
[reno.scanner] 000003 34d185deeee6118b373715c2567324010465a94b updating current version to 6.0.0.0b1
[reno.scanner] 000007 41653bc9535b2eef278153b59b6a662b6ee1083d updating current version to 5.0.0
[reno.scanner] reached end of branch after 7 commits at 41653bc9535b2eef278153b59b6a662b6ee1083d with tags [u'5.0.0']
[reno] got versions []

looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [ 50%] index
writing output... [100%] unreleased

generating indices... genindex
writing additional pages... search
copying static files... done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded.

The HTML pages are in releasenotes/build/html.
_______________________________________ summary _______________________________________
  releasenotes: commands succeeded
  congratulations :)

Changed in masakari-monitors:
assignee: nobody → Shilpa Devharakar (shilpasd)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to masakari-monitors (master)

Fix proposed to branch: master
Review: https://review.openstack.org/582457

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

Reviewed: https://review.openstack.org/582457
Committed: https://git.openstack.org/cgit/openstack/masakari-monitors/commit/?id=22925f1ee688822d62f232614020f99ba1813dd7
Submitter: Zuul
Branch: master

commit 22925f1ee688822d62f232614020f99ba1813dd7
Author: shilpa.devharakar <email address hidden>
Date: Wed Jul 11 21:31:09 2018 +0530

    Fix stable branch releasenotes

    This patch fixes stable branch releasenotes by adding respective source
    files.

    Change-Id: I2cbeb3fd324e16d10ed8f3945a67849cad914f0e
    Closes-Bug: #1781239

Changed in masakari-monitors:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/masakari-monitors 6.0.0.0b3

This issue was fixed in the openstack/masakari-monitors 6.0.0.0b3 development milestone.

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.