Public bug reported:
When other services like Nova talks to the Neutron REST API, it uses an
admin token, in some scenarios like setting the port binding on a port.
In these cases, the admin token is used to ensure only Nova has access
to the binding API, not the end user.
With the introduction
. They all uses same endpoint which
represents value of this config field.
We can move this configuration to defaults section, so that we don't
have to configure same config value in multiple groups.
** Affects: nova
Importance: Undecided
Assignee: Pushkar Umaranikar (pushkar-
Public bug reported:
Placement API error log messages contain too many new line characters.
This could be because of the way that webob formatting error responses.
** Affects: nova
Importance: Undecided
Assignee: Pushkar Umaranikar (pushkar-umaranikar)
Status: New
** Tags
database.
** Affects: nova
Importance: Undecided
Assignee: Pushkar Umaranikar (pushkar-umaranikar)
Status: New
** Tags: db
** Tags added: db
** Changed in: nova
Assignee: (unassigned) => Pushkar Umaranikar (pushkar-umaranikar)
--
You received this bug notification beca
ects: nova
Importance: Undecided
Assignee: Pushkar Umaranikar (pushkar-umaranikar)
Status: New
** Tags: db
** Tags added: db
** Changed in: nova
Assignee: (unassigned) => Pushkar Umaranikar (pushkar-umaranikar)
--
You received this bug notification because you are a me
I think reserved_host_memory is the amount of disk resources reserved so that
they are always available to host.
The disk usage gets reported back to the scheduler from nova-compute running
on the compute nodes. To prevent the disk resources from being considered as
available, this option is
No progress on bug for > 4 weeks. Marking as invalid. Feel free to
reopen.
** Tags added: api
** 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).
As Sean suggested, marking this bug has invalid. Feel free to reopen.
** 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).
This bug lacks the necessary information to effectively reproduce and
fix it, therefore it has been closed. Feel free to reopen the bug by
providing the requested information and set the bug status back to
''New''.
** Changed in: nova
Status: Incomplete => Invalid
--
You received this
This bug lacks the necessary information to effectively reproduce and
fix it, therefore it has been closed. Feel free to reopen the bug by
providing the requested information and set the bug status back to
''New''.
** Changed in: nova
Status: Incomplete => Invalid
** Tags added: api
--
This bug lacks the necessary information to effectively reproduce and
fix it, therefore it has been closed. Feel free to reopen the bug by
providing the requested information and set the bug status back to
''New''.
** Changed in: nova
Status: Incomplete => Invalid
--
You received this
I think there is an rpc cast call from nova api to network api
https://github.com/openstack/nova/blob/master/nova/compute/rpcapi.py#L789.
rpc cast sends a message, doesn't wait for a reply. This is a async
operation. For async API operations, you don't return an error code from
the API if the
Marking it as "invalid" due to existing similar patch
https://review.openstack.org/#/c/96345/
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Can you please reply with why you are using long value? Attributes of nova
flavor-create command including uuid, amount of ram, vcpus etc. should be
positive integers. From the command in the bug description, it seems like you
are passing long value for ram. It expects an integer value. Hence,
I tried resizing of instances with preallocation strategy for nano and micro
flavors and tried same for few instances of tiny flavor.
I could not reproduce bug.
At the same time, I am not able to check with other flavors due to hardware
resources restriction I have. But I don't think we need API
Public bug reported:
Under compute -> instances, we can filter instances by instance name,
image id, flavor id or status. We can add another filter where user can
filter instances based on subnet id or name.
It is useful when user has multiple subnets in project and he wants to
view/list
Public bug reported:
"Manage Attachments" option for attaching Cinder volume to an instance is not
available under instance actions.
User has to switch to Compute -> Volume tab to attach volume to an instance.
Instead we can add option for "Manage Attachments" under instance actions.
Steps to
17 matches
Mail list logo
