Just an FYI if anyone trying to help or following this - I pretty much
nuked my controller and rebuilt it and now dont have this error anymore. No
clue why it fixed now. Im having other issues now with nova-conductor and
Nova Computer service, another authentication error it seems. I posted that
qu
—
Raghu
On Wednesday, Nov 12, 2014 at 2:13 PM, John Griffith
, wrote:
On Wed, Nov 12, 2014 at 11:16 AM, Amit Anand wrote:
> Hi all,
>
> So been trying to figure out why this is happening I was hoping yall could
> maybe shed some light on it asI really would not like to have recreate
> ever
On Wed, Nov 12, 2014 at 11:16 AM, Amit Anand wrote:
> Hi all,
>
> So been trying to figure out why this is happening I was hoping yall could
> maybe shed some light on it asI really would not like to have recreate
> everything on my controller node!
>
> So whenever I try to sync the nova database:
Hi all,
So been trying to figure out why this is happening I was hoping yall could
maybe shed some light on it asI really would not like to have recreate
everything on my controller node!
So whenever I try to sync the nova database:
su -s /bin/sh -c "nova-manage db sync" nova
I get this error in
Hello everyone,
Due to a number of issues discovered in the published Nova 2014.2 RC1
(including a security regression during the Juno development cycle), we
generated a new Juno release candidate. You can find the list of
bugfixes in this RC and a link to a source tarball at:
https://launchpad.n
