** Also affects: cinder
Importance: Undecided
Status: New
--
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/1368815
Title:
qemu-img convert intermittently corrupts output
** Tags added: icehouse-backport-potential
--
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/1297962
Title:
[sru] Nova-compute doesnt start
To manage notifications about this bug go to:
I can confirm that 1.0.46 fixes the issue. The force delete command
works properly without errors in syslog
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1305343
Title:
tgt connection
Public bug reported:
Under heavy load, openiscsi will sometimes report connection errors when
using tgt:
Apr 8 22:02:44 node003-cont001 iscsid: Connection2:0 to [target:
iqn.2010-10.org.openstack:volume-b32d317e-4063-4e4f-963e-b0fdc29198f9,
portal: 172.21.1.1,3260] through [iface: default] is
I believe this may be fixed by:
https://github.com/fujita/tgt/commit/e6e8d0fd3b83208278fb7ed765c3665ae7c5ab49
but also may require:
https://github.com/fujita/tgt/commit/05fc2cb424863fbf2f3c60a8b617308ef1e370c5
I'm doing a test of build 1.0.46 tgt to see if it resolves the issue.
--
You
** Changed in: nova
Status: New = Invalid
--
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/1091939
Title:
nova-network applies too liberal a SNAT rule
To manage notifications
Are you still seeing this? I suspect a packaging bug here. Perhaps an
old version of consoleauth is getting run or it has incorrect settings?
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova
Status: New = Invalid
--
You received this bug
** Also affects: nova/folsom
Importance: Undecided
Status: New
** Changed in: nova/folsom
Importance: Undecided = Medium
** Changed in: nova/folsom
Assignee: (unassigned) = Vish Ishaya (vishvananda)
** Changed in: nova/folsom
Assignee: Vish Ishaya (vishvananda) = Adam
Cinder and nova-api-os-volume use the same port on purpose. You have to
disable the volume api in nova if you want to use cinder.
As mentioned in point 10 here:
http://wiki.openstack.org/MigrateToCinder
You should make sure osapi_volume is ignored in your conf file.
force_hosts is not a hint meant to be exposed to a user. if you want to
force a host as an admin you can use the availability zone syntax:
nova boot --image uuid --flavor m1.tiny --key_name mykey
--availability-zone nova:sleepy
** Changed in: nova
Status: New = Won't Fix
--
You received
** Project changed: nova = openstack-manuals
--
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/1061665
Title:
Filter scheduler not respecting the force_hosts hint
To manage
this looks like a packaging bug to me.
state_path = /var/lib/cinder
or
volume_dir = /var/lib/cinder/volumes
should be being set in the conf file by the packaging.
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nova (Ubuntu)
** Also affects:
This sounds like a packaging issue, not a nova issue.
** 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/1066845
** Changed in: nova
Importance: Undecided = High
** Tags added: folsom-backport-potential
--
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/1065785
Title:
volume and snapshot IDs do
ugh, this is nasty. Looks like we need a migration for this. For
backport we could add a translation using the ec2_id table to convert
from the old name to the new one. Some testing needs to be done to
figure out if the new iqns are actually there in all cases or if there
is a case where the old
** Also affects: cinder
Importance: Undecided
Status: New
** Changed in: cinder
Importance: Undecided = High
--
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/1065702
Title:
** Tags removed: folsom-rc-potential
** Tags added: folsom-backport-potential
--
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/1029430
Title:
KVM guests networking issues with no virbr0
** Changed in: nova
Status: New = Triaged
** Changed in: nova
Importance: Undecided = Medium
--
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/1029430
Title:
KVM guests
I can't reproduce this on master.
** Changed in: nova
Status: New = Invalid
--
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/1033444
Title:
Deleting an added floating IP just
Do you have iscsi_ip_address set on the volume host? It needs to be an
ip that the compute hosts can hit. When the volume is created this ip is
stored for connection information in the database, so if you don't have
it set, you will probably need to set it, restart nova-volume and
recreate volumes
it should be getting the url from keystone anyway, so I don't imagine
that the nova url is a problem. I think it is far more likely that you
have an older version of novaclient that is overiding the one from
precise. Perhaps you have pip installed novaclient or done a setup.py
install?
--
You
Ah, deprecated auth is most likely the problem. I suspect deprecated
auth doesn't support multiple endpoints. It really is only still there
to allow you to transition to keystone. Is there some reason you haven't
switched?
--
You received this bug notification because you are a member of Ubuntu
it looks like precise has an older version of novaclient? this was
changed around e-3 timeframe when we gave the volume api its own
endpoint.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Here was the commit: a6ac8af69351cb39aa07f53e3327ff29b90383bc
We only left deprecated auth in essex for the purpose of migration, so
running a production system of deprecatd auth is definitely not
supported. That said, it is probably a pretty easy fix.
Add back in the project_id on register and
** Changed in: nova
Importance: Undecided = High
--
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/973377
Title:
/var/lib/nova/instances/_base has wrong permissions
To manage
Verified this bug exists in devstack as well:
2012-04-04 17:10:34 ERROR nova.manager [-] Error during
ComputeManager._run_image_cache_manager_pass: [Errno 13] Permission denied:
'/home/vagrant/_base/87ad83b59bbed6a3d3cea9afdf3e1fd36c694ac2'
2012-04-04 17:10:34 TRACE nova.manager Traceback (most
fyi, regression was introduced in
2c5112e5938e3d567504748f923fb198fad3117e
--
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/973377
Title:
/var/lib/nova/instances/_base has wrong
** Changed in: nova
Milestone: None = essex-rc4
--
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/973377
Title:
/var/lib/nova/instances/_base has wrong permissions
To manage
** Changed in: nova
Assignee: Vish Ishaya (vishvananda) = Chuck Short (zulcss)
--
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/973377
Title:
/var/lib/nova/instances/_base has
** Changed in: nova
Assignee: Vish Ishaya (vishvananda) = Adam Gandelman (gandelman-a)
--
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/959426
Title:
nova + glance services die
** Changed in: nova
Milestone: None = essex-rc2
--
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/959426
Title:
nova + glance services die if started before db is reachable
To
we discussed on irc. This is a separate bug
** Changed in: nova
Importance: Undecided = Medium
** Tags added: essec-rc-potential
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Changed in: nova
Importance: Undecided = High
** Changed in: nova
Status: New = Triaged
** Changed in: nova
Milestone: None = essex-rc1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Changed in: nova
Milestone: None = essex-rc1
--
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/954692
Title:
cannot detach volume from terminated instance
To manage notifications
** Changed in: nova
Assignee: Vish Ishaya (vishvananda) = Adam Gandelman (gandelman-a)
--
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/956366
Title:
self-referential security
** Changed in: nova
Assignee: Vish Ishaya (vishvananda) = Adam Gandelman (gandelman-a)
--
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/954692
Title:
cannot detach volume from
** Changed in: nova
Milestone: None = essex-4
--
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/934534
Title:
metadata ami-launch-index always returning 1
To manage notifications
hmm, looks like that fix wasn't quite right. Let me try another one.
** Changed in: nova
Assignee: Adam Gandelman (gandelman-a) = Vish Ishaya (vishvananda)
** Changed in: nova
Status: Fix Committed = In Progress
--
You received this bug notification because you are a member
Roman: can you see if the above fix works for you?
--
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/922232
Title:
Volumes fail to attach without discovery using tgt
To manage
** Changed in: nova
Assignee: (unassigned) = Vish Ishaya (vishvananda)
** Changed in: nova
Status: New = In Progress
** Changed in: nova
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud
review was here:
https://review.openstack.org/#change,706
Last request was if the ringbuffer handling could be done by a separate
helper binary so nova-compute could go down for a bit without locking up
instances.
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: nova
Assignee: (unassigned) = Vish Ishaya (vishvananda)
** Changed in: nova
Importance: Undecided = High
** Changed in: nova
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova
** Tags added: diablo-backport
--
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/859587
Title:
nova-network deletes default route
To manage notifications about this bug go to:
** Changed in: nova
Status: In Progress = Fix Committed
--
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/859587
Title:
nova-network deletes default route
To manage notifications
** Changed in: nova
Importance: Undecided = High
** Changed in: nova
Status: New = Confirmed
** Changed in: nova
Status: Confirmed = In Progress
** Changed in: nova
Assignee: (unassigned) = Vish Ishaya (vishvananda)
** Changed in: nova
Milestone: None = 2011.3
Hmm, this looks like a packaging issue. It looks like by default the
nova.conf is importing a new flagfile for nova-compute. If nova-compute
isn't installed that file won't exist. The error won't actually stop
anything from working, but it is annoying to see it pop up
Not sure about the best
Since there is a workaround, I'm setting this to low. We should at
least provide a flag allowing deployers to turn off key injection if
they don't want it.
** Changed in: nova
Importance: Undecided = Low
** Changed in: nova
Status: New = Triaged
--
You received this bug notification
This seems important, but I think we need a repro case. Dave: if uec-
publish-tarball is important for deployments, perhaps the best solution
is to do a test deployment using S3 frontend for swift and see if it is
possible to get nova to work with that instead of nova-objectstoer
--
You
Made a fix to this in my volume cleanup branch. backporting.
** Changed in: nova
Assignee: (unassigned) = Vish Ishaya (vishvananda)
** Changed in: nova
Status: New = In Progress
** Changed in: nova
Importance: Undecided = Low
--
You received this bug notification because you
** Branch linked: lp:~vishvananda/nova/remove-openwrt
--
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/810051
Title:
Copyright/legal issues in Nova (from Debian upstream)
To manage
** Changed in: nova
Status: Confirmed = Fix Committed
--
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/766352
Title:
novarc in nova.zip does not work perfectly as symlink
--
So turns out the pushd popd was to make novarc work on a mac/bsd. Also
not sure what the -f is for in readlink, but it doesn't work on a mac.
** Changed in: nova
Status: Fix Committed = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
found one for bash zsh and mac. linked branch
** Branch linked: lp:~vishvananda/nova/fix-novarc-mac
--
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/766352
Title:
novarc in nova.zip
53 matches
Mail list logo
