[00:16] alright, utlemming uploaded. [00:17] i kind of am planning on doing an 0.7.4 release to just tie this fix in and anything else that flushes out in the nexst 36 hours. [01:26] smoser: ack [02:05] utlemming, it just made it through [02:05] so please get builds in if you can [12:35] Running 2 OS, in the same OpenStack system, Ubuntu gets the userdata through Ec2 and the other OS doesn't receive anything.. [13:34] I've got the two log files: [13:35] -Ubuntu: http://paste.ubuntu.com/6209011/ [13:35] -The other: http://paste.ubuntu.com/6209024/ [13:49] I even downgraded my cloud-init version to 0.7.2, but still not working [13:53] neat that btrfs resize worked. that was mostly theoretical [13:53] :) [13:55] :) [13:59] Oct 08 11:15:33 baserock cloud-init[196]: [CLOUDINIT] __init__.py[DEBUG]: Searching for data source in: ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet', 'DataSourceAltCloud', 'DataSourceOVFNet', 'DataSourceNone'] [13:59] that is your problem [14:01] i'm not sure whats causing it, but for some reason its not looknig for the DataSourceEc2, while it seems like you've configured that. [14:01] Oct 08 11:15:33 baserock cloud-init[196]: [CLOUDINIT] __init__.py[DEBUG]: Looking for for data source in: ['NoCloud', 'ConfigDrive', 'AltCloud', 'OVF', 'MAAS', 'Ec2', 'None'], via packages ['', 'cloudinit.sources'] that matches dependencies ['FILESYSTEM', 'NETWORK'] [14:02] That's exactly what I was checking right now [14:03] yes, it is on my cfg file: datasource_list: [ NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, None ] [14:09] smoser: there is a module called "disable-ec2-metadata" [14:11] I have tried to make it works with and without it [14:21] Seems like the importer can't import it: importer.py[DEBUG]: Found DataSourceEc2 with attributes ['get_datasource_list'] in [] [14:23] pedroalvarez, disable-ec2-metdata not related. [14:24] well... disable-ec2-metadata would most certainly disable your ec2metadata [14:24] pedroalvarez, what is your python version ? [14:25] smoser: Python 2.7.2 [14:26] and I have already disabled the "disable-ec2-metadata" module [14:26] that wont affect cloud-init [14:26] that runs late in the boot process [14:26] and if it is enabled by user data [14:26] then it routes the url off [14:26] Is the python version enough? [14:26] i think so [14:27] i thought it might have an issue if it was 2.6 or 2.6 [14:27] err 2.5 [14:28] smoser: I could try using configDrive instead Ec2, but I don't know how to configure OpenStack to do it [14:29] no. yo ushoudl fix ec2. [14:30] i'm not sure why you're not finding that datasource, though. [14:30] can you let me into an instance? [14:31] It's not visible from outside I think [14:31] Let me ask [14:40] I can't, but maybe I can try to upload it to a free Openstack online [14:40] (trystack) [15:01] hmm.. do you know another alternative than trystack? [15:11] pedroalvarez, i dont know. [15:11] you could put it on amazon [15:12] oh, or even do a devstack *in* amazon [15:12] or tunnel out of theinstance [15:31] can you let me into the bootstrap node ? [15:31] ssh-import-id smoser [16:18] smoser: found the problem I think. I didn't import boto, essential for run Ec2. I will let you know. Thanks [16:19] hum.. i'd have thoguht we'd see a traceback log there. [16:19] maybe there was on the consoel [16:21] there isn't: [16:21] except ImportError: [16:21] pass [16:22] boooo [16:23] Solution: [16:23] except ImportError, e: [16:23] LOG.debug("Failed to import %s: %r", full_path, e) [16:24] i'd use util.logexc [16:24] but yeah [20:10] harlowja, pedroalvarez hit a but that was hidden somewhat by the fact that the datasource loader hides import errors [20:45] :-/ [20:45] hmmm [21:19] so the datsource loading [21:19] tried to load ddatasourceec2 [21:19] which eneeded boto [21:19] and so tboto import-errored [21:19] and then the laoder just swallowd that up. [21:20] so i couldn't figure out from his log why he wasn't seeing the datasource ec2 (or attempting to use it) [22:03] hmmm [22:03] ya durn imports of imports failing [22:03] those are tough ones [22:03] maybe we should log something at least [22:04] maybe to start a debug message [22:04] around try: [22:04] mod = import_module(full_path) [22:04] except ImportError: [22:04] pass [22:07] except its hard to tell the difference between import not existing (which might be ok) and import having a dependency that is failing [22:07] both come out as import errors