Re: [Openstack] [OpenStack] Files Injection in to Windows VMs

2013-04-25 Thread Balamurugan V G
Thanks for link! By running the OpenHiddenSystemDrive exe, I am able to see
the injected file.

Regards,
Balu


On Thu, Apr 25, 2013 at 10:30 AM, Wangpan hzwang...@corp.netease.comwrote:

 **
 have you open and check the 'system reserved partition'? see the refer at
 bellow:

 http://www.techfeb.com/how-to-open-windows-7-hidden-system-reserved-partition/

 2013-04-25
  --
  Wangpan
  --
  *发件人:*Balamurugan V G
 *发送时间:*2013-04-25 12:34
 *主题:*Re: [Openstack] [OpenStack] Files Injection in to Windows VMs
 *收件人:*Wangpanhzwang...@corp.netease.com
 *抄送:*openstack@lists.launchpad.netopenstack@lists.launchpad.net

  Hi Wanpan,

 While I am able to inject files in to WindowsXP, CentOS5.9 and
 Ubuntu12.04. I am unable to do it for Windows8Entrprise OS. I did
 search the entire drive for the file I injected but couldnt file.
 Below is the log from nova-compute.log.


 2013-04-24 01:41:27.973 AUDIT nova.compute.manager
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Starting instance...
 2013-04-24 01:41:28.170 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Attempting claim:
 memory 1024 MB, disk 10 GB, VCPUs 1
 2013-04-24 01:41:28.171 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total Memory: 3953
 MB, used: 2048 MB
 2013-04-24 01:41:28.171 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Memory limit: 5929
 MB, free: 3881 MB
 2013-04-24 01:41:28.172 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total Disk: 225 GB,
 used: 15 GB
 2013-04-24 01:41:28.172 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Disk limit not
 specified, defaulting to unlimited
 2013-04-24 01:41:28.173 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total CPU: 2 VCPUs,
 used: 2 VCPUs
 2013-04-24 01:41:28.173 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] CPU limit not
 specified, defaulting to unlimited
 2013-04-24 01:41:28.174 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Claim successful
 2013-04-24 01:41:33.998 INFO nova.virt.libvirt.driver
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Creating image
 2013-04-24 01:41:34.281 INFO nova.virt.libvirt.driver
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Injecting files into
 image 65eaa160-d0e7-403e-a52c-90bea3c22cf7
 2013-04-24 01:41:36.534 INFO nova.virt.libvirt.firewall
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Called
 setup_basic_filtering in nwfilter
 2013-04-24 01:41:36.535 INFO nova.virt.libvirt.firewall
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Ensuring static
 filters
 2013-04-24 01:41:38.555 13316 INFO nova.compute.manager [-] Lifecycle
 event 0 on VM aa46445e-1f86-4a5a-8002-a7703ff98648
 2013-04-24 01:41:38.763 13316 INFO nova.virt.libvirt.driver [-]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Instance spawned
 successfully.
 2013-04-24 01:41:38.996 13316 INFO nova.compute.manager [-] [instance:
 aa46445e-1f86-4a5a-8002-a7703ff98648] During sync_power_state the
 instance has a pending task. Skip.
 2013-04-24 01:41:59.494 13316 AUDIT nova.compute.resource_tracker [-]
 Auditing locally available compute resources
 2013-04-24 01:42:00.345 13316 AUDIT nova.compute.resource_tracker [-]
 Free ram (MB): 881
 2013-04-24 01:42:00.346 13316 AUDIT nova.compute.resource_tracker [-]
 Free disk (GB): 200
 2013-04-24 01:42:00.346 13316 AUDIT nova.compute.resource_tracker 

Re: [Openstack] [OpenStack] Files Injection in to Windows VMs

2013-04-25 Thread Balamurugan V G
Is there was way to inject in to the regular filesystem(C: drive) in
Windows7/Windows8?

Regards,
Balu


