| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-11-22 | |||
| 19:31:54 | dansmith | actions have been there a long time, with lots of useful information | |
| 19:32:02 | melwitt | no, I agree that more async is good. I'm just saying that to me, in my own perception, it's a shift from the past habit | |
| 19:32:26 | dansmith | if the users don't know about it, then we probably have some doc gaps, but I don't think that really changes anything | |
| 19:32:27 | melwitt | my habit was not to use instance actions. my habit will be to use instance actions from now on, now that I know | |
| 19:32:38 | dansmith | and I also don't think that actions are some obscure corner of the nova world | |
| 19:32:41 | mriedem | the shift happened years ago then, is my point | |
| 19:32:57 | melwitt | ok, mine didn't, and I figured maybe I'm not the only one | |
| 19:32:59 | dansmith | I think that some people might never go looking for it and just infer what they can from status, return codes, etc, but they're missing part of the story | |
| 19:33:01 | mriedem | after yesterday's meeting i have a todo to write a doc about using actoins | |
| 19:33:16 | mriedem | but i'm still working on this resize/cold migrate doc for artom | |
| 19:33:27 | dansmith | I totes don't see how this is a shift | |
| 19:33:39 | melwitt | I get that you guys don't | |
| 19:33:46 | dansmith | when actions became a thing, there was more information available, that's not a shift, that's just more | |
| 19:33:54 | artom | mriedem, I'll handle the sequence diagram, fwiw | |
| 19:34:18 | dansmith | inferring things from api behavior is.. a thing I guess, and over time those inferences will have to change because they're based on assumptions | |
| 19:34:45 | dansmith | so there is a shift in those inferences I guess, but not in like fundamental behavior of how one uses nova or anything | |
| 19:34:51 | melwitt | it was a shift for me as a user, that's all I'm saying. and the only reason this came up is that, it's a shift for me, I see how important it is, so therefore I have a new interest in fixing the osc command for it | |
| 19:35:43 | melwitt | it means I will change my habit in how I use nova and it might change others too | |
| 19:35:52 | mriedem | artom: i'm about to push it | |
| 19:36:00 | mriedem | artom: i don't want you putting rebuild in the diagram somewhere | |
| 19:36:04 | mriedem | ZING | |
| 19:36:10 | artom | *ded* | |
| 19:36:27 | artom | mriedem, you saw my review, btw? | |
| 19:36:31 | artom | Before you push | |
| 19:36:45 | mriedem | nope, looking | |
| 19:37:12 | artom | mriedem, nothing major, but probably better to see it before pushing again | |
| 19:37:41 | sean-k-mooney | artom: by the way ill adress your comments on my patches on monday i didnt get to them this week but i still plan to adress them shortly | |
| 19:37:58 | sean-k-mooney | but im ment ot be in limerick in 20 mins so i better go o/ | |
| 19:38:21 | artom | sean-k-mooney, drive safe | |
| 19:39:31 | dansmith | our docs should probably have something like this: | |
| 19:39:32 | dansmith | https://support.metacloud.com/hc/en-us/articles/115003922347-Using-the-Instance-Action-List-for-Troubleshooting | |
| 19:39:52 | dansmith | which doesn't even say anything about error state or fault that I know of, | |
| 19:39:52 | melwitt | let's copy it | |
| 19:40:03 | dansmith | but specifically is like "my instance is stopped, whyforisthat?" | |
| 19:40:14 | melwitt | again, maybe it's just me, I'm the lone person who never used instance actions. like a rebel | |
| 19:40:15 | dansmith | which is exactly what we're talking about I think | |
| 19:40:32 | dansmith | melwitt: I think it's entirely possible that it may just be you :P | |
| 19:40:42 | melwitt | uh huh | |
| 19:40:45 | dansmith | heh | |
| 19:41:09 | mriedem | dansmith: that's basically the kind of doc i was going to write, just cli though | |
| 19:41:21 | mriedem | and using resize as an example where the claim on the dest fails | |
| 19:41:22 | dansmith | mriedem: there's cli below | |
| 19:41:25 | dansmith | yep | |
| 19:41:30 | mriedem | using the nova clie | |
| 19:41:31 | mriedem | *cli | |
| 19:41:33 | mriedem | i'd use osc | |
| 19:41:53 | mriedem | anyway, same idea | |
| 19:41:56 | dansmith | I guess if we have no "how do I figure out why my instance is unhappy" doc, then people will make assumptions about how to (or not do) that, which might stop at the instance detail output | |
| 19:41:59 | melwitt | well, if everyone else knows, then that's ideal. I'm glad to hear it | |
| 19:42:10 | mriedem | what are instance actions, when are they useful, how to use them, give an example scenario using resize where the claim fails | |
| 19:42:29 | dansmith | mriedem: well, I think starting with the use-case of debugging an unknown state of an instance is useful, | |
| 19:42:42 | dansmith | because if people _don't_ know what actions are, they're not looking for a doc on actions | |
| 19:43:06 | dansmith | melwitt: amirite/ | |
| 19:43:46 | dansmith | maybe "unknown state" is the wrong term, but.. debugging why something failed or isn't expected on the instance, | |
| 19:43:52 | melwitt | dansmith: yeah, I think so. case in point, gregwork was here earlier and a volume attach failed and there was no indication. I told him to look at instance actions based on the resize/migration thing from yesterday | |
| 19:43:56 | dansmith | which might be a weird state and might be "resize never happend" | |
| 19:44:25 | melwitt | and in there, it showed the volume attach with 'error' as the result | |
| 19:44:38 | dansmith | melwitt: I think gregwork is just lonely and wanted to talk to someone and not read docs, so not sure that would have helped him | |
| 19:45:23 | melwitt | so there's already a doc? what did I miss | |
| 19:45:33 | mriedem | no | |
| 19:45:37 | mriedem | i was joking, | |
| 19:45:43 | melwitt | what | |
| 19:46:08 | mriedem | how do i say politely, if you guys want to write the doc(s), go ahead | |
| 19:46:45 | melwitt | I'll copy metacloud's | |
| 19:46:52 | gregwork | heh i was just reporting something strange that i observed. normally openstack is very vocal about errors that get thrown | |
| 19:47:06 | gregwork | i thought it was unusual that not a lot of fuss was happening | |
| 19:48:36 | gregwork | and ultimately heat would just fail to deploy the stack after some time (token expiry) | |
| 19:48:40 | KeithMnemonic | mridem: melwitt: i can help as well and then abandon my hack sitting out there ;-) | |
| 19:48:52 | gregwork | usually if a resource barfs heat catches it and also barfs | |
| 19:48:57 | gregwork | this went off into space | |
| 19:49:05 | melwitt | KeithMnemonic: sorry, what's your hack? | |
| 19:49:21 | KeithMnemonic | using id only | |
| 19:49:34 | melwitt | gregwork: sounds like heat needs to look at INSTANCE ACTIONS | |
| 19:49:45 | KeithMnemonic | https://review.opendev.org/691045 | |
| 19:49:57 | melwitt | oh that, ok | |
| 19:50:29 | KeithMnemonic | gyee and i played with it a while trying to get the name to work and we never could | |
| 19:50:44 | melwitt | that sounds hard then :) | |
| 19:51:32 | melwitt | I'll try to help, it's related to the server event thing, so hopefully once figured out once it will work for all | |
| 19:51:57 | melwitt | I don't have that much experience with osc | |
| 19:52:58 | openstackgerrit | Merged openstack/nova stable/rocky: Don't delete compute node, when deleting service other than nova-compute https://review.opendev.org/695382 | |
| 19:53:04 | openstackgerrit | Merged openstack/nova master: tests: Use consistent URL regex substitution https://review.opendev.org/665949 | |
| 19:53:07 | melwitt | gregwork: I'm joking but it's probably true. would need to open a bug with them and explain they need to use and parse instance actions | |
| 19:53:12 | openstackgerrit | Merged openstack/nova master: Give the policy vision document a facelift https://review.opendev.org/644615 | |
| 19:53:25 | openstackgerrit | Merged openstack/nova master: test cleanup: Remove skipIf test decorator https://review.opendev.org/685375 | |
| 19:53:32 | melwitt | to be able to pick up the volume attach fail | |
| 19:59:49 | KeithMnemonic | melwitt this is what we saw http://paste.openstack.org/show/785530/ | |
| 20:00:44 | melwitt | KeithMnemonic: yeah, I was gonna say, (and gyee's comment says the same) that not even the legacy novaclient can lookup a deleted server by name | |
| 20:00:49 | KeithMnemonic | and some where there is a case statement/loop that tried different lookups and that is where it never finds the server when a name is used | |
| 20:01:05 | mriedem | since https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/server-event.html doesn't take a --delete option, to fix the bug there i'd probably handle a NotFound when looking up the server by name or id, and if --os-compute-api-version >= 2.21 then just assume you were given an ID and pass it through | |
| 20:01:15 | mriedem | it'll either work or the user will get a 404 anyway | |
| 20:02:13 | melwitt | KeithMnemonic: yeah, like I said, I think even with the legacy client, the underlying binding that osc is using, there's no way to lookup deleted by name | |
| 20:02:37 | melwitt | so if you want that, you'd have to add it to the novaclient python binding too, afaik | |
| 20:02:38 | mriedem | i'm not sure that's true - if you're admin you can list servers filtering on deleted=True and name | |
| 20:03:01 | melwitt | list you can, but I'm not sure about like nova show | |
| 20:03:16 | mriedem | right, not in the api - it would be client side sugar | |
| 20:03:48 | melwitt | yeah, that's what I mean. novaclient needs something to be able to. unless you're saying on the cli can't and that the python api can | |
| 20:03:58 | mriedem | heh, "Filters the response by a server name, as a string. You can use regular expressions in the query. For example, the ?name=bob regular expression returns both bob and bobb. If you must match on only bob, you can use a regular expression that matches the syntax of the underlying database server that is implemented for Compute, such as MySQL or PostgreSQL." | |
| 20:04:13 | mriedem | "if you know the cloud you're talking to is using mysql or postgres, just fashion your filtering that way" | |
| 20:04:37 | melwitt | lol | |
| 20:05:02 | melwitt | I'm super rusty on the clients, gotta get back in there | |