| Summary: | Fedora Cloud Image Problem (ami-5f16d836) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Scott Weigand <sweigand> | ||||
| Component: | distribution | Assignee: | Justin M. Forbes <jforbes> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Bill Nottingham <notting> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 16 | CC: | dennis, jforbes, paulej, rvokal | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-02-13 14:56:29 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Sorry about the delayed response - does this still happen? Yep, still happening. I'm using a US-East-1c Zone, Small Implementation (1.7gb). It hangs at setting hostname (sometimes localhost.localdomain, sometimes the IP address). Just to provide an update, I worked with Ryan@AWS and the end-solution was to disable SELinux. I mounted the volume as a secondary on another instance, disabled SELinux, and remounted to the original instance. As much as SELinux is a great feature, I have found (in my experience) that it causes more problems than it fixes. I am suffering from the same issue, but disabling SELinux did not resolve the problem. I try to start an instance of Fedora 16 and I cannot connect to it. The machine will not respond to a ping (even from another EC2 instance in the same availability zone). I followed the instructions Ryan@AWS provided, disabling SELinux and re-starting the instance, but it was still unresponsive. I'm also trying to start a 32-but small instance. After more experimentation, it seems to be an availability zone issue. I was able to launch the 64-bit instances in the availability zone, but not the 32-bit instances. I then moved to a different availability zone and the 32-bit instance started just fine. I tested all availability zones and the 32-bit image will start just fine in all but the availability zone I was testing. My luck... I would suggest closing this bug now that Fedora is nearly two release down the road. I am no longer able to try to reproduce it now and 64-bit images definitely present no issues. I've not tried 32-bit images since reporting this issue. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 538604 [details] System Log from 2011-11-30 Description of problem: While spinning up an Amazon EC2 Fedora 16 AMI (ami-5f16d836), the system hangs while booting up. System hangs at [ 3.889032] systemd[1]: Set hostname to <localhost.localdomain>. Version-Release number of selected component (if applicable): Fedora 16 AMI (ami-5f16d836), no updates. How reproducible: Should be reproducible. Steps to Reproduce: 1. Created a Fedora 16 AMI (ami-5f16d836) instance 2. Check System Logs via Amazon Web Services (AWS) Console 3. System hanging Actual results: System is hanging. Expected results: Should be awaiting login. Additional info: Attached a copy of the system log, maybe I missed something.