On 08 Jun 10:11, Finucane, Stephen wrote:
> On 07 Jun 11:36, Chris Friesen wrote:
> > Hi,
> >
> > The full details are available at
> > https://bugs.launchpad.net/nova/+bug/1590091 but the short version
> > is this:
> >
> > 1) I'm running stable
On 07 Jun 11:36, Chris Friesen wrote:
> Hi,
>
> The full details are available at
> https://bugs.launchpad.net/nova/+bug/1590091 but the short version
> is this:
>
> 1) I'm running stable/mitaka in devstack. I've got a small system
> with 2 pCPUs, both marked as available for pinning. They're
I'm working on a fix [1] for bug #1538227, "Failed `nova-manage db
sync` returns exitcode of 0" [2]. Having done this, I've noted that
there seems to be no consistent policy around (a) what return codes to
use (if any), and (b) whether to use logging or printing. Are there
any guidelines on this
Nova cores,
I would like to request a SFE for the below fix:
https://review.openstack.org/#/c/170190/
https://bugs.launchpad.net/nova/+bug/1438226
This change adds a useful error message to help users debug incompatibilities
with some versions of a dependency (libvirt). Without
