Reviewed: https://review.openstack.org/620861
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=96b5ef34563d7c38b0a978ca7689032bc2cf1a04
Submitter: Zuul
Branch:master
commit 96b5ef34563d7c38b0a978ca7689032bc2cf1a04
Author: Takashi NATSUME
Date: Thu Nov 29 09:36:09 2018
Public bug reported:
doc/source/admin/policies.rst
Some problems:
* it mentions the policy "Brain", which was removed circa 2012
* mentions some API calls that don't exist, for example, PUT
/v2/images/
* contains references to the v1 API
* missing some policies (e.g., the locations policies)
Public bug reported:
As currently implemented, cloud-init will read either OVF CDrom *or* the
vmware IMC data.
That means if user-data is provided in the OVF environment file then it
will not be consumed at all by cloud-init.
It seems we need to either:
a.) support reading and merging these
Reviewed: https://review.openstack.org/333829
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=0fce3ca2c1641fbcfb8327a86d7225e2c3972263
Submitter: Zuul
Branch:master
commit 0fce3ca2c1641fbcfb8327a86d7225e2c3972263
Author: Jens Harbott
Date: Mon Oct 29 17:08:33 2018
Public bug reported:
Seen here:
http://logs.openstack.org/22/606122/7/check/nova-tox-
functional/1f3126b/testr_results.html.gz
There are different failures, but the tests were introduced with this
change:
https://review.openstack.org/#/c/591733/
For example, in
Public bug reported:
Seen here:
http://logs.openstack.org/22/606122/7/check/openstack-tox-
py27/d70a4d5/testr_results.html.gz
ft1.7:
nova.tests.unit.virt.libvirt.test_driver.LibvirtSnapshotTests.test_raw_with_rbd_clone_failure_does_cold_snapshot_StringException:
pythonlogging:'': {{{
Reviewed: https://review.openstack.org/621186
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=de69edd0402146d76c65cec6cc7879c71259fbbf
Submitter: Zuul
Branch:master
commit de69edd0402146d76c65cec6cc7879c71259fbbf
Author: Ivan Kolodyazhny
Date: Fri Nov 30 17:33:21
Reviewed: https://review.openstack.org/619286
Committed:
https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=2a7994851cc0767e6a7b192a4101e8b43681ae6a
Submitter: Zuul
Branch:master
commit 2a7994851cc0767e6a7b192a4101e8b43681ae6a
Author: Édouard Thuleau
Date: Wed Nov 21
Public bug reported:
The following commit changed dependencies of nova in the stable/pike
branch and switched it to use stestr. There aren't any other projects
(as far as I can tell) that use stestr in pike. This causes issues, for
example, the Ubuntu cloud archive for pike doesn't have stestr.
It should be relatively easy to write a functional regression test
similar to
https://review.openstack.org/#/c/545123/5/nova/tests/functional/wsgi/test_servers.py
but for this scenario.
** Changed in: nova
Status: New => Triaged
** Changed in: nova
Importance: Undecided => Medium
**
Public bug reported:
If a number of instances are booted from volumes in parallel and some of
the build requests failed in nova-conductor with exception
TooManyInstances [1] because of the setting quota.recheck_quota=True
being set in nova.conf, some instances will end up in the ERROR state.
If
Public bug reported:
After merging commit 0d163613265e036818fe567793a4fc88fe140d4a, we see
some UT breakage in horizon plugins.
bgpvpn-dashboard https://bugs.launchpad.net/bgpvpn/+bug/1805240
neutron-fwaas-dashboard https://review.openstack.org/621155
neutron-vpnaas-dashboard
The same basic issue is in cloud-init
and had a MP proposed at
https://code.launchpad.net/~adobrawy/cloud-init/+git/cloud-init/+merge/354680
** Merge proposal linked:
https://code.launchpad.net/~adobrawy/cloud-init/+git/cloud-init/+merge/354680
** Also affects: cloud-init
Importance:
Public bug reported:
In the context of a live datacenter, sometimes the network teams re-
organize their VLANs by changing VLAN IDs. This is pretty
straightforward in the context of network configuration and physical
servers, but when using ML2 VLAN provider networks, those IDs cannot be
Public bug reported:
The floatingIP can be created in an external network, but after updating the
external network to internal, the floatingIP is still in that internal network.
The updating from internal network to external should be prevented if there are
FloatingIP existing or it is allowed
Public bug reported:
When instructing cloud-init to use `type: dhcp6`, the end-result is that
`/etc/sysconfig/network` contains `IPV6_AUTOCONF=no`. This causes router
advertisements to be ignored and no default route set up.
Public bug reported:
Bug Description
Description:
The type:hostroutes validator is not properly validating subnets that
have non-zero values in the host portion of the network address (e.g.,
1.2.3.1/24 rather than 1.2.3.0/24). This can cause issues for backends/drivers
that
Public bug reported:
Weights are applyed by the scheduler.
This means that if using "max_placement_results" with a number bellow to the
existing resources,
the weight policy will only be applied to the subset of allocation candidates
retrieved by placement.
As consequence we lose the policy to
18 matches
Mail list logo
