Friday, 2017-05-05

*** slaweq has joined #openstack-shade00:23
*** slaweq has quit IRC00:28
*** gouthamr has joined #openstack-shade01:16
openstackgerritOpenStack Proposal Bot proposed openstack-infra/shade master: Updated from global requirements  https://review.openstack.org/46137501:17
*** gouthamr has quit IRC01:48
*** gouthamr has joined #openstack-shade01:50
*** jamielennox is now known as jamielennox|away01:55
*** jamielennox|away is now known as jamielennox02:19
*** slaweq has joined #openstack-shade02:24
*** yolanda has joined #openstack-shade02:26
*** slaweq has quit IRC02:29
*** gouthamr has quit IRC02:37
*** gouthamr has joined #openstack-shade03:18
*** gkadam has joined #openstack-shade03:20
*** gouthamr has quit IRC03:58
*** slaweq has joined #openstack-shade04:12
*** slaweq has quit IRC04:16
*** slaweq has joined #openstack-shade06:17
*** slaweq has quit IRC06:21
*** slaweq has joined #openstack-shade08:18
*** slaweq has quit IRC08:23
openstackgerritChristian Zunker proposed openstack-infra/shade master: extend security_group and _rule with project id  https://review.openstack.org/46287508:47
*** cdent has joined #openstack-shade08:49
*** ioggstream has joined #openstack-shade09:08
*** fbaca has joined #openstack-shade10:06
*** slaweq has joined #openstack-shade10:19
*** slaweq has quit IRC10:24
*** yolanda has quit IRC11:10
fbacahi guys, I am using the shade library with ansible (os_server module) to create new instances in an OpenStack based cloud. When I define the flavor and try to run the playbook, many times it fails with the following error: "Multiple matches found for normal1" . The reason seems to be that this implementation has mixed the Name and the ID, thus creating11:34
fbacaduplicates. The full flavor list is found here: https://pastebin.com/xPincXC2 . Any idea if there is a workaround for this?11:34
*** cdent has quit IRC11:52
*** cdent has joined #openstack-shade12:18
*** yolanda has joined #openstack-shade12:33
*** cdent_ has joined #openstack-shade12:53
*** yolanda has quit IRC13:02
*** cdent has quit IRC13:02
*** cdent_ is now known as cdent13:02
*** yolanda has joined #openstack-shade13:08
*** gkadam has quit IRC13:29
*** gkadam has joined #openstack-shade13:29
mordredfbaca: hi! so - a) WOW13:40
mordredfbaca: there is a way to work around that on the shade side - but I do not believe it's exposed up through the ansible layer - let me look real quick13:41
mordred(well, actually, in this specific case, you could just say "0005" and that uniquely matches the flavor with the name flavor113:42
mordredbut I'm still looking at the other thing13:42
openstackgerritChristian Zunker proposed openstack-infra/shade master: extend security_group and _rule with project id  https://review.openstack.org/46287513:48
fbacamordred: true, for 0005 it would work but it will fail for normal213:55
mordredfbaca: yes - for normal2 you'dhave to use 0001 ... however, you should be able to pass a dict to flavor (we're not blocking this in ansible) - so if you do: http://paste.openstack.org/show/608986/13:57
mordredI believe it should work (I have not explicitly tested)13:57
fbacamordred: would you be able to confirm this is also an issue on the openstack flavor definiton side as they actually mix ids and names?13:58
fbacamordred: many thanks, I will try that on Monday as I need to leave now and I will confirm whether it works13:59
mordredfbaca: it is, unfortunately, I think just bad form on their side - nothing in nova would prevent them from doing that14:00
mordredI mean - I do not think they should do that, obviously :)14:00
fbacamordred: i agree with that, just want to confirm my assumptions because i've hit so many issues during the Ansible implementation because of the way they setup OpenStack and these guys always try to blame the tools I use :)14:03
mordredhah14:09
*** gouthamr has joined #openstack-shade15:02
morganmordred: reminder, i'm on vacation next week. I'll be turning my bouncer off, if you need me (like.. EMERGENCY), ping via other methods.16:00
mordredmorgan: ++16:12
morgani figure it will be much better to not have a ton of notifications i will just clear when i get back ;)16:13
morganand we have IRC logs ^_^16:13
*** gkadam has quit IRC16:22
*** yolanda has quit IRC16:23
mordredyes we do!16:33
*** yolanda has joined #openstack-shade16:54
*** cdent has quit IRC16:56
*** slaweq has joined #openstack-shade17:32
*** slaweq has quit IRC17:36
*** cdent has joined #openstack-shade17:56
*** openstackgerrit has quit IRC18:18
*** slaweq has joined #openstack-shade18:36
*** slaweq has quit IRC18:45
*** slaweq has joined #openstack-shade19:49
rodsmordred once we have removed all the clients we can get rid of some of the Fake* objects20:36
rodsshould simplify tests a lot20:36
*** yolanda has quit IRC21:01
*** gouthamr has quit IRC21:47
*** cdent has quit IRC22:05
*** gouthamr has joined #openstack-shade22:23
mordredrods: +10022:38
*** ioggstream has quit IRC22:46
*** openstackgerrit has joined #openstack-shade23:23
openstackgerritSlawek Kaplonski proposed openstack-infra/shade master: Remove neutronclient mocks from floating ips tests  https://review.openstack.org/46307023:23
slaweqmordred: hello23:24
slaweqplease take a look at https://review.openstack.org/463070 if You will have time23:24
slaweqI added uri mocks for floating ips tests23:25
slaweqbut I'm not sure if it should be changed this way there :)23:25
slaweqbecause in many tests there was in fact no mock of neutronclient but mocks of other openstackcloud methods23:26
slaweqI replaced all of them with mocks of REST calls but I'm not sure if it's exactly what You want here :)23:26
openstackgerritRosario Di Somma proposed openstack-infra/shade master: Remove cinderclient mocks from snapshot tests  https://review.openstack.org/46307123:43
*** slaweq has quit IRC23:44
*** slaweq has joined #openstack-shade23:45
*** slaweq has quit IRC23:52

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