On Thu, Apr 25, 2013 at 11:46 AM, Balamurugan V G
balamuruga...@gmail.comwrote:

 Thanks for link! By running the OpenHiddenSystemDrive exe, I am able to
 see the injected file.

 Regards,
 Balu


 On Thu, Apr 25, 2013 at 10:30 AM, Wangpan hzwang...@corp.netease.comwrote:

 **
 have you open and check the 'system reserved partition'? see the refer at
 bellow:

 http://www.techfeb.com/how-to-open-windows-7-hidden-system-reserved-partition/

 2013-04-25
  --
  Wangpan
  --
  *发件人:*Balamurugan V G
 *发送时间:*2013-04-25 12:34
 *主题:*Re: [Openstack] [OpenStack] Files Injection in to Windows VMs
 *收件人:*Wangpanhzwang...@corp.netease.com
 *抄送:*openstack@lists.launchpad.netopenstack@lists.launchpad.net

  Hi Wanpan,

 While I am able to inject files in to WindowsXP, CentOS5.9 and
 Ubuntu12.04. I am unable to do it for Windows8Entrprise OS. I did
 search the entire drive for the file I injected but couldnt file.
 Below is the log from nova-compute.log.


 2013-04-24 01:41:27.973 AUDIT nova.compute.manager
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Starting instance...
 2013-04-24 01:41:28.170 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Attempting claim:
 memory 1024 MB, disk 10 GB, VCPUs 1
 2013-04-24 01:41:28.171 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total Memory: 3953
 MB, used: 2048 MB
 2013-04-24 01:41:28.171 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Memory limit: 5929
 MB, free: 3881 MB
 2013-04-24 01:41:28.172 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total Disk: 225 GB,
 used: 15 GB
 2013-04-24 01:41:28.172 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Disk limit not
 specified, defaulting to unlimited
 2013-04-24 01:41:28.173 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total CPU: 2 VCPUs,
 used: 2 VCPUs
 2013-04-24 01:41:28.173 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] CPU limit not
 specified, defaulting to unlimited
 2013-04-24 01:41:28.174 AUDIT nova.compute.claims
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Claim successful
 2013-04-24 01:41:33.998 INFO nova.virt.libvirt.driver
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Creating image
 2013-04-24 01:41:34.281 INFO nova.virt.libvirt.driver
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Injecting files into
 image 65eaa160-d0e7-403e-a52c-90bea3c22cf7
 2013-04-24 01:41:36.534 INFO nova.virt.libvirt.firewall
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Called
 setup_basic_filtering in nwfilter
 2013-04-24 01:41:36.535 INFO nova.virt.libvirt.firewall
 [req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5
 117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Ensuring static
 filters
 2013-04-24 01:41:38.555 13316 INFO nova.compute.manager [-] Lifecycle
 event 0 on VM aa46445e-1f86-4a5a-8002-a7703ff98648
 2013-04-24 01:41:38.763 13316 INFO nova.virt.libvirt.driver [-]
 [instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Instance spawned
 successfully.
 2013-04-24 01:41:38.996 13316 INFO nova.compute.manager [-] [instance:
 aa46445e-1f86-4a5a-8002-a7703ff98648] During sync_power_state the
 instance has a pending task. Skip.
 2013-04-24 01:41:59.494 13316 AUDIT nova.compute.resource_tracker [-]
 Auditing locally available compute resources
 2013-04-24 01:42:00.345 13316 AUDIT 

Re: [Openstack] [OpenStack] Files Injection in to Windows VMs

2013-04-25 Thread Wangpan
I check the master codes of nova several days ago, and find the first logical 
partition of root disk will be choosed to inject files, so you may have to 
change the nova code to implement what you want.
I also will try to fix this issue in the havana edition.

2013-04-25



Wangpan



发件人:Balamurugan V G
发送时间:2013-04-25 14:18
主题:Re: Re: [Openstack] [OpenStack] Files Injection in to Windows VMs
收件人:Wangpanhzwang...@corp.netease.com
抄送:openstack@lists.launchpad.netopenstack@lists.launchpad.net

Is there was way to inject in to the regular filesystem(C: drive) in 
Windows7/Windows8?


Regards,
Balu




On Thu, Apr 25, 2013 at 11:46 AM, Balamurugan V G balamuruga...@gmail.com 
wrote:

Thanks for link! By running the OpenHiddenSystemDrive exe, I am able to see the 
injected file.


Regards,
Balu




On Thu, Apr 25, 2013 at 10:30 AM, Wangpan hzwang...@corp.netease.com wrote:

have you open and check the 'system reserved partition'? see the refer at 
bellow:
http://www.techfeb.com/how-to-open-windows-7-hidden-system-reserved-partition/

2013-04-25



Wangpan



发件人:Balamurugan V G
发送时间:2013-04-25 12:34
主题:Re: [Openstack] [OpenStack] Files Injection in to Windows VMs
收件人:Wangpanhzwang...@corp.netease.com
抄送:openstack@lists.launchpad.netopenstack@lists.launchpad.net

Hi Wanpan, 

While I am able to inject files in to WindowsXP, CentOS5.9 and 
Ubuntu12.04. I am unable to do it for Windows8Entrprise OS. I did 
search the entire drive for the file I injected but couldnt file. 
Below is the log from nova-compute.log. 


2013-04-24 01:41:27.973 AUDIT nova.compute.manager 
[req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5 
117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e] 
[instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Starting instance... 
2013-04-24 01:41:28.170 AUDIT nova.compute.claims 
[req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5 
117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e] 
[instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Attempting claim: 
memory 1024 MB, disk 10 GB, VCPUs 1 
2013-04-24 01:41:28.171 AUDIT nova.compute.claims 
[req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5 
117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e] 
[instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total Memory: 3953 
MB, used: 2048 MB 
2013-04-24 01:41:28.171 AUDIT nova.compute.claims 
[req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5 
117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e] 
[instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Memory limit: 5929 
MB, free: 3881 MB 
2013-04-24 01:41:28.172 AUDIT nova.compute.claims 
[req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5 
117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e] 
[instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total Disk: 225 GB, 
used: 15 GB 
2013-04-24 01:41:28.172 AUDIT nova.compute.claims 
[req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5 
117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e] 
[instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Disk limit not 
specified, defaulting to unlimited 
2013-04-24 01:41:28.173 AUDIT nova.compute.claims 
[req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5 
117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e] 
[instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Total CPU: 2 VCPUs, 
used: 2 VCPUs 
2013-04-24 01:41:28.173 AUDIT nova.compute.claims 
[req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5 
117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e] 
[instance: aa46445e-1f86-4a5a-8002-a7703ff98648] CPU limit not 
specified, defaulting to unlimited 
2013-04-24 01:41:28.174 AUDIT nova.compute.claims 
[req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5 
117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e] 
[instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Claim successful 
2013-04-24 01:41:33.998 INFO nova.virt.libvirt.driver 
[req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5 
117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e] 
[instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Creating image 
2013-04-24 01:41:34.281 INFO nova.virt.libvirt.driver 
[req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5 
117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e] 
[instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Injecting files into 
image 65eaa160-d0e7-403e-a52c-90bea3c22cf7 
2013-04-24 01:41:36.534 INFO nova.virt.libvirt.firewall 
[req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5 
117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e] 
[instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Called 
setup_basic_filtering in nwfilter 
2013-04-24 01:41:36.535 INFO nova.virt.libvirt.firewall 
[req-6b571df0-9608-4bc5-93a7-afb3a2f17ba5 
117e0142ab40418eafc56955f0ab2ba3 7a416e3eaa814734bda41ffca7c2d01e] 
[instance: aa46445e-1f86-4a5a-8002-a7703ff98648] Ensuring static 
filters 
2013-04-24 01:41:38.555 13316 INFO nova.compute.manager [-] Lifecycle 
event 0 on VM aa46445e-1f86-4a5a-8002-a7703ff98648 
2013-04-24 01:41:38.763 13316 INFO nova.virt.libvirt.driver [-] 
[instance: 

Re: [Openstack] [OpenStack] Grizzly: Does metadata service work when overlapping IPs is enabled

2013-04-25 Thread Leen Besselink
Balu ?

Have you tried looking in the /var/lib/dhcp directory (the directory might 
depend
on the DHCP-client you are using) of the Ubuntu image ?

As this isn't a clean image but it has been connected to an other network, 
maybe a
previous DHCP-server told it to add the route ? And now the client is just 
re-using
an old lease ?

On Wed, Apr 24, 2013 at 10:13:52PM -0700, Aaron Rosen wrote:
 I'm not sure but if it works fine with the ubuntu cloud image and not with
 your ubuntu image than there is something in your image adding that route.
 
 
 On Wed, Apr 24, 2013 at 10:06 PM, Balamurugan V G
 balamuruga...@gmail.comwrote:
 
  Hi Aaron,
 
  I tried the image you pointed and it worked fine out of the box. That is
  it did not get the route to 169.254.0.0.26 on boot and I am able to
  retrieve info from metadata service. The image I was using earlier is a
  Ubuntu 12.04 LTS desktop image. What do you think could be wrong with my
  image? Its almost the vanilla Ubuntu image, I have not installed much. on
  it.
 
  Here is the quantum details you asked and more. This was taken before I
  tried the image you pointed to. And by the way, I have not added any host
  route as well.
 
  root@openstack-dev:~# quantum router-list
 
  +--+-++
  | id   | name| external_gateway_info
 |
 
  +--+-++
  | d9e87e85-8410-4398-9ddd-2dbc36f4b593 | router1 | {network_id:
  e8862e1c-0233-481f-b284-b027039feef7} |
 
  +--+-++
  root@openstack-dev:~# quantum net-list
 
  +--+-+-+
  | id   | name| subnets
  |
 
  +--+-+-+
  | c4a7475e-e33f-47d0-a6ff-d0cf50c012d7 | net1|
  ecdfe002-658e-4174-a33c-934ba09179b7 192.168.2.0/24 |
  | e8862e1c-0233-481f-b284-b027039feef7 | ext_net |
  783e6a47-d7e0-46ba-9c2a-55a92406b23b 10.5.12.20/24  |
 
  +--+-+-+
  *root@openstack-dev:~# quantum subnet-list
 
  +--+--++--+
  | id   | name | cidr   |
  allocation_pools |
 
  +--+--++--+
  | 783e6a47-d7e0-46ba-9c2a-55a92406b23b |  | 10.5.12.20/24  |
  {start: 10.5.12.21, end: 10.5.12.25} |
  | ecdfe002-658e-4174-a33c-934ba09179b7 |  | 192.168.2.0/24 |
  {start: 192.168.2.2, end: 192.168.2.254} |*
 
  +--+--++--+
  root@openstack-dev:~# quantum port-list
 
  +--+--+---++
  | id   | name | mac_address   |
  fixed_ips
 |
 
  +--+--+---++
  | 193bb8ee-f50d-4b1f-87ae-e033c1730953 |  | fa:16:3e:91:3d:c0 |
  {subnet_id: 783e6a47-d7e0-46ba-9c2a-55a92406b23b, ip_address:
  10.5.12.21}  |
  | 19bce882-c746-497b-b401-dedf5ab605b2 |  | fa:16:3e:97:89:f6 |
  {subnet_id: 783e6a47-d7e0-46ba-9c2a-55a92406b23b, ip_address:
  10.5.12.23}  |
  | 41ab9b15-ddc9-4a00-9a34-2e3f14e7e92f |  | fa:16:3e:45:58:03 |
  {subnet_id: ecdfe002-658e-4174-a33c-934ba09179b7, ip_address:
  192.168.2.2} |
  | 4dbc3c55-5763-4cfa-a7c1-81b254693e87 |  | fa:16:3e:83:a7:e4 |
  {subnet_id: ecdfe002-658e-4174-a33c-934ba09179b7, ip_address:
  192.168.2.3} |
  | 59e69986-6e8a-4f1e-a754-a1d421cdebde |  | fa:16:3e:91:ee:76 |
  {subnet_id: ecdfe002-658e-4174-a33c-934ba09179b7, ip_address:
  192.168.2.1} |
  | 65167653-f6ff-438b-b465-f5dcc8974549 |  | fa:16:3e:a7:77:0b |
  {subnet_id: 783e6a47-d7e0-46ba-9c2a-55a92406b23b, ip_address:
  10.5.12.24}  |
 
  +--+--+---++
  root@openstack-dev:~# quantum floatingip-list
 
  +--+--+-+--+
  | id   | fixed_ip_address |
  floating_ip_address | 

Re: [Openstack] Ceilometer does not collect metrics like vcpus and memory

2013-04-25 Thread Nicolas Barcet
Hello Giuseppe,

I am not sure which Hypervisor you are using, but it seems that it is not
KVM which would be the reason why only partial information is collected.
 At this time, KVM is the only fully instrumented Hypervisor, even though
we would really welcome patches from users of other hypervisors.

Best,
Nick


On Wed, Apr 24, 2013 at 5:11 PM, Giuseppe Civitella 
giuseppe.civite...@gmail.com wrote:

 Hi all,

 I'm trying to collect Ceilometer's metrics from my test install of
 Openstack Grizzly.
 I'm able to collect most of the metrics from the central collector and the
 nova-compute agents.
 But I'm still missing some values like memory and vcpus.
 This is an abstract from ceilometer's log on a nova-compute node:

 http://paste.openstack.org/show/36567/

 vcpus and memory_mb are empty values.
 Any idea about how to get them?

 Thanks a lot
 Giuseppe






 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




-- 
Nicolas Barcet nico...@barcet.com
a.k.a. nijaba, nick
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Should we discourage KVM block-based live migration?

2013-04-25 Thread Sylvain Bauza
Waiting Daniel's reply, but afaik, the new NBD server is available since 
qemu-1.4 and libvirt 1.0.2

Daniel, feel free to confirm or blame me.

Btw, kvm capabilities are available in upstream qemu since qemu-1.3 
which works like a charm with Nova (Folsom).

-Sylvain

Le 24/04/2013 23:23, Lorin Hochstein a écrit :



On Wed, Apr 24, 2013 at 11:59 AM, Daniel P. Berrange d...@berrange.com 
mailto:d...@berrange.com wrote:


On Wed, Apr 24, 2013 at 11:48:35AM -0400, Lorin Hochstein wrote:
 In the docs, we describe how to configure KVM block-based live
migration,
 and it has the advantage of avoiding the need for shared storage of
 instances.

 However, there's this email from Daniel Berrangé from back in
Aug 2012:
 http://osdir.com/ml/openstack-cloud-computing/2012-08/msg00293.html

 Block migration is a part of the KVM that none of the upstream
developers
 really like, is not entirely reliable, and most distros
typically do not
 want to support it due to its poor design (eg not supported in
RHEL).

 It is quite likely that it will be removed in favour of an
alternative
 implementation. What that alternative impl will be, and when I will
 arrive, I can't say right now.

 Based on this info, the OpenStack Ops guide currently recommends
against
 using block-based live migration, but the Compute Admin guide has no
 warnings about this.

 I wanted to sanity-check against the mailing list to verify that
this was
 still the case. What's the state of block-based live migration
with KVM?
 Should we say be dissuading people from using it, or is it
reasonable for
 people to use it?

What I wrote above about the existing impl is still accurate. The new
block migration code is now merged into libvirt and makes use of an
NBD server built-in to the QMEU process todo block migration. API
wise it should actually work in the same way as the existing
deprecated
block migration code.  So if you have new enough libvirt and new
enough
KVM, it probably ought to 'just work' with openstack without needing
any code changes in nova. I have not actually tested this myself
though.

So we can probably update the docs - but we'd want to checkout just
what precise versions of libvirt + qemu are needed, and have someone
check that it does in fact work.


Thanks, Daniel. I can update the docs accordingly. How can I find out 
what are the minimum versions of libvirt and qemu are needed?


Also, I noticed you said qemu and not kvm, and I see that 
http://wiki.qemu.org/KVM says that qemu-kvm fork for x86 is 
deprecated, use upstream QEMU now.  Is it the case now that when 
using KVM as the hypervisor for a host, an admin will just install a 
qemu package instead of a qemu-kvm package to get the userspace stuff?


Lorin




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [OpenStack] Grizzly: Does metadata service work when overlapping IPs is enabled

2013-04-25 Thread Leen Besselink
On Thu, Apr 25, 2013 at 12:45:03PM +0530, Balamurugan V G wrote:
 Hi Leen,
 
 I do not have any other DHCP sever which can do this other than the one
 created by quantum. Infact, If i delete the route manually and restart the
 network(interface down and up), I get the routed added back. Please refer
 below:
 

Then the an other cause could be that you added something in /etc to try and 
fix a
problem you had before.

Have you checked that yet ?:

grep -R 169.254 /etc/ 2/dev/null

Just to be sure.



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] nova-network no ip for vm

2013-04-25 Thread Arindam Choudhury
Hi,

I am really stuck, any help will be highly appreciated.

I installed a two node openstack deployment on debian wheezy:

# nova-manage service list
Binary   Host Zone Status   
  State Updated_At
nova-network aopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-certaopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-conductor   aopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-consoleauth aopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-scheduler   aopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-network aopcso1  internal enabled  
  :-)   2013-04-25 08:05:15
nova-compute aopcso1  nova enabled  
  :-)   2013-04-25 08:05:15

# nova-manage network list
id   IPv4  IPv6   start address  DNS1   
DNS2   VlanID projectuuid   
1192.168.100.0/24  None   192.168.100.2  8.8.4.4
None   None   None   
5f6a8ef4-7003-48f8-8922-5303f37d0ce8

But when boot up a vm(the cirros from the tutorial), it dont get any ip.

Starting network...
udhcpc (v1.18.5) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40network failed

### ifconfig a
eth0  Link encap:Ethernet  HWaddr FA:16:3E:CD:3B:97  
  inet6 addr: fe80::f816:3eff:fecd:3b97/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1361 errors:0 dropped:6 overruns:0 frame:0
  TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:159974 (156.2 KiB)  TX bytes:902 (902.0 B)

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

In controller or compute node the nova-network.log does not generate any 
logging of events.

on the horizon I dont have any network listing.



  ___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] horizon error

2013-04-25 Thread Heiko Krämer
Hi Mballo,

looks good to me. Please check your keystone endpoints too. You need to
check the other service parts too if all endpoints are correct.
Do you see on your project page your images, networks and volumes? It's
mostly a good indicator if your horizon can communicate with these API's.



Greetings
Heiko

Am 23.04.2013 18:12, schrieb Mballo Cherif:

 Hi Hiho,

 Thanks you for your answers. In fact when I lauch nova-manage service
 list I get this:

  

 /nova-certopenstack-grizzly.linux.gem 
 internal enabled:-)   2013-04-23 16:05:03/

 /nova-conductor   openstack-grizzly.linux.gem 
 internal enabled:-)   2013-04-23 16:05:03/

 /nova-consoleauth openstack-grizzly.linux.gem 
 internal enabled:-)   2013-04-23 16:05:03/

 /nova-scheduler   openstack-grizzly.linux.gem 
 internal enabled:-)   2013-04-23 16:05:03/

 /nova-compute openstack-grizzly.linux.gem 
 nova enabled:-)   2013-04-23 16:05:04/

  

  

 is it normal not having nova-api in the list ?. Otherwise when I check
 service nova-api status the service is running well (/nova-api
 start/running, process 13421/)

  

  

  

 *From:*Openstack
 [mailto:openstack-bounces+cherif.mballo=gemalto@lists.launchpad.net]
 *On Behalf Of *Heiko Krämer
 *Sent:* mardi 23 avril 2013 17:30
 *To:* openstack@lists.launchpad.net
 *Subject:* Re: [Openstack] horizon error

  

 Hiho,

 this occurs if an service not running or not reachable. In your case
 mostly api or compute.
 Check if each service are running and reachable from your Horizon host.

 Check if all endpoints in keystone are configured correctly.

 Greetings
 Heiko


 On 23.04.2013 17:25, Mballo Cherif wrote:

 Hi everybody, when I'm authenticate with horizon I have this
 message *Error: *Unauthorized: Unable to retrieve usage
 information. And *Error: *Unauthorized: Unable to retrieve quota
 information.

 How can I fix this issue?

  

 Thanks you for your help!

  

 Sheriff!

  




 ___

 Mailing list: https://launchpad.net/~openstack 
 https://launchpad.net/%7Eopenstack

 Post to : openstack@lists.launchpad.net 
 mailto:openstack@lists.launchpad.net

 Unsubscribe : https://launchpad.net/~openstack 
 https://launchpad.net/%7Eopenstack

 More help   : https://help.launchpad.net/ListHelp

  


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] nova-network no ip for vm

2013-04-25 Thread Staicu Gabriel
Hi,

A place to look for eventually error messages is also /var/log/messages. Look 
for dnsmasq related message and post them here.

Regards,
Gabriel



 From: Arindam Choudhury arin...@live.com
To: openstack openstack@lists.launchpad.net 
Sent: Thursday, April 25, 2013 11:10 AM
Subject: [Openstack] nova-network no ip for vm
 


 
Hi,

I am really stuck, any help will be highly appreciated.

I installed a two node openstack deployment on debian wheezy:

# nova-manage service list
Binary   Host Zone Status   
  State Updated_At
nova-network aopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-cert    aopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-conductor   aopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-consoleauth aopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-scheduler   aopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-network aopcso1  internal enabled  
  :-)   2013-04-25 08:05:15
nova-compute aopcso1  nova enabled  
  :-)   2013-04-25 08:05:15

# nova-manage network list
id       IPv4      IPv6       start address      DNS1   
        DNS2       VlanID     project        uuid   
1        192.168.100.0/24      None       192.168.100.2      8.8.4.4
        None       None       None       
5f6a8ef4-7003-48f8-8922-5303f37d0ce8

But when boot up a vm(the cirros from the tutorial), it dont get any ip.

Starting network...
udhcpc (v1.18.5) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40network failed

### ifconfig a
eth0  Link encap:Ethernet  HWaddr FA:16:3E:CD:3B:97  
  inet6 addr: fe80::f816:3eff:fecd:3b97/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1361 errors:0 dropped:6 overruns:0 frame:0
  TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:159974 (156.2 KiB)  TX bytes:902 (902.0 B)

lo    Link encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

In controller or compute node the nova-network.log does not generate any 
logging of events.

on the horizon I dont have any network listing.




___
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Keystone Grizzly install

2013-04-25 Thread Viktor Viking
Community,

That did the trick. Just install repoze-lru and keystone can start.

--
Viktor


On Thu, Apr 25, 2013 at 12:09 AM, Viktor Viking
viktor.viking...@gmail.comwrote:

 Hi Dolph,

 Now I got an exception. It seems like I am missing repoze.lru. I will
 download and install it. I will let you know if it works.

 Thank you,
 Viktor



 On Wed, Apr 24, 2013 at 11:25 PM, Dolph Mathews 
 dolph.math...@gmail.comwrote:

 What happens when you run keystone-all directly?


 -Dolph


 On Wed, Apr 24, 2013 at 4:23 PM, Viktor Viking 
 viktor.viking...@gmail.com wrote:

 Community,

 I am trying to install Keystone Grizzly following these instructions:
 http://docs.openstack.org/trunk/openstack-compute/install/yum/content/install-keystone.html

 When I try to start the service (before db sync), I get the following
 error message: Starting keytonestartproc: exit status of parent of
 /usr/bin/keystone-all  1 failed.

 /var/log/keystone/keystone.log is not giving me any clue wrt what is
 wrong.

 Could anyone let me know where to look?
 Viktor

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] nova-network no ip for vm

2013-04-25 Thread Arindam Choudhury
Hi,

Thanks for your reply.

Here is the logs from /var/log/messages:

Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered 
promiscuous mode
Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) entering 
forwarding state
Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) entering 
forwarding state
Apr 25 11:14:55 aopcso1 kernel: [589272.014705] br100: port 2(vnet0) entering 
forwarding state

and the logs from /var/log/syslog:

Apr 25 11:14:07 aopcso1 dnsmasq[12485]: direcciónes /etc/hosts - 23 leídas
Apr 25 11:14:07 aopcso1 dnsmasq-dhcp[12485]: read 
/var/lib/nova/networks/nova-br100.conf
Apr 25 11:14:39 aopcso1 NetworkManager[3980]:SCPlugin-Ifupdown: devices 
added (path: /sys/devices/virtual/net/vnet0, iface: vnet0)
Apr 25 11:14:39 aopcso1 NetworkManager[3980]:SCPlugin-Ifupdown: device 
added (path: /sys/devices/virtual/net/vnet0, iface: vnet0): no ifupdown 
configuration found.
Apr 25 11:14:39 aopcso1 NetworkManager[3980]: warn 
/sys/devices/virtual/net/vnet0: couldn't determine device driver; ignoring...
Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered 
promiscuous mode
Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) entering 
forwarding state
Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) entering 
forwarding state
Apr 25 11:14:44 aopcso1 ntpd[4796]: Listen normally on 67 vnet0 
fe80::fc16:3eff:fe8a:f597 UDP 123
Apr 25 11:14:44 aopcso1 ntpd[4796]: peers refreshed
Apr 25 11:14:50 aopcso1 kernel: [589267.164541] vnet0: no IPv6 routers present
Apr 25 11:14:55 aopcso1 kernel: [589272.014705] br100: port 2(vnet0) entering 
forwarding state




Date: Thu, 25 Apr 2013 01:53:02 -0700
From: gabriel_sta...@yahoo.com
Subject: Re: [Openstack] nova-network no ip for vm
To: arin...@live.com; openstack@lists.launchpad.net

