Hi,
I faced the same issue few weeks ago while setting up a similar
environment. The issue then was that during the installation Fuel master
node (
https://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/install/install_set_up_fuel.html
),
I had incorrectly set up DHCP Gateway t
Hi Vidal,
Yes, eventually I found the problem. But that's weird, actually my def
route to fuel server. But, at some point default gw becomes mgmt
192.168.0.4 - I don't know why. So if I manually change def gw to fuel
master - everything works fine.
Anyone knows why fuel slaves during deployment g
>Is there an actual DNS service that will correctly return the IP address
>associated with these names or is it just a local host naming convention?
>
>- Mark
Hi Mark,
If you have the Neutron DNS extension enabled via extension_drivers = dns in
ml2_conf.ini. The DHCP agent's Dnsmasq will act a
Hello Guys
I'm facing a metadata issue just when using allowed address pairs and
static ip address.
Steps:
1. Create new instance
2. Allow the IP address on neutron port: neutron port-update
--allowed-address-pairs type=dict list=true
mac_address=,ip_address=
3. Inside the instance, configure th
You won't be able to use the metadata service using an IP that isn't in the
fixed_ips list for a port. The way the metadata service associates a
request with an instance is only based on that field.
So if you want an IP to work with metadata, you'll have to add it to the
fixed_ips field for the po
Has anyone had a problem with Mirantis Fuel giving a 'nailgund not
available' error when attempting to save any changes to a cloud
environment? I'm encountering this problem after a fresh install of
Mirantis Fuel 9.0 and then immediately upgrading to 9.2 (didn't even
login to the Fuel web inte
