| *** tetsuro has joined #openstack-placement | 00:02 | |
| melwitt | prometheanfire: what version of the os-traits library do you have? | 00:09 |
|---|---|---|
| melwitt | that trait was added in this commit https://github.com/openstack/os-traits/commit/56531c2a81e4938fd790d6fc05791ee745da5f03 | 00:09 |
| prometheanfire | 0.11.0 | 00:09 |
| melwitt | ok, that should have it | 00:10 |
| prometheanfire | hmm, from what I read nova-compute should be the first to add it? | 00:10 |
| melwitt | I don't know enough about it to know why/how placement will reject a 'standard' trait PUT request | 00:10 |
| prometheanfire | they both have 0.11.0 as well | 00:11 |
| prometheanfire | nor I | 00:11 |
| melwitt | yeah, this is part of the compute capabilities as traits change I think | 00:11 |
| prometheanfire | have some debug | 00:13 |
| prometheanfire | 2019-04-16 19:12:26.390 25324 DEBUG placement.requestlog [req-d0831879-30a4-4a20-8bd0-d6465c962022 e589d5a63cf245f381869ee8cb7ca092 48ddb9bf27c342e8a9640fe4e526519f - default default] Starting request: 10.10.2.3 "PUT /traits/COMPUTE_NET_ATTACH_INTERFACE" __call__ /usr/lib64/python3.6/site-packages/placement/requestlog.py:38 | 00:13 |
| prometheanfire | 2019-04-16 19:12:26.396 25324 DEBUG placement.wsgi_wrapper [req-d0831879-30a4-4a20-8bd0-d6465c962022 e589d5a63cf245f381869ee8cb7ca092 48ddb9bf27c342e8a9640fe4e526519f - default default] Placement API returning an error response: The trait is invalid. A valid trait must be no longer than 255 characters, start with the prefix "CUSTOM_" and use following characters: "A"-"Z", "0"-"9" and | 00:13 |
| prometheanfire | "_" call_func /usr/lib64/python3.6/site-packages/placement/wsgi_wrapper.py:31 | 00:13 |
| prometheanfire | 2019-04-16 19:12:26.399 25324 INFO placement.requestlog [req-d0831879-30a4-4a20-8bd0-d6465c962022 e589d5a63cf245f381869ee8cb7ca092 48ddb9bf27c342e8a9640fe4e526519f - default default] 10.10.2.3 "PUT /traits/COMPUTE_NET_ATTACH_INTERFACE" status: 400 len: 402 microversion: 1.6 | 00:13 |
| melwitt | https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#compute-capabilities-as-traits | 00:13 |
| melwitt | I guess you already linked that | 00:14 |
| prometheanfire | heh, yep | 00:14 |
| melwitt | unfortunately the person who implemented that just logged off a little while ago, aspiers | 00:15 |
| melwitt | according to that error message, the API is saying you can't PUT a trait that doesn't being with CUSTOM_ | 00:17 |
| prometheanfire | eh, it's not too big of a deal today, home testing | 00:17 |
| prometheanfire | yep | 00:17 |
| melwitt | but I don't understand that considering this is running in the gate | 00:17 |
| * prometheanfire shrugs | 00:19 | |
| prometheanfire | I'm patient :D | 00:19 |
| melwitt | haha ok | 00:21 |
| *** mriedem has quit IRC | 00:38 | |
| *** tetsuro has quit IRC | 01:27 | |
| *** mriedem has joined #openstack-placement | 02:11 | |
| *** mriedem has quit IRC | 04:08 | |
| *** david-lyle has joined #openstack-placement | 04:13 | |
| *** dklyle has quit IRC | 04:16 | |
| *** e0ne has joined #openstack-placement | 04:35 | |
| *** e0ne has quit IRC | 04:42 | |
| *** e0ne has joined #openstack-placement | 04:44 | |
| *** e0ne has quit IRC | 05:16 | |
| openstackgerrit | Tetsuro Nakamura proposed openstack/osc-placement master: Improve aggregate version check error messages with min_version https://review.openstack.org/652100 | 05:30 |
| openstackgerrit | Tetsuro Nakamura proposed openstack/osc-placement master: Expose version error message generically https://review.openstack.org/653285 | 05:31 |
| *** e0ne has joined #openstack-placement | 05:40 | |
| *** e0ne has quit IRC | 05:59 | |
| *** belmoreira has joined #openstack-placement | 06:17 | |
| *** bhagyashris has joined #openstack-placement | 06:49 | |
| *** belmoreira has quit IRC | 07:09 | |
| *** belmoreira has joined #openstack-placement | 07:10 | |
| openstackgerrit | Merged openstack/osc-placement master: Improve aggregate version check error messages with min_version https://review.openstack.org/652100 | 07:37 |
| *** tssurya has joined #openstack-placement | 07:43 | |
| *** e0ne has joined #openstack-placement | 07:51 | |
| *** ttsiouts has joined #openstack-placement | 08:06 | |
| *** ttsiouts has quit IRC | 08:17 | |
| *** ttsiouts has joined #openstack-placement | 08:17 | |
| *** ttsiouts has quit IRC | 08:22 | |
| *** ttsiouts has joined #openstack-placement | 08:28 | |
| *** e0ne has quit IRC | 08:38 | |
| *** e0ne has joined #openstack-placement | 08:42 | |
| *** e0ne has quit IRC | 08:43 | |
| *** e0ne has joined #openstack-placement | 08:43 | |
| *** e0ne has quit IRC | 08:58 | |
| *** e0ne has joined #openstack-placement | 08:59 | |
| *** e0ne has quit IRC | 09:02 | |
| *** e0ne has joined #openstack-placement | 09:09 | |
| *** ttsiouts has quit IRC | 09:17 | |
| *** ttsiouts has joined #openstack-placement | 09:18 | |
| *** ttsiouts_ has joined #openstack-placement | 09:19 | |
| *** ttsiouts has quit IRC | 09:19 | |
| *** e0ne has quit IRC | 09:37 | |
| *** e0ne has joined #openstack-placement | 09:40 | |
| *** e0ne has quit IRC | 09:46 | |
| *** bhagyashris has quit IRC | 09:49 | |
| *** e0ne has joined #openstack-placement | 09:53 | |
| *** e0ne has quit IRC | 10:27 | |
| *** e0ne has joined #openstack-placement | 10:31 | |
| *** ttsiouts_ has quit IRC | 10:37 | |
| *** ttsiouts has joined #openstack-placement | 10:38 | |
| *** ttsiouts has quit IRC | 10:42 | |
| *** ttsiouts has joined #openstack-placement | 11:08 | |
| *** ttsiouts has quit IRC | 11:20 | |
| *** ttsiouts has joined #openstack-placement | 11:21 | |
| *** ttsiouts has quit IRC | 11:25 | |
| *** ttsiouts has joined #openstack-placement | 11:27 | |
| *** cdent has joined #openstack-placement | 11:36 | |
| *** ttsiouts has quit IRC | 11:43 | |
| *** ttsiouts has joined #openstack-placement | 11:44 | |
| *** ttsiouts_ has joined #openstack-placement | 11:46 | |
| *** ttsiouts has quit IRC | 11:47 | |
| *** ttsiouts_ has quit IRC | 11:51 | |
| *** cdent has quit IRC | 11:59 | |
| *** e0ne has quit IRC | 12:00 | |
| *** cdent has joined #openstack-placement | 12:04 | |
| *** e0ne has joined #openstack-placement | 12:10 | |
| edleafe | prometheanfire: What were you trying to do with that call? Standard traits are defined in os-traits. You can only create custom traits, hence the error message about the format for custom traits. | 12:22 |
| *** e0ne has quit IRC | 12:34 | |
| *** mriedem has joined #openstack-placement | 12:57 | |
| *** e0ne has joined #openstack-placement | 12:58 | |
| sean-k-mooney | cdent: efried just an fyi i plaid around with improveing the syncing of gerrty last night instead of sleeping | 13:19 |
| sean-k-mooney | https://review.openstack.org/#/q/topic:better_concurrancy+(status:open+OR+status:merged) | 13:19 |
| sean-k-mooney | i havent done much testing(and gerrty has not tests at all) but it seams to work | 13:20 |
| cdent | nice | 13:20 |
| sean-k-mooney | retrofiting gertty with concurent futres instead of the manual treading its uses all over the place is more work then i had hopped but thats start at least. | 13:23 |
| cdent | i bet | 13:26 |
| sean-k-mooney | its built using a varient of the command pateren so each action/command is a task object that is submitted to a queue and then sync trhead has a while true that just decuse the tasks and runs it | 13:28 |
| sean-k-mooney | the queue is a manual implemeantion of basically a priority cure anthe task object are also acting as custom futures | 13:28 |
| sean-k-mooney | so the code itself is actully resonaly well encausated but its also really tightly coupled to its current execution model. | 13:30 |
| *** e0ne has quit IRC | 13:30 | |
| sean-k-mooney | anyway im going to use it locally for a bit and i might see if it helps things | 13:30 |
| *** cdent has quit IRC | 13:36 | |
| *** cdent has joined #openstack-placement | 13:36 | |
| *** cdent has quit IRC | 13:40 | |
| tssurya | cdent: thanks for opening https://storyboard.openstack.org/#!/story/2005473 I'll see if melwitt wants to work on it if not I'll take it up | 14:13 |
| *** cdent has joined #openstack-placement | 14:28 | |
| *** david-lyle is now known as dklyle | 14:35 | |
| *** e0ne has joined #openstack-placement | 14:53 | |
| *** cdent has quit IRC | 15:11 | |
| *** belmoreira has quit IRC | 15:32 | |
| *** cdent has joined #openstack-placement | 15:54 | |
| *** dims has quit IRC | 16:07 | |
| cdent | mriedem: have you had a chance to gaze upon https://review.openstack.org/#/c/651939/ (placementfixture in osc-placement) yet? I'm hoping you will have the chutzpah to dig in | 16:11 |
| efried | oo, there's no way he'll resist a challenge to his yiddish intestinal fortitude | 16:12 |
| cdent | whatever it takes | 16:13 |
| mriedem | oy vey | 16:16 |
| mriedem | lemme polish this nova bug fix turd and i'll dig into it | 16:16 |
| cdent | mriedem is a real mensch | 16:18 |
| *** cdent has left #openstack-placement | 16:20 | |
| *** cdent has joined #openstack-placement | 16:20 | |
| *** david-lyle has joined #openstack-placement | 16:24 | |
| *** dklyle has quit IRC | 16:27 | |
| *** dims has joined #openstack-placement | 16:54 | |
| mriedem | cdent: done | 16:57 |
| cdent | thanks | 16:57 |
| cdent | yeah, good comments mriedem, i knew it | 16:59 |
| *** dims has quit IRC | 16:59 | |
| mriedem | i'll reward myself with lunch and jelly beans | 17:00 |
| *** e0ne has quit IRC | 17:01 | |
| *** dims has joined #openstack-placement | 17:01 | |
| openstackgerrit | Chris Dent proposed openstack/osc-placement master: Use PlacementFixture in functional tests https://review.openstack.org/651939 | 17:50 |
| *** david-lyle is now known as dklyle | 17:55 | |
| *** tssurya has quit IRC | 17:58 | |
| prometheanfire | edleafe: I'm just starting nova-compute, it tries to populate that trait but can't (rejected by placement) | 18:13 |
| edleafe | prometheanfire: it shouldn't be trying to create standard traits, which by definition already exist | 18:13 |
| prometheanfire | the trait it's trying to create is not populated in the nova_api or placement databases (old/new) | 18:14 |
| edleafe | But it's in os-traits, right? | 18:14 |
| openstackgerrit | Chris Dent proposed openstack/osc-placement master: Use PlacementFixture in functional tests https://review.openstack.org/651939 | 18:18 |
| prometheanfire | edleafe: it's in 0.11.0 as a test | 18:26 |
| prometheanfire | os_traits/tests/test_os_traits.py: self.assertIn(ot.COMPUTE_NET_ATTACH_INTERFACE, traits) | 18:26 |
| prometheanfire | but that's the only line | 18:27 |
| edleafe | prometheanfire: looking at https://github.com/openstack/os-traits/commit/56531c2a81e4938fd790d6fc05791ee745da5f03#diff-f41fbcbcd9f737e2226d06ab0bb1903a, it seems that it was added in 0.12.0 | 18:54 |
| prometheanfire | edleafe: looks like that's needed in stein, which is 0.11.0 | 18:55 |
| prometheanfire | https://github.com/openstack/requirements/blob/stable/stein/upper-constraints.txt#L343 | 18:55 |
| prometheanfire | so, backport and 0.11.1 release? | 18:56 |
| prometheanfire | edleafe: that says it's in 0.7.0+ so it's in 0.11.0 | 18:56 |
| edleafe | interestinghuh, yeah, it shows up in https://github.com/openstack/os-traits/commit/8888c528776f27c632d34bec52de09991385bb54 | 18:57 |
| edleafe | which is from the 0.7.0 release | 18:58 |
| * edleafe is confused | 18:58 | |
| edleafe | Ah, I guess I'm misreading the tag line for https://github.com/openstack/os-traits/commit/56531c2a81e4938fd790d6fc05791ee745da5f03 | 18:59 |
| edleafe | it's in every release from 0.7.0 to 0.12.0 | 18:59 |
| prometheanfire | ya | 19:00 |
| cdent | prometheanfire, edleafe when you figure out what's going on here, can you write it down somewhere or tell me about it tomorrow or something? I need to go, but I'm curious | 19:03 |
| prometheanfire | so, I'm guessing the problem isn't as mich as not adding COMPUTE_NET_ATTACH_INTERFACE, but that the api rejects all traits not starting with CUSTOM_? | 19:03 |
| cdent | it's supposed to do that | 19:04 |
| cdent | actually, no, not gonna get sucked in, please let me know what's up, later :) | 19:04 |
| * cdent waves | 19:04 | |
| *** cdent has quit IRC | 19:04 | |
| prometheanfire | so, the compute node tries to add COMPUTE_NET_ATTACH_INTERFACE (because it's not in the traits table), but is correctly rejected? | 19:04 |
| prometheanfire | :P | 19:04 |
| edleafe | The problem is that it checks the reported traits against known traits. That list of known traits *should* include the NET_ATTACH one. It should only attempt to PUT it if it isn't in the known set | 19:05 |
| edleafe | "known traits" should include all of os-traits, plus any previously-defined custom traits | 19:05 |
| prometheanfire | right, so the question becomes why it's not in the traits table | 19:06 |
| edleafe | prometheanfire: yeah, looking at https://github.com/openstack/nova/blob/master/nova/scheduler/client/report.py#L968-L1003, it means that that trait didn't get returned, so it's in the traits_to_create set | 19:08 |
| prometheanfire | yep | 19:09 |
| prometheanfire | placement db_sync doesn't add it (or didn't for me) | 19:09 |
| edleafe | It's not something that I've seen before, so I'm wondering if you might have a wonky installation of os-traits | 19:12 |
| mriedem | did you restart nova-compute with newer os-traits before restarting placement with newer traits? | 19:16 |
| mriedem | that's probably not something we've really considered or handled very well in nova, | 19:16 |
| mriedem | we just require a min version of os-traits and assume we're good, but that doesn't mean the placement we're talking to is using that same min version | 19:16 |
| *** e0ne has joined #openstack-placement | 19:17 | |
| *** e0ne has quit IRC | 19:20 | |
| *** e0ne has joined #openstack-placement | 19:22 | |
| prometheanfire | mriedem: no traits upgrade/install was done before nova | 19:41 |
| prometheanfire | and and it's 0.11.0 all around for what's in use | 19:42 |
| mriedem | COMPUTE_NET_ATTACH_INTERFACE is in 0.11.0 so i don't get it http://git.openstack.org/cgit/openstack/os-traits/tree/os_traits/compute/net.py?h=0.11.0#n17 | 19:46 |
| mriedem | did you check the traits table in the placement db? | 19:46 |
| prometheanfire | yes | 19:47 |
| prometheanfire | it's not in there | 19:47 |
| prometheanfire | (164 rows) | 19:49 |
| mriedem | what happens if you restart the placement-api service? | 19:49 |
| mriedem | got any pyc damage or anything? | 19:50 |
| prometheanfire | want me to remove all pyc/pyo files from os-traits/placement? | 19:51 |
| prometheanfire | as for restarting, everything seems to work | 19:51 |
| mriedem | there should be a log message on restart where the service loads up the new traits | 19:52 |
| mriedem | sec | 19:52 |
| mriedem | btw is this placement-in-nova or extracted placement? | 19:52 |
| prometheanfire | extracted | 19:52 |
| mriedem | this is what should get hit on startup https://github.com/openstack/placement/blob/stable/stein/placement/deploy.py#L93 | 19:53 |
| mriedem | trait.ensure_sync(ctx) | 19:53 |
| mriedem | do you see this logged? https://github.com/openstack/placement/blob/stable/stein/placement/objects/trait.py#L300 | 19:54 |
| prometheanfire | looking | 19:54 |
| prometheanfire | never | 19:54 |
| prometheanfire | grep 'Synced traits from os_traits into API DB' /var/log/placement/placement.log | 19:54 |
| prometheanfire | debug true, log file /var/log/placement/placement.log log dir /var/log/placement | 19:55 |
| prometheanfire | checked uwsgi logs just in case too | 19:55 |
| mriedem | hmm, idk what's going on - we would have hit something obvious in grenade from rocky to stein with these changes i'd think | 19:58 |
| mriedem | what if you drop everything in the traits table and restart the placement service? | 19:58 |
| mriedem | does it show up then? | 19:58 |
| prometheanfire | could try | 19:59 |
| prometheanfire | mriedem: should I truncate resource_provider_traits as well, since... | 20:02 |
| prometheanfire | ERROR: cannot truncate a table referenced in a foreign key constraint | 20:02 |
| prometheanfire | DETAIL: Table "resource_provider_traits" references "traits". | 20:02 |
| mriedem | blag | 20:03 |
| mriedem | *blarg | 20:03 |
| mriedem | you'd have to wipe your resource providers to do that... | 20:04 |
| mriedem | which would get regenerated from your computes, but...is this a test/dev env? | 20:04 |
| prometheanfire | kinda? it's my home env | 20:06 |
| mriedem | oh, heh | 20:06 |
| mriedem | well maybe before that you want to add some debug logging to https://github.com/openstack/placement/blob/stable/stein/placement/objects/trait.py#L269 and see if you can spot something obvious | 20:07 |
| mriedem | like dump the std_traits and db_traits | 20:08 |
| prometheanfire | k | 20:08 |
| prometheanfire | https://gist.github.com/prometheanfire/715b26b57fe5218b72eda0301c784164 | 20:12 |
| prometheanfire | looks like a lot of things need syncing | 20:13 |
| prometheanfire | there's definitely stuff in batch_args | 20:13 |
| mriedem | ok COMPUTE_NET_ATTACH_INTERFACE is in std_traits | 20:14 |
| prometheanfire | seeing if it's passed | 20:14 |
| mriedem | and need_sync | 20:14 |
| prometheanfire | and in the to be sync'd list/batch args | 20:14 |
| prometheanfire | WE DID NOT SYNC, for shame | 20:14 |
| prometheanfire | so it is passed, (excepted) | 20:15 |
| mriedem | hmm, wonder if you're hitting a duplicate | 20:16 |
| mriedem | did you log that? | 20:16 |
| prometheanfire | it's not logged, just passed, writing a log now | 20:16 |
| prometheanfire | I wonder if we should be inserting one at a time? | 20:17 |
| prometheanfire | since all I'll get is that the batch failed I think | 20:17 |
| mriedem | the duplicate entry should say which one was causing the problem | 20:17 |
| prometheanfire | ok | 20:17 |
| prometheanfire | DETAIL: Key (id)=(24) already exists. | 20:19 |
| prometheanfire | which for me is... | 20:19 |
| prometheanfire | 2018-03-21 23:26:25.3102 | | 24 | HW_CPU_X86_SHA | 20:19 |
| mriedem | that one doesn't show up in your need_sync output | 20:20 |
| mriedem | or batch_args | 20:20 |
| prometheanfire | because it already exists | 20:20 |
| mriedem | right, | 20:20 |
| prometheanfire | placement is trying to insert it with an id that's already in use | 20:20 |
| mriedem | but my point is we shouldn't be inserting that one and triggering the dupblice entry error | 20:20 |
| prometheanfire | this time it was DETAIL: Key (id)=(26) already exists. | 20:21 |
| prometheanfire | let me get a log with everything (since ordering changes per run it looks like) | 20:21 |
| mriedem | i guess i'm not understanding since we're not trying to insert HW_CPU_X86_SHA per your logs | 20:21 |
| prometheanfire | https://gist.githubusercontent.com/prometheanfire/1fd41c3d8c0153a1b94e687477ab8223/raw/77d1206d112591a51c0079aa9aff7fa890b308a7/gistfile1.txt | 20:21 |
| prometheanfire | right, but something else was trying to be inserted using the same id, the id clashed, not the name | 20:22 |
| mriedem | what db are you using? mysql? | 20:22 |
| prometheanfire | but the insert doesn't include the id, odd | 20:23 |
| prometheanfire | psql | 20:23 |
| mriedem | of course | 20:23 |
| prometheanfire | :P | 20:23 |
| prometheanfire | have to have at least one guinea pig | 20:23 |
| mriedem | zzzeek: have you ever heard of bulk insert autoincrement failing with postgresql? | 20:25 |
| mriedem | prometheanfire: i've got something you can try, sec | 20:30 |
| prometheanfire | https://gist.github.com/prometheanfire/ff494588ad06fc9c2f55c30524b23478 | 20:30 |
| prometheanfire | that's odd | 20:30 |
| *** e0ne has quit IRC | 20:31 | |
| prometheanfire | and that's not a name in the db either | 20:31 |
| openstackgerrit | Matt Riedemann proposed openstack/placement master: WIP: help prometheanfire for crazy postgresql bulk insert https://review.openstack.org/653552 | 20:32 |
| mriedem | prometheanfire: try that ^ | 20:32 |
| prometheanfire | lol | 20:33 |
| prometheanfire | k | 20:33 |
| prometheanfire | reqs meeting now | 20:34 |
| prometheanfire | failed hard | 20:36 |
| prometheanfire | 2019-04-17 15:35:15.376 6402 ERROR placement sqlalchemy.exc.InvalidRequestError: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (psycopg2.IntegrityError) duplicate key value violates unique constraint "traits_pkey" | 20:36 |
| mriedem | ok same as before | 20:37 |
| mriedem | wtf | 20:37 |
| mriedem | the sqla docs say we could set return_defaults=True to insert them one at a time | 20:37 |
| mriedem | maybe that's worth a try | 20:37 |
| mriedem | at the expense of performance | 20:37 |
| mriedem | but it also says, " If the rows to be inserted only refer to a single table, then there is no reason this flag should be set as the returned default information is not used." | 20:38 |
| mriedem | idk, need help from jaypipes and/or zzzeek here | 20:38 |
| mriedem | https://stackoverflow.com/questions/15834569/how-to-bulk-insert-only-new-rows-in-postresql doesn't help me | 20:39 |
| prometheanfire | I tried inserting just one and had the error | 20:39 |
| prometheanfire | see https://gist.github.com/prometheanfire/ff494588ad06fc9c2f55c30524b23478 | 20:39 |
| mriedem | seems like the autoincrement isn't being honored at all | 20:40 |
| prometheanfire | here's the table schema https://gist.githubusercontent.com/prometheanfire/fa71a3c093dc5f1d25ca00fc60238a93/raw/e0ebbdce6b56ca728a9a1e433d47dfc335c29a58/gistfile1.txt | 20:42 |
| melwitt | are these inserts with explicit id? googled and found this https://stackoverflow.com/questions/9108833/postgres-autoincrement-not-updated-on-explicit-id-inserts | 20:42 |
| mriedem | no | 20:42 |
| mriedem | just bulk inserting records with the name and assuming the db will autogenerate/increment the id pkey | 20:43 |
| melwitt | hm | 20:43 |
| mriedem | prometheanfire: what version of sqla do you have? | 20:43 |
| prometheanfire | whatever is in upperconstraints | 20:44 |
| prometheanfire | 1.2.18 | 20:44 |
| zzzeek | mriedem: "autoincerment" in postgresql comes from a sequence object that is independent of the table itself | 20:45 |
| zzzeek | mriedem: so if the table has rows that were hand-inserted into it using ids that the sequence has not addressed yet, "autoincrement" inserts can fail unless the sequence is bumped manually | 20:45 |
| prometheanfire | that's why then | 20:45 |
| prometheanfire | since I did the manual table import (didn't see the migrate script for postgres) | 20:46 |
| zzzeek | prometheanfire: so you need to find the sequences in quesstion and do ALTER SEQUENCE | 20:46 |
| zzzeek | to bump them up | 20:46 |
| prometheanfire | ok, will after reqs meeting is done | 20:47 |
| mriedem | prometheanfire: ah... | 20:47 |
| prometheanfire | mriedem: yep | 20:47 |
| mriedem | we should maybe document a known issue in https://docs.openstack.org/placement/latest/upgrade/to-stein.html | 20:49 |
| mriedem | in case others miss the pg script - or maybe the pg script is missing something | 20:49 |
| prometheanfire | it may be missing something, as it imports the table and does not strip the ID | 20:50 |
| prometheanfire | at least when I read it | 20:51 |
| mriedem | hmm, we have a grenade postgresql job but i think it's in the experimental queue, maybe that's hitting this in stable/stein as well | 20:51 |
| prometheanfire | same might happen in other tables with sequences (user, tec) | 20:52 |
| prometheanfire | looks like that fixed it | 21:00 |
| mriedem | prometheanfire: probably a good idea to report a bug just so it's tracked if someone else hits it (windriver uses postgresql i think, as does huawei...) | 21:00 |
| mriedem | https://storyboard.openstack.org/#!/project/1113 | 21:00 |
| prometheanfire | I will | 21:00 |
| openstackgerrit | Matt Riedemann proposed openstack/placement stable/stein: DNM: log trait sync duplicate entry failure https://review.openstack.org/653585 | 21:06 |
| mriedem | testing grenade-postgresql in stein here https://review.openstack.org/#/c/653587/ | 21:08 |
| prometheanfire | https://storyboard.openstack.org/#!/story/2005478 | 21:10 |
| prometheanfire | thanks | 21:10 |
| *** takashin has joined #openstack-placement | 21:50 | |
| *** mriedem has quit IRC | 22:10 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!