Bug 1624486
| Summary: | RFE: Port novajoin to support versioned notifications | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Harry Rybacki <hrybacki> |
| Component: | python-novajoin | Assignee: | Grzegorz Grasza <ggrasza> |
| Status: | CLOSED ERRATA | QA Contact: | Pavan <pkesavar> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 15.0 (Stein) | CC: | acanan, ggrasza, gregraka, jamsmith, kbasil, rcritten |
| Target Milestone: | Upstream M2 | Keywords: | FutureFeature, TechPreview, Triaged |
| Target Release: | 15.0 (Stein) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-novajoin-1.1.2-0.20190529150411.2c8c868.el8ost | Doc Type: | Technology Preview |
| Doc Text: |
As a technology preview in Red Hat OpenStack Platform 15, the novajoin service tech uses the new, versioned format of notifications sent by the Compute service (nova).
To enable the new format, set the value of the new configuration setting, configuration_format, to "versioned." The default value for configuration_format is "unversioned".
In a future version of RHOSP, unversioned notifications will be deprecated.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-09-21 11:18:54 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1730058, 1730068, 1730072, 1730076, 1732866, 1743485 | ||
| Bug Blocks: | |||
|
Description
Harry Rybacki
2018-08-31 19:15:35 UTC
Greg, I fixed the doc text - the service that implemented the new format is novajoin (this bug), not nova, which started implementing the new format a couple of releases back. For reference - nova team is looking into dropping the unversioned notifications: http://lists.openstack.org/pipermail/openstack-dev/2018-August/133071.html Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:2811 |