Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2021-05-05
10:51:53 nightmare_unreal I see, thanks for the suggestion . I will first try with restart I think
10:51:53 nightmare_unreal I see, thanks for the suggestion . I will first try with restart I think
10:51:55 sean-k-mooney the compute node being down is a signal to the operator that the node is cannot be managed and you need to investigate
10:51:55 sean-k-mooney the compute node being down is a signal to the operator that the node is cannot be managed and you need to investigate
10:52:17 nightmare_unreal there are no VMs on that compute node
10:52:17 nightmare_unreal there are no VMs on that compute node
12:33:32 openstackgerrit Cedric Jeanneret proposed openstack/nova stable/train: [Train-Only] Update setup.cfg with new names https://review.opendev.org/c/openstack/nova/+/789822
12:33:32 openstackgerrit Cedric Jeanneret proposed openstack/nova stable/train: [Train-Only] Update setup.cfg with new names https://review.opendev.org/c/openstack/nova/+/789822
16:01:40 openstackgerrit Balazs Gibizer proposed openstack/nova master: Adapt to SQLAlchemy 1.4 https://review.opendev.org/c/openstack/nova/+/788471
16:01:40 openstackgerrit Balazs Gibizer proposed openstack/nova master: Adapt to SQLAlchemy 1.4 https://review.opendev.org/c/openstack/nova/+/788471
16:03:00 openstackgerrit Balazs Gibizer proposed openstack/nova master: DNM: test nova with SQLAlchemy 1.4 https://review.opendev.org/c/openstack/nova/+/789916
16:03:00 openstackgerrit Balazs Gibizer proposed openstack/nova master: DNM: test nova with SQLAlchemy 1.4 https://review.opendev.org/c/openstack/nova/+/789916
16:08:47 openstackgerrit Balazs Gibizer proposed openstack/placement master: Adapt to SQLAlchemy 1.4 https://review.opendev.org/c/openstack/placement/+/789921
16:09:47 openstackgerrit Balazs Gibizer proposed openstack/placement master: DNM: test with SQLAlchemy 1.4 https://review.opendev.org/c/openstack/placement/+/789922
#openstack-nova - 2021-05-06
00:53:13 openstackgerrit melanie witt proposed openstack/nova master: WIP Enable unified limits in the nova-next job https://review.opendev.org/c/openstack/nova/+/789963
02:34:25 openstackgerrit Brin Zhang proposed openstack/nova master: Replace os-simple-tenant-usage with os-simple-project-usage https://review.opendev.org/c/openstack/nova/+/768852
02:34:26 openstackgerrit Brin Zhang proposed openstack/nova master: Replace tenant_id with project_id in os-quota-sets path https://review.opendev.org/c/openstack/nova/+/768851
02:34:26 openstackgerrit Brin Zhang proposed openstack/nova master: Replace tenant_id with project_id in Limits API https://review.opendev.org/c/openstack/nova/+/768862
02:34:27 openstackgerrit Brin Zhang proposed openstack/nova master: Replace tenant* with project* in codes https://review.opendev.org/c/openstack/nova/+/769329
02:44:19 openstackgerrit David Vallee Delisle proposed openstack/os-vif master: Creating oslo.config.opts entry_points for plugins https://review.opendev.org/c/openstack/os-vif/+/789645
05:59:22 openstackgerrit Balazs Gibizer proposed openstack/placement master: Adapt to SQLAlchemy 1.4 https://review.opendev.org/c/openstack/placement/+/789921
05:59:24 openstackgerrit Balazs Gibizer proposed openstack/placement master: DNM: test with SQLAlchemy 1.4 https://review.opendev.org/c/openstack/placement/+/789922
07:36:57 openstackgerrit Balazs Gibizer proposed openstack/placement master: Adapt to SQLAlchemy 1.4 https://review.opendev.org/c/openstack/placement/+/789921
07:36:57 openstackgerrit Balazs Gibizer proposed openstack/placement master: Adapt to SQLAlchemy 1.4 https://review.opendev.org/c/openstack/placement/+/789921
07:37:23 openstackgerrit Balazs Gibizer proposed openstack/placement master: DNM: test with SQLAlchemy 1.4 https://review.opendev.org/c/openstack/placement/+/789922
07:37:23 openstackgerrit Balazs Gibizer proposed openstack/placement master: DNM: test with SQLAlchemy 1.4 https://review.opendev.org/c/openstack/placement/+/789922
07:43:46 openstackgerrit melanie witt proposed openstack/nova master: WIP Enable unified limits in the nova-next job https://review.opendev.org/c/openstack/nova/+/789963
07:48:16 openstackgerrit melanie witt proposed openstack/nova master: WIP Enable unified limits in the nova-next job https://review.opendev.org/c/openstack/nova/+/789963
07:54:08 openstackgerrit melanie witt proposed openstack/nova master: WIP Enable unified limits in the nova-next job https://review.opendev.org/c/openstack/nova/+/789963
09:01:31 openstackgerrit Takashi Natsume proposed openstack/python-novaclient master: Refactor constructing request body https://review.opendev.org/c/openstack/python-novaclient/+/790017
09:01:31 openstackgerrit Takashi Natsume proposed openstack/python-novaclient master: Refactor constructing request body https://review.opendev.org/c/openstack/python-novaclient/+/790017
10:08:06 sean-k-mooney gibi: do you remember this http://lists.openstack.org/pipermail/openstack-discuss/2019-November/011044.html
10:08:06 sean-k-mooney gibi: do you remember this http://lists.openstack.org/pipermail/openstack-discuss/2019-November/011044.html
10:08:28 gibi sean-k-mooney: yes
10:08:45 sean-k-mooney we might need to go impmente the api change and neutron code
10:08:45 sean-k-mooney we might need to go impmente the api change and neutron code
10:08:55 gibi I think we fixed it in neutron
10:08:55 gibi I think we fixed it in neutron
10:09:10 sean-k-mooney nope
10:09:17 sean-k-mooney its still using socket.gethostname()
10:09:17 sean-k-mooney its still using socket.gethostname()
10:09:29 gibi https://bugs.launchpad.net/neutron/+bug/1853840
10:09:31 gibi https://bugs.launchpad.net/neutron/+bug/1853840
10:09:31 openstack Launchpad bug 1853840 in neutron "Neutron fails to create bandwidth providers if CONF.host is set" [High,Fix released] - Assigned to Bence Romsics (bence-romsics)
10:09:31 openstack Launchpad bug 1853840 in neutron "Neutron fails to create bandwidth providers if CONF.host is set" [High,Fix released] - Assigned to Bence Romsics (bence-romsics)
10:09:41 gibi there is configuration to override it
10:09:41 gibi there is configuration to override it
10:09:46 gibi at least in neutron
10:09:46 gibi at least in neutron
10:09:51 sean-k-mooney there is
10:09:51 sean-k-mooney there is
10:10:01 sean-k-mooney but you should not need to do that by default
10:10:01 sean-k-mooney but you should not need to do that by default
10:11:05 sean-k-mooney https://bugzilla.redhat.com/show_bug.cgi?id=1900500 and https://bugzilla.redhat.com/show_bug.cgi?id=1952073
10:11:12 sean-k-mooney https://bugzilla.redhat.com/show_bug.cgi?id=1900500 and https://bugzilla.redhat.com/show_bug.cgi?id=1952073
10:11:12 openstack bugzilla.redhat.com bug 1900500 in openstack-neutron "Hostname in neutron agent's config don't match what is stored in placement by nova" [High,New] - Assigned to skaplons
10:11:12 openstack bugzilla.redhat.com bug 1900500 in openstack-neutron "Hostname in neutron agent's config don't match what is stored in placement by nova" [High,New] - Assigned to skaplons
10:11:13 openstack bugzilla.redhat.com bug 1952073 in openstack-nova "[OSP16.1] Failed to schedule VMs with minimum bandwidth - SR-IOV bandwidth aware scheduling" [High,Closed: duplicate] - Assigned to nova-maint
10:11:13 openstack bugzilla.redhat.com bug 1952073 in openstack-nova "[OSP16.1] Failed to schedule VMs with minimum bandwidth - SR-IOV bandwidth aware scheduling" [High,Closed: duplicate] - Assigned to nova-maint
10:11:14 sean-k-mooney are basically caused by this
10:11:14 sean-k-mooney are basically caused by this
10:11:21 sean-k-mooney they could use the config options
10:11:21 sean-k-mooney they could use the config options
10:11:35 gibi the fix was the config opiton
10:11:35 gibi the fix was the config opiton
10:11:38 gibi option
10:11:38 gibi option
10:11:51 gibi I don't get why they don't use it
10:11:51 gibi I don't get why they don't use it
10:11:56 gibi why they cannot use it
10:11:56 gibi why they cannot use it
10:12:16 sean-k-mooney they could but really neutron should use the hypervior api no?
10:12:16 sean-k-mooney they could but really neutron should use the hypervior api no?
10:13:18 sean-k-mooney gibi: they can totally workaround it using the config options
10:13:18 sean-k-mooney gibi: they can totally workaround it using the config options
10:13:19 gibi I assume this naming is static so it can be configured deployment time
10:13:19 gibi I assume this naming is static so it can be configured deployment time
10:13:38 sean-k-mooney it could but the UX of that approch sucks
10:13:38 sean-k-mooney it could but the UX of that approch sucks
10:14:05 sean-k-mooney it works but it would be nice if it just worked out of hte box
10:14:05 sean-k-mooney it works but it would be nice if it just worked out of hte box
10:14:46 gibi I don't get how this can be working without input from the deployer who know what are the matching host names
10:14:46 gibi I don't get how this can be working without input from the deployer who know what are the matching host names
10:15:29 sean-k-mooney by default socket.gethostname() will match the hostname returned by libvirt
10:15:29 sean-k-mooney by default socket.gethostname() will match the hostname returned by libvirt
10:15:45 gibi if the neutron agent sees a different hostname than the nova-compute then how can the nova hypervisor API help in that
10:15:45 gibi if the neutron agent sees a different hostname than the nova-compute then how can the nova hypervisor API help in that
10:16:46 sean-k-mooney gibi: we reqire the [DEFAULT]/host config option to be the same in both the nova and neutron config
10:16:46 sean-k-mooney gibi: we reqire the [DEFAULT]/host config option to be the same in both the nova and neutron config
10:16:59 sean-k-mooney so you can find the compute service assocatied with the host
10:16:59 sean-k-mooney so you can find the compute service assocatied with the host
10:17:14 sean-k-mooney then get its uuid
10:17:14 sean-k-mooney then get its uuid
10:17:35 gibi so the problematic case is when the hypervisor_hostname != hostname? But why that happen in case of libvirt?
10:17:35 gibi so the problematic case is when the hypervisor_hostname != hostname? But why that happen in case of libvirt?
10:17:58 sean-k-mooney because of https://github.com/libvirt/libvirt/blob/master/src/util/virutil.c#L454-L473
10:17:59 sean-k-mooney because of https://github.com/libvirt/libvirt/blob/master/src/util/virutil.c#L454-L473
10:18:52 sean-k-mooney if you have the fqdn as the canonical host name in /etc/hosts then libvirt will return an fqdn but socket.gethostname() will be the short hostname
10:18:52 sean-k-mooney if you have the fqdn as the canonical host name in /etc/hosts then libvirt will return an fqdn but socket.gethostname() will be the short hostname
10:19:44 gibi and don't we require CONF.host to be set to fqdn is enough in this case?

Earlier   Later