On Jul 27, 2016, at 1:02 PM, Abhishek Shrivastava wrote:
>
> http://cloudbytestorages.github.io/blog/general/issues/openstack/2016/05/15/No-valid-host-was-found.html
My take from that is this section:
937472 2015-03-20 13:49:44.014 27294 TRACE nova.compute.manager [instance:
cddc4641-3f2d-42
Hi Turbo,
Follow the following link and then try, maybe it can help:
-
http://cloudbytestorages.github.io/blog/general/issues/openstack/2016/05/15/No-valid-host-was-found.html
On Wed, Jul 27, 2016 at 4:52 PM, Turbo Fredriksson wrote:
> On Jul 27, 2016, at 10:04 AM, Silvia Fichera wrote
On Jul 27, 2016, at 1:03 PM, Silvia Fichera wrote:
> I have created manually br-int, it was not created by devstack, should I
> also manually add br-ex?
Don't know. I've don't use devstack, I did it the "hard" way by installing
packages manually :D
But I guess so. From what (very!) little I know
enp0s3 and enp0s8 are the "new" names of eth0 and eth1, in fact ubuntu
16.04 uses this new names.
I have created manually br-int, it was not created by devstack, should I
also manually add br-ex?
As far as I remember, previous versions of devstack stop the script when it
is not possible to find br-
On Jul 27, 2016, at 10:04 AM, Silvia Fichera wrote:
> here my outputs:
I'm not sure if it's part/source of your problem, but you're missing
the 'br-ex' interface. That's the interface to your external/physical
network.
And from your output, I'm guessing that's either 'enp0s3' or 'enp0s8'.
But lo
here my outputs:
ifconfig
br-intLink encap:Ethernet IndirizzoHW 5e:5d:d9:fb:02:40
indirizzo inet6: fe80::5c5d:d9ff:fefb:240/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:8
[Please keep this on the list so others can help]
On Jul 25, 2016, at 10:21 PM, Silvia Fichera wrote:
> the result of ifconfig br-int is this:
> br-intLink encap:Ethernet IndirizzoHW 5e:5d:d9:fb:02:40
> indirizzo inet6: fe80::5c5d:d9ff:fefb:240/64 Scope:Link
> UP BROADCAST
Hi Silvia,
If you want to test neutron and ONOS connectivity then it can be done using
networking-onos.
For details you can refer
https://github.com/openstack/networking-onos/blob/master/devstack/README.rst
Thanks
Vikram
On Sun, Jul 24, 2016 at 3:45 PM, Turbo Fredriksson wrote:
> On Jul 24, 2
On Jul 24, 2016, at 11:03 AM, Silvia Fichera wrote:
> ^[[00mlibvirtError: Cannot get interface MTU on 'br-int': No such device
>
> But ovs-vsctl show tells me that the bridge in created.
Tripple check with:
ifconfig br-int
--
Med ett schysst järnrör slår man hela världen med häpnad
-
Hi Leslie,
I've checked the log in the compute nodes and the error is related to the
bridge:
^[[01;31m2016-07-20 23:30:44.470 TRACE nova.compute.manager
^[[01;35m[instance: dcf75116-fcaa-4f43-bac0-f93bc1fcaa9a]
^[[00mlibvirtError: Cannot get interface MTU on 'br-int': No such device
But ovs-vsctl
Hello,
to clarify, the nova-scheduler is just saying that the boot process
can't succeed because none of your registered computes fit, or there is
none at all (from scheduler pov).
First thing first:
- flavor specs ?
- do the computes register correctly their resources ? (check that in
nova-comp
Hi Brent,
I've installed openstack using devstack, so I just created the local.conf
file before stacking.
I noticed that the br-int is created only when I set the network devices in
ONOS (it is connected to the nodes) and not when the during the set up of
the nodes.
I can attach my local.conf if it
have you configured nova network to use 'br-int' ? it looks like br-int is
not plumbed or available on the host.
as a start, it looks like you need to ensure your host network needs to be
configured properly as per nova configuration.
On Thu, Jul 21, 2016 at 11:03 AM, Silvia Fichera
wrote:
>
I also found an error in the compute node in n-cpu.log related to libvirt:
I noticed that the error is similar but not the same:
ERROR nova.compute.manager
[^[[01;36mreq-f1fdf348-c333-4436-bcc0-d5cbd76428e6 ^[[00;36madmin
admin^[[01;31m] ^[[01;35m[instance: dcf75116-fcaa-4f43-bac0-f93bc1fcaa9a]
14 matches
Mail list logo