Hi,
A place to look for eventually error messages is also /var/log/messages. Look 
for dnsmasq related message and post them here.
Regards,Gabriel
From: Arindam Choudhury arin...@live.com
 To: openstack openstack@lists.launchpad.net 
 Sent: Thursday, April 25, 2013 11:10 AM
 Subject: [Openstack] nova-network no ip for vm
   



Hi,

I am really stuck, any help will be highly appreciated.

I installed a two node openstack deployment on debian wheezy:

# nova-manage service list
Binary   Host Zone Status   
  State Updated_At
nova-network aopcach  internal enabled  
  :-)   2013-04-25
 08:05:18
nova-certaopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-conductor   aopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-consoleauth aopcach  internal
 enabled:-)   2013-04-25 08:05:18
nova-scheduler   aopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-network aopcso1  internal enabled  
  :-)   2013-04-25 08:05:15
nova-compute aopcso1 
 nova enabled:-)   2013-04-25 08:05:15

# nova-manage network list
id   IPv4  IPv6   start address  DNS1   
DNS2   VlanID projectuuid   
1192.168.100.0/24  None  
 192.168.100.2  8.8.4.4None   None  
 None   5f6a8ef4-7003-48f8-8922-5303f37d0ce8

But when boot up a vm(the cirros from the tutorial), it dont get any ip.

Starting network...
udhcpc (v1.18.5) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40network failed

### ifconfig a
eth0  Link encap:Ethernet  HWaddr FA:16:3E:CD:3B:97  
  inet6 addr: fe80::f816:3eff:fecd:3b97/64 Scope:Link
  UP
 BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1361 errors:0 dropped:6 overruns:0 frame:0
  TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:159974 (156.2 KiB)  TX bytes:902 (902.0 B)

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0
 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

In controller or compute node the nova-network.log does not generate any 
logging of events.

on the horizon I dont have any network listing.



  

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : 

Re: [Openstack] Should we discourage KVM block-based live migration?

2013-04-25 Thread Daniel P. Berrange
On Wed, Apr 24, 2013 at 05:23:11PM -0400, Lorin Hochstein wrote:
 On Wed, Apr 24, 2013 at 11:59 AM, Daniel P. Berrange d...@berrange.comwrote:
 
  On Wed, Apr 24, 2013 at 11:48:35AM -0400, Lorin Hochstein wrote:
   In the docs, we describe how to configure KVM block-based live migration,
   and it has the advantage of avoiding the need for shared storage of
   instances.
  
   However, there's this email from Daniel Berrangé from back in Aug 2012:
   http://osdir.com/ml/openstack-cloud-computing/2012-08/msg00293.html
  
   Block migration is a part of the KVM that none of the upstream
  developers
   really like, is not entirely reliable, and most distros typically do not
   want to support it due to its poor design (eg not supported in RHEL).
  
   It is quite likely that it will be removed in favour of an alternative
   implementation. What that alternative impl will be, and when I will
   arrive, I can't say right now.
  
   Based on this info, the OpenStack Ops guide currently recommends against
   using block-based live migration, but the Compute Admin guide has no
   warnings about this.
  
   I wanted to sanity-check against the mailing list to verify that this was
   still the case. What's the state of block-based live migration with KVM?
   Should we say be dissuading people from using it, or is it reasonable for
   people to use it?
 
  What I wrote above about the existing impl is still accurate. The new
  block migration code is now merged into libvirt and makes use of an
  NBD server built-in to the QMEU process todo block migration. API
  wise it should actually work in the same way as the existing deprecated
  block migration code.  So if you have new enough libvirt and new enough
  KVM, it probably ought to 'just work' with openstack without needing
  any code changes in nova. I have not actually tested this myself
  though.
 
  So we can probably update the docs - but we'd want to checkout just
  what precise versions of libvirt + qemu are needed, and have someone
  check that it does in fact work.
 
 
 Thanks, Daniel. I can update the docs accordingly. How can I find out what
 are the minimum versions of libvirt and qemu are needed?
 
 Also, I noticed you said qemu and not kvm, and I see that
 http://wiki.qemu.org/KVM says that qemu-kvm fork for x86 is deprecated,
 use upstream QEMU now.  Is it the case now that when using KVM as the
 hypervisor for a host, an admin will just install a qemu package instead
 of a qemu-kvm package to get the userspace stuff?

It depends on the distro to be honest. eg on Fedora you'd use qemu-kvm
which is a virtual package which will pull in qemu-system-$ARCH for your
particular host.

Regards,
Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] (no subject)

2013-04-25 Thread daniels cai
hi community

i create a port which contains two subnet
and quantum returns the following json.

{
port: {
status: DOWN,
name: ,
admin_state_up: true,
network_id: f9d3bd8e-377b-4f21-bfc6-64ae4257e44d,
tenant_id: 82da519b676d400ab24e9ee38d138c3c,
binding:vif_type: ovs,
device_owner: ,
binding:capabilities: {
port_filter: false
},
mac_address: fa:16:3e:e8:0c:75,
fixed_ips: [
{
subnet_id: 3a6c08b6-cb0e-4949-9e3f-dae76fc98741,
ip_address: 20.20.1.1
},
{
subnet_id: dfe2a150-5a87-4256-80c7-fd88b9dae113,
ip_address: 20.20.2.20
}
],
id: 843cb8da-ccac-4550-b777-fa1455ee02fe,
device_id: 
}
}

when i try to boot a vm with this port (command showed below)


nova boot --nic port-id=f9d3bd8e-377b-4f21-bfc6-64ae4257e44d --key-name hi
--flavor 1 --block_device_mapping
vda=21f4dfc5-9752-4f5e-8133-0540a1dc3eb5:::0 vm7


the vm's network doesn't work , dhcp doesn't work and only one nic showed .
( if only one subnet specified, dhcp and other plugins works fine)

any one can help?

Daniels Cai
http://dnscai.com
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Ceilometer Install

2013-04-25 Thread Riki Arslan
I have encountered other problems too.

First of all, when starting the Central Agent I have had Glance endpoint
404 not found errors. As, Julien pointed out (
https://bugs.launchpad.net/ceilometer/+bug/1083104), I have removed the
v1 from the Glance URLs and it worked well.

Secondly, when starting the API Server, I have received ImportError: No
module named mako.template error. Thus, I have installed python-mako
module (sudo apt-get install python-mako), and the error disappeared.

Now, I am receiving another error within the API Server. The error is as
follows:
AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'

Do you think it has something to do with mod_wsgi (
http://docs.openstack.org/developer/ceilometer/install/mod_wsgi.html)?

I would appreciate your help on this.

Thanks.


On Thu, Apr 25, 2013 at 12:27 AM, Riki Arslan riki.ars...@cloudturk.netwrote:

 Hi Doug,

 Your email helped me. It was actually glanceclient version 0.5.1 that was
 causing the conflict. After updating it, the conflict error disappeared.

 I hope this would help someone else too.

 Thanks again.


 On Wed, Apr 24, 2013 at 11:49 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Wed, Apr 24, 2013 at 9:17 AM, Riki Arslan 
 riki.ars...@cloudturk.netwrote:

 Hi,

 We are trying to install ceilometer-2013.1~g2.tar.gz which presumably
 has Folsom compatibility.

 The requirment is python-keystoneclient=0.2,0.3 and we have
 the version 2.3.

 But, still, setup quits with the following message:

 error: Installed distribution python-keystoneclient 0.2.3
 conflicts with requirement python-keystoneclient=0.1.2,0.2

 The funny thing is, although pip-requires states
 python-keystoneclient=0.2,0.3, the error message complains that it is
 not python-keystoneclient=0.1.2,0.2.


 Something else you have installed already wants an older version of the
 keystone client, so the installation of ceilometer is not able to upgrade
 to the version we need.

 Doug



 Your help is greatly appreciated.

 Thank you in advance.

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [OpenStack][Swift] Swift Storage nodes leave db.pending files after failed requests

2013-04-25 Thread Sergio Rubio
For the sake of completion, the whole thing was a false alarm, has
nothing to do with db.pending files and it has been documented here:

https://bugs.launchpad.net/swift/+bug/1172358


On Tue, Apr 23, 2013 at 11:39 AM, Sergio Rubio rubi...@frameos.org wrote:
 Howdy folks,

 While populating an empty Swift test cluster with
 swift-dispersion-populate some container creation requests failed,
 leaving 'db.pending' files.

 This is standard operation I think
 (http://docs.openstack.org/developer/swift/overview_architecture.html#updaters)
 however the pending files are never removed (the updaters aren't
 picking up those changes?) and I can see periodic errors in the
 storage node error log:

 pre
 root@swift-002:/srv/node# find|grep pending
 ./cd6b760c-bf47-4733-b7bb-23659dd8ee1d/accounts/523880/adc/e2cfc6be58be71d5ad6111364fff0adc/e2cfc6be58be71d5ad6111364fff0adc.db.pending
 ./7e0cfcfc-7c6e-41a4-adc8-e4173147bd2a/accounts/523880/adc/e2cfc6be58be71d5ad6111364fff0adc/e2cfc6be58be71d5ad6111364fff0adc.db.pending
 ./7cf651d7-e2f7-4dc4-ada0-7cd0dc832449/containers/498724/d1d/bd66b837c7b9a95dec68b3ca05a75d1d/bd66b837c7b9a95dec68b3ca05a75d1d.db.pending
 /pre


 pre
 Apr 23 11:06:26 swift-001 account-server ERROR __call__ error with PUT
 /d3829495-9f10-4075-a558-f99fb665cfe2/464510/AUTH_aeedb7bdcb8846599e2b6b87bb8a947f/dispersion_916bc3a9cc1548aca41be6633c1bd194
 : #012Traceback (most recent call last):#012  File
 /usr/lib/python2.7/dist-packages/swift/account/server.py, line 333,
 in __call__#012res = method(req)#012  File
 /usr/lib/python2.7/dist-packages/swift/common/utils.py, line 1558,
 in wrapped#012return func(*a, **kw)#012  File
 /usr/lib/python2.7/dist-packages/swift/common/utils.py, line 520, in
 _timing_stats#012resp = func(ctrl, *args, **kwargs)#012  File
 /usr/lib/python2.7/dist-packages/swift/account/server.py, line 112,
 in PUT#012req.headers['x-bytes-used'])#012  File
 /usr/lib/python2.7/dist-packages/swift/common/db.py, line 1431, in
 put_container#012raise DatabaseConnectionError(self.db_file, DB
 doesn't exist)#012DatabaseConnectionError: DB connection error
 (/srv/node/d3829495-9f10-4075-a558-f99fb665cfe2/accounts/464510/adc/e2cfc6be58be71d5ad6111364fff0adc/e2cfc6be58be71d5ad6111364fff0adc.db,
 0):#012DB doesn't exist
 /pre

 The test cluster has two storage nodes with 12 drives each, packaged
 Swift 1.8.0 from Ubuntu Cloud Archive and the account/container
 configuration is the following:
 https://gist.github.com/rubiojr/6ea3d0ea0c4d00949d33

 The cluster is fully operational and there are no other known issues
 ATM. I can easily reproduce the problem by emptying the cluster and
 populating it again with swift-dispersion-populate.

 I've exhausted all the possibilities (bug reports, mailing lists,
 google, etc) so I decided to ask before start digging the source code
 trying to gather evidence to open a bug report.

 If anyone can shed some light on the issue that would be great.

 Thanks!

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Hava sumit presentations

2013-04-25 Thread Anton Massoud
Hi,
Does anybody know where to find all the presentation material for the sessions 
held during Havana summit?
I'm especially interested in the NOVA related ones.
/Anton
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Hava sumit presentations

2013-04-25 Thread Jarret Raim
http://www.openstack.org/summit/portland-2013/session-videos

Jarret

From: Openstack 
[mailto:openstack-bounces+jarret.raim=rackspace@lists.launchpad.net] On 
Behalf Of Anton Massoud
Sent: Thursday, April 25, 2013 6:14 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] Hava sumit presentations

Hi,
Does anybody know where to find all the presentation material for the sessions 
held during Havana summit?
I'm especially interested in the NOVA related ones.
/Anton
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] New instances stuck in BUILD

2013-04-25 Thread YIP Wai Peng
Dear all,

I am running openstack grizzly on 2 nodes, with multi-host options and
without conductor.

Node 1 has compute, api, network, etc

Node 2 has compute, network

When launching new instances, those that are launched on the 1st node
launches fine. Those not on node 2 gets stuck in BUILD. nova show xxx
prints the following (snipped)

| status  | BUILD
   |
| updated | 2013-04-25T11:37:29Z
|
| OS-EXT-STS:task_state   | scheduling

I've been reviewing the logs and there are no errors. I have a few
questions and hope someone can help.

1) How do I start tracing this error?

2) In multi-host mode, are the compute nodes supposed to connect to AMQP of
the main node, or themselves? I specified rabbit_host and it still shows
nova-compute connecting to localhost.

3) In scheduler.log, there is the following
2013-04-25 19:37:29.064 WARNING nova.scheduler.host_manager
[req-2272a45e-8e8a-4af0-96cd-b8a387e051fa 91cd099661f54df7bad0c7248c0451ca
c91d0ed52321439c8b7d0c05b89bb0c8] No service for compute ID 2
Is this what is causing the problem?

4) If I were to use conductor in multi-host, do I need a conductor for each
compute node? If not, how do I specify where is the conductor?

Any advice is greatly appreciated.

Thanks,
WP
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] nova-manage fails with unable to open database file None None

2013-04-25 Thread Daniel Ellison
Hi all,

I've come across a situation that has stumped me. I've searched the archives 
here but can find no solution. I /did/ find a bug filed in Launchpad 
(https://bugs.launchpad.net/nova/+bug/1169439) that may be what's happening, 
but there's no solution.

When I run the command nova-manage --debug service list I get this output, 
the last line being most pertinent:

2013-04-25 07:36:59.797 15203 DEBUG nova.servicegroup.api [-] ServiceGroup 
driver defined as an instance of db __new__ 
/usr/lib/python2.7/dist-packages/nova/servicegroup/api.py:61
2013-04-25 07:36:59.869 DEBUG nova.openstack.common.lockutils 
[req-4383e6cf-d92c-4ab0-bbea-6db89825c073 None None] Got semaphore 
dbapi_backend for method __get_backend... inner 
/usr/lib/python2.7/dist-packages/nova/openstack/common/lockutils.py:186
Command failed, please check log for more info
2013-04-25 07:37:00.092 CRITICAL nova [req-4383e6cf-d92c-4ab0-bbea-6db89825c073 
None None] (OperationalError) unable to open database file None None

This happens with almost all nova-manage commands. Additionally, there is /no/ 
log output in /var/log/nova-manage.log. The log file is there, but has zero 
length.

The bug I referenced implies that nova-manage is trying to open a sqlite 
database despite the fact that a MySQL database has been specified in 
nova.conf. I have definitely defined MySQL as the database, and it works fine 
in all other cases. I've logged into MySQL with the credentials I've defined in 
nova.conf with no problem. I've removed the nova.sqlite file, stopped/started 
all of the nova-* services and still I get this error.

Is this familiar to anyone?

Thanks,
Daniel
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] nova-network no ip for vm

