I'm new for openstack. I used this command:
keystone user-list
but it showed:
Authorization Failed: The resource could not be found. (HTTP 404)
(Request-ID: req-0022eaa4-c2f9-480b-b069-bc93eeed8d06)
and then i used this:
openstack user-list
and it worked.
So, I wonder if "keystone user-list" was removed?
thanks for answer
Related
UPGRADE FAILED: Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post : x509: certificate signed by unknown authority
this is the exact error which comes when I am using helm upgrade.
tried to apply the previous local values file to helm upgrade. did not work
Running the following command fixed the problem. I am unable to find the root cause of the same
kubectl delete -A ValidatingWebhookConfiguration ingress-nginx-admission
※I am a beginner, so if you have any information you need, please comment.
Based on the yaml file, I am trying to publish a sample app that has already been launched in Pod via Ingress.
$kubectl apply -f ./overlays/stg/bookinfo-ingress.yaml
■Errormessage
Error from server (InternalError): error when creating "./overlays/stg/bookinfo-ingress.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": failed to call webhook: Post "https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1/ingresses?timeout=10s": x509: certificate signed by unknown authority
Currently, we are trying to setup neutron for our cloud server. Since everyone is new to this, we are struggling a bit. When we entered this command:
openstack network create --share --external \
--provider-physical-network provider \
--provider-network-type flat provider
And it throws this error:
Error while executing command: HttpException: 503, The Keystone service is temporarily unavailable.: 503 Service Unavailable: The server is currently unavailable. Please try again at a later time.
We are following openstack docs guide to a T.
Does anyone know what causes this error and how to fix it?
Thanks.
I fixed it, it was a problem with MariaDB. When we updated it from 10.1 to 10.3, I couldn't access my DB, so when I fixed that error it works now.
I am currently trying to install Openstack for the first time.
I followed the installation guide given by Openstack (here)
The basic setup is done , and I am now trying to install the four "basic" services of Openstack : Keystone, Glance , Nova and Neutron.
But I have an error with Keystone , I followed the tutorial , but when I am trying to test Keystone , by launching even the simplest command (openstack role create myrole for example)
I have the following message
The request you have made requires authentication. (HTTP 401) (Request-ID: req-e9164787-381f-4f69-af7f-7ea4932c3a0b)
You can find here all the command I previously entered here , here is the command openstack domain list --debug output and here the Keystone.log
As you can see in the keystone.log , I have the message
2019-01-16 20:45:53.064 7056 WARNING keystone.auth.core [req-fd1b7466-cf24-406f-82ce-2549156ae4d6 - - - - -] Could not find domain: default.: DomainNotFound: Could not find domain: default.
It seems that Keystone do not know the Default Domain , how can I change that.
I have already tried "Default" and "default' (with and without the lower-case) , but no change.
I cannot even create another domain , or create a Token (I read on other thread that it might be the problem source)
Let me know if you need anything more , and thanks in advance !
I am trying to create an Instance from command line using the command,
nova boot --config-drive=true --flavor 2 --key-name key1 --image c28bc1e8-a25f-413c-9e13-fecdd5d6f522 instance1
But I got this error,
ERROR (BadRequest): Network 00000000-0000-0000-0000-000000000000,
11111111-1111-1111-1111-111111111111 could not be found. (HTTP 400)
(Request-ID: req-6dd0352e-008a-40c4-91e2-454529712ba9)
Guide me how to resolve this problem.
I’m guessing you may have the rax_default_network_flags_python_novaclient_ext Python package installed, which automatically adds those networks to the request, but are not booting an instance in the Rackspace public cloud.
This can likely be resolved using the --no-service-net and --no-public arguments, or by uninstalling the above mentioned Python module.