16:04:06 #startmeeting openstack_ansible_meeting 16:04:07 Meeting started Tue May 30 16:04:06 2017 UTC and is due to finish in 60 minutes. The chair is evrardjp. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:04:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:04:12 The meeting name has been set to 'openstack_ansible_meeting' 16:04:46 o/ 16:04:48 #topic rollcall -- knock knock 16:04:55 * mhayden toots 16:05:19 Nolan Brubaker proposed openstack/openstack-ansible-os_glance master: Run service test during glance upgrade https://review.openstack.org/467666 16:05:23 \o/ 16:05:27 Here and half paying attention 16:05:47 Hey I noticed we missed last week:) 16:06:59 no there was a bug triage last week, which brings us to: 16:07:08 #topic last week AP 16:07:17 odyssey4me to confirm/triage https://bugs.launchpad.net/openstack-ansible/+bug/1687369 16:07:19 Launchpad bug 1687369 in openstack-ansible "ocata installation fails for aodh,ceilometer and designate when sqlalchemy version is 1.1.9 version " [Undecided,New] - Assigned to Jesse Pretorius (jesse-pretorius) 16:07:38 it's been 3 weeks, should we release it from you odyssey4me? 16:07:42 I haven't had any chance yet - perhaps unassign to let someone else take it 16:07:58 ok let's keep it for this week triage then 16:08:21 let's start 16:08:27 #topic this week's bugs 16:08:33 #link https://bugs.launchpad.net/openstack-ansible/+bug/1694265 16:08:34 Launchpad bug 1694265 in openstack-ansible "repo build fails multiple architecture environment" [Undecided,New] 16:09:19 Isn't power and amd64 already working? 16:09:23 I'm surprised of this 16:09:41 Guys, I removed "debug: true" out from my user_variables.yml, how to apply it? 16:09:42 hmm 16:10:08 im surprised by that too evrardjp 16:10:51 I think this deserves more input 16:10:54 yeah 16:10:57 what version is that etc 16:11:06 It looks like u'repo_servers_16.04s390x' doesn't exist, so I guess the architecture is s390x 16:11:22 hmm 16:12:22 I've answered 16:12:28 marking incomplete 16:12:29 ok? 16:12:47 Any objections? 16:12:57 5 16:12:58 4 16:13:00 3 16:13:01 2 16:13:02 1 16:13:06 Done, next! 16:13:16 #link https://bugs.launchpad.net/openstack-ansible/+bug/1694222 16:13:17 Launchpad bug 1694222 in openstack-ansible "When deploying nova with spice, sometime Spice port binding is failing" [Undecided,New] 16:14:26 do we have spice in our gates? 16:15:24 maybe we should have this as a scenario 16:17:02 Opinion anyone? 16:17:13 could someone confirm? 16:17:38 lemme check 16:17:44 i think default changed to novnc 16:18:18 hmm nope 16:18:21 spice is on by default 16:18:35 that's what I thought too. Novnc is only in RPC IIRC :p 16:18:57 I think that's why mhayden had issues recently with keymaps 16:18:58 i thought upstream nova default changed but probably not then 16:19:08 oh 16:19:17 my bad, that's not what I meant 16:19:28 that would be good to track too 16:19:46 that error is still weird 16:19:47 in any case, i'd be inclined to say it's a configuration issue 16:19:54 did you see the IP? 16:20:03 yeah 16:20:20 we need more info about what that IP is, at least I'd say 16:20:33 I ask on the bug and mark it incomplete 16:20:37 ok? 16:21:21 yeah 16:21:24 that sounds sensible 16:22:06 ArchiFleKs: are you there by any chance? 16:22:34 5 16:22:40 3 16:22:44 1 16:22:54 #link https://bugs.launchpad.net/openstack-ansible/+bug/1693234 16:22:54 Launchpad bug 1693234 in openstack-ansible "Using galera_my_cnf_overrides brakes cluster config" [Undecided,New] 16:23:13 that sounds like a config template bug 16:23:30 evrardjp: hi 16:25:03 evrardjp: yeah agreed. thats weird though - but should be easy to test 16:25:04 we moved to another bug now, but don't hesitate to scroll, and if you want we can talk about your bug later 16:25:06 would say tahts high though 16:25:13 agreed. 16:25:32 let's mark it as confirmed and high because we don't have a test for that 16:25:47 even if it works 16:27:11 cloudnull: do you have time to take a config_template issue? 16:28:51 ok let's roll 16:28:52 #link https://bugs.launchpad.net/openstack-ansible/+bug/1692044 16:28:53 Launchpad bug 1692044 in openstack-ansible "Tempest failing on os_nova role on CentOS 7" [Undecided,New] 16:29:13 mhayden: did you got more chance to dig into this deeper? 16:31:56 I can assume this is confirmed? 16:32:10 I trust this. 16:32:59 fun stuff triaging alone. 16:33:38 on top of it I can't change statuses on launchpad 16:33:50 I'll mark it as confirmed high when LP is working again 16:34:11 #link https://bugs.launchpad.net/openstack-ansible/+bug/1691749 16:34:12 Launchpad bug 1691749 in openstack-ansible "Generated no_proxy env string can be too long for pam_env" [Undecided,New] 16:34:30 this 16:34:31 hmm 16:35:48 so it looks like its just docs left - it sounds like we just need some work done on the docs 16:36:20 " Introducing an alternative method" ? 16:36:26 think containers get FQDNs now, maybe no_proxy could be wildcarded 16:36:50 hmm 16:37:02 now we are talking. 16:37:32 jmccrory: should we prepare something for this? 16:37:39 Spec/change/anything? 16:38:01 It would be good to not lose this valuable comment in the depth of irc logs. 16:38:03 maybe doc change, don't know if it's mentioned or used within any roles 16:38:30 Could I assign this to you, with low priority, and point to our conversation in the bug? 16:38:32 sure 16:38:38 great 16:38:42 i'll try to test out somewhere as well 16:39:16 cool 16:39:19 thanks! 16:39:23 #link https://bugs.launchpad.net/openstack-ansible/+bug/1691130 16:39:24 Launchpad bug 1691130 in openstack-ansible "fails at repo_build : Build package requirements file" [Undecided,New] - Assigned to Jesse Pretorius (jesse-pretorius) 16:40:05 I'll mark this as incomplete, this way we'll see if we get the author's response 16:40:11 sounds good 16:40:24 at least when LP works again 16:40:25 :p 16:40:28 next 16:40:30 #link https://bugs.launchpad.net/openstack-ansible/+bug/1691120 16:40:31 Launchpad bug 1691120 in openstack-ansible "use find instead of grep" [Undecided,New] 16:40:37 confirmed wishlist 16:40:42 low-hanging-fruit 16:40:47 ok? 16:40:49 agreed 16:40:50 yep 16:41:19 oh it seems that LP takes my status changes again... Woot! 16:41:24 anyway 16:41:36 #link https://bugs.launchpad.net/openstack-ansible/+bug/1687369 16:41:37 Launchpad bug 1687369 in openstack-ansible "ocata installation fails for aodh,ceilometer and designate when sqlalchemy version is 1.1.9 version " [Undecided,New] 16:42:14 seems like it was a deploy error 16:42:30 sounds like it 16:42:35 maybe checked staging docs? 16:42:36 Invalid? 16:43:02 yeah 16:43:14 #link https://bugs.launchpad.net/openstack-ansible/+bug/1692750 16:43:15 Launchpad bug 1692750 in openstack-ansible "deprecate glance_api_version option" [Low,New] - Assigned to zhongshengping (chdzsp) 16:43:52 Could we move this as confirmed? 16:43:58 yeah sorry that was my bad last week 16:44:01 i should've marked it as confirmed 16:44:13 there was maybe a reason :p 16:44:16 ok next 16:44:27 #link https://bugs.launchpad.net/openstack-ansible/+bug/1692017 16:44:29 Launchpad bug 1692017 in openstack-ansible "[WARNING]: Failure using method (v2_runner_on_ok) in callback plugin" [Low,New] 16:44:43 confirmed. I've that in many places 16:44:45 its just an annoying warning 16:44:47 yeah 16:45:02 low though, it's a callback it's just for displaying things 16:45:29 I'll take it 16:45:38 it bothers me too 16:46:09 that's it for the current list. ArchiFleKs want to discuss your bug again? 16:46:50 Or any other topic, everyone? 16:46:58 if not I'm closing the deal for today. 16:47:14 60 seconds! 16:47:20 the countdonw is on! :P 16:47:31 evrardjp: actually it is a compute node 16:47:37 andymccr: let's do it in the street. 16:48:16 so the thing is we didn't see that in gates, could you tell us more that can help the triage? 16:48:27 For a fix, we could discuss that after the triage meeting 16:48:36 but at least know if we can confirm it or leave it as is. 16:49:14 i'm using ocata, I had this bug at first, then I switched back to novnc and at some point I upgraded osa and switch back to spice it was working again and maybe a week ago i updated to ocata branch and redeployed and ran into the same issue 16:49:35 are you sure it's not already running on the node? 16:49:35 :p 16:49:53 that would be a good reason to fail: the port is already used. 16:50:01 evrardjp: i'm not sure it is related to osa 16:50:14 It probably is linked to your host right now 16:50:14 actually yes but libvirt is supposed to do the port automaticly 16:50:29 indeed 16:50:40 it doesn't sound OSA related at the end 16:50:53 I'll mark this as invalid then. 16:51:05 We can discuss that in our channel after triage 16:51:17 if you had vnc set when building an instance, that will remain configured for the VM for its lifetime 16:51:26 so the port will be a novnc port 16:51:27 i believe you have a port range that starts at 5900 and increase 16:52:01 you would have to change the db entry if you want to convert from novnc to spice or vice-versa 16:52:08 Could you at least output a list of the ports already assigned on this machine? 16:52:22 odyssey4me: i'll check that, i did not had time to check but i recall running into this when we first deployed and they were no instances 16:52:28 once the db entry is changed, you'd have to shut down and possibly even migrate the instance to another host to make the instance actually get the new config 16:52:50 that's why we switched back but yes maybe right now there is a mixup between spice and novnc 16:52:52 the console type is typically set for the lifetime of the instance 16:53:12 ok let's conclude it's not osa related 16:53:33 Thanks everyone for your today's triage attendance! 16:53:41 #endmeeting