Hello, sorry for late in my answer
the following is the content of my ocata repo file:
[centos-openstack-ocata]
name=CentOS-7 - OpenStack ocata
baseurl=http://mirror.centos.org/centos/7/cloud/$basearch/openstack-ocata/
gpgcheck=1
enabled=1
On Wed, Oct 17, 2018 at 4:46 PM Ignazio Cassano
wrote:
> Hello, here the select you suggested:
>
> MariaDB [nova]> select * from shadow_services;
> Empty set (0,00 sec)
>
> MariaDB [nova]> select * from shadow_compute_nodes;
> Empty set (0,00 sec)
>
> As far as the upgrade tooling is concerned,
Hello, here the select you suggested:
MariaDB [nova]> select * from shadow_services;
Empty set (0,00 sec)
MariaDB [nova]> select * from shadow_compute_nodes;
Empty set (0,00 sec)
As far as the upgrade tooling is concerned, we are using only yum update on
old compute nodes to have same packages
Hello, I am sure we are not using nova-compute with duplicate names.
As I told previously we tried on 3 differents openstack installations and
we faced the same issue.
Procedure used
We have an openstack with 3 compute nodes : podto1-kvm01, podto1-kvm02,
podto1-kvm03
1) install a new compute node
On 10/17/2018 9:13 AM, Ignazio Cassano wrote:
Hello Sylvain, here the output of some selects:
MariaDB [nova]> select host,hypervisor_hostname from compute_nodes;
+--+-+
| host | hypervisor_hostname |
+--+-+
| podto1-kvm01 |
On 10/17/2018 01:41 AM, Ignazio Cassano wrote:
Hello Jay, when I add a New compute node I run nova-manage cell_v2
discover host .
IS it possible this command update the old host uuid in resource table?
No, not unless you already had a nova-compute installed on a host with
the exact same
Hello Sylvain, here the output of some selects:
MariaDB [nova]> select host,hypervisor_hostname from compute_nodes;
+--+-+
| host | hypervisor_hostname |
+--+-+
| podto1-kvm01 | podto1-kvm01|
| podto1-kvm02 |
On Wed, Oct 17, 2018 at 12:56 AM Jay Pipes wrote:
> On 10/16/2018 10:11 AM, Sylvain Bauza wrote:
> > On Tue, Oct 16, 2018 at 3:28 PM Ignazio Cassano
> > mailto:ignaziocass...@gmail.com>> wrote:
> >
> > Hi everybody,
> > when on my ocata installation based on centos7 I update (only update
On 10/16/2018 10:11 AM, Sylvain Bauza wrote:
On Tue, Oct 16, 2018 at 3:28 PM Ignazio Cassano
mailto:ignaziocass...@gmail.com>> wrote:
Hi everybody,
when on my ocata installation based on centos7 I update (only update
not changing openstack version) some kvm compute nodes, I
hello Iain, it is not possible.
I checked hostnames several times.
No changes .
I tried same procedure on 3 different ocata installations because we have
3 distinct openstack . Same results.
Regards
Ignazio
Il Mar 16 Ott 2018 17:20 iain MacDonnell ha
scritto:
>
> Is it possible that the
Is it possible that the hostnames of the nodes changed when you updated
them? e.g. maybe they were using fully-qualified names before and
changed to short-form, or vice versa ?
~iain
On 10/16/2018 07:22 AM, Ignazio Cassano wrote:
Hi Sylvain,
I mean launching "yum update" on compute
Hi Sylvain,
I mean launching "yum update" on compute nodes.
Now I am going to describe what happened.
We had an environment made up of 3 kvm nodes.
We added two new compute nodes.
Since the addition has been made after 3 or 4 months after the first
openstack installation, the 2 new compute nodes
On Tue, Oct 16, 2018 at 3:28 PM Ignazio Cassano
wrote:
> Hi everybody,
> when on my ocata installation based on centos7 I update (only update not
> changing openstack version) some kvm compute nodes, I diescovered uuid in
> resource_providers nova_api db table are different from uuid in
>
Hi everybody,
when on my ocata installation based on centos7 I update (only update not
changing openstack version) some kvm compute nodes, I diescovered uuid in
resource_providers nova_api db table are different from uuid in
compute_nodes nova db table.
This causes several errors in nova-compute
14 matches
Mail list logo
