*** This bug is a duplicate of bug 1303876 ***
https://bugs.launchpad.net/bugs/1303876
Having dug into the workings of the vpn-agent for icehouse, this bug
report now makes alot of sense.
The vpn-agent is a superset of the function of the l3-agent; so in
effect, it provides both l3 services
** Also affects: neutron (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/havana
Importance: Undecided
Status: New
** Changed in: neutron (Ubuntu Saucy)
Status:
** Changed in: neutron (Ubuntu)
Assignee: James Page (james-page) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1243352
Title:
Installing Neutron LinuxBridge
I really struggle to support this change. It is a clearly impactful
change. FFe raised on the day of Final Freeze. Feels rushed. There is
no commentary on the regression potential, or the testing done.
Not to mention that RC1 was happily released with a broken MAAS
installer, that took 2 weeks
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: juju-core (Ubuntu Trusty)
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu Trusty)
Status: New = Triaged
** Changed in: juju-core (Ubuntu Trusty)
Importance:
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu Trusty)
Status: New = Triaged
** Changed in: juju-core (Ubuntu Trusty)
Importance:
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: juju-core (Ubuntu Trusty)
Hello Chuck, or anyone else affected,
Accepted neutron into saucy-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/neutron/1:2013.2.3-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu Trusty)
Status: New = Triaged
** Changed in: juju-core (Ubuntu Trusty)
Importance:
Hello Chuck, or anyone else affected,
Accepted ceilometer into saucy-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/ceilometer/2013.2.3-0ubuntu1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Chuck, or anyone else affected,
Accepted nova into saucy-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/nova/1:2013.2.3-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu Trusty)
Importance: Undecided = Medium
** Changed in: juju-core (Ubuntu Trusty)
Hello Chuck, or anyone else affected,
Accepted cinder into saucy-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/cinder/1:2013.2.3-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Chuck, or anyone else affected,
Accepted heat into saucy-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/heat/2013.2.3-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Chuck, or anyone else affected,
Accepted horizon into saucy-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/horizon/1:2013.2.3-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: juju-core (Ubuntu Trusty)
Same tests repeated for the Ubuntu Cloud Archive -proposed pocket; no
problems found.
Targetting 17th for release to -updates (probably alongside 2013.2.3).
** Changed in: cloud-archive
Status: New = Invalid
** Changed in: cloud-archive/havana
Status: New = Fix Committed
**
This bug was fixed in the package neutron - 1:2014.1~rc2-0ubuntu3
---
neutron (1:2014.1~rc2-0ubuntu3) trusty; urgency=medium
* Fix the Breaks/Replaces from the previous version, as they were
accidentally added to the wrong package (and with the wrong versioning).
neutron
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1293676
Title:
internal server error when marking nodes as
Hi Dave,
It is a certification requirement hence needs to be on the ISO. We had
discussed this with Adam and he had been reviewing the code and gave us
pointer to address. He unofficially approved the FFe before final freeze.
On Apr 11, 2014 4:50 AM, Dave Walker davewal...@ubuntu.com wrote:
I
Andres, is that Fix Released in Saucy too?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1301569
Title:
Missing import in maas-ipmi-autodetect-tool
To manage notifications about
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1187826
Title:
Cannot upload files with maas-cli
To manage
There's no regression potential per se because this doesn't affect the
current Maas operation as this will only be in effect if the user enables
the capability. Other than that this has been QA'd and testes on the field.
On Apr 11, 2014 4:50 AM, Dave Walker davewal...@ubuntu.com wrote:
I really
I wouldn't say I unofficially approved the FFe, that's twisting my
words and the content of our conversations. I gave you the reasons why
I would flat out reject the upload (FFe or not), and even petition to
have it removed from the archive if the install non-free software by
default feature
Hi Adam,
Sorry for the misunderstanding but to me the answer to my question (Yeah,
I think that would satisfy me.) as to whether this was enough to get the
FFe approved sounds like an unofficial ACK.
So the question is now... Will this be ACK'd or NACK'd?
On Apr 11, 2014 8:16 AM, Adam Conrad
Can you test the crap out of the new codepaths here, especially in any
way that they interact with existing functionality (ie: the web UI,
etc)? If you guys are satisfied that this won't make anything any more
broken than it already is, I might be inclined to be a Very Nice Person,
and let you
** Tags removed: need-duplicate-check
--
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/1306575
Title:
package nova-common 1:2014.1~rc2-0ubuntu1 failed to install/upgrade:
Public bug reported:
Upgrade test from Precise AMD64 to Trusty with nearly all of main
installed.
Note that nova.conf has not been manually modified before upgrade.
From apt-term.log:
Setting up nova-common (1:2014.1~rc2-0ubuntu1) ...
Installing new version of config file
Adam,
This was tested yesterday both manually by us and was also tested at a
customer site with successful results. We will give him another round of
testing. Sorry if I've been causing too much of a headache for you! I hope
you understand that me pushing this is due comes from high up. Thanks.
On Friday 11 Apr 2014 12:26:59 Adam Conrad wrote:
Can you test the crap out of the new codepaths here, especially in any
way that they interact with existing functionality (ie: the web UI,
etc)? If you guys are satisfied that this won't make anything any more
broken than it already is, I
This bug was fixed in the package cherrypy3 - 3.2.2-4ubuntu5
---
cherrypy3 (3.2.2-4ubuntu5) trusty; urgency=medium
* Use python3:* variables in debian/control.
-- Matthias Klose d...@ubuntu.com Tue, 25 Mar 2014 17:01:18 +0100
** Changed in: cherrypy3 (Ubuntu)
Status: In
The manpage moves in 1.13.1~rc1-0ubuntu1 did not have appropriate
Breaks/Replaces, resulting in overrwrite errors.
** Also affects: swift-storage (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: swift-storage (Ubuntu)
** Also affects: swift (Ubuntu)
Importance:
** Changed in: walinuxagent (Ubuntu Saucy)
Importance: Undecided = Critical
** Changed in: walinuxagent (Ubuntu Saucy)
Status: New = In Progress
** Changed in: walinuxagent (Ubuntu Saucy)
Assignee: (unassigned) = Robert C Jennings (rcj)
--
You received this bug notification
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1303649
Title:
systemd-logind spins in cgmanager_ping_sync()
Public bug reported:
The default configuration of dnsmasq creates an open recursive name
server, meaning that from anywhere on the Internet a request can be sent
to dnsmasq. This is problematic as UDP packets can be spoofed and DNS
has a high amplification factor, which makes it a ready tool for
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: New = Confirmed
** Changed in: maas (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: systemd (Ubuntu)
Status: New = Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because
Confirmed fix in a new install using Trusty iso 2014-apr-11 ... MAAS
front end is functional on first boot.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1298559
Title:
Internal
Public bug reported:
this package fails after upgrading to ubuntu 14.04.
After the upgrade I had issue same issue as know , was fixed by uninstalling
and then reinstalling , but now I get the same error when starting up cold
computer
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1306664
Title:
package libkadm5srv-mit8 (not installed) failed to install/upgrade:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Looks like 2.69 was released on 9 April. We have been in feature freeze
for Trusty since 20 Februrary, and final freeze was yesterday, so I
don't think that we'll be able to do this in time for Trusty. But as
Actually the source of the problem is that I was calling
nih_dbus_setup(), which actually sets up the mainloop. It is not needed
- as I thought it was - for making *_sync calls from cgmanager-
client.so. So the right fix is to not call that.
Two comments on this. First, nih_dbus_setup() seems
This was superceded by a security upload and will need to be redone for
Saucy and Precise.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/743858
Title:
sshd not appending to
This was fix-committed to trunk at revno 2241.
** Changed in: maas (Ubuntu)
Status: New = Triaged
** Changed in: maas (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
Public bug reported:
The current packaged version of /etc/maas/bootresources.yaml references daily
builds of trusty.
This is because until recently there was nothing marked 'release' (because
release wasn't done yet).
Having the daily stream installed by default is not acceptable as the
daily
** Changed in: maas (Ubuntu)
Importance: High = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1306335
Title:
maas-dhcp needs to quote interface name in
You have been subscribed to a public bug:
Cloud Sigma has asked that we update the DataSource in Cloud-init to
support the 14.04 VendorData construct. The regression potential for
this change is low, as only the cloud-init Cloud-Sigma datasource is
changed, a test suite has been provided and it
Public bug reported:
E: Could not get lock /var/cache/apt/archives/lock - open (11: Resource
temporarily unavailable)
E: Unable to lock directory /var/cache/apt/archives/
This is Ubuntu 12.04 LTS
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: postfix (not installed)
** Description changed:
The current packaged version of /etc/maas/bootresources.yaml references daily
builds of trusty.
This is because until recently there was nothing marked 'release' (because
release wasn't done yet).
Having the daily stream installed by default is not acceptable as
Attached patch showing that changes only affect the Cloud Sigma DS.
** Summary changed:
- CloudSigma Datasource doesn't handle vendor-data correctly
+ [FFe] CloudSigma Datasource doesn't handle vendor-data correctly
** Changed in: cloud-init
Assignee: (unassigned) = Ben Howard (utlemming)
Right. So to be completely clear, by calling nih_dbus_setup(), nih was
registering a libdbus handler that runs on the client side such that
whenever libdbus deemed necessary, it would attempt to wake up the
clients main loop by calling nih_main_loop_interrupt(). However, since
the client didn't
** Changed in: dnsmasq (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1306646
Title:
dnsmasq provides recursive answers to the
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1306710
Title:
package postfix (not installed) failed to install/upgrade: subprocess
So, yes, this is something that should be fixed, however, if you have
access to the database, you can just add data to it to tell Juju to spin
up a unit on the bootstrap node that runs as root and you can then do
whatever you want with it. So, while it would be better for
appearances' sake to not
** Description changed:
Cloud Sigma has asked that we update the DataSource in Cloud-init to
support the 14.04 VendorData construct. The regression potential for
this change is low, as only the cloud-init Cloud-Sigma datasource is
changed, a test suite has been provided and it has been
If this is well tested, the change looks small and sane enough to me.
Go for it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1303986
Title:
[FFe] CloudSigma Datasource
The change is small and looks reasonable to me, so FFe granted. However
we are in final freeze, so you'll need to justify why we need this now
rather than post-release as a SRU.
** Changed in: cloud-init (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are
FYI, python-sendfile also needs a MIR.
** Also affects: py-sendfile (Ubuntu)
Importance: Undecided
Status: New
** Changed in: py-sendfile (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: juju-core
Milestone: 1.18.1 = 1.19.0
** Also affects: juju-core/1.18
Importance: Undecided
Status: New
** Changed in: juju-core/1.18
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core/1.18
Importance: Undecided = Critical
** Changed in:
** Branch linked: lp:ubuntu/saucy-proposed/ceilometer
** Branch linked: lp:ubuntu/saucy-proposed/heat
** Branch linked: lp:ubuntu/saucy-proposed/horizon
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Branch linked: lp:ubuntu/trusty-proposed/systemd
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1303649
Title:
systemd-logind spins in cgmanager_ping_sync()
To manage notifications
** Branch linked: lp:~ubuntu-server-dev/nova/icehouse
--
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/1306484
Title:
Icehouse: nova-compute-vmware requires genisoimage package
To
** Changed in: cloud-archive
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1304107
Title:
Libvirt error launching instance - Device 'virtio-net-pci'
Thanks all for the comments and discussion.
Responding to some key points:
* building confidence in code changes both for this FFE and subsequent
SRUs is important, the archive and RM teams have a mandate to seek
comfort on that front before ack'ing an upload under either
circumstances
* in
This bug was fixed in the package lxc - 1.0.3-0ubuntu2
---
lxc (1.0.3-0ubuntu2) trusty; urgency=medium
* Cherry-pick upstream fix for cgmanager integration. (LP: #1303649)
-- Stephane Graber stgra...@ubuntu.com Fri, 11 Apr 2014 12:17:41 -0400
** Changed in: lxc (Ubuntu)
This bug was fixed in the package tgt - 1:1.0.43-0ubuntu4
---
tgt (1:1.0.43-0ubuntu4) trusty; urgency=medium
* debian/patches/fix_delayed_management_request.patch: Adjust patch to fix
a FTBFS.
* debian/patches/fix_leak_of_task_in_scsi_flag.patch: Adjust patch to fix
a
** No longer affects: py-sendfile (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to heat in Ubuntu.
https://bugs.launchpad.net/bugs/1267557
Title:
[MIR] heat
To manage notifications about this bug go to:
Scott, thanks for the information. I wasn't aware of that.
Given the new rationale, I think we can mark this bug as triaged.
** Changed in: maas
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas
Also, thank you Adam for pointing out that we need to do the same sort
of ubiquity- and jockey-like calling out of the issues associated with
binary blobs on servers that we do on the PC. I'll get the MAAS folks to
make that very clear on the node page as a way of socialising the
benefits of open
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
--
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/1306484
Title:
Icehouse: nova-compute-vmware requires
Right, so the key here (on the software freedom front), as it was with
ubiquity when we discussed it, is that the option needs to be off by
default. If a sysadmin turns it on (and I don't doubt that many will),
that's entirely fine, but they need to be the ones explicitly making the
call.
If we
(To be clear to people following along, I'm fine with Mark's assessment
and explicit ACK of the FFe, and we'll happily accept the feature being
uploaded under his conditions of being heavily tested, etc, the above
quibbling is only about if the feature is on or off in a default setup)
--
You
So, it's been noted that this is slightly different from the
desktop/ubiquity case only in that the ubiquity case presents the user
up-front with the do you want non-free stuff? toggle on an installer
page, while maas is putting it in a settings page.
So, for starters, I think the settings page
** Also affects: cloud-init (Ubuntu Trusty)
Importance: Undecided
Assignee: Ben Howard (utlemming)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssh (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
** Changed in: juju-core/1.18
Status: Fix Committed = Fix Released
--
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/1303880
Title:
Juju 1.18.0, can not deploy local charms
** Changed in: juju-core/1.18
Status: Fix Committed = Fix Released
--
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/1303735
Title:
public-address change to internal bridge
** Changed in: juju-core/1.18
Status: Fix Committed = Fix Released
--
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/1306296
Title:
juju cannot downgrade to same major.minor
** Changed in: juju-core/1.18
Status: Fix Committed = Fix Released
--
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/1303697
Title:
peer relation disappears during upgrade of
** Changed in: juju-core/1.18
Status: Fix Committed = Fix Released
--
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/1299802
Title:
upgrade-juju 1.16.6 - 1.18 (tip) fails
To
** Changed in: juju-core/1.18
Status: Fix Committed = Fix Released
--
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/1306208
Title:
juju scp no longer allows multiple extra
** Changed in: libnih (Ubuntu)
Status: Confirmed = Invalid
** Changed in: cgmanager (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I still was not able to reproduce this, using virt-manager on trusty and
using mostly the defaults.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/746114
Title:
FreeBSD freeze
In comment #9 you said with vanilla kernel - can you please list the
exact kernel versions you've tried (and which qemu versions you tried
with them, including whether they were hand-built from git or packages
from Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package systemd - 204-5ubuntu19
---
systemd (204-5ubuntu19) trusty; urgency=medium
* cgmanager: don't call nih_dbus_setup() since we won't use the
nih_mainloop(). (LP: #1303649)
-- Serge Hallyn serge.hal...@ubuntu.com Fri, 11 Apr 2014 10:17:04
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1218959
Title:
KVM virbr# no longer forwards multicast
Public bug reported:
When upstart is enabled, sshd stops accepting new connections after
reloading configuration by initctl reload ssh.
It looks like sshd is frozen with SIGSTOP after receiving SIGHUP.
[nya@sora ~]% ps auxww | grep sshd
root 10557 0.0 0.1 61364 3056 ?Ss 13:46
Public bug reported:
Hi there;
libvirt in trusty has a bug where VM's fail to get defined due to PCI
bus ordering bugs.
Redhat bug tracker info here: https://bugzilla.redhat.com/show_bug.cgi?id=823535
Appears to be the same bug.
Steps to reproduce:
* Open Virt-manager
* Define a new VM
(
89 matches
Mail list logo
