Bug 1546168
Summary: | Some libvirt domains created by nova have an empty "<nova:owner>" attribute in the embedded metadata | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Lars Kellogg-Stedman <lars> | ||||||
Component: | openstack-nova | Assignee: | Lee Yarwood <lyarwood> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Joe H. Rahme <jhakimra> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 12.0 (Pike) | CC: | awaugama, berrange, dasmith, eglynn, kchamart, lars, lyarwood, sbauza, sferdjao, sgordon, srevivo, vromanso | ||||||
Target Milestone: | z5 | Keywords: | Triaged, ZStream | ||||||
Target Release: | 11.0 (Ocata) | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | openstack-nova-15.0.8-13.el7ost | Doc Type: | If docs needed, set a value | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | |||||||||
: | 1558103 (view as bug list) | Environment: | |||||||
Last Closed: | 2018-05-18 17:14:38 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: | 1558103 | ||||||||
Attachments: |
|
Description
Lars Kellogg-Stedman
2018-02-16 13:41:47 UTC
Created attachment 1397039 [details]
output of openstack server event list
lyarwood suggests that the result of 'openstack server event list' for one of the servers might be of interest.
(In reply to Lars Kellogg-Stedman from comment #1) > Created attachment 1397039 [details] > output of openstack server event list > > lyarwood suggests that the result of 'openstack server event list' for one > of the servers might be of interest. I think this could be linked to the evacuation of the instance but I've not attempted to reproduce. It appears we tried to use a request context with user_name, project_id and project_name all set to None, that results in LibvirtConfigGuestMetaNovaOwner.format_dom() returning <nova:owner/> : nova/virt/libvirt/driver.py 3842 def _get_guest_config_meta(self, context, instance): 3843 """Get metadata config for guest.""" [..] 3854 if context is not None: 3855 ometa = vconfig.LibvirtConfigGuestMetaNovaOwner() 3856 ometa.userid = context.user_id 3857 ometa.username = context.user_name 3858 ometa.projectid = context.project_id 3859 ometa.projectname = context.project_name 3860 meta.owner = ometa nova/virt/libvirt/config.py 2476 class LibvirtConfigGuestMetaNovaOwner(LibvirtConfigObject): [..] 2489 def format_dom(self): 2490 meta = super(LibvirtConfigGuestMetaNovaOwner, self).format_dom() 2491 if self.userid is not None and self.username is not None: 2492 user = self._text_node("user", self.username) 2493 user.set("uuid", self.userid) 2494 meta.append(user) 2495 if self.projectid is not None and self.projectname is not None: 2496 project = self._text_node("project", self.projectname) 2497 project.set("uuid", self.projectid) 2498 meta.append(project) 2499 return meta https://review.openstack.org/#/c/399679/ actually landed in Pike and has switched to using the instance object to populate these fields. I'll try to backport this to Ocata and Newton for OSP to help avoid this going forward. For this customer the best way to workaround this now is to stop and start the instances, forcing the domain XML to be recreated with the correct owner details on Pike. Can you confirm that this resolves the issue with Ceilometer? FWIW I'd also suggest following up with that team to handle this situation. I will ask the customer about stopping/starting these servers. That may not be possible at this time. On the ceilometer side, I have opened https://bugs.launchpad.net/ceilometer/+bug/1749960 upstream and submitted a fix that would make ceilometer less sensitive to this sort of issue. https://bugzilla.redhat.com/show_bug.cgi?id=1546176 is the bugzilla version of the upstream bug. 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-2018:1624 |