2013-04-25 Thread Arindam Choudhury
Hi,

The problem was nbd module. I installed it and now it good.

Date: Thu, 25 Apr 2013 02:47:39 -0700
From: gabriel_sta...@yahoo.com
Subject: Re: [Openstack] nova-network no ip for vm
To: arin...@live.com; openstack@lists.launchpad.net

Hi,
What I would do now it to make a tcpdum on interface br100 to look for the 
bootpc packets that the port receives and sends.Also here from your paste of 
ifconfig -a I don't see the bridge interface...
Regards,Gabriel
From: Arindam Choudhury arin...@live.com
 To: Staicu Gabriel gabriel_sta...@yahoo.com; openstack 
openstack@lists.launchpad.net 
 Sent: Thursday, April 25, 2013 12:17 PM
 Subject: RE: [Openstack] nova-network no ip for vm
   



Hi,

Thanks for your reply.

Here is the logs from /var/log/messages:

Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered 
promiscuous mode
Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) entering 
forwarding state
Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) entering 
forwarding state
Apr 25 11:14:55 aopcso1 kernel: [589272.014705] br100: port 2(vnet0) entering 
forwarding state

and the logs from /var/log/syslog:

Apr 25 11:14:07 aopcso1 dnsmasq[12485]: direcciónes /etc/hosts - 23 leídas
Apr 25 11:14:07 aopcso1 dnsmasq-dhcp[12485]: read 
/var/lib/nova/networks/nova-br100.conf
Apr 25 11:14:39 aopcso1 NetworkManager[3980]:SCPlugin-Ifupdown: devices 
added (path: /sys/devices/virtual/net/vnet0, iface: vnet0)
Apr 25 11:14:39 aopcso1 NetworkManager[3980]:SCPlugin-Ifupdown: device 
added (path:
 /sys/devices/virtual/net/vnet0, iface: vnet0): no ifupdown configuration found.
Apr 25 11:14:39 aopcso1 NetworkManager[3980]: warn 
/sys/devices/virtual/net/vnet0: couldn't determine device driver; ignoring...
Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered 
promiscuous mode
Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) entering 
forwarding state
Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) entering 
forwarding state
Apr 25 11:14:44 aopcso1 ntpd[4796]: Listen normally on 67 vnet0 
fe80::fc16:3eff:fe8a:f597 UDP 123
Apr 25 11:14:44 aopcso1 ntpd[4796]: peers refreshed
Apr 25 11:14:50 aopcso1 kernel: [589267.164541] vnet0: no IPv6 routers present
Apr 25 11:14:55 aopcso1 kernel: [589272.014705] br100: port 2(vnet0) entering 
forwarding state




Date: Thu, 25 Apr
 2013 01:53:02 -0700
From: gabriel_sta...@yahoo.com
Subject: Re: [Openstack] nova-network no ip for vm
To: arin...@live.com; openstack@lists.launchpad.net

Hi,
A place to look for eventually error messages is also /var/log/messages. Look 
for dnsmasq related message and post them here.
Regards,Gabriel
From: Arindam Choudhury arin...@live.com
 To: openstack openstack@lists.launchpad.net 
 Sent: Thursday, April 25, 2013
 11:10 AM
 Subject: [Openstack] nova-network no ip for vm
   



Hi,

I am really stuck, any help will be highly appreciated.

I installed a two node openstack deployment on debian wheezy:

# nova-manage service list
Binary   Host Zone Status   
  State Updated_At
nova-network aopcach  internal enabled  
  :-)   2013-04-25
 08:05:18
nova-certaopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-conductor   aopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-consoleauth aopcach  internal
 enabled:-)   2013-04-25 08:05:18
nova-scheduler   aopcach  internal enabled  
  :-)   2013-04-25 08:05:18
nova-network aopcso1  internal enabled  
  :-)   2013-04-25 08:05:15
nova-compute aopcso1 
 nova enabled:-)   2013-04-25 08:05:15

# nova-manage network list
id   IPv4  IPv6   start address  DNS1   
DNS2   VlanID projectuuid   
1192.168.100.0/24  None  
 192.168.100.2  8.8.4.4None   None  
 None   5f6a8ef4-7003-48f8-8922-5303f37d0ce8

But when boot up a vm(the cirros from the tutorial), it dont get any ip.

Starting network...
udhcpc (v1.18.5) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40network failed

### ifconfig a
eth0  Link encap:Ethernet  HWaddr FA:16:3E:CD:3B:97  
  inet6 addr: fe80::f816:3eff:fecd:3b97/64 Scope:Link
  UP
 BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1361 errors:0 dropped:6 overruns:0 frame:0
  TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:159974 (156.2 KiB)  TX bytes:902 (902.0 B)

loLink encap:Local Loopback  
  

Re: [Openstack] Ceilometer Install

2013-04-25 Thread Doug Hellmann
On Thursday, April 25, 2013, Riki Arslan wrote:

 I have encountered other problems too.

 First of all, when starting the Central Agent I have had Glance endpoint
 404 not found errors. As, Julien pointed out (
 https://bugs.launchpad.net/ceilometer/+bug/1083104), I have removed the
 v1 from the Glance URLs and it worked well.

 Secondly, when starting the API Server, I have received ImportError: No
 module named mako.template error. Thus, I have installed python-mako
 module (sudo apt-get install python-mako), and the error disappeared.


Mako is a dependency do sqlalchemy, I think. Are you using the sqlalchemy
storage driver for ceilometer?



 Now, I am receiving another error within the API Server. The error is as
 follows:
 AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'


That sounds like a problem with the config module. Was there a full
traceback? If not, try adding the --debug option when starting the service.

Doug



 Do you think it has something to do with mod_wsgi (
 http://docs.openstack.org/developer/ceilometer/install/mod_wsgi.html)?

 I would appreciate your help on this.

 Thanks.


 On Thu, Apr 25, 2013 at 12:27 AM, Riki Arslan 
 riki.ars...@cloudturk.netjavascript:_e({}, 'cvml', 
 'riki.ars...@cloudturk.net');
  wrote:

 Hi Doug,

 Your email helped me. It was actually glanceclient version 0.5.1 that was
 causing the conflict. After updating it, the conflict error disappeared.

 I hope this would help someone else too.

 Thanks again.


 On Wed, Apr 24, 2013 at 11:49 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com javascript:_e({}, 'cvml',
 'doug.hellm...@dreamhost.com'); wrote:




 On Wed, Apr 24, 2013 at 9:17 AM, Riki Arslan 
 riki.ars...@cloudturk.netjavascript:_e({}, 'cvml', 
 'riki.ars...@cloudturk.net');
  wrote:

 Hi,

 We are trying to install ceilometer-2013.1~g2.tar.gz which presumably
 has Folsom compatibility.

 The requirment is python-keystoneclient=0.2,0.3 and we have
 the version 2.3.

 But, still, setup quits with the following message:

 error: Installed distribution python-keystoneclient 0.2.3
 conflicts with requirement python-keystoneclient=0.1.2,0.2

 The funny thing is, although pip-requires states
 python-keystoneclient=0.2,0.3, the error message complains that it is
 not python-keystoneclient=0.1.2,0.2.


 Something else you have installed already wants an older version of the
 keystone client, so the installation of ceilometer is not able to upgrade
 to the version we need.

 Doug



 Your help is greatly appreciated.

 Thank you in advance.

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net javascript:_e({}, 'cvml',
 'openstack@lists.launchpad.net');
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Ceilometer Install

2013-04-25 Thread Riki Arslan
I thought Ceilometer did not set a dependency on any DB drivers. I have
installed the driver Mongo using sudo pip install pymongo.

Regarding the current problem; the traceback is as follows:

Traceback (most recent call last):
  File /usr/local/bin/ceilometer-api, line 5, in module
pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
  File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
run_script
self.require(requires)[0].run_script(script_name, ns)
  File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235, in
run_script
execfile(script_filename, namespace, namespace)
  File
/usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
line 38, in module
service.prepare_service()
  File
/usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/service.py,
line 80, in prepare_service
cfg.CONF(argv[1:], project='ceilometer')
  File
/usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
line 1024, in __call__
self._cli_values, leftovers = self._parse_cli_opts(args)
  File
/usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
line 1527, in _parse_cli_opts
opt._add_to_cli(self._oparser, group)
  File
/usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
line 591, in _add_to_cli
container = self._get_argparse_container(parser, group)
  File
/usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
line 633, in _get_argparse_container
return group._get_argparse_group(parser)
AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'

Thank for the help.


On Thu, Apr 25, 2013 at 3:27 PM, Doug Hellmann
doug.hellm...@dreamhost.comwrote:



 On Thursday, April 25, 2013, Riki Arslan wrote:

 I have encountered other problems too.

 First of all, when starting the Central Agent I have had Glance endpoint
 404 not found errors. As, Julien pointed out (
 https://bugs.launchpad.net/ceilometer/+bug/1083104), I have removed the
 v1 from the Glance URLs and it worked well.

 Secondly, when starting the API Server, I have received ImportError: No
 module named mako.template error. Thus, I have installed python-mako
 module (sudo apt-get install python-mako), and the error disappeared.


 Mako is a dependency do sqlalchemy, I think. Are you using the sqlalchemy
 storage driver for ceilometer?



 Now, I am receiving another error within the API Server. The error is as
 follows:
 AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'


 That sounds like a problem with the config module. Was there a full
 traceback? If not, try adding the --debug option when starting the service.

 Doug



 Do you think it has something to do with mod_wsgi (
 http://docs.openstack.org/developer/ceilometer/install/mod_wsgi.html)?

 I would appreciate your help on this.

 Thanks.


 On Thu, Apr 25, 2013 at 12:27 AM, Riki Arslan 
 riki.ars...@cloudturk.netwrote:

 Hi Doug,

 Your email helped me. It was actually glanceclient version 0.5.1 that
 was causing the conflict. After updating it, the conflict error disappeared.

 I hope this would help someone else too.

 Thanks again.


 On Wed, Apr 24, 2013 at 11:49 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Wed, Apr 24, 2013 at 9:17 AM, Riki Arslan riki.ars...@cloudturk.net
  wrote:

 Hi,

 We are trying to install ceilometer-2013.1~g2.tar.gz which
 presumably has Folsom compatibility.

 The requirment is python-keystoneclient=0.2,0.3 and we have
 the version 2.3.

 But, still, setup quits with the following message:

 error: Installed distribution python-keystoneclient 0.2.3
 conflicts with requirement python-keystoneclient=0.1.2,0.2

 The funny thing is, although pip-requires states
 python-keystoneclient=0.2,0.3, the error message complains that it is
 not python-keystoneclient=0.1.2,0.2.


 Something else you have installed already wants an older version of the
 keystone client, so the installation of ceilometer is not able to upgrade
 to the version we need.

 Doug



 Your help is greatly appreciated.

 Thank you in advance.

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Fwd: Nova API Keypairs

2013-04-25 Thread Anne Gentle
Hi all, especially our friendly neighborhood Horizon developers -

Can you better explain to Jamie how keypair injection works and what
Compute API commands correspond with the Dashboard creation and association
of keypairs?

Thanks,
Anne

-- Forwarded message --
From: Jamie Marshall ijm...@hotmail.com
Date: Wed, Apr 24, 2013 at 11:59 PM
Subject: RE: Nova API Keypairs
To: Anne Gentle a...@openstack.org


Hello Anne,

Thanks for your answer. Yes I know how to add the keypairs through the
dashboard and then to log in using the SSH. My issue is replicating what
the dashboard is to be able to do what HORIZON is doing but by using only
the official NOVA REST API.

I build a SECURITY GROUP with SECURITY RULES
I select an IMAGE
I select a FLAVOR
I create a SERVER for tyhe selected IMAGE, FLAVOR and SECURITY GROUP
I then associate the FLOATING IP to the SERVER

I then wait for the SERVER to become available and then I install and
configure the application software.

All of this is done by the Accords Platform of CompatibleOne and works
great.

Now I need to push forward and be able to handle the KEYPAIRS in this
automatic sequence to be able to use images
that have not been prepared to include our COSACS application configuration
interface.

I do not want to use the METADATA and PERSONALITY since I have found that
it is not at all reliable being very much hypervisor dependant.

I must therefore rely on KEYPAIR injection to allow SSH and SCP access to
the automated tool set.

I can create, list, retrieve and delete KEYPAIRS using the NOVA REST API.

The only piece of information that eludes me is the way that the KEYPAIR is
to be attatched, injected or associated with a SERVER.
I see how it is done using the nova command line tool using the -key_name
keynamevalue option but this cannot be used for remote operation.

Someone in the OpenStack community must know how this works.

Sincerely
Jamie
CTO CompatibleOne

--
From: a...@openstack.org
Date: Wed, 24 Apr 2013 13:20:07 -0500

Subject: Re: Nova API Keypairs
To: ijm...@hotmail.com

If you only have Dashboard access, then you can still use ssh -i keyname to
log into the instance.

You can see this done in this demo:
http://www.youtube.com/watch?v=yNdIRCn6Mo8 On the launch instance dashboard
screen at about :55 you'll see adding a keypair using the dashboard. Then
in the Terminal when I use ssh to get to the instance I use the .pem file.

Some images may not allow this, however. Can you talk to your cloud
provider to better understand how to do what you're trying to do?

Anne

On Sat, Apr 20, 2013 at 5:00 AM, Jamie Marshall ijm...@hotmail.com wrote:

Dear Thierry and Anne,

I am writing to you to try and find precise information concerning the use
of keypairs through the NOVA API for OpenStack. The documentation that is
currently available via api.openstack.org show how key pairs may be
created, via POST, retrieved and listed, via GET, and of course deleted.
There is however no perspective with respect to the use of the key pair
with a deployed compute or server instance. There is information dating
from early 2012 which leands me to believe that the relation between the
key pair and a compute instance is through the instance name. This is not
clear to me since the standard nova tool uses a key_name command line
switch to specify a previously created key pair name to be associated with
the soon to be created compute instance.  There is currently no reference
to a key pair name attribute or element in the official API description of
the request message for the POST /servers request. I need to be able to
manage this aspect completly within the OpenStack PROCCI interface of the
CompatibleOne Accords Platform and would appreciate if either of you could
point me to the corresponding documents or persons that would allow me to
complete this final aspect of OpenStack Automated provisioning.

Sincerely
Jamie Marshall
CTO CompatibleOne
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Fwd: Nova API Keypairs

2013-04-25 Thread Dean Troyer
On Thu, Apr 25, 2013 at 8:34 AM, Anne Gentle a...@openstack.org wrote:
 Can you better explain to Jamie how keypair injection works and what Compute
 API commands correspond with the Dashboard creation and association of
 keypairs?

I'll take a stab at the basic use of keypairs from the Nova CLI.  I
don't think Horizon does anything drastically different than this.

DevStack has an example in
https://github.com/openstack-dev/devstack/blob/master/exercises/boot_from_volume.sh
that may be useful.  Lines 123-129 demonstrate removing an old keypair
and adding a new one with the same name. (In the DevStack case, a new
keypair is generated on every run, this is not how things normally
work, hence the delete.)  This shows how Nova will generate the pair
and return the private key as the output.  You must capture it then,
there is no way to get it later.  Line 161 shows how to use it during
the server boot process.

The other way is to use existing ssh keypairs and is how I do things
in my own scripts.  Add an existing ssh public key to Nova (set
KEYNAME to something unique, I often use `hostname`):

# ensure keypair is present
if ! nova keypair-list | grep -q $KEYNAME; then
nova keypair-add --pub_key=$HOME/.ssh/id_rsa.pub $KEYNAME
echo Added keypair for $KEYNAME
fi
KEY=--key-name=$KEYNAME

Then, later in the nova boot command:

nova boot ... $KEY ... servername

In either case you should be able to ssh directly into the instance.
In the first case (Nova generating the keypair) remember to tell ssh
to use the private file with -i private-key-file.

dt

--

Dean Troyer
dtro...@gmail.com

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Savanna] Weekly IRC meeting

2013-04-25 Thread Sergey Lukjanov
Hi,

today there will be regular Savanna community meeting at 18:00 UTC on irc 
channel #openstack-meeting-alt at freenode.

Come along.

Sergey Lukjanov


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] KVM on Ubuntu server 13.04

2013-04-25 Thread skible.openst...@gmail.com

Hi,

Was anyone able to install kvm package on ubuntu server 13.04.
It keeps on switching to another package named qemu-system-x86
Message returned when i do apt-get install kvm = Note, selecting 
'qemu-system-x86' instead of 'kvm'


Without KVM, i can't create VMs !

Anyhelp or advice is highly appreciated.

regards,
Bilel

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] KVM on Ubuntu server 13.04

2013-04-25 Thread Jaren Janke
Hi Bilel,

qemu-system-x86 is a virtual package which includes the required kvm
libraries...

Regards,

Jaren


On Thu, Apr 25, 2013 at 9:27 AM, skible.openst...@gmail.com 
skible.openst...@gmail.com wrote:

 Hi,

 Was anyone able to install kvm package on ubuntu server 13.04.
 It keeps on switching to another package named qemu-system-x86
 Message returned when i do apt-get install kvm = Note, selecting
 'qemu-system-x86' instead of 'kvm'

 Without KVM, i can't create VMs !

 Anyhelp or advice is highly appreciated.

 regards,
 Bilel

 __**_
 Mailing list: 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 More help   : 
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] KVM on Ubuntu server 13.04

2013-04-25 Thread Heling Yao
Hi,

If your cpu doesn't support virtualization, kvm wouldn't run properly;
maybe that's why qemu-system-x86 is selected.

Other than that, I have no idea why.

Cheers,

Heling


On Thu, Apr 25, 2013 at 11:27 PM, skible.openst...@gmail.com 
skible.openst...@gmail.com wrote:

 Hi,

 Was anyone able to install kvm package on ubuntu server 13.04.
 It keeps on switching to another package named qemu-system-x86
 Message returned when i do apt-get install kvm = Note, selecting
 'qemu-system-x86' instead of 'kvm'

 Without KVM, i can't create VMs !

 Anyhelp or advice is highly appreciated.

 regards,
 Bilel

 __**_
 Mailing list: 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 More help   : 
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] nova-network: how to remove

2013-04-25 Thread Arindam Choudhury
Hi,

I mistakenly installed nova-network in a compute node and its became the 
default one. Though I can start the nova-network in the controller, it does not 
start the dnsmasq. How to disable the nova-network from the compute node and 
enable the one in the controller?
  ___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] KVM on Ubuntu server 13.04

2013-04-25 Thread Brian Cline
It's likely installing QEMU as an alternative to KVM (which will work) because 
your CPU doesn't support KVM extensions. Can you paste the output of the 
command kvm-ok? You can install the kvm-ok command via apt-get install 
cpu-checker.

Brian

-Original Message-
From: Openstack 
[mailto:openstack-bounces+bcline=softlayer@lists.launchpad.net] On Behalf 
Of skible.openst...@gmail.com
Sent: Thursday, April 25, 2013 10:28 AM
To: openstack@lists.launchpad.net
Cc: m...@tls.msk.ru
Subject: [Openstack] KVM on Ubuntu server 13.04

Hi,

Was anyone able to install kvm package on ubuntu server 13.04.
It keeps on switching to another package named qemu-system-x86 Message returned 
when i do apt-get install kvm = Note, selecting 'qemu-system-x86' instead of 
'kvm'

Without KVM, i can't create VMs !

Anyhelp or advice is highly appreciated.

regards,
Bilel

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] KVM on Ubuntu server 13.04

2013-04-25 Thread skible.openst...@gmail.com

On 04/25/2013 05:53 PM, Brian Cline wrote:

apt-get install cpu-checker

Thanks all for the quick reply.
This is what i get when i do the kvm-ok command =
kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used

Actually, i had Folsom on my compute nodes(ubuntu server 12.10) and i am 
trying to upgrade to ubuntu 13.04 to update my openstack to grizzly.


I used to create VM normally in folsom since i am using the KVM package, 
now with this qemu-kvm staff, i can't !


When i read about it in ubuntu 13.04 wiki, it seems that they are 
ditching KVM package (dummy package) and replacing it with qemu-KVM. 
Don't know why are they doing that or what's the effect !


Anyway, Qemu is generally for testing environment, i am in production 
ones now and KVM is much more performer than QEMU.


Who got this to work fine on ubuntu 13.04 ? anyone ?

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] nova-network no ip for vm

2013-04-25 Thread Arindam Choudhury
Hi,
Actually the problem was solved by installing nbd module. Now I have one weird 
problem. I have mistakenly installed nova-network in compute node and it had 
became the default one. Can you tell be how to fix it?

To: arin...@live.com
Subject: Re: [Openstack] nova-network no ip for vm
From: jsbry...@us.ibm.com
Date: Thu, 25 Apr 2013 11:32:18 -0500

Arindam,



I realized last night that the iptables
command I sent didn't have the right network interface specification for
your environment.  



It should have been:  iptables
-I INPUT -i interface on control node to the compute nodes -p udp
--dport 67:68 --sport 67:68 -j ACCEPT .



It looks like that might be vnet0?  Sorry,
I don't use iptables much and just stumbled upon the fix for our environment
out of luck.  :-)







Jay S. Bryant

Linux Developer - 

OpenStack Enterprise Edition

   

Department 7YLA, Building 015-2, Office E125, Rochester, MN

Telephone: (507) 253-4270, FAX (507) 253-6410

TIE Line: 553-4270

E-Mail:  jsbry...@us.ibm.com



 All the world's a stage and most of us are desperately unrehearsed.

   -- Sean
O'Casey









From:  
 Arindam Choudhury arin...@live.com

To:  
 Staicu Gabriel gabriel_sta...@yahoo.com,
openstack openstack@lists.launchpad.net, 

Date:  
 04/25/2013 04:19 AM

Subject:
   Re: [Openstack]
nova-network no ip for vm

Sent by:
   Openstack
openstack-bounces+jsbryant=us.ibm@lists.launchpad.net








Hi,



Thanks for your reply.



Here is the logs from /var/log/messages:



Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered promiscuous
mode

Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) entering
forwarding state

Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) entering
forwarding state

Apr 25 11:14:55 aopcso1 kernel: [589272.014705] br100: port 2(vnet0) entering
forwarding state



and the logs from /var/log/syslog:



Apr 25 11:14:07 aopcso1 dnsmasq[12485]: direcciónes /etc/hosts - 23 leídas

Apr 25 11:14:07 aopcso1 dnsmasq-dhcp[12485]: read 
/var/lib/nova/networks/nova-br100.conf

Apr 25 11:14:39 aopcso1 NetworkManager[3980]:SCPlugin-Ifupdown:
devices added (path: /sys/devices/virtual/net/vnet0, iface: vnet0)

Apr 25 11:14:39 aopcso1 NetworkManager[3980]:SCPlugin-Ifupdown:
device added (path: /sys/devices/virtual/net/vnet0, iface: vnet0): no ifupdown
configuration found.

Apr 25 11:14:39 aopcso1 NetworkManager[3980]: warn 
/sys/devices/virtual/net/vnet0:
couldn't determine device driver; ignoring...

Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered promiscuous
mode

Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) entering
forwarding state

Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) entering
forwarding state

Apr 25 11:14:44 aopcso1 ntpd[4796]: Listen normally on 67 vnet0 
fe80::fc16:3eff:fe8a:f597
UDP 123

Apr 25 11:14:44 aopcso1 ntpd[4796]: peers refreshed

Apr 25 11:14:50 aopcso1 kernel: [589267.164541] vnet0: no IPv6 routers
present

Apr 25 11:14:55 aopcso1 kernel: [589272.014705] br100: port 2(vnet0) entering
forwarding state










Date: Thu, 25 Apr 2013 01:53:02 -0700

From: gabriel_sta...@yahoo.com

Subject: Re: [Openstack] nova-network no ip for vm

To: arin...@live.com; openstack@lists.launchpad.net



Hi,



A place to look for eventually
error messages is also /var/log/messages. Look for dnsmasq related message
and post them here.



Regards,

Gabriel




From: Arindam Choudhury arin...@live.com

To: openstack openstack@lists.launchpad.net 

Sent: Thursday, April 25, 2013 11:10 AM

Subject: [Openstack] nova-network no ip for vm



Hi,



I am really stuck, any help will be highly appreciated.



I installed a two node openstack deployment on debian wheezy:



# nova-manage service list

Binary   Host
 
  Zone Status
State Updated_At

nova-network aopcach
 internal
enabled:-)   2013-04-25
08:05:18

nova-certaopcach
 internal
enabled:-)   2013-04-25
08:05:18

nova-conductor   aopcach
 internal
enabled:-)   2013-04-25
08:05:18

nova-consoleauth aopcach  
   internal  
  enabled:-)   2013-04-25 08:05:18

nova-scheduler   aopcach
 internal
enabled:-)   2013-04-25
08:05:18

nova-network aopcso1
 internal
enabled:-)   2013-04-25
08:05:15

nova-compute aopcso1
 nova  
  enabled:-)   2013-04-25
08:05:15



# nova-manage network list

id   IPv4
 IPv6  
start address  DNS1  
DNS2   

[Openstack] multiple snapshots at once?

2013-04-25 Thread Steve Heistand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

when I try to snapshot multiple instances at the same time weird things happen.
should I be able to do this or do I really need to do only 1 at a time?

thanks

s

- -- 

 Steve Heistand  NASA Ames Research Center
 email: steve.heist...@nasa.gov  Steve Heistand/Mail Stop 258-6
 ph: (650) 604-4369  Bldg. 258, Rm. 232-5
 Scientific  HPC ApplicationP.O. Box 1
 Development/OptimizationMoffett Field, CA 94035-0001

 Any opinions expressed are those of our alien overlords, not my own.

# For Remedy#
#Action: Resolve#   
#Resolution: Resolved   #
#Reason: No Further Action Required #
#Tier1: User Code   #
#Tier2: Other   #
#Tier3: Assistance  #
#Notification: None #
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEARECAAYFAlF5XEEACgkQoBCTJSAkVrFeWQCff8pbD+2kVi9L6BxKEGVO+bIR
I4cAoJ8YfGFil4jPrpWoGYPyPFzVxy/q
=n5mr
-END PGP SIGNATURE-

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] nova-network no ip for vm

2013-04-25 Thread Jay S Bryant
Arindam,

You need to make sure that nova-network is not started and that quantum is 
started on your control node.  Also ensure that your /etc/nova/nova.conf 
is configured to use quantum and a plugin.

For my setup I have:

network_api_class = nova.network.quantumv2.api.API
quantum_admin_username = username
quantum_admin_password = password
quantum_admin_auth_url = http://localhost:5000/v2.0/
quantum_auth_strategy = keystone
quantum_admin_tenant_name = service
quantum_url = http://localhost:9696/
libvirt_vif_driver = 
nova.virt.libvirt.vif.LibvirtOpenVswitchVirtualPortDriver
linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver
linuxnet_ovs_integration_bridge = br-int
quantum_ovs_bridge = br-int

In the default section of my nova.conf.  Obviously those will vary 
depending on your hypervisor and which plugin you are using.



Jay S. Bryant
Linux Developer - 
OpenStack Enterprise Edition
   
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-4270
E-Mail:  jsbry...@us.ibm.com

 All the world's a stage and most of us are desperately unrehearsed.
   -- Sean O'Casey




From:   Arindam Choudhury arin...@live.com
To: Jay S Bryant/Rochester/IBM@IBMUS, openstack 
openstack@lists.launchpad.net, 
Date:   04/25/2013 11:42 AM
Subject:RE: [Openstack] nova-network no ip for vm



Hi,
Actually the problem was solved by installing nbd module. Now I have one 
weird problem. I have mistakenly installed nova-network in compute node 
and it had became the default one. Can you tell be how to fix it?

To: arin...@live.com
Subject: Re: [Openstack] nova-network no ip for vm
From: jsbry...@us.ibm.com
Date: Thu, 25 Apr 2013 11:32:18 -0500

Arindam, 

I realized last night that the iptables command I sent didn't have the 
right network interface specification for your environment.   

It should have been:  iptables -I INPUT -i interface on control node to 
the compute nodes -p udp --dport 67:68 --sport 67:68 -j ACCEPT . 

It looks like that might be vnet0?  Sorry, I don't use iptables much and 
just stumbled upon the fix for our environment out of luck.  :-)



Jay S. Bryant
Linux Developer - 
   OpenStack Enterprise Edition
  
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-4270
E-Mail:  jsbry...@us.ibm.com

All the world's a stage and most of us are desperately unrehearsed.
  -- Sean O'Casey
 



From:Arindam Choudhury arin...@live.com 
To:Staicu Gabriel gabriel_sta...@yahoo.com, openstack 
openstack@lists.launchpad.net, 
Date:04/25/2013 04:19 AM 
Subject:Re: [Openstack] nova-network no ip for vm 
Sent by:Openstack 
openstack-bounces+jsbryant=us.ibm@lists.launchpad.net 



