Bug 1264740
| Summary: | RHEL OSP Director must be configure with nova-event-callback by default | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ofer Blaut <oblaut> | |
| Component: | rhosp-director | Assignee: | Jay Dobies <jason.dobies> | |
| Status: | CLOSED ERRATA | QA Contact: | Ofer Blaut <oblaut> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | high | |||
| Version: | 7.0 (Kilo) | CC: | beagles, calfonso, dmacpher, emacchi, jason.dobies, jcoufal, jslagle, lbezdick, lpeer, mburns, mwagner, nyechiel, oblaut, ohochman, rhel-osp-director-maint, sclewis, tfreger, yguenane | |
| Target Milestone: | y2 | Keywords: | Triaged | |
| Target Release: | 7.0 (Kilo) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-tripleo-heat-templates-0.8.6-89.el7ost | Doc Type: | Bug Fix | |
| Doc Text: |
Neutron uses Nova's event callback to make sure the Neutron port is configured before running a VM. The director did not include configuration for this feature. This fix add the configuration in the director's Heat templates. Now Neutron uses Nova's event callback successfully.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1273409 1298608 (view as bug list) | Environment: | ||
| Last Closed: | 2015-12-21 16:55:17 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1273409, 1298608 | |||
|
Description
Ofer Blaut
2015-09-21 06:28:47 UTC
Just a heads up that, if memory serves, that the nova part (vif_plugging_is_fatal = True) needs to be set to True on the compute nodes as well. The defaults would be preferable to what there is now. It seems that it might be being set to false in openstack-tripleo-heat-templates/puppet/hierdata/common.yaml - which might explain how this regression wheedled in. The neutron config needs to have the appropriate entries to know "how to talk" to nova. The properties can be seen starting on line 331 or the sample neutron.conf on http://docs.openstack.org/kilo/config-reference/content/section_neutron.conf.html I imagine that this stuff was configured in the installer version so it is probably just a matter of enabling it (openstack-puppet/modules/neutron/manifests/server/notifications.pp?) as long as nothing else gets in the way. Forgot to mention that we probably should have an U/S bug on this once the details of the real culprits are figured out. Patch submitted upstream in TripleO Heat Templates: https://review.openstack.org/225962 note that vif_plugging_timeout also needs to use the default upstream value of 300 instead of the TripleO value of 30. this has been pointed out on the above review as well Currently working on the undercloud part: https://review.openstack.org/234325 And also on the overcloud side: https://review.openstack.org/225962 Doesn't seem to be working neutron.conf is missing nova_admin_tenant_id = nova_admin_password = nova_admin_username = openstack-tripleo-heat-templates-0.8.6-87.el7ost.noarch openstack-tripleo-heat-templates-0.8.6-92.el7ost.noarch
tested with creating VMs
[root@overcloud-controller-2 ~]# tail -f /var/log/nova/nova-api.log -f /var/log/neutron/server.log | grep -n --line-buffered -e'^==> .* <==$' -e'event'
1:==> /var/log/nova/nova-api.log <==
13:==> /var/log/neutron/server.log <==
22:2015-12-15 08:36:38.581 3831 INFO neutron.notifiers.nova [-] Nova event response: {u'status': u'completed', u'tag': u'287cd79b-41fd-4c80-bfcb-63e23589e34a', u'name': u'network-vif-plugged', u'server_uuid': u'5cb77bbb-153d-44f3-8f0c-1eaf1faafbcc', u'code': 200}
23:2015-12-15 08:36:39.916 3832 INFO neutron.notifiers.nova [-] Nova event response: {u'status': u'completed', u'tag': u'25db17fe-9ff9-484e-9412-43fd3dbec936', u'name': u'network-vif-plugged', u'server_uuid': u'9e0186f5-e548-498e-8823-bc17717858af', u'code': 200}
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2015:2651 |