| smoser | dojordan: https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-ci-nightly/ | 06:34 |
|---|---|---|
| smoser | that is nightly runs. the #260 was a platform failure unrelated to cloud-init it looks like. | 06:34 |
| smoser | powersj: 2018-03-07 06:41:50,707 - tests.cloud_tests - ERROR - stage: collect for platform: lxd encountered error: 'Operation' object has no attribute 'description' | 06:42 |
| smoser | that make any sense to you ? | 06:42 |
| powersj | uhhh no | 06:42 |
| smoser | http://paste.ubuntu.com/p/64jsHzV4bh/ | 06:44 |
| powersj | lxd 3.0.0.beta3 | 06:45 |
| * smoser recreates tox | 06:45 | |
| smoser | yeah. | 06:45 |
| powersj | how long have you been running 3.0? | 06:45 |
| powersj | I'm wondering if pylxd and lxd are out of sync again | 06:45 |
| smoser | i have no idea, but that was my first question too | 06:45 |
| smoser | do3meli: you there ? | 08:44 |
| do3meli | smose: sure i am ;-) | 08:47 |
| smoser | we have a integration test harness | 08:49 |
| smoser | and it has a salt minion test. | 08:49 |
| smoser | it does not run by default, but is currently failing | 08:49 |
| smoser | before i merged your changes i wanted to make sure that it was running (which is how i found it fails) | 08:49 |
| smoser | we dont run it by default because (I think) we did not want to depend on 3rd party | 08:49 |
| smoser | so... | 08:50 |
| smoser | what i'm asking is that we need to kind of get that sorted, and verify that your change will work (or should work) with theintegration tets | 08:50 |
| smoser | would you be interested in taking a look at that ? i can point you at how to run and suc. | 08:50 |
| smoser | a vm with ubuntu and lxd is the easiest way to set up that environment | 08:51 |
| * smoser wonders if he scared do3meli away | 08:52 | |
| do3meli | haha. no still here. no worries. | 08:57 |
| do3meli | i am happy to help with that integration test but would require you to point me into the right direction: a) in which file are those tests define? b) ho to run the integration test? and c) are there any docs describing how to setup an integration test env? | 09:01 |
| smoser | do3meli: http://cloudinit.readthedocs.io/en/latest/topics/tests.html | 09:02 |
| smoser | that is the doc we have on interation test. | 09:02 |
| smoser | i just ran | 09:03 |
| smoser | tox-venv citest python3 -m tests.cloud_tests run --platform=lxd --os-name=xenial --preserve-data --data-dir=results.lxd.d --verbose --test=tests/cloud_tests/testcases/modules/salt_minion.py | 09:03 |
| smoser | and saw the failure | 09:03 |
| smoser | 'tox-venv' is in ./tools/ but it is basically just a "run this command in the tox venv". you could also do... | 09:03 |
| smoser | tox -e citest run --platform=lxd --os-name=xenial --preserve-data --data-dir=results.lxd.d --verbose --test=tests/cloud_tests/testcases/modules/salt_minion.py | 09:03 |
| smoser | oh. in order to *run* that test you have to http://paste.ubuntu.com/p/FVF8VvPkcY/ | 09:04 |
| do3meli | smoser: you run this command in a freshly new installed ubuntu vm after cloning the git. is that correct? | 09:05 |
| do3meli | which ubuntu vm image did you use? cloud? server? desktop? | 09:11 |
| smoser | do3meli: well you could | 09:12 |
| smoser | i would use an ubuntu cloud image. but youc an do the install for sure. | 09:12 |
| smoser | h... | 09:12 |
| do3meli | ok. let me try to get a test env up and running and see if i can reproduce the failing integration test. will get back to you once there... | 09:18 |
| smoser | do3meli: where will you start ... | 09:21 |
| smoser | as in is your working system freebsd ? | 09:21 |
| smoser | just let me know if you ahve any questions. | 09:23 |
| smoser | if i have to.. i can launch you a vm somewhere too | 09:23 |
| do3meli | i thought about spinning up an ubuntu cloud vm - i have an env ready to do this. my working system is ubuntu btw. | 09:24 |
| smoser | oh. well then i suggest just installing and using lxd on the working system. | 09:35 |
| smoser | that make sense ? | 09:35 |
| smoser | lxd is really nice | 09:35 |
| smoser | just apt-get install lxd and then 'lxd init' | 09:35 |
| smoser | i think that is probably all you should need. | 09:36 |
| do3meli | smoser: good point - let me try lxd then | 10:31 |
| do3meli | smoser: do i have to setup the citest tox-env somehow? i get "no module named "six". | 10:42 |
| smoser | hm. | 10:48 |
| smoser | tox --notest -e citest | 10:49 |
| smoser | but tox-venv i thought would do that. | 10:49 |
| smoser | do3meli: ^ sorry for slow reply. that make sense ? | 10:53 |
| smoser | yeah, my ~/bin/tox-venv *does* do the create. but the one in cloud-init does not. sorry. | 10:54 |
| do3meli | after installing bzr it was able to setup citest requirements. now tox-venv cmd fails with: | 10:54 |
| do3meli | File "/home/doemeli/git/cloud-init/.tox/citest/lib/python3.5/site-packages/pylxd/client.py", line 267, in __init__ | 10:54 |
| do3meli | raise exceptions.ClientConnectionFailed() | 10:54 |
| do3meli | do i have to start an lxd container first? | 10:56 |
| do3meli | or will the tox-venv do that for me ? | 10:56 |
| smoser | the harness should do that for you. | 11:01 |
| do3meli | ahh think i got it. as i first installed lxd my user was not yet in that group | 11:01 |
| smoser | i suspect you just arent able to run a lxd container first | 11:01 |
| smoser | try | 11:01 |
| do3meli | after getting a new shell now seems to work ;-) | 11:01 |
| smoser | lxc launch ubuntu-daily:xenial testme | 11:02 |
| smoser | then lxc delete --force testme | 11:02 |
| do3meli | i think it works now. need to enable the ci test now and rerun it | 11:02 |
| smoser | ok. yeah, you problably didn't have access to the lxd socket (group / sggroup stuff) | 11:02 |
| do3meli | so just to confirm smoser: the test you mentioned in the beginning of this discussion was producing this failure: AssertionError: 'role: web' not found in '' ? | 11:06 |
| smoser | yep | 11:08 |
| smoser | and i probably regressed it (if you git blame) | 11:08 |
| do3meli | allright, then let me dig into that now ;-) | 11:09 |
| do3meli | just a general question: do you still want to have this test to be disabled per default? or is it may better to have it enabled? | 11:09 |
| smoser | have to think | 11:11 |
| smoser | what I do not want... is for c-i failures based on external things changing | 11:11 |
| smoser | (ubuntu archive is ok) | 11:11 |
| smoser | but if this generally works, and doens't have a dependency on , say salt-minion.com/something | 11:12 |
| smoser | then i'm good with enabling it | 11:12 |
| do3meli | the only dependency i see is the pkg install of the salt-minion. | 11:15 |
| do3meli | depending on the apt sources settings this is external or the default ubuntu repo ( i think it is in there too in a very old version - i personally use the official salt repos from repo.saltstack.com) - but as we dont manage the repository this is kind of 50/50 chance if it works or not. for the cloud-init ci system it will always work as long as the ubuntu repo contains the minion pkg. | 11:18 |
| do3meli | but for setups in the wild it basically comes down to the repo setting. | 11:18 |
| smoser | http://paste.ubuntu.com/p/P8dMDPhfNK/ | 13:25 |
| smoser | do3meli: i'm looking at that . we'll get it fixed | 13:26 |
| do3meli | smoser: thanks - please ping me once resolved | 14:18 |
| smoser | do3meli: so i think ifyou just drop the --results-dir it will work | 14:52 |
| smoser | i think | 14:52 |
| do3meli | let me see | 14:52 |
| smoser | https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/341045 | 16:07 |
| smoser | do3meli, powersj ^ thanks for your patience do3meli | 16:07 |
| blackboxsw | https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/338366 powersj <--- | 16:31 |
| dojordan | @blockboxsw you there? | 17:11 |
| dojordan | @blackboxsw* you there? | 17:16 |
| === r-daneel_ is now known as r-daneel | ||
| === r-daneel_ is now known as r-daneel | ||
| === r-daneel_ is now known as r-daneel | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!