Earlier  
Posted Nick Remark
#openstack-nova - 2019-10-22
20:33:41 melwitt this is what I had to do last time to fix enablement of tls between nova-compute and the proxy https://review.opendev.org/643045
20:34:05 mriedem we aren't even getting that far because https://review.opendev.org/#/c/643045/9/lib/nova@659
20:34:15 mriedem [[ ${NOVA_CONSOLE_PROXY_COMPUTE_TLS} = "True" ]]
20:34:33 mriedem NOVA_CONSOLE_PROXY_COMPUTE_TLS: true
20:34:45 melwitt oh, you're saying that flag is not getting reflected as true? O.o
20:34:51 KeithMnemonic is this a valid command option, using --deleted and --limit -1. it seems to cause an infinite hang on Rocky. i did not check newwer releases yet
20:35:11 mriedem melwitt: hard to say because local.conf here looks OK https://zuul.opendev.org/t/openstack/build/9726aebf48804b83bbebe290bd8187ac/log/controller/logs/local_conf.txt.gz#54
20:35:30 melwitt hmm
20:36:14 melwitt KeithMnemonic: I didn't think that limit -1 was a thing. unlimited happens by omitting --limit, I thought. but regardless of that, there shouldn't be an indefinite hang, that I would call a bug
20:36:37 mriedem limit=-1 is a novaclient thing to page until there are no more results
20:37:02 melwitt oh :\ I thought it did that on its own in the absence of --limit
20:37:04 KeithMnemonic 'osapi_max_limit' will be used instead.
20:37:04 KeithMnemonic than 'osapi_max_limit' option of Nova API,
20:37:04 KeithMnemonic -1, all servers will be displayed. If limit is greater
20:37:04 KeithMnemonic Maximum number of servers to display. If limit equals
20:37:04 KeithMnemonic " --limit <num-servers>
20:37:05 KeithMnemonic "
20:37:11 melwitt nevermind, sorry
20:37:13 KeithMnemonic from the cli help
20:37:27 mriedem melwitt: nope, by default limit is 1000 results in the api
20:37:27 KeithMnemonic ok i can log a bug. i will see if this happens on something newer
20:37:36 KeithMnemonic i did not see anything open around this currently
20:37:52 melwitt mriedem: that I know, but I thought the client would auto-page by itself without need to tell it
20:37:56 melwitt and I was wrong
20:38:12 KeithMnemonic in the env i tested, i only have maybe 20 deleted at most
20:38:34 melwitt yeah, something is whack there, I think
20:39:35 KeithMnemonic let me see what debug i can get to add to the bug to help isolate it
20:39:49 mdbooth mriedem: Responded. I still think that's good to go. I'd prefer to make the requested changes in the backports. They're trivial enough.
20:40:47 melwitt KeithMnemonic: yeah run with --debug to see where it gets stuck
20:50:16 mriedem melwitt: oh here is the vencrypt stuff, i was looking in the wrong config file (there are only 20 nova configs in a devstack job)
20:50:17 mriedem https://zuul.opendev.org/t/openstack/build/9726aebf48804b83bbebe290bd8187ac/log/controller/logs/etc/nova/nova_cell1_conf.txt.gz#32
20:51:46 mriedem so i wonder if NOVA_CONSOLE_PROXY_COMPUTE_TLS=True just doesn't work for the subnode since we've never had a multinode job use that yet
20:52:33 melwitt mriedem: ah yeah. awhile back I split things at stephenfin request (and I agree was a good idea) to only config which settings were required on the proxy and compute host, respectively. so they don't just all appear in all configs like they used to back in the day
20:54:20 melwitt mriedem: the subnode is nova-compute only, right? if so, then it would make sense to *not* run the proxy service there and it might just be that we have a wrong assumption in the conditional that the service will necessarily be running if we're doing tls between the computes and the proxy?
20:54:46 mriedem yeah subnode is nova-compute only
20:54:53 mriedem no n-novnc service running on the subnode
20:55:07 melwitt and maybe the intermittent is because depending on whether the instance being tested for vnc lands on the subnode or not?
20:55:13 mriedem yup i think so
20:56:00 melwitt yeah, so it sounds like we need to use some other condition for whether to do the stuff, not the presence of the tls proxy service thing
20:57:39 mriedem ok so maybe for now i'll rev this patch, comment out the usage of NOVA_CONSOLE_PROXY_COMPUTE_TLS since it doesn't work for multinode jobs, and see if that at least gets this patch moving forward
21:00:14 melwitt ok. and I can work on a change in devstack to make it work with multinode, and then stack a change on top of yours that Depends-On it, to see if it clears up the problem
21:00:47 melwitt or sorry, I'll just do the devstack change and then you can uncomment and Depends-On to test
21:01:21 mriedem sure that works, thanks
21:01:25 openstackgerrit Matt Riedemann proposed openstack/nova master: Make nova-next multinode and drop tempest-slow-py3 https://review.opendev.org/683988
21:11:31 KeithMnemonic so what i can tell is first it calls /server/detail?deleted=True and this returns a good list, then the next call is that same but with &marker=<id of last server> and it loops here
21:12:43 KeithMnemonic so something about the marker. if i try and call it using curl i get a 401 but my guess is you that is not a valid test
21:12:48 openstackgerrit Matt Riedemann proposed openstack/nova master: Revert "Log CellTimeout traceback in scatter_gather_cells" https://review.opendev.org/690417
21:13:05 mriedem KeithMnemonic: you're getting a 401 with curl b/c you're not providing a token
21:13:11 KeithMnemonic no i am
21:13:17 KeithMnemonic it only 401 with &marker
21:13:28 KeithMnemonic with just ?delete=True it is fine
21:13:38 mriedem 401 is an auth issue so that doesn't make much sense
21:15:31 KeithMnemonic http://paste.openstack.org/show/785488/
21:15:49 KeithMnemonic you can see something with adding &marker, but it could be my test is wrong
21:15:58 KeithMnemonic i was just trying to curl what is was looping on
21:16:24 KeithMnemonic the --debug show it loops once it adds on &marker=<last deleted UUID>
21:19:24 openstack Launchpad bug 1773945 in OpenStack Compute (nova) "nova client servers.list crashes with bad marker" [Medium,Incomplete]
21:19:24 KeithMnemonic https://bugs.launchpad.net/nova/+bug/1773945
21:20:22 mriedem i think i see the problem
21:20:30 KeithMnemonic not quite my issue , but something with markers
21:20:57 mriedem https://review.opendev.org/#/c/527564/1/nova/compute/api.py
21:21:14 mriedem objects.BuildRequestList.get_by_filters returns an empty list if filtering on deleted=True,
21:21:36 mriedem the code assumes that if there was a marker and we got a build request list (not MarkerNotFound), we found our marker and can set marker=None since we won't find it in a cell,
21:21:41 mriedem but that's not the case here
21:22:00 mriedem that goes beyond rocky https://review.opendev.org/#/q/I1aa3ca6cc70cef65d24dec1e7db9491c9b73f7ab
21:22:53 mriedem https://review.opendev.org/#/c/527564/1/nova/objects/build_request.py@376
21:24:10 mriedem KeithMnemonic: in your reproduce do you have any deleted servers in the db?
21:24:15 KeithMnemonic especially since i only have 18 deleted, it seems it should not need the marker right?
21:24:19 mriedem you must otherwise you wouldn't get a marker
21:26:28 melwitt maybe the deleted instances are located across separate cells?
21:26:44 mriedem i meant i see the reason for the infinite loop
21:26:47 mriedem KeithMnemonic: did you open a bug?
21:27:18 KeithMnemonic not yet, was trying to get more debug to make the bug report useful
21:27:27 KeithMnemonic that is when i found it looped on marker
21:27:41 melwitt I was talking about why a marker when only 18 deleted?
21:27:54 melwitt I dunno
21:27:56 mriedem because limit is in the request i think
21:28:01 mriedem limit == paging
21:28:22 KeithMnemonic correct --limit -1
21:28:23 melwitt oh ok
21:29:04 KeithMnemonic mriedem, ok i can open the bug, do you need anything specific in it or you have a handle on the issue?
21:29:16 mriedem the paste is useful and recreate steps
21:29:35 KeithMnemonic ok let me add all of that
21:31:08 mriedem nice to know that regressions i introduced in queens are coming back to find me now
21:32:13 KeithMnemonic lol
21:34:39 efried mriedem: serves you right for not giving your features enough soak time.
21:40:19 mriedem heh
21:40:32 mriedem doesn't really fit here, but i can see that's been smoldering in your pocket for awhile
21:42:14 mriedem i can never remember if you specify marker if the marker instance comes back as the first item in the list
21:42:19 mriedem or if it's everything after the marker
21:43:13 mriedem results after this value."
21:43:13 mriedem aha, ":param marker: the last item of the previous page; we returns the next
21:52:58 mriedem KeithMnemonic: ok i've got a recreate functional test ready to push up whenever you have this bug filed
22:00:39 openstackgerrit Matt Riedemann proposed openstack/nova master: Add functional regression test for bug xxxxxx https://review.opendev.org/690428
22:00:40 openstackgerrit Matt Riedemann proposed openstack/nova master: Fix listing deleted servers with a marker https://review.opendev.org/690429
22:06:56 mriedem ok well there is the reproduce and fix ^, will update once i have a bug id
#openstack-nova - 2019-10-23
00:39:18 openstackgerrit melanie witt proposed openstack/nova master: Fix policy doc for host_status and extended servers attribute https://review.opendev.org/689833
02:27:18 openstack Launchpad bug 1849409 in OpenStack Compute (nova) "openstack server list --deleted --limit -1 hangs" [Undecided,New]
02:27:18 KeithMnemonic mriedem here is the bug report https://bugs.launchpad.net/nova/+bug/1849409
02:29:26 KeithMnemonic let me know if you need anything changed/added to the bug report

Earlier   Later