Cannot create stack user: "Could not determine host ip address"

Bug #1644145 reported by Markus Zoeller (markus_z)
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
devstack
Invalid
Undecided
Unassigned

Bug Description

Description
===========
The minimal settings of the `local.conf` of Devstack as described in
http://docs.openstack.org/developer/devstack/ are *not* enough to create
a stack user which is necessary/recommended for the whole stack process.

Steps to reproduce
==================

    $ git clone https://github.com/openstack-dev/devstack/
    $ cd devstack
    $ git checkout 4bfbc291eefd92d8b7885f36275b7ff541e067ab
    $ tools/create-stack-user.sh

Expected result
===============
The stack user should be created and this command should be possible:

    $ sudo su - stack

Actual result
=============
The stack user *doesn't* get created but an error message is shown:

    [Call Trace]
    tools/create-stack-user.sh:32:source
    /opt/stack/devstack/stackrc:780:die
    [ERROR] /opt/stack/devstack/stackrc:780 Could not determine host ip
    address. See local.conf for suggestions on setting HOST_IP.

Environment
===========
1. I use this vagrant setup to create my VM:
   https://github.com/markuszoeller/openstack/tree/master/scripts/vagrant/aio-U1404-VB

2. The devstack commit which introduced this is 4bfbc291eefd92
   If I use that commit's parent 7976f31 then the expected result is happening.

Logs & Configs
==============
local.conf: https://github.com/markuszoeller/openstack/blob/master/scripts/vagrant/aio-U1404-VB/files/local.conf.aio

Revision history for this message
venkatamahesh (venkatamaheshkotha) wrote :

Without mentioning HOST_IP the same error is coming

summary: - Cannot create stack user: "Could not determine host ip addres"
+ Cannot create stack user: "Could not determine host ip address"
Changed in devstack:
status: New → Confirmed
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote :

> Without mentioning HOST_IP the same error is coming

Please note that the `local.conf` I used *has* HOST_IP set. See https://github.com/markuszoeller/openstack/blob/master/scripts/vagrant/aio-U1404-VB/files/local.conf.aio

Revision history for this message
Michael Lekkas (mikelekkas) wrote :

Potentially related expired bug is https://bugs.launchpad.net/devstack/+bug/1013481

What I have done as a temporary solution is to modify stackrc and set HOST_IP=${HOST_IP:-10.0.2.15}

Changed in devstack:
assignee: nobody → zhangdetong (zhangdetong)
assignee: zhangdetong (zhangdetong) → nobody
Revision history for this message
Andreas Scheuring (andreas-scheuring) wrote :

Root cause seems to be [1]

The issue is that the IPs that vagrant assigns by default are in the newly introduced private subnet range 10.0.0.0/22. Due to that devstack filters them out [2] and ends with no valid IP

You should be able to workaround that by either
* Configuring your Vagrantfile to use a different subnet range
config.vm.provider "virtualbox" do |vb|
   vb.customize ['modifyvm', :id, '--natnet1', '192.168.222.0/24']
end

or Configuring your local.conf to use a different subnet for FIXED_RANGE
FIXED_RANGE=10.0.0.0/24

[1] https://review.openstack.org/#/c/398012/
[2] https://github.com/openstack-dev/devstack/blob/master/functions-common#L678

Revision history for this message
Sean Dague (sdague) wrote :

This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.

Changed in devstack:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.