Relnotes for Pike contains an entry from a past release
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Akihiro Motoki |
Bug Description
https:/
The solution for this is to use 'ignore-notes' directive option from reno. This is available since reno 2.5.0.
Note that reverting the patch does not solve the problem as reno still considers a relnote updated in the master branch
This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:
- [X] This doc is inaccurate in this way: ______
- [ ] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: input and output.
If you have a troubleshooting or support issue, use the following resources:
- Ask OpenStack: http://
- The mailing list: http://
- IRC: 'openstack' channel on Freenode
-------
Release: 11.0.0.0b4.dev37 on 2017-08-03 22:11
SHA: 8f79a92e45c8481
Source: https:/
URL: https:/
Changed in neutron: | |
importance: | Undecided → High |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
this seems like the same problem as bug 1682776.
i thought reno was supposed to handle updates of release notes. isn't it the case?