Bug 1056381
| Summary: | [RFE][nova]: Disable file injection by default | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | RHOS Integration <rhos-integ> | |
| Component: | openstack-nova | Assignee: | RHOS Maint <rhos-maint> | |
| Status: | CLOSED ERRATA | QA Contact: | Ami Jeain <ajeain> | |
| Severity: | low | Docs Contact: | ||
| Priority: | low | |||
| Version: | unspecified | CC: | markmc, ndipanov, sgordon, slong, vpopovic, yeylon | |
| Target Milestone: | Upstream M3 | Keywords: | FutureFeature | |
| Target Release: | 5.0 (RHEL 7) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| URL: | https://blueprints.launchpad.net/nova/+spec/disable-file-injection-by-default | |||
| Whiteboard: | upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved | |||
| Fixed In Version: | openstack-nova-2014.1-3.el7ost | Doc Type: | Deprecated Functionality | |
| Doc Text: |
File injection into VM images is now deprecated; instead, Red Hat recommends that you use the ConfigDrive and metadata server facilities to modify guests at launch.
File injection is now disabled by default in OpenStack Compute. To enable file injection, modify the inject_key and inject_partition configuration keys in /etc/nova/nova.conf and restart the Compute services. Note that the file-injection mechanism will probably be disabled in a future release.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1082398 (view as bug list) | Environment: | ||
| Last Closed: | 2014-07-08 15:28:02 UTC | Type: | --- | |
| 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: | ||||
| Bug Blocks: | 1082398 | |||
|
Description
RHOS Integration
2014-01-22 05:04:06 UTC
Updating based on BP milestone 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. http://rhn.redhat.com/errata/RHEA-2014-0853.html |