Hi,

Thanks for your reply.

Here is the logs from /var/log/messages:

Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered 
promiscuous mode
Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) 
entering forwarding state
Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) 
entering forwarding state
Apr 25 11:14:55 aopcso1 kernel: [589272.014705] br100: port 2(vnet0) 
entering forwarding state

and the logs from /var/log/syslog:

Apr 25 11:14:07 aopcso1 dnsmasq[12485]: direcciónes /etc/hosts - 23 leídas
Apr 25 11:14:07 aopcso1 dnsmasq-dhcp[12485]: read 
/var/lib/nova/networks/nova-br100.conf
Apr 25 11:14:39 aopcso1 NetworkManager[3980]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/vnet0, iface: vnet0)
Apr 25 11:14:39 aopcso1 NetworkManager[3980]:SCPlugin-Ifupdown: device 
added (path: /sys/devices/virtual/net/vnet0, iface: vnet0): no ifupdown 
configuration found.
Apr 25 11:14:39 aopcso1 NetworkManager[3980]: warn 
/sys/devices/virtual/net/vnet0: couldn't determine device driver; 
ignoring...
Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered 
promiscuous mode
Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) 
entering forwarding state
Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) 
entering forwarding state
Apr 25 11:14:44 aopcso1 ntpd[4796]: Listen normally on 67 vnet0 
fe80::fc16:3eff:fe8a:f597 UDP 123
Apr 25 11:14:44 aopcso1 ntpd[4796]: peers refreshed
Apr 25 11:14:50 aopcso1 kernel: [589267.164541] vnet0: no IPv6 routers 
present
Apr 25 11:14:55 aopcso1 kernel: [589272.014705] br100: port 2(vnet0) 
entering forwarding state




Date: Thu, 25 Apr 2013 01:53:02 -0700
From: gabriel_sta...@yahoo.com
Subject: Re: [Openstack] nova-network no ip for vm
To: arin...@live.com; 

Re: [Openstack] nova-network no ip for vm

2013-04-25 Thread Arindam Choudhury
Thanks.



To: arin...@live.com
CC: openstack@lists.launchpad.net
Subject: RE: [Openstack] nova-network no ip for vm
From: jsbry...@us.ibm.com
Date: Thu, 25 Apr 2013 11:59:10 -0500

Arindam,



You need to make sure that nova-network
is not started and that quantum is started on your control node.  Also
ensure that your /etc/nova/nova.conf is configured to use quantum and a
plugin.



For my setup I have:



network_api_class = nova.network.quantumv2.api.API

quantum_admin_username = username

quantum_admin_password = password

quantum_admin_auth_url = http://localhost:5000/v2.0/

quantum_auth_strategy = keystone

quantum_admin_tenant_name = service

quantum_url = http://localhost:9696/

libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtOpenVswitchVirtualPortDriver

linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver

linuxnet_ovs_integration_bridge = br-int

quantum_ovs_bridge = br-int



In the default section of my nova.conf.
 Obviously those will vary depending on your hypervisor and which
plugin you are using.







Jay S. Bryant

Linux Developer - 

OpenStack Enterprise Edition

   

Department 7YLA, Building 015-2, Office E125, Rochester, MN

Telephone: (507) 253-4270, FAX (507) 253-6410

TIE Line: 553-4270

E-Mail:  jsbry...@us.ibm.com



 All the world's a stage and most of us are desperately unrehearsed.

   -- Sean
O'Casey









From:  
 Arindam Choudhury arin...@live.com

To:  
 Jay S Bryant/Rochester/IBM@IBMUS,
openstack openstack@lists.launchpad.net, 

Date:  
 04/25/2013 11:42 AM

Subject:
   RE: [Openstack]
nova-network no ip for vm








Hi,

Actually the problem was solved by installing nbd module. Now I have one
weird problem. I have mistakenly installed nova-network in compute node
and it had became the default one. Can you tell be how to fix it?




To: arin...@live.com

Subject: Re: [Openstack] nova-network no ip for vm

From: jsbry...@us.ibm.com

Date: Thu, 25 Apr 2013 11:32:18 -0500



Arindam, 



I realized last night that the iptables command I sent didn't have the
right network interface specification for your environment.  




It should have been:  iptables -I INPUT -i interface on control
node to the compute nodes -p udp --dport 67:68 --sport 67:68 -j ACCEPT
. 



It looks like that might be vnet0?  Sorry, I don't use iptables much
and just stumbled upon the fix for our environment out of luck.  :-)







Jay S. Bryant

Linux Developer - 

   OpenStack Enterprise Edition

  

Department 7YLA, Building 015-2, Office E125, Rochester, MN

Telephone: (507) 253-4270, FAX (507) 253-6410

TIE Line: 553-4270

E-Mail:  jsbry...@us.ibm.com



All the world's a stage and most of us are desperately unrehearsed.

  -- Sean
O'Casey

 







From:Arindam
Choudhury arin...@live.com 

To:Staicu
Gabriel gabriel_sta...@yahoo.com, openstack openstack@lists.launchpad.net,


Date:04/25/2013
04:19 AM 

Subject:Re:
[Openstack] nova-network no ip for vm


Sent by:Openstack
openstack-bounces+jsbryant=us.ibm@lists.launchpad.net









Hi,



Thanks for your reply.



Here is the logs from /var/log/messages:



Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered promiscuous
mode

Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) entering
forwarding state

Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) entering
forwarding state

Apr 25 11:14:55 aopcso1 kernel: [589272.014705] br100: port 2(vnet0) entering
forwarding state



and the logs from /var/log/syslog:



Apr 25 11:14:07 aopcso1 dnsmasq[12485]: direcciónes /etc/hosts - 23 leídas

Apr 25 11:14:07 aopcso1 dnsmasq-dhcp[12485]: read 
/var/lib/nova/networks/nova-br100.conf

Apr 25 11:14:39 aopcso1 NetworkManager[3980]:SCPlugin-Ifupdown:
devices added (path: /sys/devices/virtual/net/vnet0, iface: vnet0)

Apr 25 11:14:39 aopcso1 NetworkManager[3980]:SCPlugin-Ifupdown:
device added (path: /sys/devices/virtual/net/vnet0, iface: vnet0): no ifupdown
configuration found.

Apr 25 11:14:39 aopcso1 NetworkManager[3980]: warn 
/sys/devices/virtual/net/vnet0:
couldn't determine device driver; ignoring...

Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered promiscuous
mode

Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) entering
forwarding state

Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) entering
forwarding state

Apr 25 11:14:44 aopcso1 ntpd[4796]: Listen normally on 67 vnet0 
fe80::fc16:3eff:fe8a:f597
UDP 123

Apr 25 11:14:44 aopcso1 ntpd[4796]: peers refreshed

Apr 25 11:14:50 aopcso1 kernel: 

Re: [Openstack] nova-manage fails with unable to open database file None None

2013-04-25 Thread Daniel Ellison
On Apr 25, 2013, at 7:48 AM, Daniel Ellison dan...@syrinx.net wrote:
 I've come across a situation that has stumped me. I've searched the archives 
 here but can find no solution. I /did/ find a bug filed in Launchpad 
 (https://bugs.launchpad.net/nova/+bug/1169439) that may be what's happening, 
 but there's no solution.

Thanks to help from George Mihaiescu, the problem has been solved! It was a 
file permission issue, though I'm not sure why this occurred. nova-manage was 
not able to read /etc/nova/nova.conf so it was defaulting to trying to read a 
non-existent SQLite database file.

Thanks, George!

Daniel
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Checkpoint VM and roll back

2013-04-25 Thread Tim Bell

I'd like to be able to

1. checkpoint a running virtual machine
2. run a test
3. rollback to the checkpoint from step 1

Has anyone had experience of doing this using OpenStack (such as with 
snapshots) ?

Tim



smime.p7s
Description: S/MIME cryptographic signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Checkpoint VM and roll back

2013-04-25 Thread Jonathan Proulx
On Thu, Apr 25, 2013 at 2:06 PM, Tim Bell tim.b...@cern.ch wrote:


 I'd like to be able to

 1. checkpoint a running virtual machine
 2. run a test
 3. rollback to the checkpoint from step 1

 Has anyone had experience of doing this using OpenStack (such as with
 snapshots) ?



For slow cycling tests like revising our base operating system images or
deploying large new config management blocks I:

1) boot from a base image
2) deploy and test change
3) on pass snapshot on fail destroy and relaunch last good snapshot
4) recurse as required for multi layered change tests

For faster cycles OpenStack snapshoting may be too cumbersome.  I've used
LVM and ZFS snapshots to provide in operating system roll back and have
read of others doing CoW overlays (unionfs as similar) but that's operating
system specific on openstack.

-Jon
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Grizzly fails on ubuntu server 13.04

2013-04-25 Thread skible.openst...@gmail.com

Hi,

So the ubuntu 13.04 has just been released. Everything is fine except 
for the virtualization using KVM.


After installing nova-compute-kvm, nova-compute does not start and this 
is what i found in my log file:


 Connection to libvirt failed: Failed to connect socket to 
'/var/run/libvirt/libvirt-sock': No such file or directory


which is obvious because there is no more KVM in ubuntu 13.04, instead a 
qemu-kvm package.


Anyone got Grizzly on ubuntu 13.04 ?


regards,
Bilel

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] How to configure nova-network for a single node

2013-04-25 Thread Daniel Ellison
On Apr 23, 2013, at 8:44 AM, Daniel Ellison dan...@syrinx.net wrote:
 I've slowly been configuring a single server with OpenStack for a 
 proof-of-concept I want to present to my managers. This single server is 
 co-located and directly exposed to the Internet. It has one active Ethernet 
 port (eth0) and one inactive and disconnected Ethernet port (eth1). I've 
 already set up br100 over eth0 (I was using KVM on this machine previously, 
 so bridging was already set up). This machine has an entire class C IPv4 
 network (256 IPs) available to it.

I managed to get everything configured. For my setup I used eth0 as the public 
interface and eth1 as the internal interface. eth1 is not connected to 
anything. I added a bridge and attached it to eth1. Here is my 
/etc/network/interfaces now:

auto lo
iface lo inet loopback
pre-up iptables-restore  /etc/iptables.up.rules

auto eth0
iface eth0 inet static
network 204.187.138.0
gateway 204.187.138.1
address 204.187.138.2
broadcast 204.187.138.255
netmask 255.255.255.0

auto eth1
iface eth1 inet manual

auto br100
iface br100 inet static
address 10.10.10.2
netmask 255.255.255.0
bridge_ports eth1
bridge_stp off
bridge_fd 0
bridge_maxwait 0

The networking section of my /etc/nova/nova.conf looks like this:

my_ip=204.187.138.2
public_interface=eth0
flat_interface=eth1
flat_network_bridge=br100
flat_network_dhcp_start=10.10.10.129
fixed_range=10.10.10.128/27
floating_range=204.187.138.128/27 
network_size=32
auto_assign_floating_ip=True

So now when I create a VM it gets an IP from the private 10.10.10.128 subnet 
and it gets assigned a floating (public) IP. This is what a running instance 
looks like with nova list:

+--+-++---+
| ID   | Name| Status | Networks
  |
+--+-++---+
| 8b62a51a-3d35-4160-a299-01e1102082af | precise | ACTIVE | 
private=10.10.10.129, 204.187.138.129 |
+--+-++---+

(Sorry if the table looks horrible with a proportional font.)

Everything works as expected: I'm able to SSH into the VM from the Internet via 
its public IP and on the server itself using either IP. I thought I would put 
all these details here for when someone else comes along looking for the same 
information. If anyone has any suggestions, improvements or corrections, please 
point them out.

Daniel
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [openstack][quantum] stuck subnet

2013-04-25 Thread Steve Heistand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

so I had a tenant that was assigned a floating IP. I deleted the project before
I freed up the floating IP. Now I cant clean up a subnet as it still thinks
there is an IP attached to it.
any ideas how to get rid of a subnet when it thinks there is a float
assigned to it that is owned by a tenant that doesnt exist?

thanks
s

- -- 

 Steve Heistand  NASA Ames Research Center
 email: steve.heist...@nasa.gov  Steve Heistand/Mail Stop 258-6
 ph: (650) 604-4369  Bldg. 258, Rm. 232-5
 Scientific  HPC ApplicationP.O. Box 1
 Development/OptimizationMoffett Field, CA 94035-0001

 Any opinions expressed are those of our alien overlords, not my own.

# For Remedy#
#Action: Resolve#   
#Resolution: Resolved   #
#Reason: No Further Action Required #
#Tier1: User Code   #
#Tier2: Other   #
#Tier3: Assistance  #
#Notification: None #
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEARECAAYFAlF5gEQACgkQoBCTJSAkVrHFOgCg6rIHRsD2BAoi5xrq5eM553qD
accAoOcRHeSXdmJ8HlDAYGgHRpKYuEXm
=zq/V
-END PGP SIGNATURE-

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Call for mentors

2013-04-25 Thread Anne Gentle
Hi all,
We are participating again in the GNOME Outreach Program for Women and are
also in the early planning stages for a mentor program for OpenStack. I'd
like to find out who in the community is interested in becoming a mentor
within the OpenStack projects.

If you're interested in being a mentor or just want to find out more,
please contact me and Stefano Maffulli. Mentors should be ready to flex
their schedule to help a newcomer contribute to OpenStack. Mentors and
interns gave a presentation at the Summit last week and you can watch it at
to get an idea of expectations and experience for mentors.
http://www.openstack.org/summit/portland-2013/session-videos/presentation/what-everyone-ought-to-know-about-openstack-internships

We have an Ideas page for OPW started at
https://wiki.openstack.org/wiki/OutreachProgramForWomen/Ideas. Feel free to
add ideas for projects using the template pattern on that page. These are 3
month projects for students or non-students, using code, community, docs,
or other ideas.

We have an Internship Ideas page for more generalized ideas for students or
others learning OpenStack at
https://wiki.openstack.org/wiki/InternshipProjects/Ideas. These can be
broad ideas but the goals are to onboard newcomers, provide 1:1 mentoring,
and get interesting projects created. Makers welcome.

Thanks all for thinking up cool, goofy, creative, fun projects. My riff off
of Rob Hirschfeld's idea is up there now. :)

Anne
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] KVM on Ubuntu server 13.04

2013-04-25 Thread Scott Moser
On Thu, 25 Apr 2013, skible.openst...@gmail.com wrote:

 Hi,

 Was anyone able to install kvm package on ubuntu server 13.04.
 It keeps on switching to another package named qemu-system-x86
 Message returned when i do apt-get install kvm = Note, selecting
 'qemu-system-x86' instead of 'kvm'

 Without KVM, i can't create VMs !

