** Changed in: openstack-manuals
Status: In Progress => 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/1530647
Title:
dhcp: Default to using local DNS resolution
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1540335
Ti
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1565105
Title:
while spining vms on large scale some vms get multiple
Public bug reported:
When a user attempts to rename a project via the PATCH
v3/projects/{project_id} API, and the new name is already in-use, rather
than return a nice error explaining that the name is in use, keystone
blows up and returns an HTTP 500:
# curl -k -1 -i -X PATCH
https://localhost:
What version of nova is this? Mitaka? It probably doesn't really matter,
the issue is here as you pointed out:
except Exception as exc:
LOG.error(_LE('Connection between volume %(vol)s and host '
'%(host)s might have succeeded, but attempt '
Public bug reported:
As in Octavia stable/mitaka branch,
http://git.openstack.org/cgit/openstack/octavia/tree/octavia/common/config.py?h=stable/mitaka
the cfgOpt is set to be "bind_host" IPOpt() type.
But in Neutron stable/mitaka,
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/comm
*** This bug is a duplicate of bug 1175464 ***
https://bugs.launchpad.net/bugs/1175464
** Changed in: nova
Assignee: Matt Riedemann (mriedem) => sahid (sahid-ferdjaoui)
** Also affects: nova/mitaka
Importance: Undecided
Status: New
** Also affects: nova/liberty
Importance:
** Changed in: nova
Assignee: Feodor Tersin (ftersin) => sahid (sahid-ferdjaoui)
** Also affects: nova/liberty
Importance: Undecided
Status: New
** Also affects: nova/mitaka
Importance: Undecided
Status: New
** Changed in: nova
Importance: Medium => High
** Changed i
The cinder change needs to be reverted also since it's a non-
discoverable API change w/o a microversion. Nova can't rely on this API
until it's in a proper microversion.
** Also affects: cinder
Importance: Undecided
Status: New
--
You received this bug notification because you are a m
I pushed the tag to gerrit. Please confirm that the release was
successful.
** 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/156498
Public bug reported:
Looks like there are a few warnings when the docs are generating on master.
Until this warnerrors change is merged, https://review.openstack.org/#/c/229951,
we have to manually run 'tox -e docs' to see if patches are introducing new
problems with the doc strings. Once that
Public bug reported:
We are requesting that the networking-hyperv release 2.0.0 be created
from the current head of the master branch. The stable/mitaka branch
needs to be created as well.
commit id: f0f7c187e57f2f2c476d7ffd5beec794f1aca43f
Branch: stable/mitaka
release version: 2.0.0
** Affec
2.5) Selected Image for Boot Source (above) :)
** Changed in: horizon
Status: In Progress => Fix Released
** Changed in: horizon
Assignee: Cindy Lu (clu-m) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
Public bug reported:
https://review.openstack.org/288050
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the
documentation bugs against it. If this needs changing, the docimpact-group
option ne
It appeared the fix was not complete. I'm reopening the bug, will upload
a fix shortly
** Changed in: neutron
Status: Fix Released => Triaged
** Tags removed: in-stable-liberty
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
Reviewed: https://review.openstack.org/294512
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=c5311439d6526006dd1354e09f2bfb86505d550d
Submitter: Jenkins
Branch:master
commit c5311439d6526006dd1354e09f2bfb86505d550d
Author: Radoslav Gerganov
Date: Fri Mar 18 12:56:04 2
Public bug reported:
oslo.config supports a "deprecation_reason" parameter, we should give
one to "domain_id_immutable" , for context on why look at this commit:
https://github.com/openstack/keystone/commit/27c4cbc9f7565ee978525de0053a1ae5f15de633
** Affects: keystone
Importance: Low
@Abhilash:
root cause
--
The nova conductor log file "n-cond.log" you attached shows the error:
Invalid input received:
Fixed IP 1.0.0.255 is not a valid ip address for network
97adf977-8b62-4996-a800-bbbdaf9c0fd9.
This gets raised in Liberty code at [1]. It's also there in
Public bug reported:
As firewall uses actions=output: which doesn't handle vlan tags,
accepted ingress traffic gets packets that are still tagged. Normal
actions take care of vlan tags according tags on ports, so those are
fine. We should use strip_vlan for all actions using
output:
** Affects: n
Public bug reported:
First nova rebuild request passes fine, but further requests fail with
the following message:
Instance b460e640-e601-4e68-b0e8-231e15201412 is already associated with
a node, it cannot be associated with this other node 10c0b922-cb39-412e-
849a-27e66042d4c0 (HTTP 409)", "code
Public bug reported:
The change introduced in 1189 ( https://bazaar.launchpad.net/~cloud-
init-dev/cloud-init/trunk/revision/1189#cloudinit/distros/debian.py )
breaks ifup at least on trusty because ifup only reads files in
/etc/network/interfaces.d that match ^[a-zA-Z0-9_-]+$. Changing the
filen
Public bug reported:
Steps:
- deploy cluster with one compute node
- login as admin to horizon
- boot an instance with name VM
- exec in CLI `$ nova migrate VM`
- refresh instances page
Actual result:
- instance has status "error"
Expected result:
- raise error message, that isn't possible migra
Public bug reported:
This bug happen in my environment with these steps on liberty release:
1. Create a instance by using centos 7 image. and boot it. every thing work
well so far
2. Create 10G volume and attach it to this instance onto /dev/vda
3. Format it and mount it, try to create
Public bug reported:
When execute "nova baremetal-node-delete" command, above error message is shown.
ERROR (BadRequest): Command Not supported. Please use Ironic command
port-create to perform this action. (HTTP 400)
port-create is incorrect, node-delete is correct.
** Affects: nova
Impor
Public bug reported:
When searching for Instances on Horizon, the query returns zero results
if there is a space at the beginning or the end.
Steps to reproduce:
1. Create instance named "test"
2. Go to Project->Compute->Instances or Admin->System Panel->Instances
3. Search for "test"
4. Search f
Public bug reported:
When execute "nova baremetal-node-create" command, above error message is shown.
ERROR (BadRequest): Command Not supported. Please use Ironic command
port-create to perform this action. (HTTP 400)
port-create is incorrect, node-create is correct.
** Affects: nova
Impo
Hi,
nova-network was designed for relatively simple networking use cases, so
it struggles to support things like this. However, for what you're
trying to achieve the neutron project should work very well! Check out
the networking guide at : http://docs.openstack.org/networking-guide/
and see about
Public bug reported:
Running horizon 9.0.0.0rc2 with the corresponding keystone V3 policy
version throws a TypeError while evaluating the policy rule
"cloud_admin": "role:admin and (token.is_admin_project:True or
domain_id:default)": 'Token' object has no attribute '__getitem__'
It seems that key
** Also affects: nova
Importance: Undecided
Status: New
** Summary changed:
- SMBFS volume driver cannot handle missing mount options
+ Hyper-V SMBFS volume driver cannot handle missing mount options
--
You received this bug notification because you are a member of Yahoo!
Engineering
Public bug reported:
Steps:
- Deploy cluster with ceph as storage backends.
- Login as admin to horizon
- Go to Project -> Containers
-> There is alert "Error: Unable to get the Swift service info."
- Create container and enter into it
- Upload a file
-> File is uploaded and obje
Public bug reported:
In the implementation of DSCP QoS rule, the QosOVSAgentDriver uses the
wrong method to modify br-int flows. It uses br_int.mod_flows() whilst
it should use br_int.mod_flow():
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/extens
Reviewed: https://review.openstack.org/277296
Committed:
https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=c5b3afc2f9f2588da3bf10fcfb93f404ccb9b086
Submitter: Jenkins
Branch:master
commit c5b3afc2f9f2588da3bf10fcfb93f404ccb9b086
Author: Itxaka
Date: Mon Feb 8 08:06:26
Reviewed: https://review.openstack.org/281498
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=87d337074066692d33197c4caa74333935bca537
Submitter: Jenkins
Branch:master
commit 87d337074066692d33197c4caa74333935bca537
Author: Ritesh Anand
Date: Wed Feb 17 07:48:07 201
** Project changed: neutron => networking-sfc
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1564455
Title:
Neutron did not start - While Stacking
Status in networking-sfc:
Incomplete
Public bug reported:
Check for snat_namespace existence in the node before any operation
in the namespace.
Today we check the self.snatnamespace which may or may not reflect
the exact state of the system.
If the snat_namespace is accidentally deleted and if we try to
remove t
Public bug reported:
* Issue Description
When creating a fip and l3 agent is restarted, if the veth devices(rtr and fip)
are created but the ip addresses are not configured. it will cause the IP
address cannot be configure no more, even if the l3 agent restart.
* Pre-conditions
Create a fip and
There is no action required in the neutron side.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1564125
Title:
Allow to use seve
Add descriptions about multiple SR-IOV nics to the corresponding page of
the networking guide.
** Also affects: openstack-manuals
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
38 matches
Mail list logo
