Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 02 2020 19:29
    apurvamayank closed #2
  • Nov 05 2017 03:09

    kordless on master

    WARNING" (compare)

  • Nov 05 2017 03:08

    kordless on master

    adding pike in (compare)

  • Mar 16 2016 06:49
    manishprabhu812 commented #35
  • Feb 19 2016 10:46
    vivek779 commented #39
  • Feb 19 2016 09:27
    vivek779 opened #39
  • Feb 18 2016 11:14
    PauraviW commented #38
  • Feb 18 2016 11:11
    vivek779 commented #38
  • Feb 18 2016 11:09
    vivek779 closed #38
  • Feb 18 2016 09:44
    vivek779 opened #38
  • Dec 18 2015 14:49
    PauraviW commented #37
  • Dec 15 2015 23:59
    sandy6768 opened #37
  • Jun 12 2015 03:50
    vince67 closed #11
  • Jan 05 2015 16:09
    msporny opened #36
  • Nov 28 2014 10:30
    atuljain opened #35
  • Nov 24 2014 21:43
    eugene-goldberg opened #34
  • Nov 02 2014 19:30
    timfallmk synchronize #33
  • Oct 30 2014 21:22
    timfallmk synchronize #33
  • Oct 29 2014 19:50
    timfallmk synchronize #33
  • Oct 29 2014 19:49
    timfallmk synchronize #33
