Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel-dev, 2015-11-05

| Channels | #fuel-dev index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:03 zhangjn joined #fuel-dev
00:19 sylwesterB joined #fuel-dev
00:22 rmoe joined #fuel-dev
00:28 Nepoc joined #fuel-dev
00:29 Nepoc Hello, would anyone be able to point me in the right direction to customize the default networks created in Fuel. I would like to add additional networks and modify the subnets that are used as defaults. For example change the 172.16.0.0/24 to 192.168.122.0/24.
00:31 jerrygb joined #fuel-dev
00:32 Nepoc I've looked at network templates however they don't really fit my needs. Essentially need to pre-configure everything without having to modify anything in the UI or run anything in CLI after the environment is created.
01:00 zhangjn joined #fuel-dev
01:06 aleksandr_null joined #fuel-dev
01:11 aleksandr_null joined #fuel-dev
01:41 aleksandr_null joined #fuel-dev
01:42 shimura_ken joined #fuel-dev
01:46 tzn joined #fuel-dev
01:46 aleksandr_null joined #fuel-dev
01:49 dims joined #fuel-dev
02:08 sylwesterB joined #fuel-dev
02:23 tzn joined #fuel-dev
02:28 tzn joined #fuel-dev
02:30 _tzn joined #fuel-dev
02:47 ilbot3 joined #fuel-dev
02:47 Topic for #fuel-dev is now #fuel-dev Fuel dev docs http://docs.mirantis.com/fuel-dev/ | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel-dev/ | gerrit traffic @ #fuel-tracker
03:01 someara2_ joined #fuel-dev
03:15 zhangjn_ joined #fuel-dev
03:57 sylwesterB joined #fuel-dev
04:25 tzn joined #fuel-dev
05:39 nihilifer joined #fuel-dev
05:41 zhangjn joined #fuel-dev
05:46 sylwesterB joined #fuel-dev
06:01 javeriak joined #fuel-dev
06:27 tzn joined #fuel-dev
06:29 tzn joined #fuel-dev
06:30 fzhadaev joined #fuel-dev
07:06 javeriak_ joined #fuel-dev
07:11 javeriak joined #fuel-dev
07:15 gongysh joined #fuel-dev
07:16 gongysh left #fuel-dev
07:18 karume joined #fuel-dev
07:23 arozdymakha joined #fuel-dev
07:27 karume joined #fuel-dev
07:35 sylwesterB joined #fuel-dev
07:50 e0ne joined #fuel-dev
07:52 sylwesterB joined #fuel-dev
07:56 zigo joined #fuel-dev
08:00 zhangjn joined #fuel-dev
08:00 [HeOS] joined #fuel-dev
08:04 e0ne joined #fuel-dev
08:07 karume joined #fuel-dev
08:14 Liuqing joined #fuel-dev
08:16 karume joined #fuel-dev
08:19 amnk joined #fuel-dev
08:19 mkwiek07 joined #fuel-dev
08:27 karume joined #fuel-dev
08:34 salmon_ joined #fuel-dev
08:34 hyperbaba joined #fuel-dev
08:34 e0ne joined #fuel-dev
08:37 Liuqing joined #fuel-dev
08:43 fzhadaev joined #fuel-dev
08:46 e0ne joined #fuel-dev
08:48 dklenov Nepoc: we do not offer an option to modify default parameters. We consider UI/CLI manipulations as necessary steps. All the operations you mentioned can be done via networking templates.
08:48 dklenov Nepoc: Can you give more details about your use case?
08:48 ekosareva joined #fuel-dev
08:50 Liuqing joined #fuel-dev
08:56 ddmitriev joined #fuel-dev
08:56 karume dklenov: hi, do you know by any chance what process or when the /etc/fuel/plugins directory is created? I'm currently getting an error during the delpoyment because this directory does not exist on the nodes, even though the plugin is installed
08:57 dmitryme mwhahaha: thanks for letting me know. For some reason I’ve missed comment from Bogdan
08:57 dmitryme replied to him
09:00 dklenov karume: I do not know. Checking with other folks.
09:01 dmitryme evgenyl, ikalnitsky: hey guys, could you please review https://review.openstack.org/#/c/241345/ ? The fix resolves a blocker issue in OpenStack CI and you are in fuel-mirror-core group :-)
09:01 alrick joined #fuel-dev
09:01 karume dklenov: thank you! if it helps, even the /etc/fuel directory does not exist on the nodes
09:24 dklenov karume: both /etc/fuel and /etc/fuel/plugins are expected to appear after plugin installation. So please check if you have any errors during plugin installation by the command fuel plugins --install <plugin package>
09:29 someara2 joined #fuel-dev
09:34 karume dklenov: I do not have any error, and actually after the plugin installation I can normally configure the custom settings from the Fuel web UI
09:34 karume dklenov: yesterday there was a guy with the same issue, we both didn't have errors during the plugin installation :(
09:36 karume e.g: Plugin midonet-fuel-plugin-2.2-2.2.52-1.noarch.rpm was successfully installed.
09:49 romcheg MorAle_ vkramskikh, akasatkin ping
09:50 MorAle_ what about arranging a meeting?
09:51 romcheg MorAle_: why?
09:51 MorAle_ won't it be faster? :)
09:52 dklenov karume: hmmm, and where have you taken this midonet plugin from? I see that this plugin is not compatible with MOS7.0, only with 6.1
09:52 dklenov https://www.mirantis.com/products/openstack-drivers-and-plugins/fuel-plugins/
09:52 romcheg MorAle_: We're not in a hurry. Since we have an open source project and this topic is not a private one, I see no reason for moving the discussion to a private channel
09:53 e0ne joined #fuel-dev
09:54 MorAle_ well, ok let me describe the problem then. https://review.openstack.org/#/c/240936/ - causes UI functional tests to fail, because now no notification about discovered nodes appears after cluster deletion
09:54 MorAle_ we need to find out how to fix this in a proper way
09:55 MorAle_ @vkramskikh @jaranovich
09:55 romcheg yup, that the problem appeared after FakeDeletionTask started restoing nodes in its own thread
09:56 romcheg so I suppose it may be the issue with the order of operations.
09:56 romcheg akislitsky_: ^
09:56 karume dklenov: I'm currently developing it for fuel 7.0
09:56 karume but I have the code in my local machine
09:56 apuimedo dklenov: karume is the developer making it
10:00 bogdando joined #fuel-dev
10:07 vkramskikh I suggest to organize a meeting - I have no idea what you guys want from me MorAle_ romcheg
10:07 romcheg vkramskikh: we can discuss this topic here
10:09 vkramskikh no we can't - there is no other python guys and I'll have a meeting in 5 minutes. we can discuss it here, but at least this discussion should be scheduled so everyone is prepared and can participate
10:10 romcheg vkramskikh: there are python guys here, we're not in a hurry and we can wait untill you're back from the meeting
10:11 romcheg vkramskikh: https://review.openstack.org/#/c/240936/ this patch moves functionality related to fake mode of Nailgun from production code
10:12 tkhno joined #fuel-dev
10:13 romcheg vkramskikh: all python tests passed, but UI tests failed. The reason for that is a missing notification about a re-discovered node
10:14 romcheg vkramskikh: while working on that patch I had some issues with the tests, caused by a different order of initialization of tests nodes
10:14 romcheg I suspect it may be the same case with UI tests as well
10:15 vkramskikh so could you ask me a question? I still have not idea what you want from me
10:16 romcheg I'd like to ask you to help me figure out, whether my suspicion is right
10:17 vkramskikh well, if
10:17 vkramskikh > The reason for that is a missing notification about a re-discovered node
10:17 vkramskikh then it means this patch introduces a regression and this should be fixed - and this would fix failing functional tests
10:18 dklenov karume: got it. I need some time to dig the answer
10:19 romcheg vkramskikh: my suspicion is that the issue is not in production code, but in tests, either from UI or python side
10:19 apuimedo thanks dklenov
10:20 vkramskikh romcheg: any reason to think so? does notification appear in fake mode after manual deletion of node?
10:20 bogdando joined #fuel-dev
10:21 vkramskikh if notification appears, that could mean the logic is slightly changed and we should probably increase waiting timeout in our tests
10:22 vkramskikh if it doesn't, then it means this is a regression and it needs to be fixed
10:22 zerda joined #fuel-dev
10:23 zhangjn joined #fuel-dev
10:23 romcheg vkramskikh: I'd say that we should check it in production mode
10:26 Liuqing joined #fuel-dev
10:27 karume dklenov: thanks!
10:35 zhangjn_ joined #fuel-dev
10:36 karume dklenov: I've changed the workaround by mixing deployment_tasks.yaml and the old tasks.yaml and could go further (now the /etc/fuel/plugins directory does exist), but now I'm getting this error: 'comparison of Fixnum with nil failed'. Full trace from astute logs here: http://paste.openstack.org/show/5Cq7lGasVMaTaEhnGACx/
10:40 tzn joined #fuel-dev
10:44 vkramskikh romcheg: what do you mean by "production code"? in our tests we use fake tasks and keep them so that we can use fake mode and run functional tests. Yes, when possible, fake tasks should reuse as many code from real tasks as possible - that was the idea
10:45 romcheg vkramskikh: my idea now is that if produciton code works well but tests fail, it's tests that should be fixed.
10:46 vkramskikh if tests fail, there could be 2 reasons: 1) fake tasks don't work properly 2) tests don't work properly
10:46 romcheg vkramskikh: I did basically nothing to the production code, except moving the code that was responsible for the fake mode to some othere place
10:46 vkramskikh to determine it, do this:
10:46 vkramskikh <vkramskikh> if notification appears, that could mean the logic is slightly changed and we should probably increase waiting timeout in our tests
10:46 vkramskikh <vkramskikh> if it doesn't, then it means this is a regression and it needs to be fixed
10:46 romcheg vkramskikh: there may be the 3rd reason actually
10:46 Liuqing joined #fuel-dev
10:47 romcheg New algorithm of FakeDeletionTask is wrong for some tests.
10:47 vkramskikh let's forget about tests and just try to delete node in fake mode and see if notification appears
10:48 vkramskikh if it doesn't, that means the fake task changed its behaviour and that should be fixed
10:48 vkramskikh if it does, we'll look into tests
10:50 MorAle_ >> let's forget about tests and just try to delete node in fake mode and see if notification appears -- no luck
10:51 BobBall joined #fuel-dev
10:51 BobBall How can I debug a failure in network verification?  "Method verify_networks. ea66f0a0-06ba-4b32-8037-15dc033b1b1f: MCollective call failed in agent 'net_probe', method 'check_repositories_with_setup', failed nodes: ID: 2 - Reason: execution expired ID: 1 - Reason: execution expired"
10:52 vkramskikh I checked out the request and notification appeared
10:52 vkramskikh let me look into tests
10:52 BobBall Astute logs just have a stack trace through various ruby files; but I want to be able to setup one of the nodes in the same way as the network verification tests so I can try and figure out why it can't access what it's trying to get at
10:54 BobBall (Summary is I've got what I believe to be identical network setup on another host, which does work fine)
10:56 huazhihao joined #fuel-dev
10:56 fzhadaev joined #fuel-dev
10:57 MorAle_ vkramskikh: have you run ./manage.py loaddata nailgun/fixtures/sample_environment.json ?
10:57 vkramskikh yes
10:58 jerrygb joined #fuel-dev
11:03 romcheg vkramskikh: did you try it in fake mode or in production mode?
11:03 MorAle_ hm, probably you are testing the wrong case - there is no notification if deleting a cluster containing with nodes?
11:04 vkramskikh romcheg: fake mode
11:05 vkramskikh MorAle_: i've got strange things - when I add a node, deploy cluster and delete it in fake mode manually - notification appears
11:05 vkramskikh if the same is done by tests - there is no notification
11:06 MorAle_ what if not deploying the cluster?
11:06 MorAle_ because I managed to easily reproduce this just using web ui
11:07 MorAle_ just repeating the steps in notifications test
11:07 yottatsa joined #fuel-dev
11:11 vkramskikh i think i found the root cause
11:12 vkramskikh current behaviour in master is wrong
11:12 vkramskikh it simulates rediscovery of nodes which weren't deployed
11:12 vkramskikh which is wrong - these node should just return to unallocated pool
11:13 vkramskikh romcheg's request fixes it
11:13 vkramskikh but introduces another issue - if not deployed cluster is removed, its not deployed nodes are just gone
11:13 vkramskikh so I think 2 things needs to be done
11:14 vkramskikh 1) the behaviour above needs to be fixed - not deployed nodes should just be returned to the pool of unallocate nodes, without "rediscovery" procedure
11:14 vkramskikh 2) tests need to be fixed so that they deploy cluster before removing it
11:28 karume dklenov: just for the record, now I've seen that /etc/fuel/* is not created when installing the plugin, but much after that during the deployment:
11:28 karume D, [2015-11-05T11:20:34.372766 #7880] DEBUG -- : execute_shell_command.rb:23:in `block in <class:Execute_shell_command>' about to execute: mkdir -p /etc/fuel/plugins/midonet-fuel-plugin-2.2/ && rsync -c -r --delete rsync://172.16.0.2:/plugins/midonet-fuel-plugin-2.2/deployment_scripts/ /etc/fuel/plugins/midonet-fuel-plugin-2.2/
11:28 amnk joined #fuel-dev
11:32 rlu joined #fuel-dev
11:32 yottatsa joined #fuel-dev
11:34 romcheg vkramskikh: my patch puts all nodes to the pull
11:35 romcheg *all nodes that were sent for deletion
11:35 vkramskikh romcheg: you can try it yourself - create a cluster on fake env with sample_environment.json, add a node, remove the cluster without deployment, look into the pool again - you won't see the nodes you added to that cluster there
11:36 * romcheg is checking
11:37 vkramskikh (and if you deloy the cluster before removal, the nodes will be back into the pool and there will be rediscovery notification - that's corrrect)
11:39 javeriak joined #fuel-dev
11:39 amnk joined #fuel-dev
11:47 fzhadaev joined #fuel-dev
11:52 someara2 joined #fuel-dev
12:08 zhangjn joined #fuel-dev
12:20 amnk_ joined #fuel-dev
12:21 amnk joined #fuel-dev
12:22 dims_ joined #fuel-dev
12:23 amnk__ joined #fuel-dev
12:27 romcheg vkramskikh, MorAle_ : btw, what do you think about putting all these commands to a tox environment? https://docs.fuel-infra.org/fuel-dev/develop/nailgun/development/env.html#running-nailgun-in-fake-mode
12:27 romcheg tox -e runfake would be much convenient
12:29 amnk joined #fuel-dev
12:33 vkramskikh it maybe, but sometimes i don't need to dropdb, sometimes i need some other fixtures, etc. - so it's hard to make a unviersal command
12:39 zhangjn joined #fuel-dev
12:40 zhangjn joined #fuel-dev
12:43 tzn joined #fuel-dev
12:47 yottatsa joined #fuel-dev
12:59 subscope joined #fuel-dev
13:03 someara2 joined #fuel-dev
13:11 jerrygb joined #fuel-dev
13:22 xarses joined #fuel-dev
13:40 yottatsa joined #fuel-dev
13:44 tzn joined #fuel-dev
13:45 someara2 joined #fuel-dev
13:55 someara2 joined #fuel-dev
14:04 jerrygb joined #fuel-dev
14:16 fzhadaev joined #fuel-dev
14:18 javeriak joined #fuel-dev
14:22 javeriak_ joined #fuel-dev
14:25 rgowrishankar joined #fuel-dev
14:40 dims joined #fuel-dev
14:45 tzn joined #fuel-dev
14:46 omartsyniuk joined #fuel-dev
14:47 jaypipes joined #fuel-dev
14:57 sylwesterB joined #fuel-dev
14:58 sylwesterB joined #fuel-dev
15:01 vsakharov joined #fuel-dev
15:09 neophy joined #fuel-dev
15:12 w_verdugo joined #fuel-dev
15:13 apuimedo joined #fuel-dev
15:16 yottatsa joined #fuel-dev
15:28 apuimedo joined #fuel-dev
15:45 tzn joined #fuel-dev
15:57 angdraug joined #fuel-dev
16:15 jerrygb joined #fuel-dev
16:26 mihgen dklenov: thanks for status in IRC meeting, sorry I just want to double check on ability to choose bootstrap. I looked at the spec. You've replied "no" on my question " in terms of UX, can I use centos to start as defaul, but then change my mind and switch to ubuntu when fuel master is already installed ?"
16:26 mihgen my use case could be "let's start with centos as I don't have Internet at all"
16:27 mihgen and then bootstrap nodes with centos, discover (for instance) that some driver is missing, and now I want to try ubuntu bootstrap
16:27 mihgen will I be able to do it by using CLI tool?
16:30 jaypipes joined #fuel-dev
16:30 dklenov mihgen: we plan to start with ubuntu by default and assemble it during fuel master installation
16:30 dklenov if it fails (e.g. no internet access), user will have a warning in UI that bootstrap is not specified
16:31 javeriak joined #fuel-dev
16:31 dklenov in this case user can generate a new ubuntu one (if connectivity problem was resolved) or upload already created
16:31 jerrygb joined #fuel-dev
16:31 dklenov and this can be any image (also centos-based) if it satisfies described format
16:33 mihgen dklenov: so we won't have centos image in the ISO by default anymore .. ?
16:34 tzn joined #fuel-dev
16:35 dklenov right
16:37 mihgen not sure if I like it, but let me think twice about it first )
16:42 asaprykin joined #fuel-dev
16:51 tuvenen_ joined #fuel-dev
16:51 someara2_ joined #fuel-dev
16:53 smakar_ joined #fuel-dev
16:54 fBigBro_ joined #fuel-dev
16:56 ktychkova_ joined #fuel-dev
16:59 preilly_ joined #fuel-dev
16:59 evgenyl_ joined #fuel-dev
16:59 ukinau joined #fuel-dev
17:00 izinovik- joined #fuel-dev
17:05 Guest88471 joined #fuel-dev
17:07 dilyin joined #fuel-dev
17:19 angdraug zigo: https://bugs.launchpad.net/fuel/+bug/1513252
17:34 subscope joined #fuel-dev
17:41 e0ne joined #fuel-dev
17:47 angdraug mattymo: http://www.gossamer-threads.com/lists/openstack/operators/41660
17:48 angdraug looks like "soft delete" is an unwritten policy, and there's a growing sentiment against it, with no concrete actions towards reverting it
17:50 amnk joined #fuel-dev
17:53 angdraug an older thread about the same: http://www.gossamer-threads.com/lists/openstack/dev/19620
17:54 e0ne joined #fuel-dev
18:04 e0ne joined #fuel-dev
18:10 jfluhmann joined #fuel-dev
18:16 javeriak joined #fuel-dev
18:24 tzn joined #fuel-dev
18:34 [HeOS] joined #fuel-dev
18:58 jerrygb joined #fuel-dev
19:03 someara2 joined #fuel-dev
19:05 tzn joined #fuel-dev
19:07 ddmitriev joined #fuel-dev
19:07 someara2 joined #fuel-dev
19:42 someara2 joined #fuel-dev
19:47 ogelbukh angdraug and team: I've cut isolated deployment spec out of this review: https://review.openstack.org/#/c/224302/
19:48 ogelbukh now it's separate CR: https://review.openstack.org/#/c/242201/
19:48 angdraug ogelbukh: thanks!
19:48 someara2 joined #fuel-dev
19:51 jfluhmann joined #fuel-dev
19:53 jerrygb joined #fuel-dev
20:00 jobewan joined #fuel-dev
20:01 zigo angdraug: The issue is puppet from Fuel using the wrong .conf file, and therefore doing the definition of the vhost twice.
20:01 zigo Writing this in the bug report...
20:09 angdraug thanks, please link the reviews we discussed yesterday to make it apparent what needs to happen to make this bug go away
20:13 mwhahaha so we might just need to make the package config go away
20:13 mwhahaha it's not a vhost config
20:16 mwhahaha the problem is our config (horizon_vhost.conf) is a vhost config, the package provided one (openstack-daskhoard-alias-only.conf) is not a vhost config
20:17 mwhahaha so the WSGIDaemonProcess is duped between the two so they can't both be in place
20:17 mwhahaha we want our vhost config and not the alias-only configuration in place
20:17 mwhahaha i believe
20:26 jfluhmann joined #fuel-dev
20:35 mwhahaha zigo: is the openstack-dashboard-alias-only.conf enabled by default via the package?
20:40 zigo mwhahaha: There 2 types of config, one that does an Alias, which is that -alias-only.conf file, and one that takes over the vhost which you can select using debconf.
20:40 mwhahaha so to be honest, i usually never want the default configs for apache packages so i'd really like an option where it doesn't do either
20:41 mwhahaha since we don't modify the existing configs this doesn't do any good to require one or the other
20:41 zigo mwhahaha: In this case, you just wouldn't install openstack-dashboard-apache, and do everything yourself.
20:41 zigo That's the point of having a separate package for the Apache config ...
20:41 zigo Just use "apt-get install openstack-dashboard" ...
20:42 mwhahaha so we need to modify puppet-horizon to make openstack-dashboard-apache optional
20:42 mwhahaha but then i don't get teh manage.py actions and that has to be done via puppet
20:42 mwhahaha i want openstack-dashboard-apache but i don't want your configs enabled
20:43 mwhahaha so maybe i'll just a2dissite openstack-dashboard-alias-only.conf
20:44 zigo mwhahaha: I wouldn't work, IMO, in case of upgrades.
20:44 zigo IE, the package would re-enable it.
20:44 artem_panchenko joined #fuel-dev
20:44 zigo The 2nd mode is using a vhost though.
20:45 zigo And it's using the /, not /horizon.
20:45 mwhahaha but like i said i don't want your configs
20:46 mwhahaha any of them
20:46 mwhahaha but i do want the compress actions :/
20:47 mwhahaha can we adjust the post the postinst do have 3 config states? vhost/alias/none but still do the manage.py, key and reload
20:51 zigo mwhahaha: The compress is already present in the openstack-dashboard package, no problem.
20:52 zigo You don't need to do it, even if you want to do the Apache config yourself.
20:52 zigo The "none" option is to not install openstack-dashboard-apache.
20:53 zigo The key thing is already handled too.
20:53 mwhahaha ok well then i guess the option is to fix the puppet module to make openstack-dashboard-apache optional
20:53 zigo Right.
20:57 mwhahaha so debian has both openstack-dashboard and openstack-dashboard-apache?
21:01 mwhahaha https://review.openstack.org/242218 assuming the answer to that question is yes
21:06 mwhahaha zigo: openstack-dashboard pulls in openstack-dashboard-apache i think
21:08 mwhahaha zigo: so if that's true we're not installing it via puppet since we aren't running debian so I can't not install it?
21:12 mwhahaha zigo: http://paste.openstack.org/show/478126/ it would appear that i cannot just install openstack-dashboard?
21:15 javeriak my controllers keep failing deployment with "/Stage[main]/Cluster::Vrouter_ocf/Service[p_vrouter] (err): Could not evaluate: undefined method `[]' for nil:NilClass"
21:16 javeriak can't figure out whats wrong
21:19 mwhahaha the good ol' `[]' for nil:NilClass
21:19 mwhahaha usually that's a null object in some ruby code but it is also really really hard to debug
21:20 mwhahaha Do you have additional logs that I can look at? The  full puppet error might be handy
21:20 javeriak sure let me pastebin
21:24 javeriak mwhahaha have tried taking out the relevant portion, please see if this helps--> http://pastebin.com/6Wi0jJBM
21:24 mwhahaha did it not have a stack trace after the undefined method line?
21:27 javeriak yes http://pastebin.com/mR4zVcfq
21:27 yottatsa joined #fuel-dev
21:27 mwhahaha what version is this?
21:27 mwhahaha 7.0?
21:28 javeriak yes 7.0
21:30 mwhahaha my assumption is that it's not able to properly query the cluster to get the information and it's not finding the primitive it's looking for and so it throws that error
21:30 mwhahaha but i'm not sure why it would be doing that
21:30 mwhahaha anything special about this environment? plugins, etc?
21:31 javeriak yes an additional neutron plugin im working on, i have been able to deploy successfully a few times before, dont know whats going on this timr around
21:33 mwhahaha might be a task ordering thing if  you're messing with that
21:35 javeriak but all my tasks are post_deployment
21:35 mwhahaha there might be an error elsewhere that ultimate results in that failure
21:35 mwhahaha would have to look through all of the logs to be certain
21:38 javeriak what logs would be pertinent?
21:38 mwhahaha probably a failure in the puppet logs
21:38 mwhahaha you could look for an 'err:' prior to that
21:38 javeriak i'll try setting up a new clean cluster
21:38 javeriak yes I've looked through the whole thing with that grep, thats the only error in it and its consistent last 3-4 runs
21:39 mwhahaha yea i'd reset fresh and if it continues file a bug with a log snapshot
21:39 javeriak alright thanks
21:41 _tzn joined #fuel-dev
22:03 HeOS joined #fuel-dev
22:10 smakar joined #fuel-dev
22:29 amnk joined #fuel-dev
22:33 dpyzhov joined #fuel-dev
22:44 yottatsa joined #fuel-dev
23:07 tzn joined #fuel-dev
23:16 tzn joined #fuel-dev
23:33 jerrygb joined #fuel-dev
23:45 jobewan joined #fuel-dev
23:49 jerrygb_ joined #fuel-dev
23:55 maximov joined #fuel-dev

| Channels | #fuel-dev index | Today | | Search | Google Search | Plain-Text | summary