R3.2-build33 (continuous build) compute service endpoint is not configured after provision through fab
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Won't Fix
|
High
|
Unassigned | ||
R3.2 |
Fix Committed
|
High
|
amudhar |
Bug Description
on build33(continuous build) of R3.2 ubuntu mitaka, the compute service endpoint is not configured and causing the sanity TCs to fail. This problem is not seen always and things work fine the compute service endpoint is created manually (This is with fab provisioning)
The error in setup_all log:
2017-08-28 13:45:47:139903: [root@10.
2017-08-28 13:45:47:140000: [root@10.
root@nodec7:
ERROR (EndpointNotFound): publicURL endpoint for compute service not found
root@nodec7:
After running the command manually:
root@nodec7:
+------
| Field | Value |
+------
| adminurl | http://
| id | cbd983ec74c24a0
| internalurl | http://
| publicurl | http://
| region | RegionOne |
| service_id | baf404e9240f4be
| service_name | nova |
| service_type | compute |
+------
root@nodec7:
root@nodec7:
+------
| host_name | service | zone |
+------
| nodec7 | scheduler | internal |
| nodec7 | console | internal |
| nodec7 | consoleauth | internal |
| nodec7 | conductor | internal |
| nodec8 | scheduler | internal |
| nodec8 | console | internal |
| nodec8 | consoleauth | internal |
| nodec8 | conductor | internal |
| nodeg36 | scheduler | internal |
| nodeg36 | console | internal |
| nodeg36 | consoleauth | internal |
| nodeg36 | conductor | internal |
| nodei1 | compute | nova |
| nodei2 | compute | nova |
| nodei3 | compute | nova |
| nodec57 | compute | nova |
+------
root@nodec7:
summary: |
R3.2-build33 (continuous build) compute service endpoint is not - configured + configured after provision through fab |
Changed in juniperopenstack: | |
status: | New → Won't Fix |
tags: |
added: provisioning sanity removed: provisi |
tags: | added: config |
Above testbed is in the bug state now.
Workaround:
root@nodec7: ~/fabric- utils# openstack endpoint create --region RegionOne <service-id> --publicurl ‘http:// 192.168. 192.25: 8774/v2. 1/$(tenant_ id)s’ --adminurl ‘http:// localhost: 8774/v2. 1/$(tenant_ id)s' --internalurl ‘http:// 192.168. 192.25: 8774/v2. 1/$(tenant_ id)s’
you may do the above command (replace service-id with service id of the compute service from keystone service-list output) to add the endpoint