Public bug reported:
This is a timing issue and can occur if instance delete call reaches to
_delete_instance method in nova/compute/manager.py module and nova-
compute crashes after setting instance vm_state to 'DELETED' but before
destroying the instance in db.
Now on restarting nova-compute
Public bug reported:
the table ml2_dvr_port_bindings is only add one item compared with the table
ml2_port_bindings.
why not combine with ml2_port_bindings.
the table only need 2 item : port_id and status and the other information can
be stored or get from the ml2_port_bindings.
** Affects:
** Changed in: horizon
Status: New => Confirmed
** Changed in: python-novaclient
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
Public bug reported:
The commit ae7dab9975bcbe3bb40cb9723b0deaed985b904c changes
'HostState.metrics' from a simple dictionary to
'objects.MonitorMetricList'. But it doesn't change the related behavior
in 'weights.MetricsWeigher'. MetricWeigher still treat
'host_state.metrics' as a dictionary of
** Also affects: networking-onos
Importance: Undecided
Status: New
** Also affects: networking-odl
Importance: Undecided
Status: New
** Changed in: networking-onos
Assignee: (unassigned) => vikram.choudhary (vikschw)
** Changed in: networking-odl
Assignee:
Case 1: Without restarting l3-agent and ovs-agent on compute node, they will
keep running as legacy mode.
Case 2: I don't think manually assign a DVR router to l3-agent should be valid,
DVR router will be scheduled based on port-bindings. So manually disassociate a
DVR router from l3-agent
Public bug reported:
It seems that to reproduce the problem we need a multi node deployment
with at least two nova-compute service.
To reproduce it do the following:
1) create a neutron port
2) boot two instances in parallel with that port
Sometimes both instances become ACTIVE in nova which is
development server doesn't work with different webroot other than /
That's unfortunate, but not a real issue. You're not sharing the dev
server with keystone.
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
** Also affects: ubuntu
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1482077
Title:
admin unable to download
It seems you are talking about the neutronclient options.
In the FWaaS API, there is no definition in "any".
In neutronclient code (fw/firewallrule.py), there is the following code:
protocol = parsed_args.protocol
if protocol == 'any':
protocol = None
Thus, this bug
Public bug reported:
when running the Django development server for openstack_dashboard in
the virttual environment (running command ./run_tests.sh --runserver
0.0.0.0:8877), we can't login to dashboard with the that port.
./run_tests.sh --runserver 0.0.0.0:8877
Checking environment.
Environment
Public bug reported:
Currently, neutron has separate big tent projects like networking-odl
[1], networking-onos [2] and so on for making the communication between
OpenStack and open controller/s (like ODL, ONOS and etc) possible. I
believe most of such controllers needs similar interfaces from
Public bug reported:
lbaas vip port IP cannot be updated by lbaas api like "neutron lb-vip-
update VIP --address NEW_IP", but it can be updated by "neutron port-
update".
This is conflict, if lbaas doesn't support update vip port IP yet,
another API shouldn't make it possible to update.
**
Public bug reported:
Reproduce the bug:
1, Create a router and it's name is router1;
2, Edit router and set it's name is blank, and it will display it's ID as name;
3,Click the name and go forward to the router's detail page and select the
interfaces tab;
4, Click "Add Interface" button and open
Public bug reported:
When instance's disk in rbd backend, compute node reports the whole
ceph cluster status, that makes sense. We get the local_gb usage in
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/storage/rbd_utils.py#L313
def get_pool_info(self):
with
** Also affects: cinder
Importance: Undecided
Status: New
** Description changed:
All projects should use only `novaclient.client` as entry point. It designed
with some version checks and backward compatibility.
Direct import of versioned client object(i.e. novaclient.v2.client)
Public bug reported:
The situation I have encounter in Liberty-3 devstack.
When creating HA router on network nodes with dead L2 agent (ovs), the
HA port cannot be properly configured on that node after starting the L2
agent - the L2 agent is treating the HA port as dead and is blocking all
the
Public bug reported:
We’ve deployed OpenStack with Ceph as a storage (rbd). The instances are
being boot using cinder volumes through Ceph too.
Sometimes the following ERROR appears at the nova-compute.log: [Errno
24] Too many open files
If we get the list of open files from any nova-compute
*** This bug is a duplicate of bug 1489372 ***
https://bugs.launchpad.net/bugs/1489372
@Arthur, you are correct. I've used 'git bisect' and found out that [1]
already fixes this issue. I will close this bug as a duplicate.
[1]: https://review.openstack.org/#/c/218118/
** Changed in: neutron
Public bug reported:
Version: glance liberty master (latest 04.09.15)
Steps to reproduce:
1. Create an artifact(type=MyArtifact) with blob property (image_file)
2. Update blob property image_file with some value:
curl -H "X-Auth-Token: 6b2e3dccf35642b89099465e7492a42a" -H
Public bug reported:
When, on a setup that has a DVR router, an OVS agent restarts, it fails
to re-create some of the flows for br-tun. For example:
$ # flows before agent restart
$ sudo ovs-ofctl dump-flows br-tun
NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=77.325s, table=0, n_packets=0,
Thanks Gary. I've set our security advisory task to won't fix status,
since you've confirmed this is a class Y report according to the VMT
taxonomy: https://security.openstack.org/vmt-process.html#incident-
report-taxonomy
** Changed in: ossa
Status: Incomplete => Won't Fix
--
You
Public bug reported:
1. After run the script of
https://git.openstack.org/cgit/openstack-infra/system-config/plain/install_puppet.sh;
execute the command of "restart ssh" but it gets hang.
2. And if we use "status ssh", we can see there is pid in the output.
3. I noticed that there are
Public bug reported:
## common/constants.py
DEVICE_OWNER_LOADBALANCER = "neutron:LOADBALANCER"
DEVICE_OWNER_LOADBALANCERV2 = "neutron:LOADBALANCERV2"
## common/utils.py
def is_dvr_serviced(device_owner):
"""Check if the port need to be serviced by DVR
Helper function to check the
Public bug reported:
The MANIFEST.in file at the Horizon root is outdated, still referring to
.less stylesheets.
** Affects: horizon
Importance: Undecided
Assignee: Rob Cresswell (robcresswell)
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
Steps to reproduce:
1. Create an artifact (type=MyArtifact)
2. Update artifact blob list with some value:
curl -H "X-Auth-Token: 1d5532fa812548f6a41bfd422f0d36a9" -H
"Content-Type:application/octet-stream" -X POST -d '{"data":
"someupdates_datawithtretrtrt"}'
Fix proposed to branch: master
Review: https://review.openstack.org/221848
** Changed in: nova
Status: Won't Fix => In Progress
** Changed in: nova
Assignee: Michael Davies (mrda) => Lucas Alvares Gomes (lucasagomes)
--
You received this bug notification because you are a member of
It sounds like the user experience issue here was fixed for both
stable/kilo and master, then. I'm sure further refactoring could be
done, but that doesn't need to be tracked in a bug.
** Changed in: keystone
Status: Triaged => Invalid
--
You received this bug notification because you
** Changed in: neutron
Status: Incomplete => 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/1411883
Title:
DVR qrouters are not created when VMs are added after the
** Also affects: mistral
Importance: Undecided
Status: New
** Changed in: mistral
Assignee: (unassigned) => Zhenguo Niu (niu-zglinux)
** Description changed:
All projects should use only `novaclient.client` as entry point. It designed
with some version checks and backward
Dropping devstack from this. As a tactical fix for liberty we're going
to just make sure the os-brick.filters contents are in volume.filters in
cinder and compute.filters in nova. This is not ideal long-term because
of the tight-coupling it creates and lockstep upgrades required for nova
and
Public bug reported:
A long time ago, novaclient doesn't provide a public interface for
discovery extensions. It was required to provide a hack due to unability
to import extension directly(there was a novaclient module refactoring).
This hack can produce another issues which can prevent to
** Changed in: ironic
Status: Fix Committed => Fix Released
** Changed in: ironic
Milestone: None => 4.1.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1489059
Title:
"db
Public bug reported:
Attempting to launch an instance and create a volume fails for both
possible values of delete on termination with an error similar to:
Error: Invalid input for field/attribute delete_on_termination. Value:
0. 0 is not of type 'boolean', 'string' (HTTP 400) (Request-ID: req-
Public bug reported:
Steps to reproduce:
on a system containing a default cloud-init configuration
1. manually create a frequency 'once' lock using:
/usr/bin/cloud-init-per once testing-cloud-init-once echo hello
2. reboot.
3. login again and repeat the above cloud-init-per command.
Public bug reported:
I am running Kilo 2015.1.0, with neutron-OVS, and iptables firewall.
I run into situations, where, the iptables SG chains/rules are
inconsistent with ovs-ports, and system interfaces - see below for an
example. In these situations, when I restart neutron-ovs-agent, I expect
*** This bug is a duplicate of bug 1353962 ***
https://bugs.launchpad.net/bugs/1353962
Public bug reported:
Occasionally an overquota exception is raised by allocate_fixed_ip when
there is quite a large amount of free fixed_ip left.
For example in this tempest postgres job run:
Calling this fix released.
** Changed in: cloud-init
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1411582
Title:
[SRU] Azure data source
Public bug reported:
The InstanceExternalEvent object use enum type for name field
https://github.com/openstack/nova/blob/279c2b0a015b67c5195ab028eeab15b00a94e5ee/nova/objects/external_event.py#L41
But there isn't any limit in the API schema
** Also affects: nova/juno
Importance: Undecided
Status: New
** Changed in: nova/juno
Status: New => Incomplete
** Changed in: nova/juno
Status: Incomplete => Confirmed
** Tags removed: kilo-backport-potential
** Tags removed: network security-groups unified-objects
**
Public bug reported:
http://logs.openstack.org/02/221502/5/gate/gate-tempest-dsvm-neutron-
dvr/621ea48/logs/testr_results.html.gz
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Public bug reported:
A number of Tempest tests fail in the gate.
An example:
http://logs.openstack.org/02/221502/5/gate/gate-tempest-dsvm-neutron-
dvr/621ea48/logs/testr_results.html.gz
The logstash query:
message:"Bad router request: Router already has a port on subnet" AND
Public bug reported:
http://logs.openstack.org/02/221502/5/gate/gate-tempest-dsvm-neutron-
dvr/621ea48/logs/testr_results.html.gz
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Public bug reported:
Currently, neutron has devstack script in tree but the rule is unclear.
** Affects: neutron
Importance: Undecided
Assignee: Hirofumi Ichihara (ichihara-hirofumi)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hirofumi Ichihara
(9:32:31 PM) mriedem: andrewbogott: btw, are you on trunk stable/kilo or like
2015.1?
(9:32:43 PM) andrewbogott: I’m using the cloud archive
(9:32:58 PM) andrewbogott: nova-compute
1:2015.1.1-0ubuntu1~cloud2
(9:34:00 PM) mriedem: nova-network?
(9:34:14 PM) andrewbogott:
Public bug reported:
After around 100 routers being scheduled to a neutron node, subsequent
schedulings fail with the following extracted signature:
38343:2015-09-09 06:53:15.305 mDEBUG neutron.agent.l3.agent
[req-d7ce10e2-b689-4c5b-b4c7-30aa4f1fdbbb admin
cdd316b857a947488ca9120aef5f6891m]
Public bug reported:
The EventReporter attempts to serialize exception messages and raises
another error in doing so if the message contains non-ascii characters,
masking the original exception.
File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 89, in
wrapped
payload)
Public bug reported:
The debug log statement in nova-conductor's object_backport_versions()
method doesn't format and looks like this:
2015-09-09 11:26:57.126 DEBUG nova.conductor.manager [req-9ff7962c-
c8b8-4579-8943-cbf2ef0be373 demo demo] Backporting %(obj)s to %(ver)s
with versions
This is how CIDRs work, there is no way to know what they meant to do.
How would we know they didn't mean to put in 192.168.0.0/25?
** Changed in: neutron
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
The bug 1488443 showed us that Unicode was broken in Horizon and we
didn't even know this. Using unicode characters in every name generator
in integration tests will help to catch some unicode issues before they
hit us hard.
** Affects: horizon
Importance: High
Public bug reported:
Minor version update broke database checking and sync. A custom field in
dlango's user model clashes? It appears there was a minor change somewhere in
the dashboard app from version openstack-dashboard-2015.1.0-7.el7.noarch
to openstack-dashboard-2015.1.1-1.el7.noarch.
Public bug reported:
A security rule can be added that ends with a /0 that makes the rule act
as if it is a 0.0.0.0/0 type of rule.
Example:
(neutron) security-group-rule-list
** Changed in: nova
Status: Opinion => Confirmed
--
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/1396965
Title:
Add capability to detach root device volume of an
** Also affects: nova (Ubuntu Vivid)
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/1457517
Title:
Unable to boot from
Public bug reported:
We have the NullHandler and StandardLogging fixtures here to detect
formatting errors in the nova logs:
http://git.openstack.org/cgit/openstack/nova/tree/nova/tests/fixtures.py#n61
We've seen a few bugs recently where we weren't substituting variables
in the log messages
Public bug reported:
The fix in bug 1492422 set the wrong class so widgets using hz-magic-
search-bar aren't getting the right css.
** Affects: horizon
Importance: Undecided
Assignee: Kevin Fox (kevpn)
Status: In Progress
--
You received this bug notification because you are
Public bug reported:
Summary:
With LBaaS V2, create a loadbalancer and two member instances. Assign
floating IPs to the instances, and to the loadbalancers. The instances
are accessible via their FIPS, but the loadbalancer is not. The
loadbalancer does work via the its fixed IP.
Reproduced
Public bug reported:
The TestTrackedResource class is designed to inject random failures into
the gate. It generates random numbers within the range of 0..1, and
will fail if it generates duplicate random numbers during its run.
class TestTrackedResource(testlib_api.SqlTestCaseLight):
58 matches
Mail list logo
