-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix server signal tests #457
Conversation
Signed-off-by: Fabricio Aguiar <fabricio.aguiar@gmail.com>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fao89 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/d31ad99a335444dda47b11c1438f860a ❌ openstack-k8s-operators-content-provider FAILURE in 10m 53s |
recheck |
/retest |
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/0b2413200e6940218dcebf577bc2d12a ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 13m 24s |
@@ -23,15 +23,15 @@ | |||
validation.run_validation true | |||
identity.v3_endpoint_type public | |||
identity.v2_admin_endpoint_type public | |||
heat_plugin.vm_to_heat_api_insecure true | |||
heat_plugin.dns_servers "192.168.122.80" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bshephar even after adding this, the test still failing with:
curl: (6) Could not resolve host: heat-api-internal.openstack.svc
curl: (6) Could not resolve host: heat-api-internal.openstack.svc
curl: (6) Could not resolve host: heat-api-internal.openstack.svc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does seem like that DNS server should have answers for this query:
$ oc exec -it dnsmasq-dns-548bf5d8cb-lbr65 -- cat /etc/dnsmasq.d/hosts/dns-svc
Defaulted container "dnsmasq-dns" out of: dnsmasq-dns, init (init)
172.17.0.80 barbican-internal.openstack.svc cinder-internal.openstack.svc glance-default-internal.openstack.svc heat-api-internal.openstack.svc keystone-internal.openstack.svc neutron-internal.openstack.svc nova-internal.openstack.svc nova-metadata-internal.openstack.svc placement-internal.openstack.svc swift-internal.openstack.svc
172.17.0.85 rabbitmq.openstack.svc
172.17.0.86 rabbitmq-cell1.openstack.svc
Can a VM deployed on the EDPM node reach that DNS Servers IP address though? Like, that would require a OpenStack network created bridging the right interface on the EDPM compute node.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question! I don't know exactly how tempest job is configured but I believe we don't do that
No description provided.