I found it worked better if it uses the v3 keystone api. I tried the v2
keystone api, and it didn't work out of the box, I had to manually modify
openstack.conf file. It seems like something is not right, but I lost
interest in the problem and just made the variables available that it
wanted.
If
Thank you for your response.
The problem was because I was using the internet of my Samsung Smartphone
via Hotspot. Please, could you tell me how I can use OpenShift using the
internet of my Smartphone?
2017-11-02 1:37 GMT+01:00 Ben Parees :
> can you confirm that your pods
On Sat, Nov 4, 2017 at 8:32 AM, Tien Hung Nguyen
wrote:
> Thank you for your response.
>
> The problem was because I was using the internet of my Samsung Smartphone
> via Hotspot. Please, could you tell me how I can use OpenShift using the
> internet of my Smartphone?
>
On 03/11/2017 22:24, Joel Pearson wrote:
Are you actually filling in those values with anything?
Yes, all have values, I just didn't want to divulge them.
I setup OpenShift on OpenStack Kilo and I needed to make sure I was
using the v3 rc file and I also had an issue with block storage the
I added this to mine:
openshift_cloudprovider_openstack_tenant_name: "{{
lookup('env','OS_TENANT_NAME') }}"
On Sat, Nov 4, 2017 at 8:50 PM Joel Pearson
wrote:
> You're missing "(openshift_cloudprovider_openstack_tenant_id or
>
You're missing "(openshift_cloudprovider_openstack_tenant_id or
openshift_cloudprovider_openstack_tenant_name )"
See: (openshift_cloudprovider_openstack_tenant_id is defined or
openshift_cloudprovider_openstack_tenant_name is defined) in the file below
Yes, I removed those because my setup file (Newton release) included this:
# unset v2.0 items in case set
unset OS_TENANT_ID
unset OS_TENANT_NAME
Is openshift expecting an earlier release?
On 04/11/2017 09:51, Joel Pearson wrote:
I added this to mine:
Yes mine too, but if you want it to work you need to add it back. I grabbed
those values from the v2 RC file.
On Sat, 4 Nov 2017 at 9:20 pm, Tim Dudgeon wrote:
> Yes, I removed those because my setup file (Newton release) included this:
>
> # unset v2.0 items in case set
>