radiofreekruzr
@radiofreekruzr
always nice when someone has already thought of it
Коrd Campbell
@kordless
no doubt!
huucuongngoclinh
@huucuongngoclinh
When I create an instances, I have an error: Error: Failed to launch instance "<name>": Please try again later [Error: No valid host was found. ]
Please help me to solve it...
THANKS.
radiofreekruzr
@radiofreekruzr
sounds like a problem with Nova
what do you find in the logs?
nordge1
@nordge1
Hey guys, I just submitted a new multi-node controller script. It all seems to work great with only 4 inputs from the user except one sed entry.
sed -e '
/^OPENSTACK_HOST =.$/s/^.$/OPENSTACK_HOST = "$ctrl_name"/
' -i /etc/openstack-dashboard/local_settings.py
instead of resulting in OPENSTACK_HOST = "controller" I get OPENSTACK_HOST =
any ideas?
Kurt Sussman
@neophiliac
Fresh install on a fresh 14.04.1 machine, and I get this error trying to start nova-api: Stderr: "Bad argument ACCEPT'\nError occurred at line: 98\nTryiptables-restore -h'
or 'iptables-restore --help' for more information.\n"
What else do you need to see? This is a clean run of the openstackgeek scripts. The only thing I did outside fo the scripts was to add a couple more images with glance (14.04.1 and CoreOS, but those should not affect the operation of nova).
Коrd Campbell
@kordless
neophaliac i’ve never seen that error before
more logging info would be useful
if i had to say, it’s due to some network misconfiguration
if nova has bad interface data, it’d be likely to throw errors when making bridges and setting iptables, for example
Kurt Sussman
@neophiliac
It was a bug back in Havana, but I diffed the code and that bug has been fixed (obviously).
Here's the whole traceback:
2014-09-24 21:52:01.959 28940 CRITICAL nova [-] ProcessExecutionError: Unexpected err
or while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf iptables-restore -c
Exit code: 2
Stdout: ''
Stderr: "Bad argument ACCEPT'\nError occurred at line: 104\nTryiptables-restore -h
' or 'iptables-restore --help' for more information.\n"
2014-09-24 21:52:01.959 28940 TRACE nova Traceback (most recent call last):
2014-09-24 21:52:01.959 28940 TRACE nova File "/usr/bin/nova-api", line 10, in <mod ule>
2014-09-24 21:52:01.959 28940 TRACE nova sys.exit(main())
2014-09-24 21:52:01.959 28940 TRACE nova File "/usr/lib/python2.7/dist-packages/nov
a/cmd/api.py", line 53, in main
2014-09-24 21:52:01.959 28940 TRACE nova server = service.WSGIService(api, use_ss
l=should_use_ssl)
2014-09-24 21:52:01.959 28940 TRACE nova File "/usr/lib/python2.7/dist-packages/nov
a/service.py", line 330, in init
2014-09-24 21:52:01.959 28940 TRACE nova self.manager = self._get_manager()
2014-09-24 21:52:01.959 28940 TRACE nova File "/usr/lib/python2.7/dist-packages/nov
a/service.py", line 374, in _get_manager
2014-09-24 21:52:01.959 28940 TRACE nova return manager_class()
2014-09-24 21:52:01.959 28940 TRACE nova File "/usr/lib/python2.7/dist-packages/nov
a/api/manager.py", line 30, in init
2014-09-24 21:52:01.959 28940 TRACE nova self.network_driver.metadata_accept()
2014-09-24 21:52:01.959 28940 TRACE nova File "/usr/lib/python2.7/dist-packages/nov
a/network/linux_net.py", line 666, in metadata_accept
2014-09-24 21:52:01.959 28940 TRACE nova iptables_manager.apply()
2014-09-24 21:52:01.959 28940 TRACE nova File "/usr/lib/python2.7/dist-packages/nov
a/network/linux_net.py", line 434, in apply
2014-09-24 21:52:01.959 28940 TRACE nova self._apply()
2014-09-24 21:52:01.959 28940 TRACE nova File "/usr/lib/python2.7/dist-packages/nov
a/openstack/common/lockutils.py", line 249, in inner
2014-09-24 21:52:01.959 28940 TRACE nova return f(args, **kwargs)
2014-09-24 21:52:01.959 28940 TRACE nova File "/usr/lib/python2.7/dist-packages/nov
a/network/linux_net.py", line 463, in _apply
2014-09-24 21:52:01.959 28940 TRACE nova attempts=5)
2014-09-24 21:52:01.959 28940 TRACE nova File "/usr/lib/python2.7/dist-packages/nov
a/network/linux_net.py", line 1211, in _execute
2014-09-24 21:52:01.959 28940 TRACE nova return utils.execute(
cmd, kwargs)
2014-09-24 21:52:01.959 28940 TRACE nova File "/usr/lib/python2.7/dist-packages/nov
a/utils.py", line 165, in execute
2014-09-24 21:52:01.959 28940 TRACE nova return processutils.execute(*cmd,
kwar
gs)
2014-09-24 21:52:01.959 28940 TRACE nova File "/usr/lib/python2.7/dist-packages/nov
a/openstack/common/processutils.py", line 193, in execute
2014-09-24 21:52:01.959 28940 TRACE nova cmd=' '.join(cmd))
I got this last time I used your scripts, after it worked correctly once. I re-ran the scripts without wiping the machine, and this was the result. I dug through the code and put in some debug output, but didn't figure it out.
Коrd Campbell
@kordless
the most likely explaination is a bad NIC name or malformed network CIDR
Kurt Sussman
@neophiliac
I added 'metadata_host=127.0.0.1' line in the nova.conf and now it works.
Коrd Campbell
@kordless
ok
Kurt Sussman
@neophiliac
There was no metadata_host in any file under /etc/nova
Коrd Campbell
@kordless
so is this icehouse or havana?
Kurt Sussman
@neophiliac
icehouse
Коrd Campbell
@kordless
are you doing a different type of network connection than in the guide?
Kurt Sussman
@neophiliac
I'm not sure what you mean. There are two NICs, em1 and em2. em1 is primary and has no special configuration. Just address, network, gateway, etc. The IP was correctly detected in the install.
Коrd Campbell
@kordless
well, specifically, I’m questioning the conclusion that it was the metadata_host entry
that error you show is an iptable syntax error
Kurt Sussman
@neophiliac
All I can tell you is that I got that error and traceback every time I started nova-api, until I added the metadata_host config. Nothing else changed. I have my /etc/directory in a git repo using etckeeper, and I can show you the log.
Коrd Campbell
@kordless
while the metadata host is important for booting things, it’s (probably) not used much for configuring the network. the iptable entry may refer to the host in question (by default it’s 169.254.169.254) but I can’t imagine why it would break on that
right, i understand it is working now, but it could still be something else
given this is the first i’ve heard of it, i’m thinking it’s something specific to your particular network setup
Kurt Sussman
@neophiliac
It's certainly possible.
Коrd Campbell
@kordless
which may or may not be related to the metadata_host entry
that’s the list of defaults and settings related to the metadata service
let me look at the nova code real quick
Kurt Sussman
@neophiliac
Maybe 'eth#' is hardcoded somewhere? I'm not sure why mine switches to 'em#'; Ubuntu does that on boot and I haven't chased it down yet. Other than that, it's pretty vanilla.
Ah, the iptable syntax error comes because the config setting is concatenated with the 'ACCEPT' and because the config setting is missing, it concatenates the error message with the 'ACCEPT' string. That is in fact an invalid iptables command line.
Коrd Campbell
@kordless
likely location of the issue - this was changed 8 days ago
and would explain why setting it to 127 works
Kurt Sussman
@neophiliac
Interesting. Good find.
Коrd Campbell
@kordless
you as well
Kurt Sussman
@neophiliac
BTW, thanks for the scripts; they do make it really easy to get OpenStack up and running.
Коrd Campbell
@kordless
i think you are right about the concat issue
what are you using openstack for?
Kurt Sussman
@neophiliac
Currently just exploring. I want to get my own services off Proxmox (OpenVZ) at some point though, and I want to have a standar API for things like orchestration and monitoring.
Коrd Campbell
@kordless
i’ll run an install later today and see what happends
not 100% certain that code is at fault - the default gets set to my_ip at the top
so, if metadata_host!=127.0.0.1 you should have a valid string in there
if you are so inclined, you could stick a debug logging statement in there and see what it’s trying to run