| Summary: | cloud-init scripts do not make hostname changes permanent in /etc/sysconfig/network | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joseph W. Breu <joseph.breu> |
| Component: | cloud-init | Assignee: | Garrett Holmstrom <gholms> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | gholms |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cloud-init-0.6.3-0.1.bzr532.fc16 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-03-17 23:38:06 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Joseph W. Breu
2011-11-03 04:56:39 UTC
Storing a value in /etc/hostname is the correct method for persisting the hostname of a system that runs systemd, which consults /etc/sysconfig/network only as a fallback when /etc/hostname does not exist. What problem are you trying to solve? Are hostnames given in cloud-config not persisting properly? The main cause of this problem seems to be a bug in systemd's transaction ordering that has since been fixed. Since Fedora's EC2 image uses packages from the release without updates, this bug will still occur until a new image is created. Even when that problem is fixed, however, there is another bug that may prevent this from working: /usr/bin/cloud-init returns with the wrong code on EC2, which does not affect upstream's upstart tasks but *does* affect Fedora's systemd units. This was recently fixed with code that should appear in the next update. Sorry for the wait. cloud-init-0.6.3-0.1.bzr532.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/cloud-init-0.6.3-0.1.bzr532.fc17 cloud-init-0.6.3-0.1.bzr532.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/cloud-init-0.6.3-0.1.bzr532.fc16 Package cloud-init-0.6.3-0.1.bzr532.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing cloud-init-0.6.3-0.1.bzr532.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-3330/cloud-init-0.6.3-0.1.bzr532.fc16 then log in and leave karma (feedback). cloud-init-0.6.3-0.1.bzr532.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. cloud-init-0.6.3-0.1.bzr532.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |