Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

2016-12-31 Thread Steven Dake (stdake) 
Jeffrey,

rax-iad uses xen as a base virtualization layer iiuc.  Perhaps kvm on xen is 
not a technical feature rax-iad supports or perhaps libvirt was modified and 
now fails with xen?  Whatever the case is, rax-iad has been a semi-constant 
source of hassle with Kolla’s gate jobs; I think partly because Kolla’s gate 
scripts need to special-case rax-iad in some way.

Just one of many possibilities.

Happy new year ☺

Regards
-steve


From: Jeffrey Zhang 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Saturday, December 31, 2016 at 6:22 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during 
launching qemu progress

I checked more than ten error gates, all of them happened in rax-iad.

On Sat, Dec 31, 2016 at 12:06 PM, Steven Dake (stdake) 
mailto:std...@cisco.com>> wrote:
Jeffrey,

Have you detected any pattern to any specific cloud provider in the logs?

Regards
-steve


From: Jeffrey Zhang mailto:zhang.lei@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Friday, December 30, 2016 at 12:41 AM
To: OpenStack Development Mailing List 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during 
launching qemu progress

Found this nova bug[0] and another talk in openstack-dev[1].

The question is: why this happens now and then? sometimes the gate is OK. and 
others not.

[0] https://bugs.launchpad.net/nova/+bug/1649527
[1] http://lists.openstack.org/pipermail/openstack-dev/2016-December/109401.html

On Fri, Dec 30, 2016 at 3:33 PM, Jeffrey Zhang 
mailto:zhang.lei@gmail.com>> wrote:
Recently, centos 7.3 is release. libvirt is upgrade to 2.0 version.

But in kolla's gate. the nova_libvirt container failed now and then.

What i found is:

1. Simple start nova_libvirt container is OK.
2. When launching a new instance, libvirt is killed without any logs in 
libvirtd.log file.
3. in system messages log, i found following line.

Dec 29 00:41:24 localhost kernel: libvirtd[24340]: segfault at 8 ip 
7f9fee072823 sp 7f9fe52dd1c0 error 4 in 
libvirt.so.0.2000.0[7f9fedf1f000+353000]

No idea why and how this happen. Any idea on this?

--
Regards,
Jeffrey Zhang
Blog: http://xcodest.me



--
Regards,
Jeffrey Zhang
Blog: http://xcodest.me

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Regards,
Jeffrey Zhang
Blog: http://xcodest.me
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Consistency in versioned notification payloads

2016-12-31 Thread Doug Hellmann 
Excerpts from Matt Riedemann's message of 2016-12-30 16:23:24 -0600:
> While reviewing patches today to add versioned notifications for CRUD 
> operations on aggregates and flavors I've come across some inconsistency.
> 
> The existing non-versioned notification for aggregate.delete just sends 
> the aggregate id, but the versioned notification is sending the whole 
> aggregate object in the payload:
> 
> https://review.openstack.org/#/c/394512/9/doc/notification_samples/aggregate-delete-end.json
> 
> But with the flavor-delete versioned notification, it's just sending the 
> flavorid:
> 
> https://review.openstack.org/#/c/398171/16/doc/notification_samples/flavor-delete.json
> 
> So which should we be doing? Either way you can correlate the id on the 
> resource in the notification back to the full record if needed, but 
> should we be sending the full object in the versioned notification 
> payload while we have it? I don't much care either way which we do as 
> long as we're consistent.
> 

When we originally wrote ceilometer's notification consumption code,
we ran into issues processing the data for delete notifications
that only included identifiers.  IIRC, the primary issue at the
time was with some of the CRUD operations in neutron, and we asked
them to add all known data about objects to all notifications so
the consumer could filter notifications based on those properties
(maybe the receive wants to only pay attention to certain tenants,
for example) and ensure it has the most current settings for an
object as it is being deleted (useful for ensuring that a billing
record includes the right flavor, for example).

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

2016-12-31 Thread Jeffrey Zhang 
I checked more than ten error gates, all of them happened in rax-iad.

On Sat, Dec 31, 2016 at 12:06 PM, Steven Dake (stdake) 
wrote:

> Jeffrey,
>
>
>
> Have you detected any pattern to any specific cloud provider in the logs?
>
>
>
> Regards
>
> -steve
>
>
>
>
>
> *From: *Jeffrey Zhang 
> *Reply-To: *"OpenStack Development Mailing List (not for usage
> questions)" 
> *Date: *Friday, December 30, 2016 at 12:41 AM
> *To: *OpenStack Development Mailing List  openstack.org>
> *Subject: *Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed
> during launching qemu progress
>
>
>
> Found this nova bug[0] and another talk in openstack-dev[1].
>
>
>
> The question is: why this happens now and then? sometimes the gate is OK.
> and others not.
>
>
>
> [0] https://bugs.launchpad.net/nova/+bug/1649527
>
> [1] http://lists.openstack.org/pipermail/openstack-dev/
> 2016-December/109401.html
>
>
>
> On Fri, Dec 30, 2016 at 3:33 PM, Jeffrey Zhang 
> wrote:
>
> Recently, centos 7.3 is release. libvirt is upgrade to 2.0 version.
>
>
>
> But in kolla's gate. the nova_libvirt container failed now and then.
>
>
>
> What i found is:
>
>
>
> 1. Simple start nova_libvirt container is OK.
>
> 2. When launching a new instance, libvirt is killed without any logs in
> libvirtd.log file.
>
> 3. in system messages log, i found following line.
>
> Dec 29 00:41:24 localhost kernel: libvirtd[24340]: segfault at 8 ip 
> 7f9fee072823 sp 7f9fe52dd1c0 error 4 in 
> libvirt.so.0.2000.0[7f9fedf1f000+353000]
>
> No idea why and how this happen. Any idea on this?
>
>
>
> --
>
> Regards,
>
> Jeffrey Zhang
>
> Blog: http://xcodest.me
>
>
>
>
>
> --
>
> Regards,
>
> Jeffrey Zhang
>
> Blog: http://xcodest.me
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Regards,
Jeffrey Zhang
Blog: http://xcodest.me
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev