byobu hangs when ec2 metadata api is blocked
Bug #1071287 reported by
Tristan Slominski
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| byobu |
Fix Released
|
Medium
|
Dustin Kirkland | ||
Bug Description
On EC2 Ubuntu 12.04 instance created from: ami-3d4ff254 (us-east-1, 64-bit, ebs)
~$ /usr/bin/sudo /sbin/iptables -A OUTPUT -d 169.254.169.254 -j DROP
~$ byobu
at this point, byobu will hang (sometimes it starts, sometimes it doesn't)
| description: | updated |
| Changed in byobu: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Dustin Kirkland (kirkland) |
Revision history for this message
| Dustin Kirkland (kirkland) wrote | #1 |
| Changed in byobu: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Dustin Kirkland (kirkland) wrote | #2 |
| Changed in byobu: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Tristan Slominski (tristan-slominski) wrote | #3 |
| Changed in byobu: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
So if, after you block the metadata service you also remove the flag ~/.byobu/
The problem is when byobu launches once when metadata is available, and then launches or runs some other time when it's *not* available, but the cached flag still exists.