Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2021-05-18
15:59:20 sean-k-mooney you did "openstack server migrate d6b5385a-dec7-4a31-b444-2ae05761915e --wait --live h9"
15:59:30 gibi admin0: you hypervisor list has 'h7.' but the error message has 'h7'
15:59:30 gibi admin0: you hypervisor list has 'h7.' but the error message has 'h7'
15:59:37 gibi there is a difference in the host name
15:59:37 gibi there is a difference in the host name
15:59:50 gibi sean-k-mooney: you won
15:59:50 gibi sean-k-mooney: you won
16:00:07 admin0 how do i fix this ? do i setup all hostnames to fqdn and retry ?
16:00:07 admin0 how do i fix this ? do i setup all hostnames to fqdn and retry ?
16:00:09 sean-k-mooney im wonderign what could ause this though
16:00:09 sean-k-mooney im wonderign what could ause this though
16:00:12 openstackgerrit norman shen proposed openstack/nova master: Saving security group to info_cache https://review.opendev.org/c/openstack/nova/+/786348
16:00:31 sean-k-mooney admin0: well on a production setup we do not support changing the host name
16:00:31 sean-k-mooney admin0: well on a production setup we do not support changing the host name
16:00:41 sean-k-mooney admin0: what is the instance.host set to
16:00:41 sean-k-mooney admin0: what is the instance.host set to
16:01:19 admin0 | OS-EXT-SRV-ATTR:host | h7 || OS-EXT-SRV-ATTR:hypervisor_hostname | h7.openstack.local
16:01:20 admin0 | OS-EXT-SRV-ATTR:host | h7 || OS-EXT-SRV-ATTR:hypervisor_hostname | h7.openstack.local
16:01:25 sean-k-mooney h7. is a rather unusal host name i would have expecte h7 of h7.some.domain
16:01:25 sean-k-mooney h7. is a rather unusal host name i would have expecte h7 of h7.some.domain
16:02:06 sean-k-mooney OS-EXT-SRV-ATTR:hypervisor_hostname | h7.openstack.local
16:02:06 sean-k-mooney OS-EXT-SRV-ATTR:hypervisor_hostname | h7.openstack.local
16:02:20 sean-k-mooney that shoudl really match what is in openstack hypervisor list
16:02:20 sean-k-mooney that shoudl really match what is in openstack hypervisor list
16:02:55 admin0 which in my case has just h7.
16:02:55 admin0 which in my case has just h7.
16:02:57 admin0 h9.
16:02:57 admin0 h9.
16:03:02 sean-k-mooney admin0: have you modified the content of /etc/hostname or /etc/hosts on this compute
16:03:02 sean-k-mooney admin0: have you modified the content of /etc/hostname or /etc/hosts on this compute
16:03:26 admin0 not that i can recall
16:03:26 admin0 not that i can recall
16:03:31 admin0 is it something in nova.conf that i can check
16:03:31 admin0 is it something in nova.conf that i can check
16:03:53 sean-k-mooney we should never end up with h7. if the instance has h7.openstack.local as the hypervior hostname
16:03:53 sean-k-mooney we should never end up with h7. if the instance has h7.openstack.local as the hypervior hostname
16:04:19 admin0 root@h7:~# hostname => h7
16:04:19 admin0 root@h7:~# hostname => h7
16:04:25 gibi stephenfin: I did a stab at your db clenanup series I left a -1 on https://review.opendev.org/c/openstack/nova/+/786292 with a question, the rest soo far looks good
16:04:25 gibi stephenfin: I did a stab at your db clenanup series I left a -1 on https://review.opendev.org/c/openstack/nova/+/786292 with a question, the rest soo far looks good
16:04:47 gibi * gibi disappears 
16:04:51 sean-k-mooney admin0: what does "virsh hostname" return
16:04:51 sean-k-mooney admin0: what does "virsh hostname" return
16:05:08 admin0 hmm.. it returns h7.
16:05:08 admin0 hmm.. it returns h7.
16:05:13 admin0 how :D ?
16:05:13 admin0 how :D ?
16:05:24 admin0 i never used . for hostnames
16:05:25 admin0 i never used . for hostnames
16:05:34 admin0 its always h1 h2 h3 c1 c2 c3 etc
16:05:34 admin0 its always h1 h2 h3 c1 c2 c3 etc
16:05:35 sean-k-mooney can you cat /etc/hostname and /etc/hosts and put it in a past bin
16:05:35 sean-k-mooney can you cat /etc/hostname and /etc/hosts and put it in a past bin
16:06:02 sean-k-mooney i think you have sometihgn wrong in your /etc/hosts file or you did somehting in dns
16:06:02 sean-k-mooney i think you have sometihgn wrong in your /etc/hosts file or you did somehting in dns
16:06:53 admin0 the /etc/hosts has one line that says 127.0.1.1 h7. h7
16:06:53 admin0 the /etc/hosts has one line that says 127.0.1.1 h7. h7
16:07:01 admin0 so that is where its coming from..
16:07:01 admin0 so that is where its coming from..
16:07:02 sean-k-mooney ya thats wrong
16:07:02 sean-k-mooney ya thats wrong
16:07:08 sean-k-mooney chnage the order
16:07:08 sean-k-mooney chnage the order
16:07:15 sean-k-mooney well
16:07:16 sean-k-mooney well
16:07:20 admin0 i will remove the h7. altogether and restart nova-compute
16:07:20 admin0 i will remove the h7. altogether and restart nova-compute
16:07:30 sean-k-mooney that shoudl fix it
16:07:31 sean-k-mooney that shoudl fix it
16:07:47 admin0 thank you
16:07:47 admin0 thank you
16:08:04 sean-k-mooney the format of /etc/hosts is <ip> <canonical host name> <any number of alias>
16:08:04 sean-k-mooney the format of /etc/hosts is <ip> <canonical host name> <any number of alias>
16:08:50 sean-k-mooney its technially ok to use the FQDN in cannonical host name but that will change the hypervior_hostneam to be the FQDN
16:08:50 sean-k-mooney its technially ok to use the FQDN in cannonical host name but that will change the hypervior_hostneam to be the FQDN
16:09:05 sean-k-mooney which is not a change you can do on an existing cloud without breaking a lot of things
16:09:05 sean-k-mooney which is not a change you can do on an existing cloud without breaking a lot of things
16:10:02 sean-k-mooney admin0: i would guess that your automation tooling tried to set canonical hostname to the fqdn but coudl not fiure out the domain but it still added the .
16:10:02 sean-k-mooney admin0: i would guess that your automation tooling tried to set canonical hostname to the fqdn but coudl not fiure out the domain but it still added the .
16:10:12 admin0 yeah
16:28:11 admin0 hostname => h7 ; hostname -f => h7 ; virsh hostname => h7 ; openstack hypervisor list => h7 ; migrate command still says => Compute host h7 could not be found.
16:28:11 admin0 hostname => h7 ; hostname -f => h7 ; virsh hostname => h7 ; openstack hypervisor list => h7 ; migrate command still says => Compute host h7 could not be found.
16:40:23 admin0 sean-k-mooney, is it possible to fix associations directly from the database ?
16:40:23 admin0 sean-k-mooney, is it possible to fix associations directly from the database ?
16:40:43 admin0 for example rename h7 -> say h77 for example, and then in nova instances update the instances as h77 as their new host
16:40:43 admin0 for example rename h7 -> say h77 for example, and then in nova instances update the instances as h77 as their new host
16:50:25 sean-k-mooney admin0: its possible but a really bad idea
16:50:25 sean-k-mooney admin0: its possible but a really bad idea
16:51:04 sean-k-mooney admin0: you need to fix it in multiple dbs nova api db , nova cell db, neutron, cinder and posibley others
16:51:04 sean-k-mooney admin0: you need to fix it in multiple dbs nova api db , nova cell db, neutron, cinder and posibley others
17:00:43 bauzas have someone tested https://docs.openstack.org/api-ref/placement/?expanded=list-resource-providers-detail#list-resource-providers with multiple 'uuid' query strings ?
17:00:43 bauzas have someone tested https://docs.openstack.org/api-ref/placement/?expanded=list-resource-providers-detail#list-resource-providers with multiple 'uuid' query strings ?
17:01:12 bauzas like /resource_providers?uuid=<uuid1>&uuid=<uuid2> ?
17:01:12 bauzas like /resource_providers?uuid=<uuid1>&uuid=<uuid2> ?
17:01:25 bauzas sean-k-mooney: do you know whether it works ? ^
17:01:25 bauzas sean-k-mooney: do you know whether it works ? ^
17:02:00 bauzas I'd like to get a list of RPs by their UUIDs
17:02:00 bauzas I'd like to get a list of RPs by their UUIDs
17:02:37 bauzas of course, I can see we don't support uuid=<uuid1>&<uuid2>
17:02:38 bauzas of course, I can see we don't support uuid=<uuid1>&<uuid2>

Earlier   Later