| paulmey | jchevalier: yep, that's the issue | 00:54 |
|---|---|---|
| paulmey | [ 59.017405] cloud-init[1306]: 2018-02-05 23:05:12,405 - util.py[WARNING]: agent command '['service', 'walinuxagent', 'start']' failed. | 00:54 |
| paulmey | I'm deploying a SUSE:SLES:12-SP2:latest vm to see if that service even exists (or maybe it's called something else) | 00:59 |
| rharper | https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1747554 | 01:01 |
| ubot5 | Ubuntu bug 1747554 in cloud-init (Ubuntu) "cloud-init status in bionic stack traces" [Undecided,New] | 01:01 |
| rharper | blackboxsw: ^^ | 01:01 |
| paulmey | jchevalier: it's called 'waagent' | 01:05 |
| paulmey | in the /etc/cloud/cloud.cfg.d/91-azure_datasource.cfg file that you created, you can add this yaml snippet to change the command it tries to execute: | 01:06 |
| paulmey | https://www.irccloud.com/pastebin/QwTiV5GT/ | 01:07 |
| paulmey | or you can also add a new file in /etc/cloud/cloud.cfg.d with this content | 01:08 |
| blackboxsw | rharper: that's fixed and landed already :/ still waiting on cloud images to build :) | 02:58 |
| * blackboxsw marks as duplicate. need to find the original | 02:58 | |
| blackboxsw | #1744796 | 02:59 |
| blackboxsw | bug #1744796 | 02:59 |
| ubot5 | bug 1744796 in cloud-init "cloud-init status traceback on successful Ec2" [Medium,Fix committed] https://launchpad.net/bugs/1744796 | 02:59 |
| Arianrhod | hi to all | 13:50 |
| Arianrhod | can i set on cloud init file a specific release for red hat SO? | 13:50 |
| Arianrhod | i found how to set user and passwd to register a vm when i create it... buit can i force to use a specific release? | 13:51 |
| smoser | Arianrhod: specific release ? | 13:58 |
| Arianrhod | yes | 13:59 |
| smoser | release of what? | 13:59 |
| Arianrhod | sorry | 13:59 |
| Arianrhod | for my new instance, that is red hat | 14:00 |
| smoser | you're wanting to tell | 14:00 |
| smoser | you're wanting to tell cloud-init what release of cloud-init ? or of redhat ? | 14:01 |
| Arianrhod | uh.. ok sorry cloud-init 0.7.9 and red hat 7.3 | 14:21 |
| Arianrhod | when i create a new instance by horizon, i add a file with an additional conf to specify user and pèassword to register the instance... i tried to use the key "release" but it tell me that "release is not a valid key" | 15:06 |
| PsyRabbit | Hi, I have a VMWare V-Cloud Director and want to use cloud init with it. What is the best way to get the meta data delivered to the VM? I'm starting from scratch and read all from the documentation... The configuration itself shoulnt be a problem I just dont understand how to get the metadata into the machine like instance id. Would be nice if someone can provide a useful link. Thanks | 16:38 |
| smoser | PsyRabbit: interesting. | 16:52 |
| smoser | we have two contributors from vmware that have focused on this, and contributed code, but i honeslyt do not know how it is all set up. | 16:53 |
| smoser | they do use the OVF datasource (a cdrom attached with ovf-environment.xml on it) | 16:53 |
| PsyRabbit | Thank you for the hint. Do you know where the code is contributed? Maybe I can figure out how they did their setup. | 17:07 |
| ybaumy | https://github.com/number5/cloud-init/tree/master/doc/sources/ovf | 17:09 |
| PsyRabbit | Thank you very much! | 17:11 |
| ybaumy | after reading a little bit i still dont get it.. i must say | 17:13 |
| ybaumy | but look at the code maybe you will figure it out | 17:13 |
| PsyRabbit | I hope so... I think they created a new VM and some external stuff communicated with the API, get the data, built the image and then the first VM start shuld be triggered via API... This will be a long night in my employers basement | 17:18 |
| smoser | PsyRabbit: if they were around, Sankar Tanguturi is stanguturi and Maitreyee Saikia is msaikia | 17:24 |
| smoser | but neither is currently here. | 17:25 |
| ybaumy | stanguturi: are you psychic? | 17:31 |
| PsyRabbit | I will look out for them... Thank you, you helped me alot. | 17:32 |
| stanguturi | ybaumy: Sorry. I didn't understand. | 17:33 |
| ybaumy | stanguturi: we were just talking about you | 17:33 |
| ybaumy | ;) | 17:33 |
| ybaumy | and then you joined | 17:33 |
| dpb1 | heh | 17:33 |
| stanguturi | ybaumy: Oh ok. Yeah about what? | 17:33 |
| stanguturi | ybaumy: May I ask the topic? | 17:33 |
| dpb1 | that might have had something to do with the email scott sent | 17:33 |
| ybaumy | dpb1: ahh ok | 17:34 |
| ybaumy | :D | 17:34 |
| dpb1 | :) | 17:34 |
| ybaumy | stanguturi: PsyRabbit has questions about ovf datasource | 17:34 |
| smoser | stanguturi: thanks for joining. | 17:35 |
| stanguturi | ybaumy: ok. will chat with PsyRabbit. | 17:35 |
| PsyRabbit | We were talking about V-Cloud Director and how to get the metadata inside. I'm starting from scratch and read all from the documentation... The configuration itself shoulnt be a problem I just dont understand how to get the metadata into the machine like instance id. smoder and ybaumy told me you did something and provided me a link to your ovf datasource | 17:35 |
| stanguturi | PsyRabbit: Have a VM with latest open-vm-tools installed and host it in V-Cloud Director. Apply the configuration spec, when the VM gets powered on, the open-vm-tools daemon picks up the necessary configuration from the hypervisor and hands over the content to cloud-init | 17:37 |
| === r-daneel_ is now known as r-daneel | ||
| === r-daneel_ is now known as r-daneel | ||
| jchevalier | Hello, I'm back with my sles cloud-init image on Azure | 21:14 |
| jchevalier | Still, I can only connect to the vm on the root user, and the script or config file given to custom-data is totally ignored | 21:16 |
| paulmey | jchevalier: did you see my messages from yesterday? | 21:17 |
| jchevalier | Hello paulmey, about the logs on azure? | 21:17 |
| paulmey | jchevalier: Add this to a .cfg file in /etc/cloud/cloud.cfg.d : https://www.irccloud.com/pastebin/QwTiV5GT/ | 21:18 |
| jchevalier | I was off a few hours, and my PC was out of battery, so I didn't got the messages unfortunately | 21:18 |
| jchevalier | Thx I'll try this now | 21:18 |
| paulmey | on SUSE, the service is named differently, so the command to start the agent needs to be slightly modified | 21:19 |
| paulmey | we should probably log a bug for the SUSE cloud-init package if that's how you installed it | 21:20 |
| jchevalier | when you say "to a config file" it has to have specific name? | 21:23 |
| jchevalier | Ok for the waagent service name | 21:23 |
| jchevalier | (my VM is booting, I crashed the last one) | 21:23 |
| paulmey | iirc, it needs to end in '.cfg' for cloud-init to pick it up | 21:25 |
| paulmey | jchevalier: 1:25 PM <paulmey> iirc, it needs to end in '.cfg' for cloud-init to pick it up | 21:25 |
| jchevalier | ok so just the .cfg is important thx | 21:26 |
| paulmey | yep: https://git.launchpad.net/cloud-init/tree/cloudinit/util.py#n946 | 21:29 |
| jchevalier | good to know | 21:30 |
| jchevalier | prep:/home/jchevalier # systemctl status waagent | 21:39 |
| jchevalier | ● waagent.service - Azure Linux Agent | 21:39 |
| jchevalier | Loaded: loaded (/usr/lib/systemd/system/waagent.service; enabled; vendor preset: disabled) | 21:39 |
| jchevalier | Active: active (running) since Tue 2018-02-06 21:32:39 UTC; 6min ago | 21:39 |
| jchevalier | waagent seems to be an available service in suse | 21:39 |
| jchevalier | is it this service you talk about paulmey? | 21:40 |
| paulmey | jchevalier: correct, but your logs from yesterday showed that cloud-init was trying to start walinuxagent instead of waagent | 21:40 |
| jchevalier | yes ok | 21:41 |
| jchevalier | I'm looking for walinuxagent in config files just in case | 21:46 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!