Welcome!
Here's a couple things that might help you get familiar with OpenStack:
https://docs.openstack.org/devstack/latest/
https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html
Here's a good place to get information about contributing:
https://docs.openstack.org/upstream-traini
https://bugs.launchpad.net/keystone/+bug/1662762
I ran into this with an install of Ocata on ubuntu from packages (not using
fuel). It sounds like you might be hitting this same issue. I was able to
resolve it by grabbing core.py from the Ocata version of the fix for this bug
and dropping it in
ages" and taken directly from there
> the file that was corresponding to the image I wanted.
> Do you believe that by "saving" it would make any difference??
>
> Any other ideas that I can try???
>
>
> All the best,
>
> G.
>
>
>
> On Sun, 26 Mar 2017 0
You might be able to change it via openstack command, probably something like
'openstack show image ' / 'openstack image set ?? '
You can definitely download the image to a file and then upload a new image,
specifying --min-disk. Something like 'openstack image save --file '
and then just 'op
You can get a better idea of what's going on by looking at the other nova
log files as Vikash suggested. I would start with the nova-scheduler log if
your nova-api log looks clean.
This slideshow is a bit dated, but has a decent overview of how nova works
when provisioning a VM. While it is old an
env as doc said(which set OS_USERNAME=admin), I also got errors as bellow.
>
> So how to do
>
> 2017-03-12 23:01 GMT+08:00 Chris Suttles :
>> Your env looks incorrect to me. Take a look here for setting those vars
>> correctly:
>>
>> https://docs.openstack.org/
Your env looks incorrect to me. Take a look here for setting those vars
correctly:
https://docs.openstack.org/ocata/install-guide-ubuntu/keystone-install.html
It's crucial that you set those variables to the same information you
provide to keystone in the steps listed there.
On Sun, Mar 12, 2017
To me, that looks like your network configuration has a problem and
fuel/nailgun is bubbling up the error when trying to provision neutron on the
node.
Since it is a fresh install, I would consider starting over, and validating
network config in fuel before restarting your deployment.
I don't
