Public bug reported:
I started the neutron api with apache with mod_wsgi approach mentioned in the
below document:
https://docs.openstack.org/neutron/latest/admin/config-wsgi.html
I have /etc/httpd/conf.d/wsgi-neutron.conf defined as below:
Listen :9696
Require all granted
:9696>
** Changed in: nova
Status: Confirmed => Opinion
** Changed in: nova
Assignee: Ritesh (rsritesh) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchp
ild_instances |
Environment
===
1. Exact version of OpenStack you are running.
Mitaka Stable
2. Which hypervisor did you use?
Libvirt + KVM
2. Which storage type did you use?
None
3. Which networking type did you use?
Neutron with OpenVSwitch
** Affects: nova
Imp
** Changed in: neutron
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1583508
Title:
Create Router fails for VDX(networking-brocade) when done with
-+--+---+---+
root@Ubu14-42-18:~# neutron router-delete Router_test
Router 13c9c988-f415-4c12-804d-a3e495c6f0b3 still has ports
Neutron server returns request_ids: ['req-083e1c92-06af-4c2d-862a-bcbad7e6ed3a']
** Affects: neu
The bug is not valid.
Ping6 works fine; was missing the security rule for allowing icmp v6.
After adding:
neutron security-group-rule-create --protocol icmp --ethertype IPv6 --direction
egress 4cf607a6-537f-4893-8531-70ba23895b3d
neutron security-group-rule-create --protocol icmp --ethertype
Public bug reported:
Not able to ping v6 address of vm on a different network. With legacy router.
Setup has one controller/network node and two compute nodes.
Steps:
0. Add security rules to allow ping traffic.
neutron security-group-rule-create --protocol icmp --direction ingress
Public bug reported:
Created a neutron network "net3".
By mistake executed nova "net-delete net3".
The case was not gracefully handled.
stack@osctrlr:~/devstack$ nova net-delete net3
ERROR (ClientException): Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach
Public bug reported:
Instance does not get IP from dhcp ipv6 subnet (slaac/slaac) with DVR,
when router interface is added after VM creation.
Instance does get IP when it is booted after interface to the subnet has
already been added to the DVR.
This ordering issue is not observed with
Yes .. it do exists.
** Changed in: horizon
Assignee: Ritesh (rsritesh) => (unassigned)
** Changed in: horizon
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Das
t;xrz".
Please see the attached image below in the comment.
** Affects: horizon
Importance: Undecided
Assignee: Ritesh (rsritesh)
Status: New
** Changed in: horizon
Assignee: (unassigned) => Ritesh (rsritesh)
--
You received this bug notification because you are a me
Public bug reported:
Steps to reproduce:
On devstack:
1. create a network.
2. create a subnet (dhcp enabled); we can see DHCP namespace with one interface
for the subnet.
3. create another subnet (dhcp enabled).
We do not see another interface for this subnet in DHCP namespace.
LOGS:
==
Public bug reported:
This is wishlist bug
Add a cancel button in following page :
http://Horizon IP /admin/defaults/update_defaults
or
Admin - Systems - Defaults - Update Defaults
** Affects: horizon
Importance: Undecided
Assignee: Ritesh (rsritesh)
Status: New
** Changed
.
This is a wishlist bug, to have this.
** Affects: horizon
Importance: Undecided
Assignee: Ritesh (rsritesh)
Status: New
** Changed in: horizon
Assignee: (unassigned) = Ritesh (rsritesh)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
Importance: Undecided
Assignee: Ritesh (rsritesh)
Status: New
** Changed in: horizon
Assignee: (unassigned) = Ritesh (rsritesh)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https
Actually it is not a bug, Currently we have flavor sorting based on
`RAM`.
IMHO, it is correct to have this , if all people agree then we can
change from `RAM` to `Name` based sorting.
** Changed in: horizon
Status: New = Invalid
--
You received this bug notification because you are a
Public bug reported:
Disassociate Floating IP button should be disabled for instances in error
state.
As per the following bug, it has disabled only Associate Floating IP.
https://bugs.launchpad.net/horizon/+bug/1374576
** Affects: horizon
Importance: Undecided
Assignee: Ritesh
Already a blueprint has been registered on this.
https://blueprints.launchpad.net/horizon/+spec/download-images-and-
snapshots
** Changed in: horizon
Status: New = Invalid
** Changed in: horizon
Assignee: Ritesh (rsritesh) = (unassigned)
--
You received this bug notification
Public bug reported:
Through horizon dashboard, I am not able to download the specific glance
images.
This facility has been provided in the glance cli and glance api
reference.
** Affects: horizon
Importance: Undecided
Assignee: Ritesh (rsritesh)
Status: New
** Changed
share the details for it.
I would like to do the code executions for this.
Thank you
RITESH.
** 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
20 matches
Mail list logo
