| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-09-28 | |||
| 13:58:04 | zigo | Looks like nova-api on Xena (over Debian Bullseye) doesn't like me... | |
| 13:58:16 | zigo | Failed to delete allocations for consumer 26ee7dd9-75c2-41f5-86f4-c714ed36aab7. Error: {"errors": [{"status": 500, "title": "Internal Server Error", "detail": "The server has either erred or is incapable of performing the requested operation.\n\n unsupported callable ", "request_id": "req-34a9215b-9387-43b0-ae24-2d85c7d2b8f5"}]} (HTTP 409) (Request-ID: req-57d65ddf-f845-4fa4-9f13-4382ec19dc72) | |
| 13:58:16 | zigo | # openstack server delete 26ee7dd9-75c2-41f5-86f4-c714ed36aab7 | |
| 13:58:55 | zigo | When doing so, nova-api just spams its log with some policy deprecation stuff... | |
| 13:59:07 | zigo | How am I supposed to generate the default policy file?!? | |
| 13:59:42 | zigo | This looks like completely broken AGAIN... :( | |
| 14:01:10 | zigo | Also, has the /healthcheck changed behavior?!? | |
| 14:02:38 | zigo | Now it wants me to be authenticated ?!? | |
| 14:02:44 | zigo | Seriously? | |
| 14:03:04 | zigo | How am I supposed to do that with the standard haproxy thingy? | |
| 14:03:25 | bauzas | afaik we haven't changed the paste.ini | |
| 14:03:40 | bauzas | the whole policy thing is different | |
| 14:04:02 | bauzas | but i need to go away or I'll be pedestrian | |
| 14:05:38 | zigo | When I do a: curl -k https:// |
|
| 14:05:49 | zigo | I'm not even sure that can be done with haproxy. | |
| 14:05:49 | opendevreview | Ivan Kolodyazhny proposed openstack/nova master: Fix NVMe volume attach https://review.opendev.org/c/openstack/nova/+/811413 | |
| 14:08:12 | zigo | It looks like its probably my bad, checking ... | |
| 14:08:24 | gibi | lyarwood: does this ring a bell to you https://review.opendev.org/c/openstack/devstack/+/811399/1#message-941958791253e3555a648888281a5de6cbf3b1c4 ? | |
| 14:12:39 | lyarwood | gibi: nope never seen that before | |
| 14:12:58 | lyarwood | http://review.opendev.org/ dead for everyone? | |
| 14:14:29 | gibi | works for me | |
| 14:14:33 | kashyap | Yeah, same here | |
| 14:14:36 | dansmith | same | |
| 14:14:38 | kashyap | (As in, works) | |
| 14:15:43 | dansmith | bauzas: is there a tentative ptg schedule yet? | |
| 14:17:42 | gibi | dansmith: we have two cross project discussions scheduled to a certain slot but top of that we haven't assigned topics to slots yet | |
| 14:17:54 | gibi | https://etherpad.opendev.org/p/nova-yoga-ptg | |
| 14:18:05 | gibi | lyarwood: ack, then I recheck :) | |
| 14:18:47 | dansmith | gibi: okay, it's always that arms race where everyone is trying to avoid others' sessions, but nobody has scheduled yet :) | |
| 14:24:16 | gibi | I think it is also part of not having the PTG planning in focus until after Xena is out of the tood | |
| 14:24:19 | gibi | door | |
| 14:24:49 | zigo | https://paste.opendev.org/show/809649/ | |
| 14:24:49 | zigo | When trying to delete a server that went into error, I get this in placement.log: | |
| 14:24:56 | zigo | Any idea why? | |
| 14:25:08 | dansmith | I dunno, I think the "I don't want to schedule X until I know of person Y is available, but person Y's schedule depends on other project Z" problem would exist either way | |
| 14:26:26 | gibi | dansmith: true | |
| 14:26:30 | gibi | zigo: interesting | |
| 14:26:49 | zigo | Maybe I should try downgrading to oslo.policy 3.7.0 to see what's going on? | |
| 14:26:56 | dansmith | that error can come from the json encoder/decoder, maybe there's something wrong with the policy file? | |
| 14:27:26 | zigo | dansmith: What I'm surprised of, is that I'm using a yaml policy file in /etc/placement/policy.d/00_default_policy.yaml | |
| 14:27:43 | dansmith | zigo: ah, good, that was going to be my next question | |
| 14:27:54 | zigo | And there, everything was supposed to be commented out, but it's not: every DEPRECATED stuff is active ... | |
| 14:28:00 | zigo | Same for Nova. | |
| 14:28:07 | zigo | (I had to comment out everything...) | |
| 14:28:51 | zigo | dansmith: So you can rule out a policy.json thingy, as I don't have one ! :) | |
| 14:30:39 | zigo | Same result with oslo.policy 3.7.0 | |
| 14:33:23 | zigo | Ok, got it to work ... | |
| 14:33:42 | zigo | Again, same stuff: oslopolicy-sample-generator is generating a default policy yaml file that DOES NOT WORK ! | |
| 14:33:52 | zigo | When commenting everything out, it works... | |
| 14:34:20 | gmann | zigo: I do not think oslopolicy-sample-generator add the deprecated rules | |
| 14:34:41 | gmann | zigo: best way is not to have policy file if no rule overridden is needed | |
| 14:34:41 | zigo | gmann: That's what it did for me ... | |
| 14:35:26 | zigo | gmann: Well, in my package, I'm writing a /etc/placement/policy.d/00_default_policy.yaml with the expectation that this fille will only contain commented out directives ... | |
| 14:35:33 | zigo | It worked this way for the last 2 or 3 releases. | |
| 14:35:36 | zigo | Now that's broken. | |
| 14:36:25 | gmann | zigo: commented out you mean except deprecated rules right? | |
| 14:36:43 | zigo | gmann: Why would there be some special cases for the deprecated rules? | |
| 14:37:32 | gmann | zigo: no, I mean everything was commented out ? because earlier you mentioned deprecated rules were not commented? | |
| 14:38:13 | zigo | gmann: That's what I mean yes, in my packages, now, I have everything commented out but all what's deprecated ... :/ | |
| 14:39:18 | gmann | I feel we should extend these tool oslopolicy-sample-generator and oslopolicy-policy-generator to add deprecated rule too with flag so that it does not break deployment not moved to new policies yet | |
| 14:40:10 | zigo | Anyway, GOT MY FIRST Xena VM UP AND RUNNING AND PINGING !!! \o/ | |
| 14:40:28 | gibi | \o/ | |
| 14:40:28 | gmann | zigo: can you paste your old (failing) policy file? | |
| 14:40:32 | gmann | zigo: perfect | |
| 14:40:38 | bauzas | dansmith: I saw gibi answered you, not for the moment | |
| 14:40:49 | dansmith | ack | |
| 14:47:13 | gmann | zigo: and that policy file (failing ) one is not generated from oslopolicy-sample-generator tool right? is it old one of wallaby or something? | |
| 14:48:35 | bauzas | dansmith: gibi: that said, I'll try to create an agenda for next week's meeting | |
| 14:48:55 | bauzas | create a *PTG tentative agenda | |
| 14:49:00 | gibi | bauzas: sounds good let me know if you need help | |
| 14:49:10 | bauzas | gibi: will copy/think/paste :p | |
| 14:49:21 | gmann | gibi: bauzas I added one more cross project topic oslo-nova about this ^^ policy file stuff L56 for now | |
| 14:49:28 | bauzas | ack | |
| 14:49:45 | gibi | bauzas: I can definitely help with the first and last step, not sure about the middle :P | |
| 14:50:02 | gmann | this keep coming in every cycle especially when new policy are implemented, I feel we can find some better solution | |
| 14:52:23 | gmann | zigo: FYI, in case you attend ptg, I have added this topic in PTG discussion. we will discuss if oslopolicy-sample-generator tool can be extended in way that it works for both deployment with old tokens + new tokens | |
| 14:53:17 | zigo | gmann: I've put the files over here: http://shade.infomaniak.ch/policy-files/ | |
| 14:53:40 | zigo | I wonder, should I add a sed in all my packages when generating the policy files then? | |
| 14:53:55 | zigo | As in, commenting-out everything that not commented? | |
| 14:55:03 | gmann | zigo: yeah or can you skip generating it (no policy file) ? I think you need to ship one in packaging ? | |
| 14:55:43 | zigo | With something like: sed -i 's/^"/#"/ $(CURDIR)/debian/nova-common/etc/nova/policy.d/00_default_policy.yaml | |
| 14:56:07 | gmann | zigo: ok, let me debug that today/tomorrow, having only deprecated rules in policy file should work | |
| 14:56:11 | zigo | gmann: I do not *NEED* to generate one, but I think it is a service to the Debian users to provide them with a policy file that has all what's possible... | |
| 14:57:04 | zigo | gmann: Well, maybe we should add an option in oslopolicy-sample-generator to comment out the DEPRECATED options ? | |
| 14:57:35 | zigo | oslopolicy-sample-generator --commented-out-deprecated-options --output-file=$(CURDIR)/debian/nova-common/etc/nova/policy.d/00_default_policy.yaml --format yaml --namespace nova | |
| 14:57:53 | gmann | zigo: oh does oslopolicy-sample-generator tool generated that file with depreacted rule not commented? | |
| 14:58:08 | zigo | gmann: Yeah, that's what I'm saying since the begining ! :) | |
| 14:58:16 | zigo | Sorry for not expressing myself correctly ... | |
| 14:58:19 | gmann | humm | |
| 14:58:28 | zigo | PYTHONPATH=$(CURDIR)/debian/tmp/usr/lib/python3/dist-packages oslopolicy-sample-generator \ | |
| 14:58:28 | zigo | mkdir -p $(CURDIR)/debian/nova-common/etc/nova/policy.d | |
| 14:58:28 | zigo | My package simply does: | |
| 14:58:29 | zigo | --output-file=$(CURDIR)/debian/nova-common/etc/nova/policy.d/00_default_policy.yaml \ | |
| 14:58:31 | zigo | --format yaml \ | |
| 14:58:33 | zigo | --namespace nova | |
| 14:58:38 | zigo | Nothing more ... | |
| 14:59:05 | zigo | (note: the PYTHONPATH setting is there to use the installed python3-nova package as if it was in the system) | |
| 15:13:45 | bauzas | lyarwood: seen this ? https://bugs.launchpad.net/nova/+bug/1945323 | |
| 15:13:56 | bauzas | gibi: the reporter proposes ^ for a RC3 | |
| 15:14:07 | bauzas | wondering whether it's a regression | |