Last modified: 2012-10-06 18:30:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T42740, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 40740 - i-0000049c / integration-wikibugs unreachable
i-0000049c / integration-wikibugs unreachable
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-03 13:13 UTC by Antoine "hashar" Musso (WMF)
Modified: 2012-10-06 18:30 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Antoine "hashar" Musso (WMF) 2012-10-03 13:13:28 UTC
I have created the instance i-0000049c / integration-wikibugs and it is still unreacheable network wise despite it being listed as "active".

The assigned IP address is 10.4.0.249 and is not reacheable from bastion1:

hashar@bastion1:~$ host integration-wikibugs.pmtpa.wmflabs
integration-wikibugs.pmtpa.wmflabs has address 10.4.0.249

hashar@bastion1:~$ ping 10.4.0.249
PING 10.4.0.249 (10.4.0.249) 56(84) bytes of data.
From 10.4.0.54 icmp_seq=1 Destination Host Unreachable
From 10.4.0.54 icmp_seq=2 Destination Host Unreachable
From 10.4.0.54 icmp_seq=3 Destination Host Unreachable
From 10.4.0.54 icmp_seq=5 Destination Host Unreachable
Comment 1 Ryan Lane 2012-10-04 22:40:03 UTC
Was this instance ever reachable? It's primary disk looks like it isn't a valid disk....

If this instance never came up, just delete it and recreate it.
Comment 2 Ryan Lane 2012-10-04 22:42:46 UTC
I see the problem now. The kernel image and loader image for lucid show up in the image list for creation. They shouldn't. The kernel image was used to build the instance, and that doesn't work.
Comment 3 Antoine "hashar" Musso (WMF) 2012-10-06 08:59:37 UTC
graaa. What is the point of the kernel images despite confusing the newbie I am ? :-]

I have deleted the i-0000049c instance and created i-000004af using the same name. Worked fine :)
Comment 4 Ryan Lane 2012-10-06 18:30:51 UTC
They shouldn't be there. I'm going to make them disappear from the list when I get a chance.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links