Public bug reported:
Latest Kilo code.
In inspect_capabilities() of nova/virt/disk/vfs/guestfs.py, guestfs api,
which is C-extension, will hang nova-compute process when it is invoked.
This problem will result in message queue time out error and instance
booting failure.
And example of this
Public bug reported:
According to RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1167496
We need to add support of port-security-enabled=False/True when creating and
updating network.
version :
]# rpm -qa |grep horizon
python-django-horizon-2015.1.0-2.el7.noarch
this flag relevant to port
Public bug reported:
According to RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1167496
Port that already created from network with --port_security_enabled=True will
not updated to False when we update network to --port_security_enabled=False.
Version:
# rpm -qa |grep neutron
** Changed in: horizon
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1364133
Title:
[Heat] Neutron LBaaS vip invisible in
Public bug reported:
1: Exact Version (Latest apt-get dist-upgrade with Kilo repositories for ubuntu
14.04.02)
ii nova-api1:2015.1~rc1-0ubuntu1~cloud0
all OpenStack Compute - API frontend
ii nova-cert
Public bug reported:
When printing help of neutron net-create / neutron net-update / neutron
port-create / neutron port-update
there is no explanation of new flag : --port_security_enabled.
version:
# rpm -qa |grep neutron
python-neutronclient-2.3.11-1.el7.noarch
Public bug reported:
The below Brocade Firewall vendor code related files refers to OpenStack
Foundation instead of Brocade in copyright section and should be fixed
https://github.com/openstack/neutron-fwaas/blob/master/neutron_fwaas/services/firewall/agents/vyatta/vyatta_utils.py
Public bug reported:
Now with neutron ml2 plugin, if we want to update port 'binding:host_id'
be None, we must set 'binding:host_id' be empty
string(binding:host_id=''), there is a problem when nova delete a VMs:
https://bugs.launchpad.net/nova/+bug/1441419
** Affects: neutron
Importance:
Public bug reported:
After being logged out due to inactivity, the next login attempt fails
with Something went wrong error. This happens with any user.
First successful login:
2015-05-11 01:56:11,986 2327 INFO openstack_auth.forms Login successful for
user gtirloni.
Second unsuccessful
As Wei Hu explained, please enable libreswan driver
https://github.com/openstack/neutron-vpnaas/blob/master/etc/vpn_agent.ini#L16
Please see this patch
https://review.openstack.org//#/c/174299
** Changed in: neutron
Status: New = Invalid
--
You received this bug notification because you
Public bug reported:
Created monitor is not shown at Associate Monitor selection at the
pool (image attached).
** Affects: horizon
Importance: Undecided
Status: New
** Attachment added: Screenshot from 2015-05-11 14:16:59.png
I completely agree, the current design directly results in the fragility
you described (I pushed for naming domain-specific configuration files
using their immutable, system-defined domain IDs instead, but lost that
argument... I think on the basis of deployer experience? I'll let Henry
Nash
Public bug reported:
The configuration file for an identity provider eg. LDAP is generally named as
keystone.domain_name.conf.
Since Keystone allows a user to update a domain name, any domain name update
makes this file for that domain name irrelevant. This file is not automatically
renamed
Public bug reported:
When performing rescue operation on an instance booted from volume it gives
error Cannot rescue a volume-backed instance, code: 400.
Steps to reproduce
1. Boot a VM from volume
curl -g -i -X POST
https://10.0.0.5:8774/v2/ee61323896a34bea9c9a5623fbb6f239/os-volumes_boot -H
Ready for the punt return? :)
Because ?id=default is not a query parameter documented or supported in
any collection API, the client is not actually making a valid API
request. And because 'id' is also a documented API convention, I'd
suggest that to provide the expected user experience, the
Setting this to invalid because some of us don't think this is a bug.
Ie, that nodes in maintenance should be counted/shown in nova. Their
resources show up as unavailable, so it seems fine.
See comments in https://review.openstack.org/177575.
** Changed in: nova
Status: In Progress =
yeah, Daniel and Nikola, you are right.
Before, I find no numa in a host by the numactl --hardware, so I think that
there may be no numa topo.
I made the following test, and find that the libvirt return a numa even if the
value from the numactl is zero.
thanks.
root@tralon-Vostro-1400:~#
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
Assignee: (unassigned) = Ihar Hrachyshka (ihar-hrachyshka)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
Commit https://review.openstack.org/#/c/162999/ changed where the
Hyper-V VM configuration files are stored. The files are being stored in
the same folder as the instance. Performing a cold resize / migration
will cause a os.rename call on the instance's folder, which fails
Public bug reported:
When a node boots, it starts the OVS and L3 agents. As an example, in
RDO systemd unit files, these services have no dependency. This means
that the L3 agent can stop before the OVS agent. It can start
configuring routers before the OVS agent finished syncing with the
server
Public bug reported:
When running ./run_tests.sh --jscs there are a few errors (trailing
whitespace).
These should be cleaned up.
** Affects: horizon
Importance: Undecided
Assignee: Matt Borland (palecrow)
Status: In Progress
** Changed in: horizon
Assignee:
Public bug reported:
https://jenkins07.openstack.org/job/gate-nova-pip-missing-
reqs/167/console
2015-05-11 15:11:26.399 | Missing requirements:
2015-05-11 15:11:26.399 | nova/test.py:43 dist=testtools module=testtools
2015-05-11 15:11:26.399 | nova/scheduler/filters/trusted_filter.py:50
Public bug reported:
As the title says, in case fullstack_fixtures.EnvironmentFixture fails
to start because 'wait_until_env_is_up' didn't return successfully (for
example, there was a problem with one of the agents), cleanUp isn't
called. This causes all the resources of the fixtures that are
Public bug reported:
http://git.openstack.org/cgit/openstack/nova/tree/nova/virt/xenapi/image/bittorrent.py#n75
There are no entry points in nova's setup.cfg for this:
matches = [ep for ep in
pkg_resources.iter_entry_points('nova.virt.xenapi.vm_utils')
Public bug reported:
We propose create an new dr-agent which speaks BGP on behalf of Neutron
to external routers. It will only announce routes on an external
network and will not yet learn routers from the external system.
These routes will include floating IPs in IPv4 and IPv6 subnets for
** Changed in: python-heatclient
Importance: Undecided = Low
** Changed in: python-heatclient
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
in VPNaas, the command :
$ python -m subunit.run discover -t ./ ./neutron_vpnaas/tests/unit
--list | grep test_ikepolicy_list
doesn't return any result, while there is a test named
test_ikepolicy_list :
https://github.com/openstack/neutron-
Public bug reported:
This feature request proposes to allow using private subnets and public
subnets together on the same physical network. The private network will
be used for router next-hops and other router communication.
This will also allow having an L3 only routed network which spans L2
Public bug reported:
Make address scopes a first class thing in Neutron and make Neutron
routers aware of them.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: rfe
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
http://git.openstack.org/cgit/openstack/nova/tree/nova/volume/cinder.py#n125
if version == '1' and not _V1_ERROR_RAISED:
msg = _LW('Cinder V1 API is deprecated as of the Juno '
'release, and Nova is still configured to use it. '
Public bug reported:
While working on cleaning up the duplicated DB schema and logic
introduced to support DVR's distributed bindings (bug 1367391), I
discovered much much of the ML2 port binding support for DVR was not
covered by existing unit tests. Ideally, tests covering this would be
written
Public bug reported:
This bug was originally written against Sahara, but it appears to be a
Horizon issue instead, so I'm reporting it here.
When trying to upload the spark-example.jar from the Sahara edp-
examples, it fails with the message Danger: There was an error
submitting the form. Please
Public bug reported:
While extending the existing ML2 port binding unit tests to cover DVR
distributed port binding (bug 1453943), I ran into a number of issues
where the PortContext passed to ML2 mechanism drivers does not provide
the information needed for distributed ports or provides it
** Changed in: glance-store
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1422699
Title:
glance api doesn't abort start up on Store
** Changed in: glance-store
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1449639
Title:
RBD: On image creation error, image is not deleted
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
I've mark the OSSA task as won't fix as it's considered a vulnerability
per se.
** Changed in: ossa
Status: Incomplete = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
In released install guide, we can see the step to set token provider to uuid,
as following:
[token]
provider = keystone.token.providers.uuid.Provider
but there are further steps to set pki token, as following:
# keystone-manage pki_setup --keystone-user keystone
This is a powervc-driver issue, and I've already fixed it, thank you.
@mzoeller
** Project changed: nova = powervc-driver
** Changed in: powervc-driver
Assignee: (unassigned) = Jerry Cai (caimin)
** Changed in: powervc-driver
Importance: Undecided = Medium
** Changed in: powervc-driver
** Changed in: horizon
Status: New = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1447678
Title:
session ID does not respect the principle of
python-keystoneclient do raise a ConnectionRefused exception if it could
not connect to the Keystone endpoint.
The horizon component that invokes keystone do actually catch this error and
log a debug msg. I can see this message in the log:
Unable to establish connection to
41 matches
Mail list logo
