DeprecationWarnings that had to be corrected in Juno release
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Low
|
Unassigned |
Bug Description
When I run tox -epy27, I get next DeprecationWarn
heat/engine/
'release.', DeprecationWarning)
heat/engine/
'release.', DeprecationWarning)
heat/engine/
'release.', DeprecationWarning)
heat/engine/
'release.', DeprecationWarning)
heat/engine/
'release.', DeprecationWarning)
Also, beside these warnings there are another DeprecationWarn
heat/engine/
warnings.
heat/engine/
warnings.
heat/engine/
warnings.
heat/engine/
warnings.
How do you think:
1) whether it is time to correct DeprecationWarnings of Juno release?
2) Is there any reason not to correct other DeprecationWarn
Changed in heat: | |
assignee: | nobody → Razumovsky Peter (prazumovsky) |
Changed in heat: | |
assignee: | Razumovsky Peter (prazumovsky) → nobody |
Changed in heat: | |
status: | In Progress → Triaged |
Changed in heat: | |
importance: | Undecided → Low |
We should've removed the "instance_user" option in Juno like we said we would, so I guess the only thing to do is to remove it in Kilo, e.g now.
For the CWLiteAlarm warning, I don't think there is anything to do, as we're not ready to remove that resource yet.