[Group.of.nepali.translators] [Bug 1634304] Re: Unable to complete install: 'Couldn't find hvm kernel for Ubuntu tree

2016-12-11 Thread Launchpad Bug Tracker 
This bug was fixed in the package virt-manager - 1:1.3.2-3ubuntu4

---
virt-manager (1:1.3.2-3ubuntu4) zesty; urgency=medium

  * Fix virt-install so that it can install 16.04 and newer images.
Error message is 'Couldn't find hvm kernel for Ubuntu tree
Closes (LP: #1634304)

 -- Dave Chiluk   Tue, 29 Nov 2016 12:52:23 -0600

** Changed in: virt-manager (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1634304

Title:
  Unable to complete install: 'Couldn't find hvm kernel for Ubuntu tree

Status in virt-manager package in Ubuntu:
  Fix Released
Status in virt-manager source package in Xenial:
  Fix Committed
Status in virt-manager source package in Yakkety:
  Fix Committed
Status in virt-manager source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * Users are unable to virt-install using xenial and newer isos.

  [Test Case]
   #!/bin/bash
  sudo virt-install \
  --connect qemu:///system \
  --virt-type kvm \
  --name labVM2 \
  --disk size=10 \
  --ram 2048 \
  --vcpus=2 \
  --graphics vnc \
  -l /home/student19s/ubuntu-16.04.1-server-amd64.iso \
  --os-variant ubuntu16.04

  * Bad output 
  WARNING  Graphics requested but DISPLAY is not set. Not running virt-viewer.
  WARNING  No console to launch for the guest, defaulting to --wait -1

  Starting install...
  Retrieving file version.info...   
  |   58 B  00:00:00 
  ERRORCouldn't find hvm kernel for Ubuntu tree.
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start labVM2
  otherwise, please restart your installation.

  * Expected output 
  Starting install...
  Retrieving file version.info...   
   |   58 B  00:00:00 
  Retrieving file linux...  
  | 6.7 MB  00:00:00 
  Retrieving file initrd.gz...  
  |  36 MB  00:00:00 
  Allocating 'labVM2-2.qcow2'   
  |  10 GB  00:00:00 
  Creating domain...
  |0 B  00:00:00 
  Domain installation still in progress. Waiting for installation to complete.

  [Regression Potential]

   * Patch is accepted into upstream virt-install

   * I have run virt-install against both iso's and netinstall trees
  *(which previously worked and now continue to work).

  [Other Info]

  
  + Original Description 
  I am trying to create a new virtual machine with Virtual Machine Manager but 
keep receiving this error "Unable to complete install: 'Couldn't find hvm 
kernel for Ubuntu tree". The OS guest I am trying to install on the VM is 
Ubuntu server 14.04.4, 64 bit. The host OS (where the virtual manager is 
installed) is KUbuntu 16.04 .

  Below is the full message that appears after completing the 5-steps VM
  creation process and clicking on finish on virt-manager:

  Unable to complete install: 'Couldn't find hvm kernel for Ubuntu
  tree.'

  Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 90, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/create.py", line 2277, in 
_do_async_install
  guest.start_install(meter=meter)
    File "/usr/share/virt-manager/virtinst/guest.py", line 482, in start_install
  self._prepare_install(meter, dry)
    File "/usr/share/virt-manager/virtinst/guest.py", line 303, in 
_prepare_install
  self.installer.prepare(self, meter)
    File "/usr/share/virt-manager/virtinst/installer.py", line 200, in prepare
  self._prepare(guest, meter)
    File "/usr/share/virt-manager/virtinst/distroinstaller.py", line 451, in 
_prepare
  self._prepare_kernel_url(guest, fetcher)
    File "/usr/share/virt-manager/virtinst/distroinstaller.py", line 360, in 
_prepare_kernel_url
  kernel, initrd, args = store.acquireKernel(guest)
    File "/usr/share/virt-manager/virtinst/urlfetcher.py", line 577, in 
acquireKernel
  {"distro": self.name, "type" : self.type})
  RuntimeError: Couldn't find hvm kernel for Ubuntu tree.

  And the package data are

  $ dpkg -s virt-manager
  Package: virt-manager
  Status: install ok installed
  Priority: optional
  Section: admin
  Installed-Size: 7285
  Maintainer: Ubuntu Developers 
  Architecture: all
  Version: 1:1.3.2-3ubuntu1.16.04.2
  Depends:

[Group.of.nepali.translators] [Bug 1647708] Re: Ephemeral disk on xenial is not mounted at boot

2016-12-11 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init -
0.7.8-67-gc9c9197-0ubuntu1

---
cloud-init (0.7.8-67-gc9c9197-0ubuntu1) zesty; urgency=medium

  * debian/cherry-pick: add utility for cherry picking commits from upstream
into patches in debian/patches.
  * New upstream snapshot.
- mounts: use mount -a again to accomplish mounts (LP: #1647708)
- CloudSigma: Fix bug where datasource was not loaded in local search. (LP: 
#1648380)
- when adding a user, strip whitespace from group list (LP: #1354694)
- fix decoding of utf-8 chars in yaml test
- Replace usage of sys_netdev_info with read_sys_net (LP: #1625766)
- fix problems found in python2.6 test.

 -- Scott Moser   Sun, 11 Dec 2016 21:22:57 -0500

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1647708

Title:
  Ephemeral disk on xenial is not mounted at boot

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed

Bug description:
  When I boot the latest xenial Azure image (containing cloud-init
  0.7.8-49-g9e904bb-0ubuntu1~16.04.1), the ephemeral disk does not end
  up mounted (though it is formatted appropriately).  Restarting the
  mnt.mount service does mount it, which suggests there is an issue in
  the ordering of the services at boot.

  $ mount | grep mnt
  $ sudo systemctl status mnt.mount 
  ● mnt.mount - /mnt
 Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
 Active: inactive (dead)
  Where: /mnt
   What: /dev/disk/cloud/azure_resource-part1
   Docs: man:fstab(5)
 man:systemd-fstab-generator(8)
  $ sudo journalctl -u mnt.mount 
  -- No entries --
  $ cat /etc/fstab 
  # CLOUD_IMG: This file was created/modified by the Cloud Image build process
  UUID=6a8554fa-8e1d-4916-ba03-4ca3837feb34 /ext4   
defaults,discard0 0
  /dev/disk/cloud/azure_resource-part1  /mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  $ sudo systemctl restart mnt.mount
  $ mount | grep mnt
  /dev/sdb1 on /mnt type ext4 (rw,relatime,data=ordered)
  $ ls /mnt/
  lost+found
  $ sudo systemctl status mnt.mount 
  ● mnt.mount - /mnt
 Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
 Active: active (mounted) since Tue 2016-12-06 12:49:06 UTC; 6s ago
  Where: /mnt
   What: /dev/sdb1
   Docs: man:fstab(5)
 man:systemd-fstab-generator(8)
Process: 1916 ExecMount=/bin/mount /dev/disk/cloud/azure_resource-part1 
/mnt -o defaults,x-systemd.requires=cloud-init.service,comment=cloudconfig 
(code=exited, status=0/SUCCESS)
  Tasks: 0
 Memory: 88.0K
CPU: 15ms

  Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounting /mnt...
  Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounted /mnt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1647708/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1648380] Re: cloud-init fails to find CloudSigma datasource with cloud-init 0.7.8-1-g3705bb5-0ubuntu1

2016-12-11 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init -
0.7.8-67-gc9c9197-0ubuntu1

---
cloud-init (0.7.8-67-gc9c9197-0ubuntu1) zesty; urgency=medium

  * debian/cherry-pick: add utility for cherry picking commits from upstream
into patches in debian/patches.
  * New upstream snapshot.
- mounts: use mount -a again to accomplish mounts (LP: #1647708)
- CloudSigma: Fix bug where datasource was not loaded in local search. (LP: 
#1648380)
- when adding a user, strip whitespace from group list (LP: #1354694)
- fix decoding of utf-8 chars in yaml test
- Replace usage of sys_netdev_info with read_sys_net (LP: #1625766)
- fix problems found in python2.6 test.

 -- Scott Moser   Sun, 11 Dec 2016 21:22:57 -0500

** Changed in: cloud-init (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1648380

Title:
  cloud-init fails to find CloudSigma datasource with cloud-init
  0.7.8-1-g3705bb5-0ubuntu1

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  [SRU justification]
  Without this fix, images built with cloud-init 0.7.8-1-g3705bb5-0ubuntu1  and 
later will not correctly boot and become unreachable

  [Impact]
  Some cloud images built with this version of cloud-init may become unusable

  [Fix]
  Reinstate the second element of the datasources list as a tuple instead of a 
string.

  [Test Case]
  This test must be done on CloudSigma to complete correctly :

  Build cloud image with only the CloudSigma datasource using cloud-init 
version 0.7.8-1-g3705bb5-0ubuntu1 or later
  Launch an instance with this image
  The instance will boot but will not be accessible through ssh

  With this fix,the instance will complete its boot sequence and be
  accessible through ssh

  [Regression]
  None expected, the second element was a tuple in previous versions of the 
CloudSigma datasource

  [Description of the problem]
  The issue materialized itself on cloud instances launched with such images 
that became unreachable through SSH with the following message:

  "Connection closed by {IP} port 22"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1648380/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1559072] Re: [SRU] exceptions.from_response with webob 1.6.0 results in "AttributeError: 'unicode' object has no attribute 'get'"

2016-12-11 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/407422
Committed: 
https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=19befa69651a41534c7d25b1a0d3a0cd407afb44
Submitter: Jenkins
Branch:master

commit 19befa69651a41534c7d25b1a0d3a0cd407afb44
Author: Akira KAMIO 
Date:   Tue Dec 6 14:10:38 2016 +0900

Handle error response for webob>=1.6.0

WebOb change https://github.com/Pylons/webob/pull/230 changed
the way in which the error response body is formatted such that
it's no longer a nested dict. So we have to handle both the
old convention of an error message key to the response body error
dict and the new way with just the error body dict.

This was reported upstream:

https://github.com/Pylons/webob/issues/235

But given this was apparently implemented as a long-overdue change
in WebOb the behavior is not likely to change.Handle error response for
webob>=1.6.0

Change-Id: I7d589415aa024588faf77c8234ac026110f6c3cd
Closes-Bug: #1559072


** Changed in: python-cinderclient
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1559072

Title:
  [SRU] exceptions.from_response with webob 1.6.0 results in
  "AttributeError: 'unicode' object has no attribute 'get'"

Status in networking-midonet:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-novaclient:
  Fix Released
Status in python-openstackclient:
  Invalid
Status in python-novaclient package in Ubuntu:
  Fix Released
Status in python-novaclient source package in Xenial:
  Fix Released
Status in python-novaclient source package in Yakkety:
  Fix Released

Bug description:
  [Impact] [Testcase]
  Running on Ubuntu 14.04.
  After installing nova from source in either the Liberty release or Mitaka, 
with WebOb 1.6.0, running any nova command generated this error:
  root@openstack-ubu-controller:~# nova service-list
  ERROR (AttributeError): 'unicode' object has no attribute 'get'

  The equivalent openstack commands work correctly. After downgrading
  WebOb to 1.5.1 AND restarting the nova-api service everything works.

  Detailed output from nova -debug service-list with the error:

  root@openstack-ubu-controller:~# nova --debug service-list
  DEBUG (extension:157) found extension EntryPoint.parse('v2token = 
keystoneauth1.loading._plugins.identity.v2:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('admin_token = 
keystoneauth1.loading._plugins.admin_token:AdminToken')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcauthcode = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAuthorizationCode')
  DEBUG (extension:157) found extension EntryPoint.parse('v2password = 
keystoneauth1.loading._plugins.identity.v2:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3password = 
keystoneauth1.loading._plugins.identity.v3:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcpassword = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectPassword')
  DEBUG (extension:157) found extension EntryPoint.parse('token = 
keystoneauth1.loading._plugins.identity.generic:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('v3token = 
keystoneauth1.loading._plugins.identity.v3:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('password = 
keystoneauth1.loading._plugins.identity.generic:Password')
  DEBUG (session:248) REQ: curl -g -i -X GET http://10.0.1.3:5000/v2.0 -H 
"Accept: application/json" -H "User-Agent: keystoneauth1/2.3.0 
python-requests/2.9.1 CPython/2.7.6"
  INFO (connectionpool:207) Starting new HTTP connection (1): 10.0.1.3
  DEBUG (connectionpool:387) "GET /v2.0 HTTP/1.1" 200 334
  DEBUG (session:277) RESP: [200] Content-Length: 334 Vary: X-Auth-Token 
Keep-Alive: timeout=5, max=100 Server: Apache/2.4.7 (Ubuntu) Connection: 
Keep-Alive Date: Fri, 18 Mar 2016 12:41:58 GMT Content-Type: application/json 
x-openstack-request-id: req-a0c68cd5-ea29-4391-942f-130cc69d15f8
  RESP BODY: {"version": {"status": "stable", "updated": 
"2014-04-17T00:00:00Z", "media-types": [{"base": "application/json", "type": 
"application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links": 
[{"href": "http://10.0.1.3:5000/v2.0/;, "rel": "self"}, {"href": 
"http://docs.openstack.org/;, "type": "text/html", "rel": "describedby"}]}}

  DEBUG (v2:63) Making authentication request to 
http://10.0.1.3:5000/v2.0/tokens
  DEBUG (connectionpool:387) "POST /v2.0/tokens HTTP/1.1" 200 2465
  DEBUG (session:248) REQ: curl -g -i -X GET 
http://10.0.1.3:8774/v1.1/b77d640e127e488fb42a7c0716ba53a5 -H "User-Agent: 
python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: 
{SHA1}381893576ad46c62b587f4963d769b89441b919a"
  INFO (connectionpool:207)

[Group.of.nepali.translators] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text

2016-12-11 Thread Jeremy Bicha 
I'm reopening the Abiword task since there is apparently a flickering
problem with abiword on Ubuntu 17.04 Alpha (using GTK 3.22) and one of
the developers pointed back to this bug.

http://bugzilla.abisource.com/show_bug.cgi?id=13815#c24

** Changed in: abiword (Ubuntu)
   Status: Invalid => Confirmed

** Bug watch added: AbiSource bug tracker #13815
   http://bugzilla.abisource.com/show_bug.cgi?id=13815

** Tags added: zesty

** Changed in: abiword (Ubuntu Xenial)
   Status: Invalid => Confirmed

** Changed in: abiword (Ubuntu Xenial)
   Importance: Undecided => High

** Description changed:

  After adding some text in a new document, the entire document (including
  gray page background, text, text cursor) starts to flicker very fast.
  The UI above does not flicker. This happens too on a different system in
  VirtualBox. (Lubuntu 16.04 i386)
  
- Workaround
- ==
+ Workaround for Ubuntu 16.04 LTS
+ ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel
- 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1574278

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in lubuntu-artwork package in Ubuntu:
  Invalid
Status in abiword source package in Xenial:
  Confirmed
Status in gtk+3.0 source package in Xenial:
  Confirmed
Status in lubuntu-artwork source package in Xenial:
  Invalid

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/abiword/+bug/1574278/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp