Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel-dev, 2014-05-19

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

All times shown according to UTC.

Time Nick Message
05:13 Ch00k joined #fuel-dev
05:31 dshulyak_ joined #fuel-dev
05:37 EeeBotu New bug #1320749 in fuel: "Show notification if disk drive is too small" [Medium, New] https://bugs.launchpad.net/bugs/1320749
06:11 salmon_ joined #fuel-dev
06:16 Ch00k joined #fuel-dev
06:30 asledzinskiy joined #fuel-dev
06:38 al_ex joined #fuel-dev
06:42 sambork joined #fuel-dev
06:51 teran joined #fuel-dev
07:14 artem_panchenko joined #fuel-dev
07:24 john3213 joined #fuel-dev
07:27 saibarspeis joined #fuel-dev
07:29 john3213 left #fuel-dev
07:44 bogdando https://review.openstack.org/93815 kernel-match-tcp-keepalive-to-nova-report-interval /Merged now, and should be backported to 4.1.1, perhaps
07:44 bogdando see https://etherpad.openstack.org/p/fuel-ha-rabbitmq
07:45 e0ne joined #fuel-dev
07:47 EeeBotu New bug #1320779 in fuel: "Deployment failed with MCollective call failed in agent 'uploadfile', method 'upload'" [High, New] https://bugs.launchpad.net/bugs/1320779
07:50 bogdando https://review.openstack.org/94147
07:55 Ch00k joined #fuel-dev
08:03 meow-nofer bug: nailgund bogs down on large number of nodes
08:03 meow-nofer Meg McRoberts: marked as fixed issue in 5.0
08:04 meow-nofer ahem
08:34 akasatkin left #fuel-dev
08:37 brain461 joined #fuel-dev
08:40 akasatkin joined #fuel-dev
08:41 mihgen bogdando: kernel-match-tcp-keepalive-to-nova-report-interval should be backported, yes, feel free to create patch for stable/4.1
08:47 EeeBotu New bug #1320795 in fuel: "[System Tests] Sahara test fails with timeout on OSTF" [High, New] https://bugs.launchpad.net/bugs/1320795
08:49 bogdando mihgen, ok. There are some more backporting comments should be addressed in the etherpad doc
08:59 EeeBotu New bug #1320801 in fuel: "Fuel CI incorrectly puts -1 for centos & ubuntu (stable/4.1)" [Critical, New] https://bugs.launchpad.net/bugs/1320801
08:59 EeeBotu New bug #1320800 in fuel: "[System Tests] ha_delete_vips test failed with timeout after deletion vips" [High, New] https://bugs.launchpad.net/bugs/1320800
08:59 mihgen bogdando: https://bugs.launchpad.net/fuel/+bug/1320801 about -1 in CI
09:10 teran joined #fuel-dev
09:28 asledzinskiy joined #fuel-dev
09:29 teran joined #fuel-dev
09:43 mihgen warpc: https://bugs.launchpad.net/fuel/+bug/1319823 reassigned to you..
09:47 EeeBotu New bug #1320810 in fuel: "sahara OSTF test fails with cluster error state" [Medium, Confirmed] https://bugs.launchpad.net/bugs/1320810
09:47 EeeBotu New bug #1320803 in fuel: "[devops] fuel-devops team is needed in LP" [High, Confirmed] https://bugs.launchpad.net/bugs/1320803
09:53 dmitryme Tatyanka_Leontov: I’ve left a comment on the bug https://bugs.launchpad.net/bugs/1320810
09:56 Tatyanka_Leontov dmitryme: Thanks, I just want to be sure that it is not system test problem (as example pure resources by cpu and nova can not get claim and mark instance with error) or infra and environment problem and understand why we do not get instance Active - that why I get this issue)
09:58 bogdando time sync in system tests https://bugs.launchpad.net/fuel/+bug/1320815. Not sure iether its a relevant one , tho
09:59 EeeBotu New bug #1320815 in fuel: "Implement/update time sync logic for CI (system tests)" [High, Confirmed] https://bugs.launchpad.net/bugs/1320815
10:05 e0ne joined #fuel-dev
10:12 akupko joined #fuel-dev
10:34 warpc https://review.openstack.org/#/c/94163  - bogdando, dilyin, please review.
10:37 zynzel bogdando: hello, i have question about yours comment to https://bugs.launchpad.net/fuel/+bug/1320183
10:37 zynzel bogdando: who should decide if we should backport this? What is procedure for backporting?
10:41 bogdando zynzel, hi. Backporting sould be done as it described here https://lists.launchpad.net/fuel-dev/msg00698.html
10:43 bogdando zynzel, once you've updated the ticket status or submitted the backport, the reviewers should decide either the ticket or backported patch should be accepted or not
10:43 sambork joined #fuel-dev
10:43 zynzel bogdando: ok, so i should wait for decision right?
10:43 mihgen zynzel: we don't have written policy yet for decision whether patch devotes to be backported to older releases or not. The rule we follow is tech lead or product owner may decide to propose for backporting if bug affects users, usually for High & Critical priority bugs only
10:43 bogdando zynzel, in order to backport the *patch* you could just checkout to stable/4.1 and cherry pick from the master accepted one
10:43 zynzel and for now, leave this as is
10:44 bogdando zynzel, ok. perhaps we'll clarify it later :)
10:45 mihgen zynzel: actually https://review.openstack.org/#/c/93884/ is very good candidate for back porting I think..
10:45 zynzel ok, so i leave this - and if anybody want to see this in 4.1 we can backport this in future
10:45 zynzel mihgen: oh ;)
10:47 bogdando zynzel, ok then, I will update the status for the ticket, so it became ready for bporting...
10:49 bogdando zynzel, now you are good to go with backporting :) Feel free to ask me, if you have a questions for a gerrit workflow on that
10:51 zynzel bogdando: i should only change branch to stable/4.1, backport patch (chery-pick, diff, anything) and push this to review
10:51 zynzel right? ;)
10:52 bogdando yes... fixing merge conflicts and submitting with ' git review stable/4.1' as well
10:53 anotchenko joined #fuel-dev
10:53 bogdando s/merge/the
10:53 EeeBotu New bug #1320834 in fuel: "Dhc relay check failed in system tests" [Critical, New] https://bugs.launchpad.net/bugs/1320834
10:53 EeeBotu New bug #1320831 in fuel: "Mongo replication typo in puppet manifest" [Low, New] https://bugs.launchpad.net/bugs/1320831
10:56 mihgen bogdando: Bogdan, about https://bugs.launchpad.net/fuel/+bug/1320210 - I think we need to analyze logs from Julia's env. It might be related to overloaded env and some issues in puppet resources dependencies, or some other random stuff
10:56 mihgen I'm still wondering why mysql is in the picture there, and ceilometer db-sync returned 1
10:58 mihgen who has free hands to reproduce https://bugs.launchpad.net/fuel/+bug/1317548 manually or start analyzing logs?
11:00 warpc please review https://review.openstack.org/#/c/94163
11:04 salmon_ mihgen: I will try to reproduce it
11:04 mihgen salmon_: cool, thanks
11:06 zynzel bogdando: mihgen https://review.openstack.org/#/c/94168/
11:06 e0ne joined #fuel-dev
11:18 e0ne joined #fuel-dev
11:20 bogdando zynzel, lgtm, thanks
11:21 holser zynzel, bogdando thanks a lot
11:21 bogdando mihgen, yes it could be related to the bad environment condition as well (there are logs from the old nodes). Puppet dependencies could not vary, tho, hence if ot couldn't be reproduced in the clear env, it should not change in the future as well
11:42 skonno joined #fuel-dev
11:52 al_ex2 joined #fuel-dev
11:53 e0ne joined #fuel-dev
11:54 EeeBotu New bug #1320842 in fuel: "Wrong dependencies for set_mysql_rootpw" [High, New] https://bugs.launchpad.net/bugs/1320842
11:57 al_ex joined #fuel-dev
12:10 mirrorbox hi
12:11 mirrorbox as you might remember we're working on adding hardware raid configuration on nodes support into fuel
12:11 mirrorbox and the flow for the node is the following
12:12 mirrorbox user configures raid -> we spawn a raid configuration task on the node -> task is complete and raid info is returned back to nailgun via the agent -> user configures the volumes on the node -> then the stuff goes as usual
12:12 mirrorbox and the node should be somehow be locked while the raid configuration task is being running on it
12:12 mirrorbox what'd be the best facility to do that?
12:13 mirrorbox we've been offered to user Cluster's is_locked, but locking a complete cluster sounds a little strange
12:13 mirrorbox it'd be annoying for a user
12:13 mirrorbox any thoughts?
12:32 higgins joined #fuel-dev
12:34 anotchenko joined #fuel-dev
12:34 dilyin dilyin
12:47 Ch00k joined #fuel-dev
12:49 mihgen bogdando: xenolog: folks, who work on HA.. there is one bug https://bugs.launchpad.net/fuel/+bug/1320222 it is always failing test in system tests suite, can someone take a look and triage whether it's tests issue or fuel-library?
12:58 meow-nofer mirrorbox, we don't have such thing as per-node locking right now on UI, but it isn't very hard to implement it on backend in the future
12:58 meow-nofer mirrorbox, by the way, is it a long process? I mean, what about manual interruption?
12:59 mirrorbox meow-nofer: let me ask how long it takes
12:59 EeeBotu New bug #1320861 in fuel: "zabbix triger for fuel ci failures" [Wishlist, New] https://bugs.launchpad.net/bugs/1320861
13:05 artem_panchenko joined #fuel-dev
13:09 mirrorbox meow-nofer: I was told it takes a few seconds
13:14 mihgen xenolog: is https://review.openstack.org/#/c/93956/, which fixes RabbitMQ controller reboot issues, ready for review / testing?
13:15 xenolog mihgen: not ready yet
13:15 vkramskikh it wouldn't be complicated to implement checks for node_id for tasks. we check for tasks names when we decide whether we should lock something on UI, will add yet another check for node_id
13:16 mihgen bogdando: holser: folks can you help in reviewing https://review.openstack.org/#/c/94169/1 ..
13:16 holser mihgen: sure thing
13:19 bogdando https://bugs.launchpad.net/fuel/+bug/1320222 ./node-1.test.domain.local/puppet-apply.log:2014-05-15T23:58:32.449793+00:00 notice:  Finished catalog run in 13423.57 seconds
13:19 bogdando perhaps we should eliminate ntp issues at last
13:23 mihgen bogdando: yep.. I think we need to go over ssh to nodes and sync time after snapshot revert, not over mcollective: https://bugs.launchpad.net/fuel/+bug/1320815/comments/1
13:26 al_ex2 joined #fuel-dev
13:26 Ch00k joined #fuel-dev
13:29 bogdando mihgen, regarding https://bugs.launchpad.net/fuel/+bug/1320222 I'd say it is a time sync issue causing the unpredictable outages (galera death , for example)
13:35 mihgen bogdando: ok, thanks for debugging. Tatyanka_Leontov, nurla do you think we can fix NTP issues ^^^ in 5.0? See https://bugs.launchpad.net/fuel/+bug/1320815/comments/1
13:36 mihgen bogdando: angdraug: MiroslavAnashkin holser alex_didenko xenolog zynzel Folks, what about this very small patch, but so many discussed? https://review.openstack.org/#/c/93883/
13:36 mihgen I see to response to Ihar Hrachyshka questions, and there is -1 from Ubuntu
13:37 mihgen also, do we really need it in 5.0, or we can easily survive without it and back port later if needed?
13:39 mihgen holser: any success with https://bugs.launchpad.net/fuel/+bug/1319942 ?
13:39 holser mihgen: yes
13:39 holser mihgen: I am trying to produce a fix right now
13:39 mihgen holser: ok, cool, thanks
13:54 bogdando mihgen, https://review.openstack.org/#/c/93883/ we have +4, perhaps we can merge it
13:54 bogdando mihgen, spreading the connections points around the nodes it is a good practice as well
13:54 bogdando for rabbitmq clustering
14:07 bogdando https://review.openstack.org/#/c/93927/ backport ready for merge
14:15 jobewan joined #fuel-dev
14:20 anotchenko joined #fuel-dev
14:21 mihgen bogdando: regarding https://review.openstack.org/#/c/93883/ - a) it's Fuel CI -1, wondering if could be CI issue; b) did we respond to the guy?
14:25 mihgen holser: if https://bugs.launchpad.net/fuel/+bug/1320831 is Low, then I'll move it to 5.1
14:25 mihgen holser: we don't keep low/medium bugs after SCF in current release
14:28 holser mihgen: feel free …
14:34 mihgen bogdando: you suggest to increase vcpu, but we should have overcommitment enabled in scheduler, do we?
14:35 mihgen bogdando: for https://bugs.launchpad.net/fuel/+bug/1320261
14:40 holser mihgen: Could you help me to classify https://bugs.launchpad.net/fuel/+bug/1320905 bug
15:08 EeeBotu New bug #1320910 in fuel: "heat-engine logs is empty on UI" [Undecided, New] https://bugs.launchpad.net/bugs/1320910
15:08 EeeBotu New bug #1320905 in fuel: "Cannot modify Networks" [Undecided, New] https://bugs.launchpad.net/bugs/1320905
15:20 xarses joined #fuel-dev
15:28 anotchenko joined #fuel-dev
15:34 mihgen bogdando: is https://bugs.launchpad.net/fuel/+bug/1320842 really High for 5.0 ?
15:35 mihgen holser: don't see issue… if you add nodes or remove, you can still modify network settings
15:36 mihgen holser: so it is not related. but once you clicked on Deploy button, network tab is locked
15:36 Ch00k joined #fuel-dev
15:36 mihgen unless you reset the whole env
15:36 holser mihgen: Deploy, delete all, and it will be locked …
15:36 mihgen if you reset, all nodes go to bootstrap and you can start modifying it again
15:37 mihgen holser: yes. Should we enable it - is it the question?
15:37 mihgen I think we should, because actually you can modify without fear that existing nodes configuration support it, because you simply don't have existing nodes
15:38 mihgen then it is the bug, vkramskikh ^^^  . I think it is rather low priority for 5.1 though
15:38 holser mihgen: if no nodes, I think we should. Case: I created env it was almost ok, so I deleted all and want to modify some minor settings, for instance adding more Public IPs rathar than creating new env from scratch
15:38 holser yeah, it’s low, but would be nice to have …
15:39 mihgen holser: yep. You could do same by resetting an env.
15:39 holser mihgen thank you for tip, as it’s not clear. I wondered why I was not able …
15:40 mihgen holser: actually your message "Add nodes to environment, but do not deploy" is not fully correct
15:40 holser Agree
15:40 mihgen you actually deployed
15:40 holser I’ll modify …
15:40 mihgen and then removed nodes, that's why vkramskikh could not reproduce. Ok, thanks
15:41 vkramskikh modify the steps then please
15:42 vkramskikh the missing steps are deploy and then delete all nodes?
15:43 holser yeah
15:43 holser I corrected title and subj
15:43 holser Sorry for wrong direction …
15:43 holser vkramskikh: ^^^
15:44 vkramskikh well, i can recall a discussion about this stuff
15:44 vkramskikh maybe a year ago
15:44 vkramskikh about whether or not cluster status should become "new" after deleting all the nodes so all the tabs become unlocked
15:45 vkramskikh i cannot remember why we keep it ready, maybe python guys can answer
15:46 holser vkramskikh: I showed the case where I needed to modify floating IP range a little bit. if I reset, I will loose all setting that are already set.
15:47 vkramskikh i see
15:47 vkramskikh the main reason for this behavior is that cluster status is "ready" even when all the nodes are deleted
15:48 jaypipes joined #fuel-dev
15:48 saibarspeis joined #fuel-dev
15:49 vkramskikh holser how did you manage to delete all the nodes? on the attempt i get an error "Environment should have 1 controller node"
15:49 vkramskikh did you use cli?
15:50 holser vkramskikh, I used UI, just checklisted all and deleted …
15:54 anotchenko joined #fuel-dev
16:08 EeeBotu New bug #1320924 in fuel: "[devops] Fuel CI for partners: document integration" [High, Confirmed] https://bugs.launchpad.net/bugs/1320924
16:08 EeeBotu New bug #1320923 in fuel: "Deployment failed with nova.openstack.common.threadgroup [-] (ProgrammingError) (1146, "Table 'nova.services' doesn't exist")" [High, New] https://bugs.launchpad.net/bugs/1320923
16:20 EeeBotu New bug #1320935 in fuel: "nailgun-net-check misses tcpdump from deps" [Medium, Confirmed] https://bugs.launchpad.net/bugs/1320935
16:29 teran joined #fuel-dev
16:37 artem_panchenko joined #fuel-dev
16:39 dshulyak_ joined #fuel-dev
16:46 tnurlygayanov joined #fuel-dev
16:57 IlyaE joined #fuel-dev
16:59 rmoe joined #fuel-dev
17:00 dshulyak_ joined #fuel-dev
17:20 angdraug joined #fuel-dev
17:28 mihgen alex_didenko: bogdando: mattymo: https://review.openstack.org/94229, https://review.openstack.org/94232
18:06 mihgen akasatkin: do you still have an env where you reproduced https://bugs.launchpad.net/fuel/+bug/1312443 ?
18:11 mihgen angdraug: xarses folks if you are back from summit
18:12 mihgen https://bugs.launchpad.net/fuel/+bug/1317548 ceph vm migration, I think we need to try to reproduce manually..
18:28 e0ne joined #fuel-dev
18:30 Ch00k joined #fuel-dev
18:37 tatyana joined #fuel-dev
18:59 xarses mihgen: will do
19:00 IlyaE joined #fuel-dev
19:47 angdraug I'll take this one
19:54 warpc joined #fuel-dev
19:54 angdraug joined #fuel-dev
19:54 jaypipes joined #fuel-dev
19:55 angdraug joined #fuel-dev
19:55 christopheraedo joined #fuel-dev
20:01 jeremydei joined #fuel-dev
20:07 tatyana joined #fuel-dev
20:41 e0ne joined #fuel-dev
20:41 Gleb joined #fuel-dev
20:43 Gleb Do anyone knows how to setup neutron for compute nodes that are running in XenServer?
20:43 Gleb Do anyone has any expirience with neutron+XenServer ?
20:45 e0ne_ joined #fuel-dev
20:57 ehuang joined #fuel-dev
21:11 prevost joined #fuel-dev
21:11 prevost left #fuel-dev
21:11 teran joined #fuel-dev
21:27 IlyaE joined #fuel-dev
22:15 teran joined #fuel-dev
22:20 teran_ joined #fuel-dev
22:38 IlyaE joined #fuel-dev
22:53 IlyaE joined #fuel-dev
23:21 xarses joined #fuel-dev
23:47 xarses joined #fuel-dev

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