Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-05-02
16:04:54 melwitt clarkb: hm, interesting. the error from the bug "UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-1: ordinal not in range(128)"
16:05:35 clarkb melwitt: and if you change it to print a.encode('utf8') I assume that works?
16:06:24 clarkb does locale -a show C.utf8 as being present locally?
16:06:25 mriedem clarkb: it does
16:06:41 melwitt clarkb: yeah, with the encode it works. I wonder if it depends on which version of python?
16:06:52 mriedem melwitt: apparently it does https://github.com/openstack/oslo.versionedobjects/blob/master/oslo_versionedobjects/base.py#L318
16:07:03 mriedem the problem is in ^ we do the %s replace before trying to encode it
16:07:07 mriedem and we blow up already
16:07:11 stvnoyes johnthetubaguy: Hi john, I updated one of the multiattach reviews to address your comments- https://review.openstack.org/#/c/456877/ pls take a look when you get a chance. also related review here - https://review.openstack.org/#/c/456851/ thx
16:07:26 clarkb mriedem: melwitt I think it either depends on locale locales (see locale -a) or the build of python and how it detects the locale?
16:07:35 clarkb I have python 2.7.13
16:08:04 melwitt okay, I have C.utf8 in locale -a
16:08:16 melwitt er, C.UTF-8
16:08:36 melwitt so it works when I use that
16:08:51 melwitt with the caps and the hyphen
16:12:24 sfinucan melwitt: You tried 'PYTHONIOENCODING=UTF-8 python ...'?
16:13:12 melwitt sfinucan: no, just setting LC_ALL=C.UTF-8 etc
16:14:18 sfinucan melwitt: I think that should fix the issue. Someone reported a similar things for pwclient (part of Patchwork) a while back https://lists.ozlabs.org/pipermail/patchwork/2017-April/004214.html
16:14:52 sfinucan the other "workarounds" are hacky as can be. Better just set the envvar
16:18:31 sdague clarkb: there is no C.UTF-8 on base centos 7
16:19:14 melwitt sdague, clarkb: trying C.UTF-8 https://review.openstack.org/#/c/461840
16:19:29 melwitt sdague: but what you just said means it's not going to work for centos 7
16:19:57 sdague melwitt: yeh, lets just use en_US.utf8, we know that works
16:19:58 clarkb sdague: is ther C.utf8?
16:20:02 melwitt sdague: k
16:20:03 sdague clarkb: nope
16:20:05 clarkb sdague: thats what it is for me on suse at least
16:20:15 sdague C
16:20:15 sdague [sdague@centos7 ~]$ locale -a | grep '^C'
16:21:10 sdague clarkb: which is actually even worse if distros are calling it different things
16:21:32 clarkb ya the different name thing is new to me and annoying
16:22:26 sdague anyway, en_US.utf8 is a thing, it's been a thing for a long time, we already force that local for pip installs because people have utf8 in their Readme files which are auto included in setup.py and break in this same way if we don't
16:25:23 edleafe dansmith: regarding the removal of 'can_host' (https://review.openstack.org/#/c/461494/) if I remove the column from the model but don't provide a migration script to remove it, the functional db test fails with "Models and migration scripts aren't in sync"
16:25:32 dansmith edleafe: yup
16:25:38 dansmith edleafe: there's an exclusion list for that I think
16:26:40 mriedem there is,
16:26:44 edleafe dansmith: ugh. ok, I'll search for that
16:26:45 mriedem because we don't drop columns
16:26:45 dansmith edleafe: example prior art: 5e9df4baf97fd1f495b81d3b8b612e24f344b325
16:26:55 clarkb sdague: ya the biggest issue is going to be if your software ends up in $location where someone has decided that don't need en_US (because they don't english or murica or whatever)
16:27:20 clarkb sdague: and aiui C/C.utf8 are supposed to be workaround for such things. By not being tied to a region/human language
16:28:59 melwitt sdague: should I do a check experimental on it to get more jobs? I can't remember what's in there for experimental and not finding it yet
16:29:14 sdague clarkb: yeh, well it's an edge condition, but so are a thousand other things. And honestly for repeatable development I'd rather just go easy
16:29:29 sdague melwitt: what was the failing job?
16:29:59 sdague I'm not sure if whatever that is in the devstack experimental list
16:30:26 melwitt sdague: gate-tempest-dsvm-cells-ubuntu-xenial, I'm looking to see if it is. just had forgotten where to look until just now
16:32:10 melwitt confirmed it's in the experimental queue for devstack
16:43:00 sdague melwitt: cool
16:43:02 cdent jaypipes: yay! all my semi-random flailing is vindicated!
16:48:54 openstackgerrit Matt Riedemann proposed openstack/nova master: db api: add service_get_by_uuid https://review.openstack.org/461428
16:48:55 openstackgerrit Matt Riedemann proposed openstack/nova master: objects: add Service.get_by_uuid method https://review.openstack.org/461429
16:48:55 openstackgerrit Matt Riedemann proposed openstack/nova master: Handle uuid in HostAPI._find_service https://review.openstack.org/461519
16:48:56 openstackgerrit Matt Riedemann proposed openstack/nova master: Handle uuid in HostAPI.compute_node_get https://review.openstack.org/461532
16:48:56 openstackgerrit Matt Riedemann proposed openstack/nova master: objects: add ComputeNode.get_by_uuid method https://review.openstack.org/461448
16:48:57 openstackgerrit Matt Riedemann proposed openstack/nova master: Add uuid to service.update notification payload https://review.openstack.org/461473
16:48:57 openstackgerrit Matt Riedemann proposed openstack/nova master: Add online data migration for populating services.uuid https://review.openstack.org/454899
16:48:58 openstackgerrit Matt Riedemann proposed openstack/nova master: db api: add compute_node_get_by_uuid method https://review.openstack.org/461447
16:58:12 openstackgerrit Chris Dent proposed openstack/nova master: Add pbr-installed wsgi application for metadata api https://review.openstack.org/459413
16:58:28 openstackgerrit Chris Dent proposed openstack/nova master: devref and reno for nova-{api,metadata}-wsgi scripts https://review.openstack.org/461289
16:59:08 cdent mriedem or johnthetubaguy can somebody re-apply the +Ws to those ^ please?
16:59:14 mriedem already did it
16:59:23 cdent word
17:32:48 mriedem gibi: i'm going to have to use an expected_projects kwarg and sentinel with this flavor.destroy notification unit test
17:33:10 mriedem because comparing the payload to the flavor_obj doesn't help as we still attempt to lazy-load the projects w/o the fix, and that results in []
17:33:12 mriedem which is the bug
17:33:26 mriedem i realized that if i removed the fix and ran the tests, things still all passed
17:33:30 mriedem b/c the expectations were wrong
17:37:12 openstackgerrit Gábor Antal proposed openstack/nova master: [WIP] Transform aggregate.update_metadata notification https://review.openstack.org/460625
17:42:33 sdague mriedem: so, we should probably talk about onboarding room tomorrow, if you have some time
17:42:38 sdague today is getting away from me
17:44:31 mriedem sdague: ok morning is best, also because of jaypipes and bauwser
17:44:42 sdague sounds good
17:45:50 jaypipes ++
17:48:31 mriedem also,
17:48:45 mriedem sdague: jaypipes: is the onboarding room in any way related to the upstream university thing that happens over the weekend?
17:48:46 openstackgerrit Matt Riedemann proposed openstack/nova master: Remove compatibility code for flavors https://review.openstack.org/460377
17:48:46 openstackgerrit Matt Riedemann proposed openstack/nova master: Don't lazy-load flavor.projects during destroy() https://review.openstack.org/461032
17:48:47 mriedem ildikov: ^?
17:48:57 mriedem the question, not the patches
17:49:18 ildikov mriedem: haha, ok :)
17:49:27 ildikov mriedem: so in theory those are two separate things
17:50:02 mriedem ok, i guess in my head up until now i had merged them,
17:50:15 mriedem and because i wasn't doing the upstream university i wasn't doing the onboarding room either
17:50:19 ildikov mriedem: in practice they can be connected in the sense of re-using the exercises from the code deep dive sessions from the training and/or build on them if someone shows up in the on boarding room who attended the training
17:50:30 mriedem i can't make the first hour of the onboarding room anyway because of session conflicts
17:50:48 sdague mriedem: no
17:50:59 mriedem ildikov: btw, if the ptg is for devs and the forum is for users/marketing/ops, why is there an onboarding room at the summit?
17:51:21 ildikov mriedem: not coming to the training should not block you participating in the on boarding room/session
17:51:54 ildikov mriedem: because the Summit/Forum is the place to get all th listed groups in connection with the devs
17:52:05 ildikov mriedem: and to on board new members
17:52:23 dansmith ildikov: forum isn't generally for contributors though, right? so who is being onboarded?
17:53:06 ildikov mriedem: as the PTG is going more into technical details and the purpose of that event is to give the possibility to the developers to sort out issues and next steps with features, etc. which are not really topics for new contributors and first timers
17:53:34 mriedem ildikov: but companies aren't sending devs to the forum now b/c it's not for devs really, the ptg is, right?
17:53:50 mriedem anyway, big can of worms, don't mean to rathole on this
17:53:51 dansmith wait.. what?
17:54:11 ildikov dansmith: I wouldn't say that it's generally not for contributors as contributors are important part for the success of the Forum
17:54:25 dansmith ildikov: ptg is for mid and above devs, but not for new contributors, and forum is for brand new people and project decision makers?
17:55:07 ildikov dansmith: on the other hand those, who're new to OpenStack can learn much during the Summit and the Forum sessions and hence the on boarding rooms are part of that event, where we have new and experienced people around as well
17:56:03 ildikov mriedem: I think that's a bit of a misunderstanding and as with all changes it will take time to find the balance
17:56:15 mriedem ok, regardless i can't make the first hour b/c i'm going to https://www.openstack.org/summit/boston-2017/summit-schedule/events/18750/operating-the-vm-and-baremetal-platform-12

Earlier   Later