Tuesday, 2018-05-15

*** srart has joined #openstack-ironic00:12
*** cjloader has joined #openstack-ironic00:20
*** cjloader has quit IRC00:24
*** bfournie has quit IRC00:25
*** bfournie has joined #openstack-ironic00:26
*** bfournie has quit IRC00:30
*** hshiina has joined #openstack-ironic00:36
*** srart has quit IRC00:39
*** Sukhdev has quit IRC00:42
*** bfournie has joined #openstack-ironic00:47
*** srart has joined #openstack-ironic00:55
*** rloo has quit IRC00:58
*** threestrands has quit IRC01:00
*** zhangfei has joined #openstack-ironic01:02
*** phuongnh has joined #openstack-ironic01:08
*** trungnv has quit IRC01:16
*** trungnv has joined #openstack-ironic01:17
*** gyee has quit IRC01:18
*** baoli has joined #openstack-ironic01:23
*** baoli has quit IRC01:28
*** tiendc has joined #openstack-ironic01:34
*** namnh has joined #openstack-ironic01:35
anupnHi I am seeing my devstack installation failing when it is trying to provision the ironic nodes. The setup waits for nodes to become available but none of the nodes become available02:02
anupnhas anyone seen similar error02:02
anupnI don't see any errors inside ir-cond logs02:03
*** hemna_ has quit IRC02:12
*** baoli has joined #openstack-ironic02:13
*** baoli has quit IRC02:18
*** phuongnh has quit IRC02:23
*** phuongnh has joined #openstack-ironic02:24
*** bfournie has quit IRC02:33
*** bfournie has joined #openstack-ironic02:34
*** hemna_ has joined #openstack-ironic02:34
*** bfournie has quit IRC02:38
*** rcernin has quit IRC02:46
*** rcernin has joined #openstack-ironic02:50
*** fragatina has quit IRC03:06
*** cjloader has joined #openstack-ironic03:15
*** cjloader has quit IRC03:19
*** zhangfei has quit IRC03:35
*** rbudden has quit IRC03:36
*** links has joined #openstack-ironic03:37
*** tuanla____ has joined #openstack-ironic03:38
*** zhangfei has joined #openstack-ironic03:47
*** gyankum has joined #openstack-ironic03:59
*** fragatina has joined #openstack-ironic04:05
*** fragatina has quit IRC04:06
*** fragatina has joined #openstack-ironic04:06
*** fragatin_ has joined #openstack-ironic04:07
*** fragatina has quit IRC04:10
*** fragatin_ has quit IRC04:13
*** namnh has quit IRC04:18
*** tuanla____ has quit IRC04:18
*** tiendc has quit IRC04:18
*** tuanla____ has joined #openstack-ironic04:18
*** tiendc has joined #openstack-ironic04:18
*** namnh has joined #openstack-ironic04:18
*** hemna_ has quit IRC04:26
*** pcaruana has joined #openstack-ironic04:31
*** linhnm has joined #openstack-ironic04:38
*** fragatina has joined #openstack-ironic04:41
*** fragatina has quit IRC04:58
*** linhnm has quit IRC05:04
*** marios has joined #openstack-ironic05:08
*** fragatina has joined #openstack-ironic05:09
*** mikal has joined #openstack-ironic05:12
*** mikal_ has quit IRC05:15
*** fragatina has quit IRC05:20
*** fragatina has joined #openstack-ironic05:26
*** linhnm has joined #openstack-ironic05:26
*** zshi has quit IRC05:27
*** zshi has joined #openstack-ironic05:28
*** fragatina has quit IRC05:31
*** mjura has joined #openstack-ironic05:41
*** Chandra has quit IRC05:41
*** jaypipes has quit IRC05:41
*** Chandra has joined #openstack-ironic05:41
*** jaypipes has joined #openstack-ironic05:41
*** masber has joined #openstack-ironic05:51
*** hshiina has quit IRC05:54
*** hshiina has joined #openstack-ironic05:55
*** linhnm has quit IRC05:56
*** fragatina has joined #openstack-ironic05:58
*** liuzz_ has quit IRC06:18
*** liuzz has joined #openstack-ironic06:18
*** linhnm has joined #openstack-ironic06:22
openstackgerritShangXiao proposed openstack/ironic-ui master: Add release notes link to README  https://review.openstack.org/56845406:26
*** rbartal has joined #openstack-ironic06:30
openstackgerritPavlo Shchelokovskyy proposed openstack/ironic master: Mark xclarity password as secret  https://review.openstack.org/56763706:48
*** trungnv has quit IRC06:54
*** phuongnh has quit IRC06:54
*** phuongnh has joined #openstack-ironic06:55
*** trungnv has joined #openstack-ironic06:55
*** namnh has quit IRC07:01
*** tuanla____ has quit IRC07:01
*** tuanla____ has joined #openstack-ironic07:01
*** namnh has joined #openstack-ironic07:01
*** fragatina has quit IRC07:03
*** ajya has joined #openstack-ironic07:06
*** rcernin has quit IRC07:13
*** tesseract has joined #openstack-ironic07:13
*** pcaruana has quit IRC07:17
*** pcaruana has joined #openstack-ironic07:17
*** pcaruana has quit IRC07:18
*** afazekas|pto is now known as afazekas07:18
*** pmannidi has quit IRC07:22
*** pcaruana has joined #openstack-ironic07:23
*** S4ren has joined #openstack-ironic07:31
openstackgerritHarald Jensås proposed openstack/ironic-inspector stable/queens: Call shutdown() on SIGTERM - controlled teardown  https://review.openstack.org/56333707:32
*** S4ren has quit IRC07:32
openstackgerritDao Cong Tien proposed openstack/ironic-python-agent master: Rescue bug: tinyipa fails to acquire IP in multitenant env  https://review.openstack.org/56627907:32
olivierb-Good morning everyone, during my investigation in fixing a GPT issue mentioned yesterday in this channel and following TheJulia's pointers and advices, I looked at the code in ironic-lib and ironic-python agent and have some questions for partitioning experts:07:34
olivierb-https://github.com/openstack/ironic-lib/blob/300e171546ed6832106596861bd3ff50fa061dce/ironic_lib/disk_utils.py#L761-L76207:35
olivierb-https://github.com/openstack/ironic-python-agent/blob/0912a24b384518e402394e63fc1ad94579d38b76/ironic_python_agent/extensions/standby.py#L472-L47907:35
*** linhnm has quit IRC07:36
*** AlexeyAbashkin has joined #openstack-ironic07:36
openstackgerritDao Cong Tien proposed openstack/ironic master: Update CI jobs for rescue mode  https://review.openstack.org/52870407:36
olivierb-doing a basic test on my problematic GPT installation I changed the code accordingly and was able to get a fully working and sound system but with 2 partitions, the second one being added by the fixed code described in the links above07:36
openstackgerritDao Cong Tien proposed openstack/ironic master: DNM: check rescue in multi-tenancy env  https://review.openstack.org/56628607:37
olivierb-however if I pnly run sgdisk -e /dev/vda I also get a working and sound GPT but this time with only 1 partition which is what I expect07:38
olivierb-my question is then any reason to really create this second partition ? I personnaly find it very confusing to get extra stuff I did not ask for on my provisioned system but again I am definitely no partitioning/GPT expert07:39
hshiinaanupn, hi, it seems that i have hit the same issue now in my environment.07:41
*** zhangfei has quit IRC07:41
hshiinaanupn, nodes are stuck in clean wait07:42
openstackgerritHarald Jensås proposed openstack/ironic-inspector stable/queens: Raise KeyboardInterrupt on SIGTERM - Workaround  https://review.openstack.org/56333707:42
openstackgerritTuan Luong-Anh proposed openstack/ironic master: [WIP] Implement iRMC BIOS configuration  https://review.openstack.org/53459507:42
hshiinaanupn, a node console displays: No bootable device07:43
olivierb-just realized that the sdgisk -e was called by _fix_gpt_structs so nevermind my questions above, will produce proper fix right now, sorry for the moise07:48
olivierb-noise07:48
*** zhangfei has joined #openstack-ironic07:58
openstackgerritVu Cong Tuan proposed openstack/ironic stable/queens: Update auth_uri option to www_authenticate_uri  https://review.openstack.org/56850107:59
*** livelace has joined #openstack-ironic07:59
openstackgerritzenghui.shi proposed openstack/ironic master: BIOS Settings: add admin doc  https://review.openstack.org/56850408:01
*** lucas-afk is now known as lucasagomes08:04
openstackgerritMerged openstack/python-ironicclient master: Stop double json decoding API error messages  https://review.openstack.org/56783608:04
openstackgerritDmitry Tantsur proposed openstack/ironic-inspector master: Add manage_boot parameter to introspection API  https://review.openstack.org/31680108:09
*** dougsz has joined #openstack-ironic08:09
*** athomas has joined #openstack-ironic08:13
openstackgerritTuan Luong-Anh proposed openstack/ironic master: [WIP] Implement iRMC BIOS configuration  https://review.openstack.org/53459508:18
openstackgerritDmitry Tantsur proposed openstack/ironic-inspector master: Add manage_boot parameter to introspection API  https://review.openstack.org/31680108:21
*** hshiina has quit IRC08:22
*** mgoddard has joined #openstack-ironic08:22
openstackgerritOlivier Bourdon proposed openstack/ironic-lib master: Expose GPT partitioning fixing method  https://review.openstack.org/56851808:27
openstackgerritNguyen Van Trung proposed openstack/ironic master: Support raid configuration for BM via irmc driver  https://review.openstack.org/51297908:30
*** baoli has joined #openstack-ironic08:38
*** priteau has joined #openstack-ironic08:38
*** MattMan has quit IRC08:41
*** MattMan has joined #openstack-ironic08:41
openstackgerritOlivier Bourdon proposed openstack/ironic-python-agent master: Fix GPT partitioning  https://review.openstack.org/56852408:42
*** baoli has quit IRC08:43
*** derekh has joined #openstack-ironic08:45
*** e0ne has joined #openstack-ironic08:50
*** trown|outtypewww has quit IRC08:52
*** trown has joined #openstack-ironic08:53
openstackgerritTuan Luong-Anh proposed openstack/ironic master: [WIP] Implement iRMC BIOS configuration  https://review.openstack.org/53459509:04
openstackgerritOlivier Bourdon proposed openstack/ironic-lib master: Expose GPT partitioning fixing method  https://review.openstack.org/56851809:07
*** ajya has quit IRC09:09
openstackgerritjiapei proposed openstack/ironic master: Add documentatin for XClarity Driver  https://review.openstack.org/55996009:10
*** linhnm has joined #openstack-ironic09:11
*** ajya has joined #openstack-ironic09:15
*** phuongnh has quit IRC09:17
*** serlex has joined #openstack-ironic09:26
*** e0ne has quit IRC09:29
*** e0ne has joined #openstack-ironic09:33
openstackgerritHarald Jensås proposed openstack/ironic-inspector stable/pike: Raise KeyboardInterrupt on SIGTERM - Workaround  https://review.openstack.org/56333809:37
*** e0ne has quit IRC09:38
*** sambetts|afk is now known as sambetts09:40
sambettsMorning all09:40
*** linhnm has quit IRC09:42
etingofsambetts, \o09:45
sambettshey etingof09:46
yolanda_hi sambetts , we were asked to write some devstack tests for bios automation. But so far, i haven't seen support for cleanup steps in devstack plugin. Have i missed something, or is some feature that should need to be added?09:56
*** e0ne has joined #openstack-ironic09:59
vdrokgood morning all10:05
sambettsyolanda_: the bios stuff currently runs as a manual cleaning step, if i remember correctly, that seems to me like a we could write a tempest test to orcastrate moving a node to managable, then trigging the cleaning process with the right steps10:05
sambettsyolanda_: but if there is any configuration needed in ironic.conf to enable it then we'll need to put that into devstack10:05
etingofvdrok, good morning ;)10:05
vdrokmorning etingof10:06
openstackgerritMerged openstack/bifrost master: upgrade setuptools before installing package requirements  https://review.openstack.org/56814710:06
yolanda_sambetts, i was looking for some sample in devstack tests, to see if soem cleanup step has been tested, but i didn't find anything. So that's why i was wondering, if that's worth to write something more generic10:07
yolanda_or we just write that specific test?10:07
sambettsyolanda_: I think currently all the cleaning steps get tested via automated cleaning, this is the first case I know of a running a manual cleaning step in the CI, I don't think we test the RAID ones10:08
yolanda_ok i will take a look at how it can be done10:11
*** namnh has quit IRC10:15
*** rh-jelabarre has joined #openstack-ironic10:17
*** tuanla_____ has joined #openstack-ironic10:18
*** tuanla____ has quit IRC10:19
*** tesseract is now known as info10:41
*** info is now known as tesseract10:41
*** tiendc has quit IRC10:51
openstackgerrityolanda.robla proposed openstack/ironic-tempest-plugin master: Add the ability to specify bios interface  https://review.openstack.org/56855110:57
*** tuanla_____ has quit IRC11:00
openstackgerrityolanda.robla proposed openstack/ironic-tempest-plugin master: Add the ability to specify bios interface  https://review.openstack.org/56855111:02
*** dtantsur|afk is now known as dtantsur11:14
dtantsurmorning ironic11:14
sambettshey dtantsur11:15
openstackgerrityolanda.robla proposed openstack/ironic-tempest-plugin master: Add the ability to specify bios interface  https://review.openstack.org/56855111:26
*** jcoufal has joined #openstack-ironic11:26
*** zhangfei has quit IRC11:32
jrollmorning y'all11:47
TheJuliaGood morning11:49
*** dprince has joined #openstack-ironic11:49
*** ajya has quit IRC11:51
*** ajya has joined #openstack-ironic11:51
*** mjura has quit IRC11:51
sambettsTheJulia: I'm building a fresh bifrost system atm, just got to enrolling the nodes and I'm getting a "TypeError: __init__() got an unexpected keyword argument 'token'" is this a known issue someones addressing? or should I dig deeper?11:55
*** mjura has joined #openstack-ironic11:56
dtantsurmorning jroll, TheJulia, sambetts11:57
TheJuliasambetts: first I'm hearing of it. I think hamzy hit an issue a few days ago with setuptools needing to be the absolute latest version, but that is it11:57
sambettsTheJulia: this seems to be coming from keystoneauth11:57
TheJuliaYeah :( Always is11:57
TheJulia:(11:57
sambettss/shade/requests/g11:58
sambetts;)11:58
TheJuliayeah11:59
openstackgerritJim Rollenhagen proposed openstack/ironic stable/pike: Tear down console during unprovisioning  https://review.openstack.org/56856912:01
openstackgerritJim Rollenhagen proposed openstack/ironic stable/ocata: Tear down console during unprovisioning  https://review.openstack.org/56857012:01
jrollpike/ocata backports for that ^12:01
sambettsTheJulia: where does the os_ironic ansible module come from, I can't seem to find the source12:16
TheJuliasambetts: it is in the ansible tree12:16
sambettsTheJulia: ah...12:16
*** bfournie has joined #openstack-ironic12:20
*** gyankum has quit IRC12:25
*** anton has left #openstack-ironic12:35
*** rbudden has joined #openstack-ironic12:44
olivierb-Hello everyone, could someone please help me fixing the code change I wrote https://review.openstack.org/568518 which is working properly AFAIK but is failing tests in CI12:47
patchbotpatch 568518 - ironic-lib - Expose GPT partitioning fixing method12:47
olivierb-I may have missed some changes in tests to adapt to new exposed code but not very familiar with these tests and all the mocking around them12:48
*** rh-jelabarre has quit IRC12:52
*** rh-jelabarre has joined #openstack-ironic12:54
sambettsTheJulia: welll... this is a weird one, so it turns out you must make sure to unset OS_AUTH_TOKEN from your environment variables when you run the ansible modules now because otherwise keystoneauth will try to pass "token=<OS_AUTH_TOKEN env var>" into the constructor of the keystone auth plugin12:55
sambettsregardless of whether it takes a token or not12:55
TheJuliaoh joy12:55
sambettsnot really sure how to address that tbh12:56
sambettsunless we make all keystone auth plugins take **kwargs and then just take the ones they care about12:57
*** jesusaur has quit IRC12:57
*** rloo has joined #openstack-ironic12:57
sambettsbut the even the error is very unfreindly12:57
*** jiapei has quit IRC12:59
TheJuliaolivierb-: so I was thinking that you could just expose _fix_gpt_structs, and not additional logic.13:03
rloogood morning all, TheJulia, sambetts, dtantsur, olivierb-, jroll13:04
olivierb-TheJulia ok my bad will fix this accordingly thanks13:04
dtantsurhi rloo13:04
olivierb-good morning rloo13:04
TheJuliaolivierb-: regardless, we likely need to fix gpt regardless if there is a config drive, but one step at a time :)13:04
TheJuliagood morning rloo13:04
TheJuliareplied in storyboard with my $0.0213:05
*** jesusaur has joined #openstack-ironic13:05
rlooTheJulia: thanks, looking...13:05
*** Goneri has joined #openstack-ironic13:06
rloodtantsur, jroll: wrt the power fault recovery work, I forgot to mention yesterday that I commented in the story: https://storyboard.openstack.org/#!/story/1596107#comment-8172113:07
olivierb-TheJulia agreed however wouldn't the code in ironic-python-agent would also need to require a test to see if device is using GPT before applying _fix_gpt_structs ? in which case I'll also need to expose _is_disk_gpt_partitioned or am I misunderstanding ?13:08
TheJuliait would, but minimally intrusive seems to make sense since it has wrapping logic around gpt13:09
rlooTheJulia: so the faults spec mentioned that the nova-ironic-virt-driver would have to be updated to also take into consideration faults in addition to maintenance. We most likely won't go there, but another reason for adding a fault_type instead of maintenance_type field.13:09
dtantsurrloo: so tl;dr s/maintenance_type/fault_type/ and do not touch maintenance at all?13:09
rlooTheJulia: and then I was thinking later, why 'fault_type' instead of just 'fault'.13:09
dtantsur(for old API versions, I guess, it means maintenance = maintenance or fault_type)13:10
TheJuliarloo: kind of, except we would have to land that change and hold off on fault recovery for a cycle... or just update maintenance13:10
rloodtantsur: no, would also need to touch maintenance -- as the code does already. we can't change that behaviour. at least not now.13:10
TheJuliaas well that is13:10
dtantsurrloo: we can change it in new API versions13:10
dtantsurso, do you suggest to only rename the new field?13:10
rloosorry, i guess i wasn't clear. i don't know if we're ready/want to talk about how to do more. for now, i am just suggesting renaming the field and NOT saving 'manual' in that field.13:11
rlooi think this 'little' change would make it easier to move forward when/if we want to.13:11
olivierb-TheJulia I am not sure to understand what you meant13:11
dtantsurrloo: I'm cool with that.13:11
TheJuliaolivierb-: I'm heating something up to eat, give me a few minutes and I'll pull the link13:12
rloodtantsur: sweet. also, do you think node.fault is sufficient? i am not sure now, that node.fault_type makes sense. but I'm not an operations person, don't know the lingo.13:12
dtantsurboth make equal sense to me, so I guess the shorter the better13:12
olivierb-of course, no pb. Looking back at the ironic-python-agent code I fixed it seems to be pretty much GPT agnostic13:13
rloodtantsur: ok. i think sort is better in case we want to support multiple faults; then we could add a node.faults :)13:13
rloos/sort/short/13:13
* sambetts is just lurking, but I like the sounds of this 13:14
TheJuliaolivierb-: oh, brain failure13:16
olivierb-nope, too many code eating ;-)13:16
olivierb-your brain is working very well, only early morning for you13:17
TheJuliaolivierb-: it is not in ipa yet, but what I was thinking purely the fix structures since it is needed outside of configuration drive use as well13:19
TheJuliaI've not had coffee yet either13:19
olivierb-will go for some myself now, take your time13:20
rloosambetts: thx (I assume you mean the power fault recovery discussion above)13:26
sambettsrloo: yeah, having a .fault initally, and then expanding it to .faults in the future makes a lot of sense to me, it feels a lot like the faults info I see on my BMC if something goes wrong like a PSU failure etc13:27
sambettsrloo: and having it separate from maintenance makes sense to me too13:28
rloosambetts: good to know! thx.13:28
*** gyankum has joined #openstack-ironic13:28
*** mjturek has joined #openstack-ironic13:28
olivierb-going through the failing tests code, I must admit that I do not understand why it is failing in case of my mods and why it was not before, seems like /dev/fake4 is replaced by UUID therefore the failure or I am misinterpreting the results ?13:31
TheJuliaI think we're going to have to sync with maintenance to begin with and then eventually decouple it after a deprecation period since the two concepts are tied together13:32
rlooTheJulia: yes. IF we decide to decouple it etc -- i think that's a separate RFE13:32
TheJuliaagreed13:32
TheJuliaa separate evolution :)13:32
* TheJulia wonders if hacking on the pxe interface and testing should only be done while intoxicated13:33
rloo:) I added another comment to the story to reflect our discussion today.13:33
* TheJulia is hacking on the pxe interface in another window and getting frustrated because of how complex the path can be13:34
TheJuliaolivierb-: thta is exactly what the test output indicates13:35
* TheJulia pulls up that code again13:35
olivierb-??13:36
dtantsurTheJulia: yep, at least one shot before even opening the editor13:36
TheJuliadtantsur: note taken!13:36
openstackgerritDmitry Tantsur proposed openstack/ironic master: Remove excessive usage of mock_the_extension_manager in unit tests - part 1  https://review.openstack.org/56858513:37
dtantsurand this requires getting wasted first ^^^13:37
TheJuliadtantsur: I was going to ask if that was what you were hitting because I decided to try and hack a pxe deploy interface last night and hit it....13:38
dtantsurTheJulia: hah, yeah. tl;dr if you're not sure you need mock_the_extension_manager - you don't13:38
dtantsurand we cargo-culted it all over the place13:39
TheJuliaYeah, once I realized what it was doing I knew we didn't need it13:39
dtantsurthere are very few places where it cannot be replaced by self.config(enabled_drivers=[something]) or removed at all13:39
TheJuliaolivierb-: oh, I see what you did, you flipped the node_uuid/device order13:40
TheJuliathe caller is device, node_uuid, your new method is node_uuid, device13:40
*** milan_ has joined #openstack-ironic13:41
olivierb-TheJulia thx let me check and correct this13:42
openstackgerritOlivier Bourdon proposed openstack/ironic-lib master: Expose GPT partitioning fixing method  https://review.openstack.org/56851813:45
*** cdearborn has joined #openstack-ironic13:45
*** fragatina has joined #openstack-ironic13:46
*** rh-jelabarre has quit IRC13:46
olivierb-should be way better now, will wait for tests results many thanks again for catching my stupid mistake, proof is that tests are very usefull as they catched it13:46
*** rh-jelabarre has joined #openstack-ironic13:49
*** baoli has joined #openstack-ironic13:51
*** cjloader has joined #openstack-ironic13:57
*** baha has joined #openstack-ironic13:58
TheJulia:)14:14
*** hemna_ has joined #openstack-ironic14:15
openstackgerrityolanda.robla proposed openstack/ironic master: Add Node BIOS support - REST API  https://review.openstack.org/51257914:16
*** rajinir has joined #openstack-ironic14:20
*** rpioso|afk is now known as rpioso14:20
rpiosoGood morning14:21
TheJuliagood morning rpioso14:24
rpiosoTheJulia: :)14:25
etingofrpioso, \0 ;)14:25
rpiosoetingof: o/14:26
* etingof gets quite frantic tracking down the lurking unittest mocks14:28
*** BernsO has joined #openstack-ironic14:35
*** trown is now known as trown|brb14:37
*** trown|brb is now known as trown14:41
*** ajya has quit IRC14:45
*** ajya has joined #openstack-ironic14:46
jrollrloo: commented in storyboard, but yeah, I'm good with this too, thanks!14:50
rloothx jroll!14:50
dtantsurrloo: do you want to update the spec to save some roundtrips between us and the contributor?14:51
rloodtantsur: sure, I can do that.14:51
rloodtantsur: will do it today14:52
dtantsurthanks!14:52
dtantsurthen we'll just ask the contributor to update the code patches accordingly14:53
rloodtantsur: makes sense :)14:53
*** r-daneel has joined #openstack-ironic14:57
*** mjura has quit IRC15:00
*** bdodd has joined #openstack-ironic15:06
*** rbartal has quit IRC15:11
*** kaifeng has joined #openstack-ironic15:12
kaifengmorning ironicers15:13
openstackgerrityolanda.robla proposed openstack/ironic-tempest-plugin master: Add manual clean step ironic standalone test  https://review.openstack.org/56861615:13
kaifengwow i saw so many messages today for the power fault feature15:13
*** serlex has quit IRC15:14
rloohey kaifeng! Yeah, I'm updating the spec now. I hope you are OK with it all.15:14
kaifenghi rloo, i haven't fully read your replies yet, just got back to computer15:15
rlookaifeng: ok15:15
kaifengbut i feel your concern is related to the naming?15:15
rlookaifeng: yes, mostly. i want to abstract 'fault' from 'maintenance'; they are two diff concepts.15:16
kaifengi see you are worried about the manual value15:16
rlookaifeng: right, because it ties that new field with the maintenance stuff. which means if we ever want to separate them, it will be harder to do.15:17
kaifengso you want a fault doesn't tie with maintenance, which means we may have a node not in maintenance, but has a fault value there15:18
rlookaifeng: i have one question for you. just reading/updating the spec now. were you planning on adding a 'dbsync online_data_migration' to set this new field, based on maintenance_reason? the spec sez 'manual', but that is wrong.15:18
rlookaifeng: no, for your work, when there is a fault, ironic still sets maintenance & maintenance_reason. just like it does now.15:19
kaifengyes, planned so, let me dig some history15:19
rlookaifeng: it is about setting things up so that in the future, we *could* change it so it doesn't set maintenance/reason.15:19
*** r-daneel has quit IRC15:19
*** r-daneel_ has joined #openstack-ironic15:19
rlookaifeng: wrt the db migration -- the only way to get it right is to parse the maintenance_reason string. argh. but we can't do that easily if it is translated.15:19
kaifengrloo: of course, power fault is tied with maintenace15:19
*** links has quit IRC15:21
kaifenghttps://review.openstack.org/#/c/555708/15:21
patchbotpatch 555708 - ironic - Power fault recovery: db and rpc implementation15:21
*** r-daneel_ is now known as r-daneel15:22
kaifengat patch set 1, dmitry suggests do the migration in alembic script15:22
kaifenghttps://review.openstack.org/#/c/555708/1/ironic/db/sqlalchemy/alembic/versions/fb3f10dd262e_add_maintenance_type_to_node_table.py@1915:23
patchbotpatch 555708 - ironic - Power fault recovery: db and rpc implementation15:23
kaifengand after several updates, Hironori points out that doesn't work for rolling upgrade15:24
NobodyCamGood Morning Ironic'ers15:24
NobodyCamHappy Not Monday15:24
kaifengso i removed it, the migration is done at rpc layer15:24
rlookaifeng: 'unknown' works for me; 'manual' doesn't. and we should do these in the dbsync online_data_migration.15:24
kaifengrloo: i wonder what we can do with 'unknown' type?15:25
rlookaifeng: so, either 'unknown', None, or we do a best-guess at what it might be by looking at the maintenance_reason value (if it hasn't been translated).15:26
rlookaifeng: 'unknown' is more accurate that None, for nodes that are already in maintenance.15:26
rlookaifeng: cuz we don't know15:27
rlookaifeng: i will suggest something in the spec15:27
kaifengrloo: ok, i will take look after you updated the spec15:28
kaifengrloo: thanks for helping15:28
rlookaifeng: thank YOU for doing the work!15:28
dtantsurmaybe just leave it as None?15:28
dtantsuraka NULL15:29
kaifengah, we consider maintenance_type is a classification to maintenance field15:30
kaifengso from the beginning, we assume maintenance_type is None when maintenance is false, right?15:30
kaifengotherwise, we needn't bother with the compatibility and data migratio15:31
kaifengmigration15:31
dtantsuryeah, I guess we keep them locked together still15:31
dtantsurso maintenance=True and fault=None means "manual maintenance" (or upgraded)15:32
dtantsurmaintenance=True and fault!=None means "power/cleaning/etc fault"15:32
dtantsurright rloo ^^^?15:32
kaifengor unknown?15:32
dtantsurunknown = upgraded15:32
rloodtantsur: true. although i am open to us adding code to try to guess the fault from the maintenance_reason string. I mention it in the spec. cuz... how will someone get their node 'hooked' into the fault stuff so that they can do power fault recovery.15:33
dtantsurrloo: it's too fragile IMO, esp. if we consider i18n15:33
sambettswhy do we need to keep them locked together now? e.g. can't we just have faults be a new thing? and the power sync state code for exmaple do if maintenance or powerfault in node.fault: pass15:33
dtantsursambetts: to simplify API changes (think about old versions that you have to keep compatible)15:34
rloodtantsur: i was thinking that we most likely do not have many clusters with i18n. a simple string match or whatever -- if it matches, great, if not, use 'unknown' or None.15:34
sambettsin the old API versions we could just do, if faults != None then maitenance=True15:34
dtantsurrloo: I recall some bugs with Japanese locale popping up15:35
dtantsurso at least we have people using it15:35
rloosambetts: we could but it is a bigger piece of work, we'd have to agree to a new spec. and even if we did, we'd probably need a deprecation period. we'd need to update nova-ironic-virt driver.15:35
rloodtantsur: actually, it'd be easy to see which languages have xlations, it is in ironic/locale or whatever directory.15:35
dtantsurright15:35
dtantsursambetts, rloo, it's a good point, we can do it, but we don't have to do it in the same API version15:36
*** gyee has joined #openstack-ironic15:39
mgoddardwe are about to perform a new deployment, and trying to learn lessons from past deployments. In particular, networking between bare metal compute and controllers/API endpoints can get hairy in when there are multiple networks involved for internal API, provisioning and cleaning. Ironic uses a single IP to configure TFTP, HTTP(iPXE) and API hosts. If provisioning net != cleaning net != API net, this implies some IP routing exists between these15:46
mgoddardnetworks. Could anyone provide information on approaches they've seen used for this in the past, and their relative merits?15:46
mgoddarde.g. do you use neutron routers, or hardware, how do you restrict access between these networks?15:48
*** hemna_ has quit IRC15:49
openstackgerritRuby Loo proposed openstack/ironic-specs master: Use node.fault field for power fault recovery work  https://review.openstack.org/56862715:49
*** hemna_ has joined #openstack-ironic15:50
rlookaifeng, dtantsur: ^^15:50
dtantsurmgoddard: we're using flat networking but IIRC we set up routing between the provisioning network and the API network15:51
dtantsurbfournie: do you remember details ^^?15:51
dtantsurthanks rloo!15:51
rloodtantsur: yw. thank you for being patient with me :)15:51
dtantsurheh, it's not too hard :)15:52
mgoddardthanks dtantsur. is that a HW router or neutron?15:52
sambettsmgoddard: we proposed a solution in one of our deployments where we ran three networks, a network for the conductors "conductor net" which is where the TFTP /http server and API server run for internal use, then a cleaning network, and a provisioning network,15:52
mgoddardsambetts: interesting: I had this idea myself this morning, but we already have more networks than I can count so wasn't sure about it15:53
dtantsurmgoddard: let's wait for bfournie, I guess. I realized I don't know15:53
mgoddardinteresting to hear someone else has considered it15:53
mgoddardsambetts: when you say proposed, was it ever implemented?15:53
kaifengrloo: thanks, added to my list :)15:54
rlookaifeng: thx!15:54
sambettsmgoddard: unforunatly the project was cut short before we could implement it, so at the time we were still running provisioning==cleaning network (API network was separate though)15:54
sambettsmgoddard: we ran an ironic API specifically for the provisioning network15:54
sambettsand hardwired that and the conductors into the network15:55
sambettsthe provisioning/cleaning network had no external router15:55
sambettswell no router at all15:55
mgoddardsambetts: and that API listened on this third network too?15:55
anupnHi Folks, how can I know what network interface the DHCP server setup with Devstack is using for sending out DHCPOFFER packets during PXE boot? is it brbm?15:55
TheJuliaanupn: it is a tap that is attached by neutron likely to brbm15:56
sambettsmgoddard: in the proposed implementation yeah, the three networks were completely isolated from each other15:57
sambettsnot from each other, from the outside world15:57
mgoddardI see15:57
dtantsurrloo: see inline, I think I know what to do with upgrades15:57
anupnTheJulia: I see. Somehow the VM that I am trying to provision is sending out BOOTP request, and another machine where Devstack is running is receiving BOOTP request from the VM on the underlying physical interface, but not hearing the DHCP offer reply15:58
anupnTheJulia: Do we specify the tap name anywhere in neutron or Ironic conf?15:58
mgoddardsambetts: so you had two two legged neutron routers to get from cleaning/provisioning to network3?15:59
anupnTheJulia: Hmm i see there is a tap named "brbm-tap"15:59
rloodtantsur: so we need to look at 3 diff faults, power, clean & rescue-abort.15:59
sambettsmgoddard: yeah, and then security group rules to lock down the communication between the the networks to just the traffic types needed by provisioning15:59
sambettscleaning15:59
rloodtantsur: but i think what you propose makes sense.16:00
mgoddardok, got it16:00
sambettsmgoddard: could maybe be done with one neutron router if the rules are written correctly16:00
dtantsurrloo: we're not going to do any automation around rescue-abort and clean, right? so maybe we can ignore them.16:00
mgoddardthanks for explaining :)16:01
*** dprince has quit IRC16:01
TheJuliaanupn: no, it is dynamicly handled by neutron from a namespace operated by the neutron-dhcp-agent16:01
rloodtantsur: nah, we shouldn't ignore, let's do it 'right' if we're going to do it.16:01
rloodtantsur: just a bit more code :)16:01
dtantsura bit, hmm :)16:01
mgoddardsambetts: in hindsight, was it a good solution?16:01
rlooha ha, 'only code'!16:01
mgoddardsambetts: I'd be a bit concerned about the router being a performance bottleneck16:03
anupnTheJulia: umm wait but then the problem I see right now is no connection between the interface where DPCP sends DHCPOFFER packet and the underlying physical interface16:03
TheJuliaanupn: so... sounds like misconfiguration, is brbm bound to the physical interface?16:03
sambettsmgoddard: in my opinion yes, it makes the ironic services pretty much as isolated as possible from themselves and from the API network, it is a little over kill though, I think having cleaning==provisioning isn't too bad, as long as that network is isolated from the outside world16:04
anupnTheJulia: No, I haven't manually added brbm to any physical interface, it is as setup by devstack16:05
anupnTheJulia: here is the tcpdump on the underlying physical interface of the host where devstack is running http://paste.openstack.org/show/721022/16:05
anupnTheJulia: you can see the BOOTP request coming in from the MAC address but on the same interface i don't see the DHCP reply going16:06
TheJuliaanupn: without the two being connected, the neutron dhcp server can never get the request16:07
bfourniemgoddard: we also have a setup with provisioning and cleaning network on same network, this was a separate isolated network in tripleo terminology, and created a neutron router to access, with security rules set up. some notes here - http://paste.openstack.org/show/721023/16:07
*** trown is now known as trown|lunch16:08
mgoddardsambetts: did the design include inspector? separate inspection network? did the inspector DHCP server listen directly on this network?16:09
*** lucasagomes is now known as lucas-afk16:09
anupnTheJulia: So I need to connect brbm to the underlying physical interface, right?16:09
anupnTheJulia: let me do that and see16:10
mgoddardgood notes bfournie, thanks for sharing16:10
bfourniemgoddard: no problem, btw our design did not have inspector as we only have inspector running in undercloud16:11
sambettsmgoddard: we actually ran inspection on a separate VLAN completely, one that wasn't managed by neutron at all, we would manually put the inspection network on the switch ports when we racked a new server / have the switch ports default to the inspection network when unconfigured, and then once inspected then node would move into cleaning causing neutron to program the cleaning network onto the16:11
sambettsports stomping on the inspection VLAN16:11
sambettsmgoddard: we did this because at inspection time we didn't have the local_link_connection infomation avaiable to program the inspection VLAN onto switch16:12
sambettsits a chicken and egg you see16:12
mgoddardsambetts: yeah, we have some automation in kayobe for putting nodes on the inspection network16:13
sambettsmgoddard: we were using full autodiscovery in our deployment, with the idea that you could roll in a rack and inspector would auto discover and enrol all the nodes for us, so we were working on the princple of not know what node was connected to what port16:15
sambettsbasically roll in a rack, set the whole switch to the inspection vlan, power on the nodes, watch them pop into ironic16:16
sambettsman... I miss working on that project..16:16
openstackgerritIlya Etingof proposed openstack/sushy-tools master: Add unittests for OpenStack nova driver  https://review.openstack.org/56863616:16
mgoddardsambetts: http://www.stackhpc.com/ironic-idrac-ztp.html16:17
mgoddardyeah that's pretty much our approach. The lack of inspection network integration with neutron gets annoying if you want to reinspect16:17
sambettsyeah reinispect is a probelm, I have talked to dtantsur about splitting discovery and inspection for a while, where discovery would find nodes and their ports etc like it does today, but then inspection would be in a neutron network and be retryable16:19
sambettsbut never had the time to work on it16:19
mgoddardhow big a feature is it? we have a summer intern joining soon with time allotted for inspector16:20
*** tesseract has quit IRC16:21
openstackgerritHarald Jensås proposed openstack/ironic-inspector stable/pike: Raise KeyboardInterrupt on SIGTERM - Workaround  https://review.openstack.org/56333816:22
sambettsmgoddard: difficult to tell, but it would definatly involve adding additional logic into the network interfaces for "(dis)connect_inspection_network" functions, its also would involve a fundimental change in how inspection nodes currently PXE boot, i.e. default DHCP, because you would be guarenteed to know the mac address of at least one port, but we already have logic in ironic for that, also16:27
sambettsit ties in with the inspection boot management stuff that dtantsur is/has been working on16:27
dtantsurtl;dr A LOT OF work16:28
olivierb-some tempest tests for https://review.openstack.org/#/c/568518/ have failed, should I relaunch/is this known ?16:28
patchbotpatch 568518 - ironic-lib - Expose GPT partitioning fixing method16:28
mgoddardI can imagine that getting out of hand once you start to pick it apart :)16:29
mgoddardprobably > 1 intern summer16:29
openstackgerritRuby Loo proposed openstack/ironic-specs master: Use node.fault field for power fault recovery work  https://review.openstack.org/56862716:29
sambettsunfortunatly yes, it could probably be somewhat broken down16:30
sambettse.g. we could add the network interface functions, and call into them from the existing inspector interface to plumb the switches if and only if we know the network info for the ports16:31
sambettselse give up and work as we do today16:31
sambettsand if we state you must turn DHCP off in the neutron inspection network, then it won't even conflict with the inspector DHCP16:32
sambettsthe ports will just have an IP address that means nothing in neutron16:32
sambetts(actually ports in neutron can be create with no IP address now, so that could also be a thing)16:32
*** dtantsur is now known as dtantsur|afk16:33
dtantsur|afksee you tomorrow16:33
sambettso/ dtantsur|afk16:33
*** pcaruana has quit IRC16:33
TheJuliagoodnight dtantsur|afk16:33
*** BernsO has quit IRC16:34
*** e0ne has quit IRC16:35
*** marios has quit IRC16:41
mgoddardok, lots of good context there sambetts. I'll put it on the list of candidates16:42
mgoddardthanks for all the great info you've provided sambetts, bfournie, dtantsur|afk16:42
sambettsmgoddard: no problem :)16:44
*** baoli has quit IRC16:50
*** dprince has joined #openstack-ironic16:56
*** dougsz has quit IRC16:58
*** derekh has quit IRC17:00
*** exodusftw has quit IRC17:00
*** kaifeng has quit IRC17:02
*** mgoddard has quit IRC17:04
*** baoli has joined #openstack-ironic17:05
*** yolanda_ has quit IRC17:09
anupnTheJulia: I connected brbm to the underlying physical interface but don't see DHCP offer still going out Here is the tcpdump on brbm http://paste.openstack.org/show/721030/17:18
anupnTheJulia: the BOOTP request happens to come in on brbm, but no DHCP offer reply17:19
anupnTheJulia: do i have to explicitly configure DHCP on one of the interface through /etc/network/interfaces?17:20
*** milan_ has quit IRC17:20
*** yolanda_ has joined #openstack-ironic17:20
TheJuliaanupn: from with-in the neutron namespace, do you see the dhcp requests?17:21
anupnTheJulia: how to see that?17:22
anupnTheJulia: inside the logs of q-dhcp?17:22
*** trown|lunch is now known as trown17:22
TheJuliaanupn: generally your logging should log if a request is received, but if you match the q-dhcp to the network namespace `ip netns list`, you can do `ip netns exec $namespace tcpdump -i namespace_interface -n`... you may want to do `ip netns exec $namespace ip link` to look at the interfaces in the namespace17:23
*** mjturek has quit IRC17:24
*** mgoddard has joined #openstack-ironic17:25
* anupn checks the q-dhcp log and netns list17:25
*** AlexeyAbashkin has quit IRC17:25
*** baha has quit IRC17:27
anupnTheJulia: for 'qdhcp-d2c109c9-ef91-4f28-9ec2-25494f413a22' I see two interfaces; one is loopback and other is  tap6ee8763f-71 with status UNKNOWN17:30
anupnTheJulia: should the status be Unknown of that interface?17:30
anupnI will do tcpdump anyways on that interface, and see if DHCP requests are coming in17:30
*** akhilaki has joined #openstack-ironic17:32
TheJuliaI think status unknown is fine since it is all in the kernel17:33
*** ElCoyote_ has joined #openstack-ironic17:35
*** BernsO has joined #openstack-ironic17:35
*** BernsO has quit IRC17:38
*** e0ne has joined #openstack-ironic17:39
anupnTheJulia: Oh okay, I don't see anything coming on that tap interface upon running tcpdump17:40
anupnTheJulia: " sudo ip netns exec qdhcp-d2c109c9-ef91-4f28-9ec2-25494f413a22 tcpdump -i tap6ee8763f-71 -vvv -n "17:41
*** priteau has quit IRC17:52
*** sambetts is now known as sambetts|afk17:54
sambetts|afknight all17:54
*** gyankum has quit IRC17:55
TheJuliaanupn: so something is not hooked up in ovs, if you work backwards in ovs, that namespace interface should be hooked into ovs ultimately to brbm18:00
*** links has joined #openstack-ironic18:01
anupnTheJulia: Hmm, when i run "ovs-vsctl show", I see the tap6ee8763f-71 under br-int bridge with a type 'internal'. Is that how it should be?18:04
anupnTheJulia: or should that tap interface be under brbm? any idea18:04
TheJuliaI really can't tell you off the top of my head since it is so dependent upon neutron configuration, and what network you set/used. https://docs.openstack.org/ironic/latest/contributor/ironic-multitenant-networking.html18:07
anupnTheJulia, hmm yeah true. Btw under the namespaces i.e. "ip netns list" I was seeing qdhcp and qrouter, I should be checking qdhcp right and not qrouter?18:10
TheJuliaqrouter just passes packets, qdhcp is what dnsmasq attaches to18:11
anupnTheJulia: alright, thanks.18:12
anupnTheJulia: I am just looking at the link you pasted above and the local.conf used in that is different than mine18:13
anupnone is I haven't specified OVS_PHYSICAL_BRIDGE=brbm option inside local.conf18:14
*** baha has joined #openstack-ironic18:14
anupnbut I saw inside devstack/lib/ironic that IRONIC_VM_NETWORK_BRIDGE is brbm so I assumed that is where DHCP offers should come18:14
*** e0ne has quit IRC18:20
*** dprince has quit IRC18:30
*** dprince has joined #openstack-ironic18:30
*** e0ne has joined #openstack-ironic18:35
*** mgoddard has quit IRC18:40
anupnTheJulia: I see the qdhcp namespace is associated with private network and the subnets are in the network 10.0.0.0/24. So DHCP server is likely be using this network, I am wondering will it be able to talk on brbm which is not in that network?18:43
*** baoli has quit IRC18:43
*** baoli has joined #openstack-ironic18:44
*** baoli has quit IRC18:44
*** baoli has joined #openstack-ironic18:44
anupnTheJulia: yes I see the tap interface attached in qdhcp namespace is carrying 10.0.0.2 IP address18:46
*** ElCoyote_ has quit IRC18:47
*** e0ne has quit IRC19:04
*** e0ne has joined #openstack-ironic19:07
gyeeTheJulia, I've commented on https://review.openstack.org/#/c/566733. Sorry I haven't had a chance to do any more testing.19:07
patchbotpatch 566733 - diskimage-builder - Add simple iscsi-boot element19:07
*** r-daneel has quit IRC19:18
*** links has quit IRC19:20
*** milan has joined #openstack-ironic19:23
*** hshiina|afk has quit IRC19:23
*** hshiina has joined #openstack-ironic19:23
*** r-daneel has joined #openstack-ironic19:35
TheJuliagyee: no worries, everyone is busy :)19:39
TheJuliaanupn: brbm is like an ethernet cable in a sense, you can have multiple logical and differently addressed networks coexist and cross over that cable19:40
anupnTheJulia: Yes i agree, but the network where DHCP is running on a network that is not going over brbm cable19:49
TheJuliaso the exact same issue you had earlier, brbm is not attached to whatever network your attempting to use19:51
*** jtomasek has quit IRC19:51
*** cjloader_ has joined #openstack-ironic20:00
*** cjloader has quit IRC20:00
*** cjloader_ has quit IRC20:02
*** cjloader has joined #openstack-ironic20:02
*** e0ne has quit IRC20:02
*** ajya has quit IRC20:07
*** cjloader has quit IRC20:13
*** cjloader has joined #openstack-ironic20:14
*** fragatina has quit IRC20:20
*** baoli has quit IRC20:20
*** baha has quit IRC20:20
*** fragatina has joined #openstack-ironic20:20
anupnTheJulia: yes brbm is attached to the underlying host, but somehow the tap interface where dhcp is running is not connecting to the brbm. I am seeing if there are options to tell neutron to run DHCP over brbm20:24
anupnsomewhere in configuration files20:25
*** e0ne has joined #openstack-ironic20:35
*** baha has joined #openstack-ironic20:36
*** r-daneel_ has joined #openstack-ironic20:36
*** mjturek has joined #openstack-ironic20:36
TheJuliaanupn: have you considered reading through the devstack plugin to see how it is all attached and how settings are used in that regard?20:36
*** r-daneel has quit IRC20:37
*** r-daneel_ is now known as r-daneel20:37
anupnTheJulia: I went a little bit over it to see is brbm specified anywhere or any other network interface name20:37
anupnI see IRONIC_VM_NETWORK_BRIDGE=brbm20:38
olivierb-could someone please have a look at CI tempest tests failure for https://review.openstack.org/#/c/568518/ please ?20:38
patchbotpatch 568518 - ironic-lib - Expose GPT partitioning fixing method20:38
anupnand that put me again in another question of does ML2 plugin connects the tap interface where DHCP server is running to brbm, or brbm is just used for internal VM network communication20:39
olivierb-I relaunched the CI tests but it keeps failing and I can not understand why20:39
olivierb-may be it is way too late for my ppor brain20:39
*** e0ne has quit IRC20:40
*** baoli has joined #openstack-ironic20:41
TheJuliaanupn: yes, and that is the default for the integration when we perform vm based testing, realistically that should be your physical network bridge if you want this to work. Alternatively it is going to have to be explicitly attached inside ovs via commands. The reason I recommend walking through the devstack plugin is so you can see how it gets assembled in the various scenarios we support with the plugin.20:47
TheJuliaanupn: ml2 plugin would in essence attach a segmentation id to a port. That would match the same segmentation id neutron is using for a network20:49
*** baha has quit IRC20:50
jrollolivierb-: I am trying but loading these logs is slowwwwwww20:50
*** mjturek has quit IRC20:50
*** cjloader has quit IRC20:50
olivierb-yep, finally got hold of them after same slowness20:50
olivierb-but could not grab what was wrong20:51
anupnTheJulia: I see good to know. Yes I am reading and understanding the devstack plugin20:51
olivierb-thanks for your time and help jroll20:51
jrolldon't thank me yet :)20:51
anupnTheJulia: Also other thing i noticed is I should specify OVS_PHYSICAL_BRIDGE in local.conf20:51
olivierb-even tried the other logs ara-reports which segment failures but did not manage to have them completed20:52
jrollI wonder if it just timed out20:52
anupnas pointed in the document that you pointed https://docs.openstack.org/ironic/pike/contributor/ironic-multitenant-networking.html20:53
jrollmust have20:53
TheJuliaolivierb-: that looks really broken20:53
jrollall I know is some of these logs are breaking my browser :|20:53
TheJuliaheh20:53
TheJuliait looks like in one case tempest failed go grok an api response20:54
jrollonly 2.2M, wtf chrome20:54
TheJuliain another, instance_info.image_source was not found and failed a api validation call20:54
TheJulia2.9MB uncompressed text20:54
TheJuliain gzip... say 10M?20:55
TheJulia :)20:55
jrollya20:55
jrollwell, size warning, but this implies a timeout to me http://logs.openstack.org/18/568518/3/check/ironic-lib-tempest-partition-agent_ipmitool/286695d/logs/tempest.txt.gz20:55
jrolland this mostly looks like a refactor20:56
jrollso idk why it'd be so much slower20:56
*** cjloader has joined #openstack-ironic20:56
* jroll calls shenanigans20:56
TheJuliathat log is still loading20:58
TheJuliait has been over two minutes20:58
* jroll goes to wget to confirm20:58
jrollin my browser it cuts off during the tempest run20:59
jrollalso your estimate was waaaaay low apparently :)20:59
jroll100M and counting20:59
TheJuliawell, it is dynamic based on content, so lots of repeating tokens....20:59
TheJuliasweet!20:59
jrollah, 106M20:59
TheJuliawow21:00
jrollbut yeah, appears to confirm ssh works, then a few api calls, and end21:00
jrollappears to be consistently doing this on the same jobs though21:01
jroll(sample size of 2)21:01
jrollhave to go for now, will check back later21:02
*** trown is now known as trown|outtypewww21:05
TheJuliaolivierb-: it does look like it is hanging in and timing out, but why doesn't make sense :\  I've issued a recheck on another unrelated patch in ironic-lib just to assess the state of CI21:23
*** racedo_ has joined #openstack-ironic21:41
*** racedo has quit IRC21:42
*** jcoufal has quit IRC21:44
*** hemna_ has quit IRC21:47
*** cjloader has quit IRC21:52
*** Goneri has quit IRC21:53
*** dprince has quit IRC21:55
*** rcernin has joined #openstack-ironic22:00
*** rbudden has quit IRC22:08
*** hemna_ has joined #openstack-ironic22:08
*** cdearborn has quit IRC22:16
*** livelace has quit IRC22:18
*** rpioso is now known as rpioso|afk22:28
*** baoli has quit IRC22:36
*** baoli has joined #openstack-ironic22:37
*** bfournie has quit IRC22:37
*** pmannidi has joined #openstack-ironic22:40
*** baoli has quit IRC22:42
*** rbudden has joined #openstack-ironic22:52
anupnTheJulia: I found by researching that there are few options that we can set to tell Neutron to consider a specific network as provisioning network, and then that will run DHCP server on that network23:16
anupnTheJulia: this pointer helped me to understand better https://docs.openstack.org/ironic/pike/contributor/ironic-multitenant-networking.html23:17
anupnTheJulia: thanks for your inputs :) I feel good to debug to this level23:17
* anupn thinks he will get few drinks of rum tonight ;)23:18
TheJuliaenjoy!23:18
*** rh-jelabarre has quit IRC23:33
*** rbudden has quit IRC23:51
*** bfournie has joined #openstack-ironic23:59

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!