** Changed in: neutron (Ubuntu)
Status: New => Fix Released
** Changed in: neutron (Ubuntu)
Assignee: Felipe Reyes (freyes) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Changed in: neutron (Ubuntu)
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677668
Title:
no GARPs during ephemeral boot
To manage notifications about this bug go to:
** Patch removed: "lp1692334-artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-neutronclient/+bug/1692334/+attachment/4880848/+files/lp1692334-artful.debdiff
** Patch added: "lp1692334-artful.debdiff"
Attaching patch for artful
** Patch added: "lp1692334-artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-neutronclient/+bug/1692334/+attachment/4880848/+files/lp1692334-artful.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Once this is fixed in Artful, I'll SRU the fix into Z, Y and X.
** Changed in: python-neutronclient (Ubuntu)
Assignee: (unassigned) => Felipe Reyes (freyes)
** Changed in: python-neutronclient (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification becau
Public bug reported:
[Impact]
Upstream's bash completion helper ( https://github.com/openstack/python-
neutronclient/blob/master/tools/neutron.bash_completion ) is not
installed.
debian/rules copies neutron.bash_completion file to $(CURDIR)/debian
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664306
Title:
[SRU] newton stable releases
To manage notifications about this bug go to:
> It's recommended to use the snap going forward. As we will be removing
> charm-tools from the archive.
>
> `snap install charm`
The current version of the charm snap does not provide charm-proof[0],
so in the meantime I have a temporary ppa with charm-tools 2.2.0 +
workaround in #16 worked. Thanks @mbirth
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Recent updates broke Ubuntu on Raspberry Pi 3
To manage notifications about this bug go to:
Public bug reported:
Steps to reproduce:
1) git clone https://github.com/juju/juju # probably any golang source code
will trigger the problem
2) cd juju
3) go vet ...
Here is a sample of one of the errors:
go version go1.7.4
checking: go fmt ...
checking: go vet ...
panic: inconsistent
Any updates on neutron 9.1.1?, neutron 9.2.0 (newton) was already
released https://docs.openstack.org/releasenotes/neutron/newton.html
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Xenial is receiving network-manager-applet 1.2.6, the SRU is being
tracked in bug 1619354
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570738
Title:
nm-applet coredumped when asking for a new
Xenial is receiving network-manager-applet 1.2.6, the SRU is being
tracked in bug 1619354
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618424
Title:
The internet applet crashes randomly.
To
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619354
Title:
[SRU] Upgrade network-manager-applet to latest point release
To manage notifications about this bug go to:
On Thu, Jan 12, 2017 at 03:56:19PM -, ChristianEhrhardt wrote:
> ** Package changed: sosreport (Ubuntu) => juju-core (Ubuntu)
This is not a juju bug, this is a sosreport bug/RFE to properly get juju
configuration which previously was stored in a file (environments.yaml)
and now available via:
Brian, is there any reason to not push this SRU into yakkety-updates as
well?, it went into xenial-updates first :\
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640919
Title:
pcs cluster setup
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580035
Title:
pcsd does not start due to missing ruby gem orderedhash
To manage notifications about this bug go to:
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580045
Title:
pcsd does only bind to IPv6
To manage notifications about this bug go to:
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640919
Title:
pcs cluster setup hangs
To manage notifications about this bug go to:
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580045
Title:
pcsd does only bind to IPv6
To manage notifications about this
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580035
Title:
pcsd does not start due to missing ruby gem orderedhash
To manage
For the record, this is the script used to setup a clean machine with
pcs:
sudo apt-get -q update
sudo apt-get -q -y install pcs
# we make sure corosync and pacemaker are stopped
sudo systemctl stop pacemaker
sudo systemctl stop corosync
# we remove corosync.conf, otherwise pcs will refuse to
The version available in yakkety-update does fix this issue. Evidence ->
http://pastebin.ubuntu.com/23737093/
** Tags added: verification-done-yakkety
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
The version available in xenial-updates does fixes this issue. Evidence
-> http://pastebin.ubuntu.com/23736947/
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The package available in xenial-updates does bind correctly to tcp and
tcp6 . Evidence -> http://pastebin.ubuntu.com/23735727/
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The version available in xenial-proposed does fix this issue. Evidence
-> http://pastebin.ubuntu.com/23735665/
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620897
Title:
Fix race on getting close notifier channel
To manage notifications about this bug go to:
The version of python-virtualenv available in xenial-proposed runs
autopkgtest without issues.
$ autopkgtest -U --apt-pocket=proposed python-virtualenv -- lxd
autopkgtest/ubuntu/xenial/amd64
autopkgtest [17:50:05]: version 4.1
...
Setting up python3-virtualenv (15.0.1+ds-3ubuntu1) ...
...
** Description changed:
+ [Impact]
+
+ autopkgtest execution for Xenial is broken, blocking automated inclusion
+ into xenial-updates of SRUs for packages that python-virtualenv depends
+ on. So human intervention is needed.
+
+ [Test Case]
+
+ $ pull-lp-source python-virtualenv xenial
+ $
While SRUing a fix for bug 1626258, it was brought my attention to this
bug as the blocker to automatically get my fix into xenial-updates, so
here I'm attaching the same fix that landed in Yakkety
** Changed in: python-virtualenv (Ubuntu Xenial)
Assignee: (unassigned) => Felipe Re
Test case for xenial passes -> http://pastebin.ubuntu.com/23457302/
Test case for yakkety passes -> http://pastebin.ubuntu.com/23457392/
** Tags removed: verification-needed
** Tags added: verification-done verification-done-xenial
verification-done-yakkety
--
You received this bug
this is a problem since 3.2+git276-g7da50d6-2 , the version available in
trusty-backport is not affected.
** Tags removed: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1635722
Title:
Public bug reported:
swapon from trusty, used by sosreport since 3.2, doesn't support the
option --show.
sos_commands/memory/swapon_--bytes_--show
swapon: unrecognized option '--bytes'
Usage:
swapon [options] []
Options:
-a, --all enable all swaps from /etc/fstab
-d, --discard
Refreshed xenial patch (using 0.4), and added Y/Z patches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626258
Title:
[SRU] AttributeError: 'Requirement' object has no attribute
'project_name'
** Patch added: "lp1626258_yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1626258/+attachment/4764567/+files/lp1626258_yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1626258_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1626258/+attachment/4764568/+files/lp1626258_xenial.debdiff
** Description changed:
[impact]
pip 8.1.1 (xenial) tries to access properties that were dropped from the
Requirement
Assignee: (unassigned) => Felipe Reyes (freyes)
** Patch removed: "lp1626258_xenial(old).debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1626258/+attachment/4746252/+files/lp1626258_xenial.debdiff
** Patch removed: "lp1626258_xenial.debdiff"
h
** Patch removed: "lp1626258_yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1626258/+attachment/4756746/+files/lp1626258_yakkety.debdiff
** Patch added: "lp1626258_yakkety.debdiff"
Attaching debdiff for yakkety
** Patch added: "lp1626258_yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1626258/+attachment/4756746/+files/lp1626258_yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
These are my findings:
1) debian/tests/*.sh scripts install a python package called 'world'[0], a new
version of that package was uploaded in August 24th (version 4.0), this new
version requires python >=3.4[1], so d/t/pip2-*.sh need to install world==3.1
2) pip tries to build a wheel during
Running autopkgtests for python-pip 8.1.1-2ubuntu0.2 (the one currently
-updates) shows the same problems in my local machine.
$ adt-run python-pip -U --apt-pocket=proposed --- qemu
adt-xenial-amd64-cloud.img
...
adt-run [14:00:00]: test pip3-editable.sh: [---
Obtaining
On Tue, 04 Oct 2016 16:20:17 -
Robie Basak <1626...@bugs.launchpad.net> wrote:
> This is currently blocked by autopkgtest regressions in python-pip and
> python-virtualenv - see http://people.canonical.com/~ubuntu-archive
> /pending-sru.html
>
> They look unrelated so I've requested retests
Another candidate to be backported
https://github.com/sosreport/sos/commit/1fd12690870e85e8ac83b0e99bb272ce4489dc60
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628749
Title:
rfd.write(html):
Upstream commit that fixes the issue
https://github.com/sosreport/sos/commit/5e4991f3d9b3b9356e6a3e1551adf9ce753a03e2
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628749
Title:
The version available in yakkety contains the fix as well
** Changed in: sosreport (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628749
Title:
** Changed in: sosreport (Ubuntu)
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628749
Title:
rfd.write(html): UnicodeEncodeError: 'as
It worked here too. Testing evidence can be found at
http://pastebin.ubuntu.com/23244256/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626258
Title:
[SRU] AttributeError: 'Requirement' object has
Updated patch to address louis' feedback (renamed patch to give a more
meaningful name, add dep3 headers)
** Patch removed: "lp1626258_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1626258/+attachment/4745640/+files/lp1626258_xenial.debdiff
** Patch added:
** Tags added: sts-sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626258
Title:
[SRU] AttributeError: 'Requirement' object has no attribute
'project_name'
To manage notifications about this
Attaching debdiff for xenial
** Patch added: "lp1626258_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1626258/+attachment/4745640/+files/lp1626258_xenial.debdiff
** Description changed:
[impact]
pip 8.1.1 (xenial) tries to access properties that were
Yakkety has pip 8.1.2, so devel series is ok, this just affects Xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626258
Title:
AttributeError: 'Requirement' object has no attribute
Wed, 11 Nov 2015 18:51:46 -0500
Subject: [PATCH] Update to use the Requirement class from packaging
https://github.com/pypa/pip/commit/8e236dd6a09bd2f70f9d4fc886da8c354d4c58f2
** Affects: python-pip (Ubuntu)
Importance: Undecided
Assignee: Felipe Reyes (freyes)
Status: New
** Tags:
Tested on trusty:
Providers tested:
* openstack (liberty)
* maas 1.9.4 + LXC containers
Environments:
* openstack basic deployment (cinder, nova, glance, neutron)
* mediawiki + memcached + mysql
* wordpress + mysql
In all the environments a clean bootstrap using 1.25.6 and upgrading
from
Tried with 4.8.0-040800rc2-generic and the problem is still there
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581088
Title:
Middle mouse (wheel-click) button stopped working after upgrade to
Andres, it seems you forgot to change the tag to verification-done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551937
Title:
lvm and multipath and xenial not happy together
To manage
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588547
Title:
Generated bonding configuration is incorrect.
To manage
...
$ gcalcli agenda
Sun Jun 26 [...]
** Tags removed: verification-needed
** Tags added: verification-done
** Changed in: python-googleapi (Ubuntu Xenial)
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bu
** Description changed:
[Impact]
When using google's python client, it's not possible to benefit from
caching capabilities provided by oauth2client due to a wrong import.
This was fixed in 1.5.1, which is the version available in yakkety.
[Test Case]
* Install gcalcli
Here I'm attaching a patch to fix Xenial, I've been testing it locally
and it works OK for my use cases.
** Changed in: python-googleapi (Ubuntu)
Assignee: (unassigned) => Felipe Reyes (freyes)
** Patch added: "lp1594437_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+
Public bug reported:
[Impact]
When using google's python client, it's not possible to benefit from
caching capabilities provided by oauth2client due to a wrong import.
This was fixed in 1.5.1, which is the version available in yakkety.
[Test Case]
* Install gcalcli (apt-get install gcalcli)
*
On Tue, 07 Jun 2016 17:31:19 -
Robie Basak <1588...@bugs.launchpad.net> wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> This is certainly worthy of a release note, and I have edited the
> Xenial release notes to highlight this issue.
>
>
** Description changed:
[Impact]
When a user has configured their authorized_keys file with the directive
"from=" to restrict the usage of those keys, if that server is upgraded
to Xenial (or Wily) the user may get locked out.
[Test Case]
* Create 3 containers (client,
** Summary changed:
- authorized_keys using from="hostnamee" no longer work when upgrading to Xenial
+ authorized_keys using from="hostname" no longer work when upgrading to Xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Impact]
When a user has configured their authorized_keys file with the directive
"from=" to restrict the usage of those keys, if that server is upgraded
to Xenial (or Wily) the user may get locked out.
[Test Case]
* Create 3 containers (client, trusty, xenial)
$ lxc
I'm filing this bug as way to document this change in the behavior and
how to restore trusty's behavior, but also to get feedback from
Foundations if this is something that could be fixed in the distro when
a openssh-server is being upgraded from older versions.
--
You received this bug
** Changed in: heat (Ubuntu Wily)
Assignee: (unassigned) => Felipe Reyes (freyes)
** Changed in: cloud-archive/liberty
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Heat from liberty-proposed fixes the issue
Evidence:
$ heat stack-create -f minimal_portneutron.yaml minimal_portneutron
+--+-++-+--+
| id | stack_name
James, sure, I'll do it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579891
Title:
[SRU] Validating a stack fails as one nested stack can't find an id
from another
To manage notifications
The version in wily-proposed fixes the problem
Evidence:
$ heat stack-create -f minimal_portneutron.yaml minimal_portneutron
+--+-++-+--+
| id |
I can commission nodes with trusty using the package from -proposed
Evidence: screenshot while commissioning node
with maas from -updates:
http://people.canonical.com/~freyes/lp1573046-from-updates.png
with maas from -proposed:
http://people.canonical.com/~freyes/lp1573046-from-proposed.png
** Description changed:
[Impact]
- when a user tries to
+ when a user tries to create nested templates, the network id cannot be
+ retrieved raising an error, this works fine in Kilo.
[Test Case]
* Deploy openstack with heat enabled
- $ bzr branch lp:openstack-charm-testing
- $
Xenial (mitaka) already contains the fix, it's just needed in Liberty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579891
Title:
[SRU] Validating a stack fails as one nested stack can't find an
** Patch added: "lp1579891_wily.debdiff"
https://bugs.launchpad.net/ubuntu/+source/heat/+bug/1579891/+attachment/4659447/+files/lp1579891_wily.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Impact]
when a user tries to create nested templates, the network id cannot be
retrieved raising an error, this works fine in Kilo.
[Test Case]
* Deploy openstack with heat enabled
$ bzr branch lp:openstack-charm-testing
$ cd openstack-charm-testing
$ juju deployer
Now xenial comes with python3-maas-client, so you can use python3, but
you can't use python2. Maybe the path to go is to use maasclient[0]: "
py2/3 maas client http://maasclient.rtfd.org/ "
[0] https://github.com/Ubuntu-Solutions-Engineering/maasclient
--
You received this bug notification
** Changed in: maas (Ubuntu Trusty)
Assignee: Felipe Reyes (freyes) => (unassigned)
** Changed in: maas (Ubuntu Wily)
Assignee: Felipe Reyes (freyes) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553815
Title:
host keys never restored following metadata api outage
To
For the record, this was fixed in revno 1188 (upstream)[0], available
since cloud-init version 0.7.7~bzr1192-0ubuntu1[1]
[0] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/1188
[1]
http://bazaar.launchpad.net/~smoser/ubuntu/xenial/cloud-init/pkg/revision/452
** Also
On Sat, 30 Apr 2016 03:43:31 -
Andres Rodriguez wrote:
> Theres currently an SRU *already* in progress.
Great, thanks for the update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) => Felipe Reyes (freyes)
** Changed in: maas (Ubuntu Wily)
Assignee: (unassigned) => Felipe Reyes (freyes)
** Changed in: maas (Ubuntu)
Assignee: Felipe Reyes (freyes) => (unassigned)
--
You received
This problem is affecting the version available in trusty-updates
(1.7.6+bzr3376-0ubuntu2~14.04.1) and Wily (1.8.3+bzr4053-0ubuntu1), I'll
SRU the fix
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Assignee: (unassigned) => Fel
you can edit the /usr/share/applications/hexchat.desktop and
replace "Exec=hexchat %U" with "Exec=env UBUNTU_MENUPROXY=0 hexchat %U"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560272
Title:
No
** Changed in: libvirt (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561019
Title:
copied cpu flags don't match host cpu
To manage notifications about
Public bug reported:
Steps to reproduce:
1) Create VM using virt-install
2) Delete the VM with its associated volume
Expected results:
The VM is removed and the volume is deleted
Actual results:
When trying to remove the volume the following error is printed:
Errors encountered while
15856773/
The command line I used to create this vm was:
$ uvt-kvm create --memory 2048 --cpu 2 lp1561019 release=trusty arch=amd64
Using virt-manager for the bootstrap of the VM doesn't produce different
results.
Best,
--
Felipe Reyes
Software Sustaining Engineer @ Canonical
STS Engineering Tea
** Description changed:
Using wily (libvirt 1.2.16-2ubuntu11.15.10.3) in a AMD FX-8350 nested
KVM doesn't work, unless in the definition of the vm the cpu is
configured with mode='host-passthrough', for other CPUs the
manifestation could be different.
+
+ Steps to reproduce:
+
+ L0:
Public bug reported:
Using wily (libvirt 1.2.16-2ubuntu11.15.10.3) in a AMD FX-8350 nested
KVM doesn't work, unless in the definition of the vm the cpu is
configured with mode='host-passthrough', for other CPUs the
manifestation could be different.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Public bug reported:
Using wily (libvirt 1.2.16-2ubuntu11.15.10.3) in a AMD FX-8350 nested
KVM doesn't work, unless in the definition of the vm the cpu is
configured with mode='host-passthrough', for other CPUs the
manifestation could be different.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
On Wed, 02 Dec 2015 09:46:49 -
David Girault <1509...@bugs.launchpad.net> wrote:
> First, thanks for your detailled comment.
> Now, did you found any way to force gdm to only use vt > 7 ?
>
No, I didn't. The workaround I found was to force the initialization
vt{2..6}, in a systemd world
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage
** Changed in: evolution (Ubuntu Wily)
Assignee: (unassigned) => Felipe Reyes (freyes)
** Changed in: evolution (Ubuntu Wily)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1518988_wily.debdiff"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1518988/+attachment/4525311/+files/lp1518988_wily.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I installed ubuntu-gnome 15.04, then upgraded to Wily. I started getting
problems when pressing "Alt+" it switches to another virtual
terminal like if I was pressing Ctrl+Alt+F, after some
troubleshooting these are the steps to reproduce:
- Logged in a gnome session
-
After some research, I think this is not strictly related to
suspend/resume and more to how gdm selects the next VT available to
spawn your session and how systemd manages VTs initialization (getty on
demand). From http://0pointer.de/blog/projects/serial-console.html
"""
Traditionally, the init
Hello,
I'm getting same problem, different laptop, bios details:
Vendor: Alienware
Version: A02
Release Date: 12/16/2014
xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
kernel version: 3.19.0-30-generic
[477531.252120] [ cut here ]
** Tags added: openstack sts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1506257
Title:
rpcapi version mismatch possible on upgrade
To manage notifications about this bug go to:
** Tags added: openstack sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506257
Title:
rpcapi version mismatch possible on upgrade
To manage notifications about this bug go to:
I could successfully sync images (create bucket + upload images) with
package from trusty-proposed[0] and vivid proposed. I'm attaching
/var/log/glance-simplestreams-sync.log for trusty and vivid as evidence.
[0] *** 0.1.0~bzr341-0ubuntu2.4 0
500
201 - 300 of 479 matches
Mail list logo