Re: [Starlingx-discuss] StarlingX Magnum cluster-template giving error as "errors"
Hi All,
Please also find attached screenshot of magnum -debug service-list.
Mit freundlichen Grüßen, with best regards, Yatindra Shashi
From: Shashi, YatindraX Sent: Tuesday, March 12, 2019 12:31 PM To: 'starlingx-discuss@lists.starlingx.io' starlingx-discuss@lists.starlingx.io Cc: Marcel Wagner (marcel.wagner@intel.com) marcel.wagner@intel.com Subject: StarlingX Magnum cluster-template giving error as "errors"
Hi All,,
While running the command to create magnum cluster template or any magnum command I receive error like ERROR: "errors" I am using simplex mode installation of the StarlingX.
I checked the log files of magnum api and it shows some authentication problem as below
" 2019-03-11 17:53:41.394 241971 WARNING oslo_reports.guru_meditation_report [-] Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports. 2019-03-11 17:53:41.395 241971 INFO magnum.api.app [-] Full WSGI config used: /etc/magnum/api-paste.ini 2019-03-11 17:53:41.493 241971 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2019-03-11 17:53:41.505 241971 INFO magnum.cmd.api [-] Starting server in PID 241971 2019-03-11 17:53:41.510 241971 INFO magnum.cmd.api [-] Serving on http://127.168.204.2:9511 2019-03-11 17:53:41.511 241971 INFO magnum.cmd.api [-] Server will handle each request in a new process up to 112 concurrent processes 2019-03-11 17:53:41.511 241971 INFO werkzeug [-] * Running on http://127.168.204.2:9511/ 2019-03-11 17:53:56.090 244289 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}: Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-361ef3fe-3749-4959-b33f-69c1a10fd84b) 2019-03-11 17:53:56.403 244289 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}: Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-06c1c183-3d8d-48fa-95f5-311c77990435) 2019-03-11 17:53:56.403 244289 CRITICAL keystonemiddleware.auth_token [-] Unable to validate token: Identity server rejected authorization necessary to fetch token data: ServiceError: Identity server rejected authorization necessary to fetch token data 2019-03-11 17:53:56.404 244289 INFO werkzeug [-] 127.168.204.3 - - [11/Mar/2019 17:53:56] "POST /v1/clustertemplates HTTP/1.1" 503 - 2019-03-12 10:02:27.172 202974 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}: Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-6be81e7b-ac2e-4943-8967-b5a1adab1139) 2019-03-12 10:02:27.481 202974 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}: Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-4c848660-982f-491f-a3a8-186a5f3f124e) 2019-03-12 10:02:27.482 202974 CRITICAL keystonemiddleware.auth_token [-] Unable to validate token: Identity server rejected authorization necessary to fetch token data: ServiceError: Identity server rejected authorization necessary to fetch token data 2019-03-12 10:02:27.482 202974 INFO werkzeug [-] 127.168.204.3 - - [12/Mar/2019 10:02:27] "GET /v1/mservices HTTP/1.1" 503 -
" Where as my magnum KEYSTONE_AUTHTOKEN configuration in magnum.conf is as below.
" # Authentication type to load (string value) # Deprecated group/name - [keystone_authtoken]/auth_plugin #auth_type = <None> auth_type = password
# Config Section from which to load plugin specific options (string value) #auth_section = <None> project_name=services username=magnum password=f7e60b57917fTi0* auth_url=http://127.168.204.2:5000"
I checked the user magnum, and its domain. It looks configured to me. Will you tell me if I am missing something. If you need any further information then please let me know.
Mit freundlichen Grüßen, with best regards, Yatindra Shashi Intel Corporation Munich, Germany
participants (1)
-
Shashi, YatindraX