Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel-dev, 2014-08-27

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

All times shown according to UTC.

Time Nick Message
00:20 rmoe joined #fuel-dev
01:02 teran joined #fuel-dev
01:11 agrebennikov joined #fuel-dev
01:29 xarses joined #fuel-dev
04:07 apodrepniy__ joined #fuel-dev
04:08 asyriy joined #fuel-dev
04:31 prmtl_ joined #fuel-dev
05:26 aepifanov joined #fuel-dev
05:29 adanin joined #fuel-dev
05:48 tzn joined #fuel-dev
05:56 prmtl joined #fuel-dev
05:59 ddmitriev1 joined #fuel-dev
06:07 aepifanov joined #fuel-dev
06:10 sambork joined #fuel-dev
06:20 Longgeek joined #fuel-dev
06:40 mihgen dshulyak: how can it be that same change-id, but https://review.openstack.org/#/c/115648/ is different from merged https://review.openstack.org/#/c/111545/ ?
06:42 mihgen dshulyak: there are so many patches refer to a single bug.. we should not lose any if we started backports
06:49 tzn joined #fuel-dev
06:50 tuvenen joined #fuel-dev
06:56 artem_panchenko joined #fuel-dev
06:56 tnurlygayanov joined #fuel-dev
06:58 artem_panchenko joined #fuel-dev
07:03 teran joined #fuel-dev
07:07 HeOS joined #fuel-dev
07:10 salmon_ joined #fuel-dev
07:20 e0ne joined #fuel-dev
07:21 sambork joined #fuel-dev
07:22 dshulyak mihgen: i've decided to squash all those patches, that is why it is different
07:24 msemenov joined #fuel-dev
07:24 mihgen dshulyak: omg not very good idea I think.. but if you did already, we would at least need to know what it is combined of - what are combined commits from master
07:25 mihgen dshulyak: the thing is that it is hard to review and understand whether it's same code which is in master, or something different
07:26 EeeBotu New bug #1361993 in fuel: "OpenStack deployment failed due to glance db connectivity" [Critical, Confirmed] https://bugs.launchpad.net/bugs/1361993
07:30 teran joined #fuel-dev
07:36 e0ne joined #fuel-dev
07:37 HeOS joined #fuel-dev
07:42 e0ne joined #fuel-dev
07:49 teran joined #fuel-dev
07:58 e0ne joined #fuel-dev
08:00 aepifano1 joined #fuel-dev
08:00 adanin_ joined #fuel-dev
08:02 HeOS joined #fuel-dev
08:04 omelchek1 joined #fuel-dev
08:04 rshon joined #fuel-dev
08:05 e0ne_ joined #fuel-dev
08:05 aglarendil fuel-library Mirantis team. look into https://etherpad.openstack.org/p/fuel-library-weekly-syncup
08:05 aglarendil and update your action items
08:06 aglarendil dilyin: holser bogdando xenolog warpc_ sbog ^^
08:06 aglarendil mattymo: ^^
08:08 SergeyLukjanov2 joined #fuel-dev
08:09 ruhe2 joined #fuel-dev
08:10 monester_ joined #fuel-dev
08:11 mattymo joined #fuel-dev
08:11 eshumkher joined #fuel-dev
08:12 shauno_ joined #fuel-dev
08:12 dilyin joined #fuel-dev
08:16 agordeev joined #fuel-dev
08:16 eshumkher joined #fuel-dev
08:18 dshulyak joined #fuel-dev
08:21 Longgeek joined #fuel-dev
08:22 SergK joined #fuel-dev
08:22 f13o joined #fuel-dev
08:27 sambork joined #fuel-dev
08:41 dancn joined #fuel-dev
08:43 Longgeek joined #fuel-dev
08:45 EeeBotu New bug #1362045 in fuel: "[system tests] AssertionError in Heat system test "heat_simple_nova"" [Critical, Confirmed] https://bugs.launchpad.net/bugs/1362045
08:49 aepifanov joined #fuel-dev
08:49 tzn joined #fuel-dev
08:52 igajsin joined #fuel-dev
09:03 shauno__ joined #fuel-dev
09:04 e0ne joined #fuel-dev
09:15 tdubyk joined #fuel-dev
09:20 skolekonov joined #fuel-dev
09:26 EeeBotu New bug #1362071 in fuel: "rpmvercmp.rb - incorrect result of comparing due to package issues in 5.0" [Critical, New] https://bugs.launchpad.net/bugs/1362071
09:26 EeeBotu New bug #1335804 in fuel: "nova-manage db sync fails due to nova-api/nova-conductor being running before the migration scripts have been applied" [High, Triaged] https://bugs.launchpad.net/bugs/1335804
09:42 e0ne https://gerrit.mirantis.com/21254 - please, review
09:44 e0ne joined #fuel-dev
10:08 HeOS joined #fuel-dev
10:11 dpyzhov joined #fuel-dev
10:16 Longgeek joined #fuel-dev
10:26 EeeBotu New bug #1362101 in fuel: "Snapshot should contain Zabbix logs" [Medium, New] https://bugs.launchpad.net/bugs/1362101
10:45 mihgen salmon_: hi
10:45 salmon_ mihgen: yo
10:45 mihgen salmon_: do we have any guidance on how to change pass if you forget it?
10:45 mihgen I assume via keystone REST API somehow or in DB
10:46 mihgen I think we should provide the easiest way to our docs
10:47 salmon_ mihgen: Meg is writing docs for it. there is description what to do if you forget password https://review.openstack.org/#/c/109777/8/pages/operations/6500-fuel-auth.rst
10:48 salmon_ "f you forget the password,42
10:48 salmon_ you can change it43
10:48 salmon_ by using the **keystone** command on the Fuel Master Node:"
10:48 mihgen --os-token=admin_token - is it hardcoded token?
10:49 mihgen or there is an explanation below
10:49 salmon_ "You can find admin_token in the */etc/fuel/astute.yaml* file."
10:49 mihgen The password must be changed in the */etc/fuel/astute.yaml - what passord?
10:49 mihgen do you mean admin token here or password?
10:50 salmon_ password, always password.
10:50 mihgen salmon_: why would you need to change it then, if it's being stored in astute.yaml?
10:50 salmon_ admin_token is randomly generated and can not be changed
10:50 mihgen salmon_: you can simply take a look into the file then
10:51 HeOS joined #fuel-dev
10:51 salmon_ mihgen: you don't need to change it there. It's only required for upgrade... I'm going to change it in 6.0
10:52 mihgen then we don't need a section about forgetting the password
10:52 mihgen if you forget it - take a look at astute.yaml
10:53 mihgen and actually I don't like it - as it is insecure. I don't want my password being in insecure form on the node, so some other ops guy can read it up
10:53 salmon_ mihgen: no, password it's not stored there. It's stored in keystone db
10:54 mihgen salmon_: well documentation then is totally messing me up
10:54 mihgen salmon_: The password is stored in the *astute.yaml* file
10:54 mihgen The password must be changed in the */etc/fuel/astute.yaml* file or it will not be possible to run the upgrade process.
10:55 salmon_ mihgen: I'm not sure why upgrade requires this password
10:56 sambork joined #fuel-dev
10:56 mihgen evgeniyl: what's the story with a passord? did you try to test upgrades if you change password in Fuel UI?
10:57 mihgen evgeniyl: why do we need it in astute.yaml, anywhere else? it's insecure
10:57 mihgen evgeniyl: it's actually not changing in /etc/fuel/astute.yaml as I can see, after changing pass in UI
10:59 evgeniyl mihgen: I don't need to try it, I know that it won't work in case if user will change password in 5.1 and then he will try to upgrade to 6.0 (or 5.1.1), it's required because upgrade script needs to authenticate in nailgun via keystone.
11:00 Longgeek joined #fuel-dev
11:00 mihgen evgeniyl: ok, so can you confirm that we don't need password in config file in 5.1 ?
11:01 mihgen and second, why do we need password for your scripts? for such a thing were invented other mechanisms, such as services tokens
11:02 mihgen that's how all openstack services get authz in keystone. no need to use user's pass at all
11:02 evgeniyl mihgen: I can confirm that we won't have problems in 5.1 release, but we will have problems in the next releases. And for 5.1 we add default credentials during the upgrade in /etc/fuel/astute.yaml
11:03 mihgen evgeniyl: so if only default admin/admin appears in config, then it is fine
11:03 mihgen but we should not store secure password of user in plain text
11:03 evgeniyl mihgen: it doesn't work, I was discussing other options with salmon_ and dshulyak
11:03 mihgen what doesn't work?
11:03 tzn joined #fuel-dev
11:04 evgeniyl mihgen: service token
11:04 mihgen evgeniyl: how comes? it does in openstack for sure
11:04 mihgen how we r different?
11:04 salmon_ mihgen: we didn't create service for nailgun, I want to fix it after 5.1 release
11:05 salmon_ mihgen: we are using admin_token to authenticate
11:05 salmon_ *to validate
11:05 mihgen salmon_: so we can do it after 5.1 then, it is fine
11:05 evgeniyl salmon_: oh, is it some another token?
11:05 evgeniyl salmon_: so, admin_token != service token
11:05 salmon_ evgeniyl: yup
11:05 mihgen but let's make sure we are good in 5.1 with not storing user's pass in plain text
11:06 mihgen and salmon_ , that you are starting the work on this then right after you fix bugs - as we would need this change even in 5.1.1
11:06 mihgen so we will have to backport it to stable/5.1
11:06 mihgen salmon_: is there a bug about it?
11:06 salmon_ mihgen: this is my plan
11:06 salmon_ mihgen: no, I don't considere is as a bug, rather bad design
11:06 mihgen evgeniyl: salmon_ can you guys please confirm that we do not store updated pass anywhere?
11:06 mihgen salmon_: well it
11:07 mihgen anyway we need to track it somehow now regardless
11:07 evgeniyl mihgen: we have default password in fuelclient config
11:07 mihgen I assume there is should be a bug or essential blueprint about it
11:08 mihgen evgeniyl: [root@fuel ~]# fuel node
11:08 mihgen Unauthorized: need authentication!
11:08 mihgen oh yeah not really good UX. Can we point a user to a config file?
11:08 mihgen where should I look for? to change a pass?
11:08 mihgen should ideally be like ~/fuelrc or something
11:09 salmon_ mihgen: /etc/fuel/client/config.yaml
11:09 salmon_ mihgen: we just used default cli config file
11:10 mihgen salmon_: neither fuel --help or fuel auth failure say about this file :(  Can you please prepare a patch so it refers to it?
11:11 salmon_ mihgen: yeah, good idea
11:14 mihgen salmon_: thanks. and don't forget about bug & bp on 5.1.1 - otherwise we gonna forget it or forget to track as that it needs resources
11:14 salmon_ mihgen: there is actually bug and fix from Kamil but it's targeted for 6.0 https://bugs.launchpad.net/fuel/+bug/1348395
11:15 salmon_ for --help
11:17 mihgen salmon_: let's do it as high thing for 5.1
11:17 salmon_ mihgen: ok, can you retriger CI test?
11:18 salmon_ mihgen: https://review.openstack.org/#/c/112220/2
11:18 mihgen salmon_: I also think that documentation piece you shown me shoud be rewritten radically - it's really messing me up. There is no any need to update any files anywhere to change the password
11:18 salmon_ mihgen: ok, I will talk with Meg
11:19 mihgen bookwar: devops, can you please help with retriggering of https://review.openstack.org/#/c/112220/2 ^^^
11:19 mihgen salmon_: I think sambork needs to remove 'work in progress' from there as well
11:20 salmon_ sambork: ^
11:20 monester mihgen, salmon_ retriggered
11:20 salmon_ monester thx
11:20 sambork Ok I removed
11:41 Tatyanka_Leontov vkramskikh:  Vitaly can someone from ui team look at this https://bugs.launchpad.net/fuel/+bug/1362138 I have environment with this problem )
11:42 evgeniyl mattymo: https://bugs.launchpad.net/fuel/+bug/1362139 aglarendil suggested always run db sync in puppet, because it looks like puppet updated all configs and failed, on the second round it didn't run db sync again
11:43 mattymo ok let's bring in lukasz as well
11:43 mattymo salmon_, ^^ look at the bug
11:43 mattymo keystone fails to upgrade
11:44 vkramskikh Tatyanka_Leontov: will look
11:45 aglarendil mattymo: salmon_ my suggestion is to introduce a flag that will determine whether we want to run db_sync all the time or only once by altering refreshonly parameter of the exec
11:46 SergK left #fuel-dev
11:47 mattymo let's not one-off keystone for master
11:47 mattymo we should either dbsync always or not
11:47 mattymo who should decide this maybe scenario?
11:48 EeeBotu New bug #1362139 in fuel: "Upgrades, keystone container fails with db schema error" [High, Triaged] https://bugs.launchpad.net/bugs/1362139
11:48 EeeBotu New bug #1362138 in fuel: "[UI]Can not deploy cluster in Ha mode with ceilometer and 1 mongo role" [High, New] https://bugs.launchpad.net/bugs/1362138
11:50 eshumkher joined #fuel-dev
11:51 vkramskikh DinaBelova: could you please comment on https://bugs.launchpad.net/fuel/+bug/1362138 ? as far as i remember you asked me to introduce this restriction
11:51 DinaBelova vkramskikh, one moment
11:51 Tatyanka_Leontov It is looks strange if we say to user that he/she can deploy ha mode with 1 controller - but we 3 mongo role
11:53 mattymo aglarendil, can you please tell me what we changed with supervisor lately? is it a package update?
11:53 aglarendil mattymo: nope
11:53 mattymo or maybe evgeniyl
11:54 aglarendil https://review.openstack.org/#/c/114193/
11:54 aglarendil mattymo:  ^^
11:54 evgeniyl mattymo: there was update for supervisor init
11:54 mattymo what a weird weird status command
11:58 salmon_ mattymo: aglarendil evgeniyl if db_sync is safe to run on each puppet run let's do it
11:59 mattymo salmon_, with one new exception.. it looks like on parallel non-primary controller deployment it causes issues
11:59 mattymo aglarendil, who was working on skipping db_sync for non-primary controller deployment?
11:59 aglarendil salmon_: well, it is idempotent. but parallel run is not the best idea, yes
11:59 aglarendil salmon_: so let's do it as an exception for keystone container
12:00 aglarendil mattymo: this code will not make it to 5.1
12:00 aglarendil mattymo: it is to monstrous
12:00 mattymo ok
12:00 evgeniyl if there were no changes in schema, it won't be applied, I think it is safe
12:00 aglarendil mattymo: we worked it around by provider modification
12:00 aglarendil mattymo: actually, db_sync on secondary controllers does not do anything as the database is already migrated
12:00 mattymo so how about an exception for just refresh db_sync in keystone-only.pp with a TODO that we're revamping db_syncs in a future release
12:00 aglarendil mattymo: I think it can make sense
12:01 aglarendil oh!
12:01 aglarendil you can alter the parameters then by using spaceship collector
12:01 mattymo well, sure of course, but what do you want to alter?
12:02 aglarendil https://docs.puppetlabs.com/puppet/2.7/reference/lang_resources.html#amending-attributes-with-a-collector
12:02 aglarendil refreshonly parameter for db_sync exec
12:08 akupko joined #fuel-dev
12:21 sbog Guys, anybody know where can I find our repos for zabbix-server-mysql package?
12:21 eshumkher joined #fuel-dev
12:23 adanin joined #fuel-dev
12:36 teran joined #fuel-dev
12:49 shauno_ joined #fuel-dev
12:51 EeeBotu New bug #1362159 in fuel: "After restore fuel master node iptables rules contain extra records" [Undecided, New] https://bugs.launchpad.net/bugs/1362159
12:51 EeeBotu New bug #1362154 in fuel: "install screen and put .screen to master node by default" [Wishlist, New] https://bugs.launchpad.net/bugs/1362154
12:53 shauno__ joined #fuel-dev
13:09 mattymo I need reviewers for https://review.openstack.org/#/c/117217/
13:09 mattymo and evgeniyl who has repeated the problem with supervisord starting?
13:15 evgeniyl mattymo: it happens very often on my env, I can try to reproduce and show you the env
13:16 mattymo great
13:16 mattymo I'm really curious why supervisord is dying
13:18 mattymo evgeniyl, looks like ulimit was put back in for supervisord on my deployment
13:19 evgeniyl mattymo: oh, yeah, I saw some error which was related to ulimit, when I was trying to debug the issue
13:21 ai joined #fuel-dev
13:26 mattymo evgeniyl, I don't think it breaks anything
13:27 mattymo evgeniyl, are you doing 5.0 to 5.1 upgrade? I'm using master upgrade tarball 478
13:28 evgeniyl mattymo: yeah, I'm running 5.0 -> 5.1 upgrade
13:29 EeeBotu New bug #1362173 in fuel: "@mirantis emails for defalut OpenStack services users" [Medium, Confirmed] https://bugs.launchpad.net/bugs/1362173
13:29 EeeBotu New bug #1362169 in fuel: "Cirros image does not properly work with vcenter" [Undecided, New] https://bugs.launchpad.net/bugs/1362169
13:29 EeeBotu New bug #1362163 in fuel: "Sometimes openstack services return 502 error code" [Undecided, New] https://bugs.launchpad.net/bugs/1362163
13:30 mattymo evgeniyl, how come mine keep working without problems? :(
13:30 vkramskikh DinaBelova: any updates?
13:30 evgeniyl mattymo: oh, this problem happens not often
13:30 mattymo oh! I reproduced it on astute
13:32 meow-nofer__ joined #fuel-dev
13:33 apodrepniy joined #fuel-dev
13:35 bogdando salmon_> mattymo, aglarendil, evgeniyl  IMHO, it would be safe only if being run at the primary controller only (see https://bugs.launchpad.net/fuel/+bug/1361676)
13:38 xdeller joined #fuel-dev
13:38 mattymo the chances are small, but we're seeing so many new race condition bugs now
13:43 mattymo yep looks like it fails if /var/run/supervisord.pid exists
13:46 mattymo ok so 2 options to solve this: remove the pidfile in start.sh or modify init script to ignore the file if that pid doesn't exist
13:48 eshumkher joined #fuel-dev
13:50 evgeniyl mattymo: did you try to delete lock and restart container? Did it help?
13:50 mihgen aglarendil: https://bugs.launchpad.net/fuel/+bug/1362163 - library folks, needs triaging
13:50 e0ne joined #fuel-dev
13:51 icq_Boy joined #fuel-dev
13:52 icq_Boy left #fuel-dev
13:54 EeeBotu New bug #1362186 in fuel: "RabbitMQ fails to launch during deployment. CentOS" [High, New] https://bugs.launchpad.net/bugs/1362186
13:56 mattymo evgeniyl, I made a small patch that should fix it
13:57 mattymo https://review.openstack.org/#/c/117250/
14:02 eshumkher joined #fuel-dev
14:04 agordeev hi, has anyone else faced with the issue with mac address changing in what ohai reports? it had started reporting the eth1 address instead of eth0
14:05 agordeev am i asking in wrong channel? just let me know where it's better to ask
14:10 evgeniyl agordeev: what fuel version do you use? We had such issues but as far as I remember it was fixed a long time ago.
14:11 mattymo agordeev, the values determined during bootstrap should stay constant after install of node
14:11 mattymo but during actual OS provisioning it could change
14:17 dukov joined #fuel-dev
14:18 dukov hello
14:18 dukov I have an issu with OAHI
14:18 agordeev evgeniyl: mattymo: actually it was dukov's question
14:19 dukov *OHAI
14:19 dukov I'm using trunk version of MOS
14:22 shauno_ joined #fuel-dev
14:23 dukov the problem is that node has been registered in Nailgun with MAC address 52:54:00:7b:35:48
14:23 dukov which is eth0
14:24 dukov but in the middle of deployment nailguin-agent started to sent a messages to nailgun with MAC 52:54:00:73:f9:f8
14:25 dukov which is eth1 according to udev rules
14:29 dukov I have figured out that OHAI retirns wrong MAC addres
14:29 dukov irb(main):002:0> os = Ohai::System.new()
14:29 dukov os.all_plugins
14:29 dukov irb(main):005:0> os[:macaddress]
14:29 dukov => "52:54:00:73:F9:F8"
14:30 dancn anyone seeing '502 bad gateway' on login after rebooting the fuel console using: fuel-community-5.1-9-2014-08-26_21-42-16.iso.  I guess that some service did not start correcly.  Any hints on how to debug and report a proper bug?
14:30 dukov did anyone see this issue?
14:32 aglarendil dancn: it shows that your nailgun container or keystone container is broken
14:32 aglarendil dancn: you can try to do
14:32 aglarendil dancn: dockerctl restart keystone
14:32 aglarendil dancn: dockerctl restart nailgun
14:33 dancn aglarendil: will try asap, after the reboot
14:33 aglarendil dukov: it is really strange. you need to file a bug
14:33 evgeniyl dukov: http://docs.getchef.com/ohai.html here is some information how ohai determines mac address, do you use neutron or nova?
14:33 aglarendil dancn: reboot should almost help you as all the containers will be restarted
14:35 dancn aglarendil: after the restart login works
14:36 dukov evgeniyl: nova
14:36 dukov one thing
14:36 dukov this is not vanilaMOS
14:37 dukov I've integrated ubuntu 14.04 into it
14:37 dancn aglarendil: maybe is because low ram... 2GB only here, where I can found some useful log?
14:37 evgeniyl dukov: we had similar issue it we fixed it like https://clck.ru/9J426
14:37 aglarendil dancn: try looking into dmesg first
14:37 teran joined #fuel-dev
14:38 aglarendil dancn: if you are out of memory, you will see Out Of Memory Killer messages
14:38 dancn aglarendil: no oom messages
14:39 dukov evgeniyl: this fix is for the post
14:40 dukov i'm experiensing issues with put
14:40 dukov any ways thanks for the link
14:40 aglarendil dancn: what is you load average?
14:40 dukov i'll try to use it as work around
14:42 dancn aglarendil:  14:42:27 up 10 min,  2 users,  load average: 0.00, 0.33, 0.39
14:42 dancn
14:42 MiroslavAnashkin dancn: 2GB should be enough for master node.
14:43 dancn aglarendil: nothing interesing, from a not experienced person in /var/log/docker-nailgun.log
14:43 aglarendil dancn: is your nailgun running right now?
14:43 aglarendil dancn: try to login to the web UI
14:45 MiroslavAnashkin dancn: dhcrelay may fail to start. Or - node boot process is quite slow and there is 1-2 minutes delay after the node reports it is started and when you may actually connect to web UI
14:46 dancn aglarendil: yes nailgun is working
14:47 aglarendil dancn: so what is your problem right now?
14:47 agrebennikov joined #fuel-dev
14:48 agrebennikov joined #fuel-dev
14:48 dancn MiroslavAnashkin: yes, I saw the cloud image, and after few mins I reloaded into the login panel, then got the 502 response (looking with firebug into network) the ui simply display login failed
14:48 dancn aglarendil: no problem right now, but if we got a clue on way the service was not started correcly maybe I can fill a proper bug report
14:49 dancn s:way:why
14:49 aglarendil dancn: MiroslavAnashkin, please help Daniele
14:50 MiroslavAnashkin dancn: Yes, please. Please attach diagnostic snaprhot to the bug report.
14:50 MiroslavAnashkin s/snaprot/snapshot/
14:52 dancn MiroslavAnashkin: will do a bug report with the diagnostic
14:52 aglarendil dancn: thank you, Daniele
14:53 dancn aglarendil, MiroslavAnashkin thanks to you, I am just starting and a friendly help is really appreciated
14:55 evgeniyl mattymo: I tried to apply your patch for supervisor, and it has side effect http://pastie.org/9507409#14 `supervisord -n` doesn't work because puppet runs supervisor
14:55 mattymo evgeniyl, are you trying to run it while supervisord is running not as a daemon?
14:55 EeeBotu New bug #1362202 in fuel: "[Update] Puppet failed on added controller node to the patched cluster" [High, New] https://bugs.launchpad.net/bugs/1362202
14:56 mattymo for example, nailgun container is running with supervisor and you just patched and ran service supervisord start?
14:57 evgeniyl mattymo: no, I don't run anything, I applied your patch in the container, which has puppet errors, then restarted the container, and got the errors which you can see in pastie
14:57 angdraug joined #fuel-dev
14:57 mattymo oh ok
14:57 mattymo great
15:01 teran joined #fuel-dev
15:03 Kupo24z1 joined #fuel-dev
15:06 dancn MiroslavAnashkin: I do not see the EeeBotu message about my bug, did I filled it wrong or it take some time?  It is at: https://bugs.launchpad.net/fuel/+bug/1362207
15:06 pasquier-s_ joined #fuel-dev
15:20 ilbot3 joined #fuel-dev
15:20 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
15:21 Longgeek joined #fuel-dev
15:22 dukov joined #fuel-dev
15:22 mattymo joined #fuel-dev
15:22 ruhe joined #fuel-dev
15:22 christopheraedo joined #fuel-dev
15:22 mirrorbox joined #fuel-dev
15:22 sanek joined #fuel-dev
15:22 akuznetsova joined #fuel-dev
15:29 mihgen aglarendil: angdraug should we change https://bugs.launchpad.net/fuel/+bug/1361993 to incomplete?
15:30 mihgen I'm going over bugs and need to count how many actual we have left
15:31 tdubyk Ребята кто нить верните в jenkins торрент линку на 5.0.26    http://jenkins-product.srt.mirantis.net:8080/job/fuel_5_iso/26/
15:31 xarses joined #fuel-dev
15:31 EeeBotu New bug #1362207 in fuel: "unable to login in fuel dashboard after reboot" [Medium, New] https://bugs.launchpad.net/bugs/1362207
15:31 mihgen tdubyk: please ping devops folks in #fuel-devops, and pls only english here as well..
15:32 tdubyk ок, no problem. thanks a lot for your help.
15:34 dancn left #fuel-dev
15:35 tdubyk joined #fuel-dev
15:41 mihgen dpyzhov: meow-nofer: folks, anyone is working on it? https://bugs.launchpad.net/bugs/1354299
15:41 mihgen xenolog: aglarendil any progress on https://bugs.launchpad.net/fuel/+bug/1355758 ?
15:42 dpyzhov meow-nofer: please add comment that we need live environment in order to investigate this issue
15:43 angdraug joined #fuel-dev
15:43 mattymo evgeniyl, you still here?
15:44 aglarendil mihgen: I asked angdraug and andrew to review the fix for https://bugs.launchpad.net/fuel/+bug/1355758
15:45 ikalnitsky mihgen: https://bugs.launchpad.net/bugs/1354299 this one is really hard to reproduce and (according to akasatkin) sometimes occurs after a regular deployment. So I think if meow-nofer didn't make the fix, we can move it to 6.0.
15:45 mihgen ikalnitsky: can u please leave corresponding comment there?
15:45 ikalnitsky mihgen: ok. i'll add a comment and move it to 6.0.
15:45 aglarendil mihgen: we are keeping https://bugs.launchpad.net/fuel/+bug/1361993 open for a while in order to be sure that it is really incomplete
15:48 eshumkher joined #fuel-dev
15:50 agrebennikov joined #fuel-dev
15:50 evgeniyl mattymo: yeah, I'm here.
15:50 ikalnitsky dpyzhov: meow-nofer: a live env will not help us, i think. we need more accurate repro-steps here.
15:50 mihgen aglarendil: so let's assign https://bugs.launchpad.net/fuel/+bug/1355758 to angdraug
15:51 mihgen reagarding keeping for a while - let's mark as incomplete if there are not enough info, and you checked logs, if you really need this to be reproduced
15:51 mihgen aglarendil: we have to go over incompletes anyway
15:51 dpyzhov ikalnitsky: oh, yeah, we need more logging. meow-nofer, have you created request with extra logging?
15:52 mihgen dmitryme: seems https://bugs.launchpad.net/fuel/+bug/1356942 that it should be wether in mos prj or marked finally as dup
15:53 ikalnitsky dpyzhov: meow-nofer: i've moved it to 6.0 until we get more logs or more accurate repro-steps.
15:53 adanin joined #fuel-dev
15:54 mihgen akasatkin: aglarendil: is xenolog is working on it?
15:54 mihgen https://bugs.launchpad.net/fuel/+bug/1360230 ^^
15:54 mattymo evgeniyl, puppet ran successfully and supervisor was started
15:54 mattymo but supervisor was still running at the end, so it should be stopped and then run in foreground
15:54 mattymo so we need this too: https://review.openstack.org/#/c/117278/
15:56 shauno_ joined #fuel-dev
15:57 HeOS_ joined #fuel-dev
15:57 evgeniyl mattymo: I've just seen the same error for astute, could you please add the same workaround for astute container?
15:57 mattymo look at astute's start.sh. it's already there
15:57 f13o joined #fuel-dev
15:57 mattymo can you pastebin the error from astute? it looks better
15:58 akasatkin mihgen: xenolog is not online...
15:59 HeOS_ joined #fuel-dev
15:59 shauno__ joined #fuel-dev
16:00 evgeniyl mattymo: http://pastie.org/9507536 the fix is there but there is the same error in astute logs
16:03 [HeOS] joined #fuel-dev
16:03 mattymo evgeniyl, you have 2 separate issues
16:03 mattymo 1 - supervisor fails to start because of issues in init script. addressed in https://review.openstack.org/#/c/117250/
16:04 mattymo 2 - supervisor in foreground fails because it's already daemonized. addressed in https://review.openstack.org/#/c/117278/
16:04 mattymo and in astute you have #1. in nailgun #2
16:04 mattymo if you apply patch #1 to your astute container and restart it, it should be okay
16:05 shauno_ joined #fuel-dev
16:09 evgeniyl mattymo: thanks for clarification, I'll check it
16:14 evgeniyl mattymo: you was right set + for your patches
16:16 scroiset left #fuel-dev
16:22 mihgen aglarendil: angdraug: xarses please help with review of critical bug https://review.openstack.org/#/c/117251/
16:39 rmoe joined #fuel-dev
16:42 eshumkher joined #fuel-dev
16:58 dshulyak_ joined #fuel-dev
16:59 jobewan joined #fuel-dev
17:12 meow-nofer__ joined #fuel-dev
17:37 prmtl joined #fuel-dev
17:49 shauno_ joined #fuel-dev
18:12 eshumkher joined #fuel-dev
18:14 e0ne joined #fuel-dev
18:16 eshumkher joined #fuel-dev
18:21 angdraug joined #fuel-dev
18:28 mihgen angdraug: rmoe: hi, please take a look: https://bugs.launchpad.net/fuel/+bug/1360044/comments/3
18:28 mihgen we are likely need to ask to open another bug for this
18:29 angdraug agreed
18:29 rmoe gg, I didn't test with any mellanox features enabled
18:30 rmoe meant to say, it looks like a different bug
18:30 angdraug imho the combination should be disallowed in UI
18:30 angdraug ie if mellanox is enabled, kernel-lt should be grayed out
18:30 mihgen also I think we should of been writing unit tests, merged without any
18:30 rmoe unit tests for what?
18:30 tzn joined #fuel-dev
18:30 mihgen angdraug: mellanox may need it
18:31 angdraug if they need it they should come up with a way to make it work
18:31 mihgen we need adanin then to explain
18:31 angdraug and that will take time
18:31 angdraug so: 1) create new bug
18:31 angdraug 2) patch ui to disable the combo
18:31 angdraug patch should be related-bug, not closes-bug
18:32 angdraug then downgrade the bug and assign it to mellanox to followup
18:32 angdraug and 1.5) flag this to mlx
18:36 salmon_ joined #fuel-dev
18:40 mihgen angdraug: should not be high priority I would say
18:40 mihgen we can easily live with this
18:42 EeeBotu New bug #1359705 in fuel: "[update] non explicit packages are not updated" [Critical, Confirmed] https://bugs.launchpad.net/bugs/1359705
18:43 angdraug if we don't fix it at least in the ui, we'll have to add it to release notes
18:43 mihgen angdraug: let's get eshumkher, adanin and mellanox team on this
18:45 angdraug eshumkher: ^^^
18:46 angdraug MiroslavAnashkin: can you clean up the escalations tracker before product strategy meeting?
18:46 eshumkher is it a Mellanox bug?
18:46 angdraug yes
18:46 angdraug mellanox integration breaks if you enable 3.10 kernel for CentOS
18:47 angdraug they should confirm if they want this combination, and it should either be fixed or disabled in UI
18:49 MiroslavAnashkin angdraug: Did you mean Blueprints section?
18:50 angdraug no, critical bugs section
18:50 angdraug blueprints section is not reviewed in the strategy meeting
18:52 angdraug just sent out an email about that, looping in Anne
18:52 dshulyak_ joined #fuel-dev
18:55 meow-nofer__ joined #fuel-dev
19:01 aepifanov joined #fuel-dev
19:03 aepifanov joined #fuel-dev
19:09 aepifanov joined #fuel-dev
19:10 eshumkher ok, will pass this bug to MLNX team
19:14 aepifanov joined #fuel-dev
19:16 aepifanov joined #fuel-dev
19:17 aepifanov joined #fuel-dev
19:18 teran joined #fuel-dev
19:18 aepifanov joined #fuel-dev
19:18 aepifanov joined #fuel-dev
19:20 aepifanov joined #fuel-dev
19:22 Kupo24z1 joined #fuel-dev
19:26 aepifanov joined #fuel-dev
19:26 teran_ joined #fuel-dev
19:27 HeOS joined #fuel-dev
19:32 adanin joined #fuel-dev
19:35 teran joined #fuel-dev
19:55 eshumkher joined #fuel-dev
20:13 aepifanov joined #fuel-dev
20:14 aepifanov joined #fuel-dev
20:16 aepifanov joined #fuel-dev
20:16 aepifano1 joined #fuel-dev
20:21 aepifano1 joined #fuel-dev
20:24 aepifano1 joined #fuel-dev
20:35 aepifano1 joined #fuel-dev
20:37 angdraug xarses: about logparse
20:38 angdraug how hard to update what we have in git with your improvements?
20:38 angdraug or is it enough of a superset that it can replace it altogether?
20:39 angdraug dilyin: is logparse used in our infra or is it for manual use only?
20:42 tldr joined #fuel-dev
20:45 xarses angdraug: shouldn't be that hard move the agent parser.
20:45 xarses damn it looks like i lost some refactoring that I had worked on =(
20:46 xarses anyway, the hopeful power was that with the extra data I've collected that introspection with some sort of viz kit would become easier
20:47 xarses and you wouldn't need to do it in the interactive parser then
20:47 xarses ahh, nevermind. Didn't lose the refactor
20:48 eshumkher joined #fuel-dev
20:48 EeeBotu New bug #1362317 in fuel: "NSX plugin: deployment fails because of  wrong service_plugins line in neutron config" [Undecided, New] https://bugs.launchpad.net/bugs/1362317
20:53 aepifano1 joined #fuel-dev
20:55 aepifano1 joined #fuel-dev
20:55 aepifanov joined #fuel-dev
21:02 aepifanov joined #fuel-dev
21:02 aepifanov joined #fuel-dev
21:03 meow-nofer__ joined #fuel-dev
21:06 angdraug_ joined #fuel-dev
21:15 e0ne joined #fuel-dev
21:22 e0ne joined #fuel-dev
21:49 apodrepniy_ joined #fuel-dev
21:49 albs joined #fuel-dev
21:52 akupko joined #fuel-dev
21:53 ykotko joined #fuel-dev
21:53 t_dmitry joined #fuel-dev
21:53 tdubyk joined #fuel-dev
21:53 tldr joined #fuel-dev
21:55 a_teem joined #fuel-dev
22:49 angdraug joined #fuel-dev
22:56 teran joined #fuel-dev
23:01 teran_ joined #fuel-dev
23:04 xarses joined #fuel-dev
23:49 angdraug xarses: https://review.openstack.org/#/c/113605/

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