Earlier  
Posted Nick Remark
#openstack-nova - 2017-02-28
15:50:30 macsz sfinucan: yeah... and I hate my change with "rm" as well, but I am so fed up with doing it manually, and I could not see the use for having this file around either way...
15:50:36 dansmith spotz: it just didn't say anything because you didn't have --verbose
15:50:42 dansmith spotz: that "checking" means the mapping is there now
15:50:57 dansmith spotz: so you should have that host_mapping in the api db and maybe even be able to create instances
15:51:29 spotz dansmith: 2017-02-28 15:31:57 | NULL | 1 | 2 | compute |
15:51:54 dansmith spotz: I need more context, can you paste the full thing in the gist?
15:51:55 spotz dansmith: I wonder why it didn't work before though, I've run the command before
15:52:19 dansmith spotz: it needs to run after the host shows up in the cell db, so if you run it before you start the service it won't find it, of course
15:52:58 spotz dansmith: It was up but I'll make sure we make a note for that
15:54:36 spotz dansmith: no joy on the instance, checking logs to see if it's something new
15:55:25 spotz dansmith: still no valid hosts in the nova-conductor.log though I do think we made progress:)
15:56:02 dansmith spotz: well paste some logs
15:59:35 spotz dansmith: api, scheduler and conductor logs up
16:00:01 mriedem spotz: where?
16:00:10 spotz mriedem: https://gist.github.com/spotz/42b9d15f016073458742268735644578
16:01:00 spotz looks like placement-api not found from compute side, gonna peek at apache
16:01:16 dansmith spotz: would be a lot easier to read those as a new gist in fixed-width font, fwiw
16:01:24 dansmith damn docs people and their variable-width nonsense :P
16:01:44 spotz dansmith: Ha I'm not really a docs person:)
16:01:58 dansmith heh
16:02:05 mriedem is the nova-compute service reporting as up?
16:02:12 mriedem nova service-list
16:02:36 spotz mriedem: Yep reporting as up
16:02:39 mriedem 2017-02-28 09:58:07.852 1621 WARNING nova.scheduler.client.report [req-62fa3550-e8f7-4111-a297-6b24b20a7e1f - - - - -] The placement API endpoint not found. Placement is optional in Newton, but required in Ocata. Please enable the placement service before upgrading.
16:02:39 mriedem hmm, but yeah
16:02:59 mriedem is the placement endpoint in "openstack endpoint list"?
16:03:34 spotz mriedem: Brian noted an apache issue last night but he's doing rhel install. Public, internal and admin present
16:03:39 mriedem my guess is, the compute node isn't reporting into placement, so when the scheduler asks placement for somewhere to build an instance, it says it doesn't know about anything and we get NoValidHost
16:04:01 mriedem are the credentials correct in the [placement] section of nova.conf on the compute node?
16:04:41 spotz mriedem: Yep
16:04:48 spotz I can paste them if you want
16:07:20 mriedem did you configure the compute before or after placement was running?
16:07:28 mriedem i.e. do you need to restart the nova-compute service?
16:07:38 spotz I did just notice os_region was there twice, once as the default openstack and the one I set to RegionOne
16:08:06 spotz mriedem: I've restarted compute several times since config. New error Quota exceeded for instances: Requested 1, but already used 10 of 10 instances (HTTP 403) (Request-ID: req-6fedaf70-89b9-4bc4-a978-9ab04090767f)
16:08:46 mriedem so you've already got 10 dead instances in ERROR state right?
16:08:53 mriedem nova list would show 10 ERROR instances
16:09:00 mriedem delete those
16:09:34 spotz mriedem: I've been clearing them out
16:09:50 openstack Launchpad bug 1667667 in OpenStack Compute (nova) "Rebuilding instance ignores image's property hw_disk_bus" [Low,Confirmed]
16:09:50 akijak hi, I've found a bug in nova concerning rebuilding and 'hw_disk_bus' image property (https://bugs.launchpad.net/nova/+bug/1667667), I'm looking for someone who could give me some directions how to fix that :) can you help?
16:09:51 spotz yeah just 2 in error currently
16:11:19 efried Howdy folks, is there a Pike equivalent of https://etherpad.openstack.org/p/ocata-nova-priorities-tracking ? I.e. somewhere I can put up-to-date status & review priorities for the PowerVM driver "subteam"?
16:11:24 lyarwood akijak: hey, have you looked at https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L2679 and how we are passing image_meta around?
16:11:31 mriedem efried: i can create one
16:11:48 efried mriedem Thanks. And wipe the agenda for Thursday's meeting?
16:11:59 mriedem efried: it's only tuesday!
16:12:09 mriedem i get to the thurs meeting agenda by about wed night
16:12:19 efried Heh. Didn't know how much lead time we were supposed to have ;-)
16:12:23 mriedem efried: if you need to change something in the meeting agenda, you can do that now
16:12:29 efried rgr
16:14:27 spotz mriedem: 0 instances in Error, same result
16:15:15 dansmith mriedem: so I noticed some weird quota behavior when I was trying to get my multicell patch working
16:15:42 dansmith spotz: what is the [database]/connection set to in the nova conf that you're using for your apis?
16:15:49 dansmith and conductors
16:16:01 dansmith maybe we're reserving in cell0
16:17:00 mriedem i assume it's mysql+pymysql://nova:linuxacademy123@controller/nova
16:17:04 mriedem from https://gist.github.com/spotz/42b9d15f016073458742268735644578
16:18:16 spotz mriedem: Yep
16:18:16 dansmith actually, it has to be or other things won't work because ocata
16:19:04 spotz I know the basic config docs that are there minus placement-api and cells work as I also built a newton cluster and it's happy
16:19:24 spotz We're missing something, whether it's a step or something out of order
16:23:09 efried mriedem: I can start populating https://etherpad.openstack.org/p/pike-nova-priorities-tracking with the structure of its ocata predecessor if you like.
16:23:29 efried You have more important (or at least more urgent) things to do ;-)
16:24:03 mriedem efried: yes please
16:24:07 mriedem i'm doing 3 things at once
16:26:47 mriedem spotz: can you make a curl request to the placement endpoint using the same creds as are in the nova.conf on the compute?
16:27:04 spotz mriedem: Yep hang on
16:27:24 mriedem to /resource_providers would be enough
16:36:38 spotz mriedem: Bad Request but it could have been my curl
16:49:40 spotz mriedem: Yeah everytime I try to curl I'm getting the 400, I'm assuming you wanted me to just get like tokens?
16:50:48 mriedem spotz: just get the /resource_providers
16:50:51 mriedem you'll need a token
16:51:48 mdbooth mriedem: https://review.openstack.org/#/c/395709/
16:52:05 mriedem mdbooth: you don't need that
16:52:06 mdbooth Nothing unexpected in the logs, either
16:52:16 mdbooth mriedem: You mean the check experimental job?
16:52:16 mriedem we run the nfs job in the nova experimental queue
16:52:27 mdbooth Yeah, we run a bunch of other stuff in there too, though
16:52:30 mriedem "check experimental" runs the set of experimental jobs on your nova change
16:52:31 mriedem directly
16:52:44 mdbooth That one only runs the nfs job, so it's kinda nice
16:54:59 mdbooth mriedem: check experimental is a bit of a nose bleed. How much of it is intended to be red vs green?
16:55:14 mriedem i need to remove some of it
16:55:25 mriedem ala https://review.openstack.org/#/c/415033/
16:55:31 mriedem but time is an issue
16:56:15 mdbooth mriedem: The nfs job it ran passed
16:57:03 mdbooth gate-tempest-dsvm-full-devstack-plugin-nfs-nv', and have it run just that job?
16:57:03 mdbooth mriedem: Incidentally, would it be practical to do 'check
16:57:28 mriedem spotz: http://paste.openstack.org/show/600806/
16:57:36 mriedem ^ is from my devstack, with curl to placement
16:57:50 mriedem mdbooth: that's not a thing
16:57:51 mdbooth Or have a much wider array of 'interest areas' maybe, like 'check nfs', or 'check storage'
16:58:08 mdbooth mriedem: Right, but is there any reason it's not a thing?
16:58:33 mriedem someone would have to do it
16:58:47 mdbooth Sure. Would it be a useful thing?
16:58:52 mriedem idk
16:59:06 mdbooth For eg, in this case we've run gate-tempest-dsvm-lxc-ubuntu-xenial, and it failed, but I don't really care.
16:59:31 mriedem what would have been useful was if the hilton didn't f up charging me for last week so my internal expense reporting tool took over an hour to trick to make up for a separate .05 charge
16:59:51 mriedem recheck hilton

Earlier   Later