this is parsing of client , nova API should not have this problem
** Project changed: nova => python-novaclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1472957
Tit
quot; AS services_binary, services.topic AS
services_topic, services.report_count AS services_report_count,
services.disabled AS services_disabled, services.disabled_reason AS
services_disabled_reason \nFROM services \nWHERE services.deleted = ? AND
services.id = ? FETCH FIRST 1 ROWS ONLY'
seems nova don't have function 'interface_list' ?
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1471041
Title:
interface_list() function doe
Public bug reported:
security_group_default_rules.py in plugs/v3 are lack of schema check
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
--
You received this
nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova
I didn't see any thing related to nova, assume heat
** Project changed: nova => heat
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1452983
Title:
can't add/del paramet
Public bug reported:
in Nova API layer, 403 is returned (HTTPForbidden) if Quota is exceeded, this
is not correct
we should return 400 (HTTPBadRequest) instead
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee
** Also affects: python-cinderclient
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1450658
Title:
VolumeBackendAPIException
Public bug reported:
If there is only one host available, calculate the weight
make no sense because whatever the weight it is, nova will
use the host. so need to identify this case.
** Affects: nova
Importance: Low
Assignee: jichenjc (jichenjc)
Status: In Progress
** Changed
t('vnc_keymap',
default='en-us',
help='Keymap for VNC'),
]
CONF = cfg.CONF
CONF.register_opts(vnc_opts)
while the others belong to rdp or serial group, we can make vnc in vnc
group like others
** Affects: nova
Importance: Unde
"/usr/local/lib/python2.7/dist-packages/libvirt.py", line 3153, in baselineCPU
2015-04-20 14:06:57.351 TRACE nova.openstack.common.threadgroup if ret is
None: raise libvirtError ('virConnectBaselineCPU() failed', conn=self)
2015-04-20 14:06:57.351 TRACE nova.openstack.common.threadgro
Public bug reported:
we can get exception.OverQuota from cinder layer
but we didn't handle it in API layer when we create volume
this may lead to a 500 error
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Ass
Public bug reported:
in v2.1 API, when create a volume through os-volumes
if the snapshot ID is invalid, we should report 404 , but now
exception.SnapshotNotFound is not correctly handled
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
fects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compu
>From following logs,looks to me nova is right ,it raise the exception ,maybe
>novaclient should take care about that
(whether report the exception), that's another story
Also, I noticed that even if the one failed, previous instances are all
updated which makes me think Eric is right ,we need
Public bug reported:
Juno version ,got following error indication , should report better
error message
[root@ip9-114-194-88 ~]# nova boot --image 67e9f04f-b5f1-4b9e-9b48-c28a310ad44b
--nic net-id=2e798297-c8e8-48e4-b361-1ecdab69c851 --flavor 99 --ephemeral 4
--ephemeral 3 ji6
ERROR (ValueError)
e162-45ce-98b0-54d9563bbb1c] VolumeNotCreated: Volume
abc781af-0960-4a65-87d2-a5cb15ce7273 did not finish being created even
after we waited 250 seconds or 61 attempts.
from this line, it indicated that create volume failed , nova did all he can do.
you need to check whether something wrong in ci
from all the logs showed, looks like a keystone bug instead of nova
** Project changed: nova => keystone
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1431588
Title:
On Kilo 2015.1.0b
| |
+--+--+++-+--+
actually, we need to return the no valid host exception because host is down
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee
from your description, I do'nt think it's a valid nova bug, maybe
something should be changed in horizon or more analysis needed
** Project changed: nova => horizon
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboa
Public bug reported:
nova had check for LOG.warn becaues of p3
compatible issue , but it didn't include the check for
the LOG.warn(msg, xxx) format
so the following violation can't be found
msg = _('abc')
LOG.warn(msg, xxx)
** Affects: nova
Importance: Undecided
it's < 0, then the periodic task is
disabled
it's = 0, then the periodic task spacing is default (60) so no need to check it
in nova manager
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee: (unass
#x27; is fine because
we don't need to wait for the return data
to make it cast also can solve the bug 1331537 though we don't know the
real cause of the problem
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: In Progress
** Changed
cided
Assignee: jichenjc (jichenjc)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.
|
++--+--+--+-+---++-+
the None at disabled_reason of id 7 is inconsistent to other columns
it should be - to avoid confusion
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Public bug reported:
we should not enable service to be deleted when it's up
see following example, the service itself is still working but we lost the
information of the services
we'd better give some flexibility to operators (e.g unless --force flag, we
can't delete active services)
[root@
| True |
but my flavor don't have a ID with 19 or 15
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
--
You received this bug notification because y
resources
resource.controller = inherits.controller
AttributeError: 'NoneType' object has no attribute 'controller'
DEBUG [nova.api.openstack] Running _register_resources on
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
**
nova => glance
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Confirmed
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
--
You received this bug notification because you are a member of Yahoo!
Engineering T
T04:06:41Z |
+-+--+
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
--
You received this bug notification because you
| jitest3 | PAUSED | - | Paused
| private=10.0.0.200 |
+--+-+++-++
we should not allow as option
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc
get access list for public flavor type.
we should check public/private before access add
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
--
You received this
migrations for the given status.
--cell_name Fetch migrations for the given cell_name.
but we don't support --cell_name as an option in the db query
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Ass
Public bug reported:
A paused instance can be shelved and then unshelved
then the instance is ACTIVE instead of PAUSE state
this also apply to SUSPEND state
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Tags: compute
** Tags added
exc_info=True)
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
due to remove comments, abandon
** Changed in: nova
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1289174
Title:
resize an instance s
Public bug reported:
there is race window between attach volume and spawn with volumes
we should reserve volumes when spawn
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
--
You received this bug notification because you are a member of
because the patch suggested is rejected and reviewers don't think it's a
valid bug
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.lau
Public bug reported:
we should catch InstanceUserDataTooLarge when we create an instance
because compute/api.py might report this exception
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Tags: api
** Tags added: api
** Changed in: nova
** Project changed: nova => python-novaclient
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1323996
Tit
** No longer affects: python-neutronclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1210598
Title:
Over quota errors originating from Neutron result in 500 error i
** Also affects: python-neutronclient
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1210598
Title:
Over quota errors origina
urrent usage
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Tags: api
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
** Tags added: api
--
You received this bug notification because you are a member of Yahoo!
Engi
this problem was already fixed about weeks ago, I didn't update my test
system to latest, sorry
** Changed in: nova
Status: New => Incomplete
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
12, it will fail now, but we can compare the real
eph disk size and see whether we an resize it or not
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
--
You received t
s, so
we will keep seeing this warning:
2014-05-28 16:12:35.031 4259 WARNING nova.compute.resource_tracker [-]
[instance: 8138f726-de38-498c-b3fa-e3d2c416ebb9] Instance not resizing,
skipping migration.
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Stat
29:12.508 4259 TRACE oslo.messaging.rpc.dispatcher ResizeError:
Resize error: Unable to resize disk down.
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
--
You received this b
Public bug reported:
There are some LOG.exception in api layer, which is not necessary , we
should downgrade them
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Tags: api
** Changed in: nova
Assignee: (unassigned) => jiche
Not a defect after carefully review the comments and routine ,mark it
invalid..
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net
Allow retrying network allocations separately
Introduce a new config option, 'network_allocate_retries', that allows
one to retry network allocations. The default is 0 for no retries to
match the current behavior.
The network allocations currently get retried by a full retry of a
my compute node logs which make me confusing
we need to avoid this kind of audit logs and give more accurate info
discussions here:
http://lists.openstack.org/pipermail/openstack-dev/2014-May/034312.html
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc
IT nova.compute.resource_tracker [-]
Free disk (GB): 29
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
--
You received this bug notification because you are a member of Yahoo!
Eng
101 - 152 of 152 matches
Mail list logo
