Earlier  
Posted Nick Remark
#openstack-nova - 2020-01-06
16:05:21 efried gibi: Perfect, thanks.
16:06:29 gibi efried: done.
17:48:54 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Remove final references to nova-network https://review.opendev.org/696516
17:48:54 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Remove 'MetadataManager' https://review.opendev.org/696748
17:48:55 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Add TODOs to remove security group-related objects https://review.opendev.org/696517
17:48:55 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Remove dependency on nova-net from fake cache https://review.opendev.org/696749
17:48:56 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Kill it https://review.opendev.org/696518
17:48:56 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Remove unused exceptions https://review.opendev.org/697149
17:48:57 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Remove unnecessary 'neutronv2' prefixes https://review.opendev.org/696776
17:48:57 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Rename 'nova.network.neutronv2' -> 'nova.network' https://review.opendev.org/696745
17:48:58 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Make the security group API a module https://review.opendev.org/696746
17:48:58 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Remove remaining nova-network quotas https://review.opendev.org/697152
17:48:59 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Remove use of legacy 'FloatingIP' object https://review.opendev.org/697153
17:48:59 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Remove use of legacy 'Network' object https://review.opendev.org/697154
17:49:00 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Remove use of legacy 'SecurityGroup' object https://review.opendev.org/697155
17:49:00 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-net: Remove unused nova-network objects https://review.opendev.org/697156
18:04:31 born2bake https://bugs.launchpad.net/kolla-ansible/+bug/1858091
18:04:31 openstack Launchpad bug 1858091 in OpenStack Compute (nova) "Nova compute api v2.1/servers in train" [Undecided,New]
19:06:37 openstackgerrit Merged openstack/os-vif master: Drop python2 support and testing https://review.opendev.org/691364
19:50:32 openstackgerrit Merged openstack/nova master: [Trivial]Fix typo instnace https://review.opendev.org/700972
19:58:37 openstackgerrit Merged openstack/nova master: Fix duplicated words issue like "during during boot time" https://review.opendev.org/701172
20:13:53 openstackgerrit Merged openstack/nova master: Create instance action when burying in cell0 https://review.opendev.org/694165
20:14:02 openstackgerrit Merged openstack/nova master: Add api for instance action details https://review.opendev.org/700123
21:06:07 openstackgerrit Matt Riedemann proposed openstack/nova stable/train: Create instance action when burying in cell0 https://review.opendev.org/701279
21:39:09 eandersson Are there any tools I can use to create fake nova notifications? I want to test designate features without having to create real VMs.
21:39:58 eandersson At home I did something crazy like this to test http://paste.openstack.org/show/787877/
21:47:09 sean-k-mooney not that i know of off hand
21:48:59 sean-k-mooney we have test fixtures for the notifcation in tree for functional and unit test but i dont think we have any standalone tools like gabbi for integration testing
22:07:38 born2bake melwitt stephenfin Hi
22:07:46 born2bake https://bugs.launchpad.net/kolla-ansible/+bug/1858091/comments/7 I found source code of that driver
22:07:46 openstack Launchpad bug 1858091 in kolla-ansible "Nova compute api v2.1/servers in train" [Undecided,New]
22:08:08 born2bake I am not sure but maybe you can help with it or give a suggestion where to look
22:24:20 sean-k-mooney born2bake: looking at the bug quickly i dont think this is a nova error. but rahter it seam like the way the service endpoint was registerd has changed in kolla between train and stien
22:27:10 sean-k-mooney openstack apis are quite flexible in that regard. in my home kolla deployment nova is at http://192.168.1.254:8774/v2.1
22:28:06 sean-k-mooney however the apache configi and be altered to require the present of compute or to expose it as a subdomain
22:36:08 sean-k-mooney born2bake: can you add the output of openstack endpoint list to the bug report
22:36:37 born2bake http://prntscr.com/qk6gbn
22:36:57 sean-k-mooney openstack:8774/compute/v2.1/servers would be a non default url. atleast it is now the location that kolla-ansible would deploy the endpoint
22:37:28 sean-k-mooney yes that is the same as my deployment more or less
22:38:18 born2bake yeah I know...so it's been changed by kolla-ansible or by nova standards?
22:38:30 sean-k-mooney neither
22:38:42 sean-k-mooney kolla still used http://10.0.225.254:8774/v2.1/os-keypairs
22:38:55 sean-k-mooney or rather http://10.0.225.254:8774/v2.1
22:39:10 born2bake yup
22:39:14 sean-k-mooney and nova does not require or use compute in the url at least not by default
22:39:31 sean-k-mooney i ckeckt the kolla ansible source and i dont see a change there
22:39:53 born2bake so why its not default then
22:40:11 sean-k-mooney there have been a few chagnes for ipv6 but the they all kept backward compatabity
22:41:50 sean-k-mooney the url format is defiend here in kolla ansible https://github.com/openstack/kolla-ansible/blob/stable/train/ansible/roles/nova/defaults/main.yml#L137-L139
22:42:54 sean-k-mooney could you have modifed nova_api_port to be 8774/compute ?
22:43:05 sean-k-mooney or could someone have?
22:43:10 born2bake no I didnt
22:43:20 born2bake if you check answers in bug report
22:44:41 born2bake https://docs.openstack.org/api-ref/compute/
22:44:55 born2bake Service URLs - For instance, if the service url is http://mycompute.pvt/compute/v2.1 then the full API call for /servers is http://mycompute.pvt/compute/v2.1/servers.
22:45:46 sean-k-mooney yes so in your case the comptue service api is registered in keystone as http://10.0.225.254:8774/v2.1
22:45:58 sean-k-mooney so the full url would be http://10.0.225.254:8774/v2.1/servers
22:46:39 sean-k-mooney which appers to be the endpoint rancher is trying to reach
22:49:13 sean-k-mooney there is no requirement to have compute in the url and we did not change that in train
22:49:54 born2bake yes, rancher is trying to reach http://10.0.225.254:8774/v2.1/servers
22:50:01 born2bake when I am trying to open it using curl
22:50:04 born2bake 404 error
22:50:16 born2bake if I am trying to curl http://10.0.225.254:8774/compute/v2.1/servers
22:50:18 born2bake it works
22:51:01 sean-k-mooney it sound like this is an issue with the haproxy config or apache config
22:51:21 born2bake so then it is related to kolla-ansible then? O_o
22:55:04 sean-k-mooney i belive so
22:56:08 sean-k-mooney given you can apperatly invoke the api fine at the other location then this is a configuration issue rather then and issue with the service
22:59:04 born2bake in bug report they mentioned that its related to nova
22:59:14 born2bake nova said that its related to rancher :)
23:00:50 sean-k-mooney nova does not know the api endpoint its api is exposed at so its not a nova issue
23:01:06 sean-k-mooney that is stored in keystone with is configured by the installation tool
23:01:52 sean-k-mooney my haproxy config for my kolla-ansible train deploy ment looks liek this http://paste.openstack.org/show/788097/
23:01:56 sean-k-mooney is yours the same
23:04:16 born2bake yup same
23:06:08 sean-k-mooney ok well its late for me so im going to call it a night. if i think of anything else ill update the bug
23:06:19 sean-k-mooney does the openstack cli work by the way
23:06:31 sean-k-mooney e.g. if you just do an openstack server list or soemthing?
23:07:10 sean-k-mooney or "openstack keypair list"
23:08:38 born2bake everything works smoothly
23:08:50 sean-k-mooney if it does you can add --debug e.g. "openstack --debug keypair list" and it will print out the raw data and effectivly thec curl command
23:08:58 sean-k-mooney ok can you try with debug
23:09:16 sean-k-mooney i just need the REQ: line
23:09:32 sean-k-mooney it will look like this "REQ: curl -g -i -X GET http://192.168.1.254:8774/v2.1/os-keypairs -H "Accept: application/json" -H "User-Agent: python-novaclient" -H "X-Auth-Token: {SHA256}ac329731a91c5c72b3a7ca81c0579cbe5ecc8d20028518e9d94735efe05121ba" -H "X-OpenStack-Nova-API-Version: 2.1""
23:09:47 sean-k-mooney thats not really the auth token by the way just a hash of it
23:10:30 born2bake REQ: curl -g -i -X GET http://10.0.225.254:8774/v2.1/os-keypairs -H "Accept: application/json" -H "User-Agent: python-novaclient" -H "X-Auth-Token: {SHA256}152dcee94db8af1a3f509137abb21fec6d7bb484433729f9b192989274bb6d95" -H "X-OpenStack-Nova-API-Version: 2.1"
23:10:31 born2bake Starting new HTTP connection (1): 10.0.225.254:8774
23:10:58 sean-k-mooney ya so the client is using the same url
23:11:44 sean-k-mooney so i would guess the 403 is likely because the keystone auth token expired or did not have the correct permissions
23:11:55 sean-k-mooney when rancher invoked the endpoint
23:12:25 born2bake it worked fine with stein
23:12:40 born2bake i installed train 1.5 weeks ago
23:14:15 sean-k-mooney yes but given the openstack client work fine and what you have already told me it looks like the openstack in stall is working correctly
23:15:49 sean-k-mooney if it was a nova issue i would expect it to also break the openstack client which seams to be working fine
#openstack-nova - 2020-01-07
00:38:15 openstackgerrit Dustin Cowles proposed openstack/nova master: WIP: Provider Config File: Enable loading and merging of provider configs https://review.opendev.org/693460
00:43:44 openstackgerrit Victor Morales proposed openstack/nova master: Update Testing NUMA documentation https://review.opendev.org/701301
00:51:30 openstackgerrit Merged openstack/nova master: docs: Add note about an image signature validation limitation when using rbd https://review.opendev.org/700152
01:30:25 openstackgerrit Merged openstack/nova master: [api-ref] Fix the incorrect link https://review.opendev.org/700362
01:30:30 openstackgerrit Merged openstack/nova master: Fix an invalid assertIsNotNone statement https://review.opendev.org/700603
05:29:26 openstackgerrit Merged openstack/nova master: Report trait 'COMPUTE_IMAGE_TYPE_PLOOP' https://review.opendev.org/698132

Earlier   Later