How to realize the non-termination repair of fuel-openstack9.0 verification network
Editor to share with you how to achieve fuel-openstack9.0 verification network non-stop repair, I hope you will gain something after reading this article, let's discuss it together!
Problem phenomenon: verifying the network status has been in the process of verification, and the problem of restarting the computer still exists.
Solution:
1. Execute fuel task-l
Found that the verify_networks task is in running state
two。 Execute fuel task-- delete-f-- tid 349
Force deletion of the task
3. View verify_networks task status, restored
4.UI validates the network and the test passes
Note:
It starts with the debug code and its postgres data failing to locate the problem
A, code survey record:
/ usr/lib/python2.7/site-packages/fuelclient/cli/actions
Response = env.verify_network ()
Def verify_network (self):
Return self.connection.put_request (
Self.network_verification_url, self.get_network_data ()
From fuelclient.objects.base import BaseObject
Connection = APIClient
From fuelclient.client import APIClient
Def put_request (self, api, data, * * params):
"" Make PUT request to specific API with some data.
: param api: API endpoint (path)
: param data: Data send in request, will be serialized to JSON
: param params: Params of query string
"
Url = self.api_root + api
Data_json = json.dumps (data)
Resp = self.session.put (url, data=data_json, params=params)
Self.print_debug ('PUT {0} data= {1}' .format (resp.url, data_json))
Self._raise_for_status_with_info (resp)
Return resp.json ()
Def _ raise_for_status_with_info (self, response):
Try:
Response.raise_for_status ()
Except requests.exceptions.HTTPError as e:
Raise error.HTTPError (error.get_full_error_message (e))
B, postgres database survey records:
# su postgres
# psql
After reading this article, I believe you have a certain understanding of "how to achieve fuel-openstack9.0 verification network non-stop repair". If you want to know more about it, welcome to follow the industry information channel, thank you for reading!