Did you *actually* find a problem or just notice that 'apt-get install
kvm' installs qemu-system-x86.

There should not be any fallout of this.
If you see any functional issues, then please open a bug in launchpad with
'ubuntu-bug qemu-system-x86'.

Scott

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] OpenStack Training

2013-04-25 Thread Chris Bartels
Hi,

 

My experience with virtualization has been limited to the ProxmoxVE
platform, and with it I'm quite adept after working with it for a few years,
however I'm looking forward to migrating to OpenStack  would like to find a
way to learn as much about it as I can, in as efficient a manner as
possible.

 

I'm currently in the process of selling my laptop on eBay so that I can buy
a cheap used server with which to tinker with the new OpenStack Grizzly
release so I can start to learn first-hand about working with the software,
so I have that to look forward to, but I'm also on the lookout for more
opportunities to soak up information.

 

Today I found the 'OpenStack Foundation' YouTube channel, and have been
watching videos all morning. I'm happy with this to a degree. One in
particular entitled Solving The OpenStack Talent Gap turned me on to a
resource called 'Cloud Academy', which seemed promising at first, but after
getting registered with them- as far as I can tell they don't have training
content up  available yet, as their project is in its infancy apparently.

 

So I come to you all here on the list for suggestions as to whether there
exists reputable formal online training that I can sign up for somewhere-
free is better however I don't mind spending a thousand dollars for
top-notch training if it provides an industry recognized certification at
the end such as the CompTIA A+ (which I'm signed up for this fall, btw-
because it's the closest I can get to what I'm after at the local community
college).

 

What do people here know that I don't know about OpenStack learning 
training? Do any programs stand out as being great that you know of?

 

Please advise.

 

 

Kindest Regards,

-Chris

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] OpenStack Training

2013-04-25 Thread John Griffith
On Thu, Apr 25, 2013 at 2:15 PM, Chris Bartels ch...@christopherbartels.com
 wrote:

 Hi,

 ** **

 My experience with virtualization has been limited to the ProxmoxVE
 platform, and with it I’m quite adept after working with it for a few
 years, however I’m looking forward to migrating to OpenStack  would like
 to find a way to learn as much about it as I can, in as efficient a manner
 as possible.

 ** **

 I’m currently in the process of selling my laptop on eBay so that I can
 buy a cheap used server with which to tinker with the new OpenStack Grizzly
 release so I can start to learn first-hand about working with the software,
 so I have that to look forward to, but I’m also on the lookout for more
 opportunities to soak up information.

 ** **

 Today I found the ‘OpenStack Foundation’ YouTube channel, and have been
 watching videos all morning. I’m happy with this to a degree. One in
 particular entitled “Solving The OpenStack Talent Gap” turned me on to a
 resource called ‘Cloud Academy’, which seemed promising at first, but after
 getting registered with them- as far as I can tell they don’t have training
 content up  available yet, as their project is in its infancy apparently.
 

 ** **

 So I come to you all here on the list for suggestions as to whether there
 exists reputable formal online training that I can sign up for somewhere-
 free is better however I don’t mind spending a thousand dollars for
 top-notch training if it provides an industry recognized certification at
 the end such as the CompTIA A+ (which I’m signed up for this fall, btw-
 because it’s the closest I can get to what I’m after at the local community
 college).

 ** **

 What do people here know that I don’t know about OpenStack learning 
 training? Do any programs stand out as being great that you know of?

 ** **

 Please advise.

 ** **

 ** **

 Kindest Regards,

 -Chris

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

 Hey Chris,

Welcome, I don't have much input regarding your questions on the best
training resources other than docs and diving in to OpenStack.

That being said, you might want to reconsider selling your laptop, you can
run OpenStack in a VM on your laptop just fine, and in fact checkout:
http://devstack.org for a very easy way to get started and experimenting
with OpenStack.

Good Luck,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Ceilometer Install

2013-04-25 Thread Doug Hellmann
On Thu, Apr 25, 2013 at 8:37 AM, Riki Arslan riki.ars...@cloudturk.netwrote:

 I thought Ceilometer did not set a dependency on any DB drivers. I have
 installed the driver Mongo using sudo pip install pymongo.


Ceilometer does use a database. You have to install the right driver. If
you want Mongo, then it sounds like you've done the right thing. It's
possible mako is also being used somewhere else, I'm not sure.



 Regarding the current problem; the traceback is as follows:

 Traceback (most recent call last):
   File /usr/local/bin/ceilometer-api, line 5, in module
 pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
 run_script
 self.require(requires)[0].run_script(script_name, ns)
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235, in
 run_script
 execfile(script_filename, namespace, namespace)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
 line 38, in module
 service.prepare_service()
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/service.py,
 line 80, in prepare_service
 cfg.CONF(argv[1:], project='ceilometer')
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1024, in __call__
 self._cli_values, leftovers = self._parse_cli_opts(args)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1527, in _parse_cli_opts
 opt._add_to_cli(self._oparser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 591, in _add_to_cli
 container = self._get_argparse_container(parser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 633, in _get_argparse_container
 return group._get_argparse_group(parser)
 AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'


That is coming from oslo.config. Can you post the ceilometer.ini file and
command line you are using to start the service?

Doug



 Thank for the help.


 On Thu, Apr 25, 2013 at 3:27 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:



 On Thursday, April 25, 2013, Riki Arslan wrote:

 I have encountered other problems too.

 First of all, when starting the Central Agent I have had Glance endpoint
 404 not found errors. As, Julien pointed out (
 https://bugs.launchpad.net/ceilometer/+bug/1083104), I have removed the
 v1 from the Glance URLs and it worked well.

 Secondly, when starting the API Server, I have received ImportError: No
 module named mako.template error. Thus, I have installed python-mako
 module (sudo apt-get install python-mako), and the error disappeared.


 Mako is a dependency do sqlalchemy, I think. Are you using the sqlalchemy
 storage driver for ceilometer?



 Now, I am receiving another error within the API Server. The error is as
 follows:
 AttributeError: 'OptGroup' object has no attribute
 '_get_argparse_group'


 That sounds like a problem with the config module. Was there a full
 traceback? If not, try adding the --debug option when starting the service.

 Doug



 Do you think it has something to do with mod_wsgi (
 http://docs.openstack.org/developer/ceilometer/install/mod_wsgi.html)?

 I would appreciate your help on this.

 Thanks.


 On Thu, Apr 25, 2013 at 12:27 AM, Riki Arslan riki.ars...@cloudturk.net
  wrote:

 Hi Doug,

 Your email helped me. It was actually glanceclient version 0.5.1 that
 was causing the conflict. After updating it, the conflict error 
 disappeared.

 I hope this would help someone else too.

 Thanks again.


 On Wed, Apr 24, 2013 at 11:49 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Wed, Apr 24, 2013 at 9:17 AM, Riki Arslan 
 riki.ars...@cloudturk.net wrote:

 Hi,

 We are trying to install ceilometer-2013.1~g2.tar.gz which
 presumably has Folsom compatibility.

 The requirment is python-keystoneclient=0.2,0.3 and we have
 the version 2.3.

 But, still, setup quits with the following message:

 error: Installed distribution python-keystoneclient 0.2.3
 conflicts with requirement python-keystoneclient=0.1.2,0.2

 The funny thing is, although pip-requires states
 python-keystoneclient=0.2,0.3, the error message complains that it is
 not python-keystoneclient=0.1.2,0.2.


 Something else you have installed already wants an older version of
 the keystone client, so the installation of ceilometer is not able to
 upgrade to the version we need.

 Doug



 Your help is greatly appreciated.

 Thank you in advance.

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp







Re: [Openstack] Heat PTL candidacy

2013-04-25 Thread Adam Young

On 04/23/2013 10:15 AM, Steven Hardy wrote:

Repost to correctly include openstack-dev on Cc

On Tue, Apr 23, 2013 at 02:45:31PM +0100, Steven Hardy wrote:

Hi!

I'd like to propose myself as a candidate for the Heat PTL role, ref
Thierry's nominations email [1]

I've been professionally involved with software engineering for around 13
years, working in a variety of industries, from embedded/kernel
development to big-enterprise customer-facing consulting.

Having been involved with the Heat project from very near the start, I've
been part of the strong core team who are making this project grow from a
good idea into something people can actually use (and are using!).

I have a deep understanding of our current code-base, and a clear view of
our future roadmap (and the challenges we face!), so I believe I am in a
good position to step into the role Steve Dake was unfortunately unable to
continue with, and do what is required to enable the Heat project to
deliver another successful release for Havana.

Having attended the summit last week, I have to say I'm even more driven
and enthusiastic about the project, so much great feedback and ideas from
our users and potential contributors.  I look forward to developing more
features our users want, and encouraging much wider community participation
in the project over the next few months.

Thanks!

Steve Hardy


[1] http://lists.openstack.org/pipermail/openstack-dev/2013-April/007724.html
+1.  I've worked with Steve Hardy on getting  the Heat/Keystone 
Delegation requirements clear.  His professionalism and deep 
understanding are fantastic.


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] list all volumes attached to a vm

2013-04-25 Thread daniels cai
hi community

i am trying to list all volumes which attached to  a vm, with a vm id
specified
.
i am not sure whether there is any command line filter to achieve this
,i use api instead

here is the ref
http://api.openstack.org/api-ref.html

invoked api is

v2/{tenant_id}/servers/{server_id}/os-volume_attachments

but  , this api seems not work properly , it returns a 404 error

openstack response: '404 Not Found#012#012The resource could not be
found.#012#012   '

in cinder's log file '/var/log/cinder/cinder-api.log'

2013-04-26 11:18:11DEBUG [routes.middleware] No route matched for GET
/82da519b676d400ab24e9ee38d138c3c/servers/cb75bb55-e9ef-4d05-af9f-3ad346fa3eb4/os-volume_attachments

any help is welcomed , thanks for advance

Daniels Cai
http://dnscai.com
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [openstack][quantum] stuck subnet

2013-04-25 Thread Vinay Bannai
I don't know of any elegant solution but one option may be to database and
delete the individual records along with the all the interconnected
records.


On Thu, Apr 25, 2013 at 12:13 PM, Steve Heistand steve.heist...@nasa.govwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 so I had a tenant that was assigned a floating IP. I deleted the project
 before
 I freed up the floating IP. Now I cant clean up a subnet as it still thinks
 there is an IP attached to it.
 any ideas how to get rid of a subnet when it thinks there is a float
 assigned to it that is owned by a tenant that doesnt exist?

 thanks
 s

 - --
 
  Steve Heistand  NASA Ames Research Center
  email: steve.heist...@nasa.gov  Steve Heistand/Mail Stop 258-6
  ph: (650) 604-4369  Bldg. 258, Rm. 232-5
  Scientific  HPC ApplicationP.O. Box 1
  Development/OptimizationMoffett Field, CA 94035-0001
 
  Any opinions expressed are those of our alien overlords, not my own.

 # For Remedy#
 #Action: Resolve#
 #Resolution: Resolved   #
 #Reason: No Further Action Required #
 #Tier1: User Code   #
 #Tier2: Other   #
 #Tier3: Assistance  #
 #Notification: None #
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.14 (GNU/Linux)

 iEYEARECAAYFAlF5gEQACgkQoBCTJSAkVrHFOgCg6rIHRsD2BAoi5xrq5eM553qD
 accAoOcRHeSXdmJ8HlDAYGgHRpKYuEXm
 =zq/V
 -END PGP SIGNATURE-

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




-- 
Vinay Bannai
Email: vban...@gmail.com
Google Voice: 415 938 7576
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [openstack][quantum] stuck subnet

2013-04-25 Thread Aaron Rosen
You should be able to delete the floating ip via an admin user and then
delete the subnet.

Aaron


On Thu, Apr 25, 2013 at 12:13 PM, Steve Heistand steve.heist...@nasa.govwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 so I had a tenant that was assigned a floating IP. I deleted the project
 before
 I freed up the floating IP. Now I cant clean up a subnet as it still thinks
 there is an IP attached to it.
 any ideas how to get rid of a subnet when it thinks there is a float
 assigned to it that is owned by a tenant that doesnt exist?

 thanks
 s

 - --
 
  Steve Heistand  NASA Ames Research Center
  email: steve.heist...@nasa.gov  Steve Heistand/Mail Stop 258-6
  ph: (650) 604-4369  Bldg. 258, Rm. 232-5
  Scientific  HPC ApplicationP.O. Box 1
  Development/OptimizationMoffett Field, CA 94035-0001
 
  Any opinions expressed are those of our alien overlords, not my own.

 # For Remedy#
 #Action: Resolve#
 #Resolution: Resolved   #
 #Reason: No Further Action Required #
 #Tier1: User Code   #
 #Tier2: Other   #
 #Tier3: Assistance  #
 #Notification: None #
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.14 (GNU/Linux)

 iEYEARECAAYFAlF5gEQACgkQoBCTJSAkVrHFOgCg6rIHRsD2BAoi5xrq5eM553qD
 accAoOcRHeSXdmJ8HlDAYGgHRpKYuEXm
 =zq/V
 -END PGP SIGNATURE-

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_glance_trunk #28

2013-04-25 Thread openstack-testing-bot
Title: precise_havana_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_glance_trunk/28/Project:precise_havana_glance_trunkDate of build:Thu, 25 Apr 2013 14:31:36 -0400Build duration:2 min 54 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFunctional tests use a clean cached db that is only created once.by jbresnaheditglance/tests/functional/__init__.pyConsole Output[...truncated 2649 lines...]Finished at 20130425-1434Build needed 00:01:29, 12080k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'glance_2013.2+git201304251431~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'glance_2013.2+git201304251431~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmpHV5l7X/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpHV5l7X/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log e6e02cd147b3b22dc39344df48d3e40abf024240..HEAD --no-merges --pretty=format:[%h] %sdch -b -D precise --newversion 1:2013.2+git201304251431~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [d415611] Functional tests use a clean cached db that is only created once.dch -a [d3c5a6c] Fixes for mis-use of various exceptionsdch -a [6335fdb] Eliminate the race when selecting a port for tests.dch -a [7d341de] Raise 404 while deleting a deleted imagedch -a [459e3e6] Sync with oslo-incubator copy of setup.py and version.pydch -a [6780571] Fix Qpid test casesdch -a [cd00848] Fix the deletion of a pending_delete image.dch -a [1e49329] Fix functional test 'test_scrubber_with_metadata_enc'dch -a [1c5a4d2] Call monkey_patch before other modules are loadeddch -a [6eaf42a] Improve unit tests for glance.api.middleware.cache moduledch -a [ae0f904] Add GridFS storedch -a [28b1129] Verify SSL certificates at boot timedch -a [b1ac90f] Add a policy handler to control copy-from functionalitydch -a [7155134] Add unit tests for glance.api.cached_images moduledebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.2+git201304251431~precise-0ubuntu1_source.changessbuild -d precise-havana -n -A glance_2013.2+git201304251431~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'glance_2013.2+git201304251431~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'glance_2013.2+git201304251431~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14641

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14641/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson8085122405562166132.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_keystone_trunk #35

2013-04-25 Thread openstack-testing-bot
Title: precise_havana_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_keystone_trunk/35/Project:precise_havana_keystone_trunkDate of build:Thu, 25 Apr 2013 16:31:36 -0400Build duration:2 min 15 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesMark LDAP password and admin_token secretby xuhanpeditkeystone/common/config.pyConsole Output[...truncated 2559 lines...]dch -a [335470d] Removed unused importsdch -a [9f7b370] Remove non-production middleware from sample pipelinesdch -a [fccfa39] Fixed logging usage instead of LOGdch -a [2eab5fd] Remove new constraint from migration downgrade.dch -a [8c67341] Sync with oslo-incubator copy of setup.pydch -a [9b9a3d5] Set empty element to ""dch -a [78dcfc6] Fixed unicode username user creation errordch -a [a62d3af] Fix token ids for memcacheddch -a [61629c3] Use is_enabled() in folsom->grizzly upgrade (bug 1167421)dch -a [28ef9cd] Generate HTTPS certificates with ssl_setup.dch -a [cbac771] Fix for configuring non-default auth plugins properlydch -a [23bd9fa] test duplicate namedch -a [e4ec12e] Add TLS Support for LDAPdch -a [97d5624] fix undefined variabledch -a [6f4096b] clean up invalid variable referencedch -a [f846e28] Clean up duplicate methodsdch -a [3f296e0] don't migrate as oftendch -a [5c217fd] use the openstack test runnerdch -a [b033538] Fix 401 status responsedch -a [a65f737] Add missing colon for documentation build steps.dch -a [9467a66] close db migration sessiondch -a [b94f62a] Use string for port in default endpoints (bug 1160573)dch -a [1121b8d] bug 1159888 broken links in rst docdch -a [6f88699] Remove un-needed LimitingReader read() function.dch -a [e16742b] residual grants after delete action (bug1125637)dch -a [0b4ee31] catch errors in wsgi.Middleware.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.2+git201304251631~precise-0ubuntu1_source.changessbuild -d precise-havana -n -A keystone_2013.2+git201304251631~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'keystone_2013.2+git201304251631~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'keystone_2013.2+git201304251631~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14642

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14642/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson1891747339410903207.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14643

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14643/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson6790004896110047701.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14644

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14644/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson3510325510816363828.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14645

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14645/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson6292074874766055372.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14646

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14646/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson5774929801560028108.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14648

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14648/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson8176636669593877174.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14649

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14649/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson98138347863162231.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_quantum_trunk #57

2013-04-25 Thread openstack-testing-bot
Title: precise_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_quantum_trunk/57/Project:precise_havana_quantum_trunkDate of build:Thu, 25 Apr 2013 18:31:36 -0400Build duration:1 min 39 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesSimplify NVP plugin configurationby amigliaccioeditquantum/tests/unit/nicira/test_nicira_plugin.pydeletequantum/tests/unit/nicira/test_defaults.pyeditquantum/plugins/nicira/common/exceptions.pyeditquantum/plugins/nicira/common/config.pyaddquantum/tests/unit/nicira/etc/nvp.ini.basic.testeditetc/quantum/plugins/nicira/nvp.inieditquantum/plugins/nicira/nvp_cluster.pyeditquantum/tests/unit/nicira/etc/nvp.ini.testeditquantum/plugins/nicira/check_nvp_config.pyaddquantum/tests/unit/nicira/test_nvpopts.pyaddquantum/tests/unit/nicira/etc/nvp.ini.full.testeditquantum/tests/unit/nicira/test_nvplib.pyeditquantum/plugins/nicira/QuantumPlugin.pyaddquantum/tests/unit/nicira/etc/nvp.ini.grizzly.testeditquantum/plugins/nicira/READMEConsole Output[...truncated 1715 lines...]git log de5c1e4f281f59d550b476919b27ac4e2aae14ac..HEAD --no-merges --pretty=format:[%h] %sdch -b -D precise --newversion 1:2013.2+git201304251831~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [ea9aeb6] Simplify NVP plugin configurationdch -a [9c21592] Imported Translations from Transifexdch -a [01a977b] Send 400 error if device specification contains unexpected attributesdch -a [62017cd] Imported Translations from Transifexdch -a [26b98b7] lbaas: check object state before update for pools, members, health monitorsdch -a [49c1c98] Metadata agent: reuse authentication info across eventlet threadsdch -a [11639a2] Imported Translations from Transifexdch -a [35988f1] Make the 'admin' role configurabledch -a [765baf8] Imported Translations from Transifexdch -a [343ca18] Imported Translations from Transifexdch -a [c117074] Remove locals() from strings substitutionsdch -a [fb66e24] Imported Translations from Transifexdch -a [e001a8d] Add string 'quantum'/ version to scope/tag in NVPdch -a [5896322] Changed DHCPV6_PORT from 467 to 547, the correct port for DHCPv6.dch -a [80ffdde] Imported Translations from Transifexdch -a [929cbab] Imported Translations from Transifexdch -a [2a24058] Imported Translations from Transifexdch -a [b6f0f68] Imported Translations from Transifexdch -a [1e1c513] Imported Translations from Transifexdch -a [6bbcc38] Imported Translations from Transifexdch -a [bd702cb] Imported Translations from Transifexdch -a [a13295b] Enable automatic validation of many HACKING rules.dch -a [91bed75] Ensure unit tests work with all interface typesdch -a [0446eac] Shorten the path of the nicira nvp plugin.dch -a [8354133] Implement LB plugin delete_pool_health_monitor().dch -a [147038a] Parallelize quantum unit testing:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-63c84ecb-623f-4faa-9175-c1ed8f683f3a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-63c84ecb-623f-4faa-9175-c1ed8f683f3a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14651

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14651/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson8523635096809360712.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14652

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14652/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson8516170802118191227.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14653

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14653/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson5110912343038542645.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14654

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14654/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson5947015765783519220.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14656

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14656/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson949504313520647791.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14657

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14657/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson3832777091130610879.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14659

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14659/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson132571726288454363.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14660

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14660/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson4972243274319868413.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14661

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14661/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson139855734590990722.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14662

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14662/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson7313621204874641916.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14663

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14663/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson3637717963454200021.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14664

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14664/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson1695026919272532807.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14665

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14665/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson9011192742049471918.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14667

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14667/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson7596403426520655102.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_keystone_trunk #36

2013-04-25 Thread openstack-testing-bot
Title: precise_havana_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_keystone_trunk/36/Project:precise_havana_keystone_trunkDate of build:Thu, 25 Apr 2013 23:01:36 -0400Build duration:2 min 36 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAllow additional attribute mappings in ldapby allanfeideditkeystone/common/config.pyedittests/test_backend_ldap.pyeditetc/keystone.conf.sampleeditkeystone/common/ldap/core.pyConsole Output[...truncated 2562 lines...]dch -a [9f7b370] Remove non-production middleware from sample pipelinesdch -a [fccfa39] Fixed logging usage instead of LOGdch -a [2eab5fd] Remove new constraint from migration downgrade.dch -a [f452c3d] Allow additional attribute mappings in ldapdch -a [8c67341] Sync with oslo-incubator copy of setup.pydch -a [9b9a3d5] Set empty element to ""dch -a [78dcfc6] Fixed unicode username user creation errordch -a [a62d3af] Fix token ids for memcacheddch -a [61629c3] Use is_enabled() in folsom->grizzly upgrade (bug 1167421)dch -a [28ef9cd] Generate HTTPS certificates with ssl_setup.dch -a [cbac771] Fix for configuring non-default auth plugins properlydch -a [23bd9fa] test duplicate namedch -a [e4ec12e] Add TLS Support for LDAPdch -a [97d5624] fix undefined variabledch -a [6f4096b] clean up invalid variable referencedch -a [f846e28] Clean up duplicate methodsdch -a [3f296e0] don't migrate as oftendch -a [5c217fd] use the openstack test runnerdch -a [b033538] Fix 401 status responsedch -a [a65f737] Add missing colon for documentation build steps.dch -a [9467a66] close db migration sessiondch -a [b94f62a] Use string for port in default endpoints (bug 1160573)dch -a [1121b8d] bug 1159888 broken links in rst docdch -a [6f88699] Remove un-needed LimitingReader read() function.dch -a [e16742b] residual grants after delete action (bug1125637)dch -a [0b4ee31] catch errors in wsgi.Middleware.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.2+git201304252301~precise-0ubuntu1_source.changessbuild -d precise-havana -n -A keystone_2013.2+git201304252301~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'keystone_2013.2+git201304252301~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'keystone_2013.2+git201304252301~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14668

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14668/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson5739824791398885118.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14669

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14669/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson5248582657792123877.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_quantum_trunk #58

2013-04-25 Thread openstack-testing-bot
Title: precise_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_quantum_trunk/58/Project:precise_havana_quantum_trunkDate of build:Thu, 25 Apr 2013 23:31:36 -0400Build duration:1 min 16 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesCreate veth peer in namespace.by maruneditquantum/tests/unit/test_linux_interface.pyeditquantum/tests/unit/test_linux_ip_lib.pyeditquantum/agent/linux/interface.pyeditquantum/agent/linux/ip_lib.pyConsole Output[...truncated 1718 lines...]dch -b -D precise --newversion 1:2013.2+git201304252331~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [ea9aeb6] Simplify NVP plugin configurationdch -a [152f3cf] Create veth peer in namespace.dch -a [9c21592] Imported Translations from Transifexdch -a [01a977b] Send 400 error if device specification contains unexpected attributesdch -a [62017cd] Imported Translations from Transifexdch -a [26b98b7] lbaas: check object state before update for pools, members, health monitorsdch -a [49c1c98] Metadata agent: reuse authentication info across eventlet threadsdch -a [11639a2] Imported Translations from Transifexdch -a [35988f1] Make the 'admin' role configurabledch -a [765baf8] Imported Translations from Transifexdch -a [343ca18] Imported Translations from Transifexdch -a [c117074] Remove locals() from strings substitutionsdch -a [fb66e24] Imported Translations from Transifexdch -a [e001a8d] Add string 'quantum'/ version to scope/tag in NVPdch -a [5896322] Changed DHCPV6_PORT from 467 to 547, the correct port for DHCPv6.dch -a [80ffdde] Imported Translations from Transifexdch -a [929cbab] Imported Translations from Transifexdch -a [2a24058] Imported Translations from Transifexdch -a [b6f0f68] Imported Translations from Transifexdch -a [1e1c513] Imported Translations from Transifexdch -a [6bbcc38] Imported Translations from Transifexdch -a [bd702cb] Imported Translations from Transifexdch -a [a13295b] Enable automatic validation of many HACKING rules.dch -a [91bed75] Ensure unit tests work with all interface typesdch -a [0446eac] Shorten the path of the nicira nvp plugin.dch -a [8354133] Implement LB plugin delete_pool_health_monitor().dch -a [147038a] Parallelize quantum unit testing:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-975b1af0-b23c-429d-94f1-4bf652b97f35', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-975b1af0-b23c-429d-94f1-4bf652b97f35', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14670

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14670/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson6770436726644945391.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_grizzly_version-drift #4

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_grizzly_version-drift/4/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_grizzly_version-drift/ws/
[cloud-archive_grizzly_version-drift] $ /bin/bash -xe 
/tmp/hudson5810821452162879588.sh
+ OS_RELEASE=grizzly
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 grizzly
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r grizzly
---
The following Cloud Archive packages for grizzly
have been superseded newer versions in Ubuntu!

nova:
Ubuntu: 1:2013.1-0ubuntu2
Cloud Archive staging: 1:2013.1-0ubuntu2~cloud1

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14672

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14672/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson4574377582318500514.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14674

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14674/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson1331799747266984925.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14675

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14675/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson600598293965009.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_quantum_trunk #60

2013-04-25 Thread openstack-testing-bot
Title: precise_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_quantum_trunk/60/Project:precise_havana_quantum_trunkDate of build:Fri, 26 Apr 2013 01:01:36 -0400Build duration:1 min 16 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesSimplify delete_health_monitor() using cascadesby rpodolyakaeditquantum/tests/unit/db/loadbalancer/test_db_loadbalancer.pyeditquantum/plugins/services/agent_loadbalancer/plugin.pyeditquantum/db/loadbalancer/loadbalancer_db.pyConsole Output[...truncated 1724 lines...]dch -a [ea9aeb6] Simplify NVP plugin configurationdch -a [152f3cf] Create veth peer in namespace.dch -a [9c21592] Imported Translations from Transifexdch -a [01a977b] Send 400 error if device specification contains unexpected attributesdch -a [62017cd] Imported Translations from Transifexdch -a [26b98b7] lbaas: check object state before update for pools, members, health monitorsdch -a [49c1c98] Metadata agent: reuse authentication info across eventlet threadsdch -a [11639a2] Imported Translations from Transifexdch -a [35988f1] Make the 'admin' role configurabledch -a [ee50162] Simplify delete_health_monitor() using cascadesdch -a [765baf8] Imported Translations from Transifexdch -a [343ca18] Imported Translations from Transifexdch -a [c117074] Remove locals() from strings substitutionsdch -a [fb66e24] Imported Translations from Transifexdch -a [e001a8d] Add string 'quantum'/ version to scope/tag in NVPdch -a [5896322] Changed DHCPV6_PORT from 467 to 547, the correct port for DHCPv6.dch -a [80ffdde] Imported Translations from Transifexdch -a [929cbab] Imported Translations from Transifexdch -a [2a24058] Imported Translations from Transifexdch -a [b6f0f68] Imported Translations from Transifexdch -a [1e1c513] Imported Translations from Transifexdch -a [6bbcc38] Imported Translations from Transifexdch -a [bd702cb] Imported Translations from Transifexdch -a [a13295b] Enable automatic validation of many HACKING rules.dch -a [91bed75] Ensure unit tests work with all interface typesdch -a [0446eac] Shorten the path of the nicira nvp plugin.dch -a [8354133] Implement LB plugin delete_pool_health_monitor().dch -a [147038a] Parallelize quantum unit testing:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-142dfb2d-b36e-4fd1-ac61-6a05fe71e985', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-142dfb2d-b36e-4fd1-ac61-6a05fe71e985', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14676

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14676/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson5680839774365577103.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14677

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14677/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson2685158444895438236.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #14678

2013-04-25 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14678/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson3696719534133891679.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as failure

-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp