Reviewed: https://review.openstack.org/618980
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=01fe73f99c456adb6d7a231e5ef6e5497d926b5f
Submitter: Zuul
Branch:master
commit 01fe73f99c456adb6d7a231e5ef6e5497d926b5f
Author: Lucian Petrut
Date: Tue Nov 20 11:51:27 2018
I think bootstrap is handling this case properly. The keystone-manage
bootstrap command needs to have a password to bootstrap with the
administrator. It doesn't look like it was provided.
I suggest rerunning the command with an additional argument
(--bootstrap-password) or sourcing it from your
Reviewed: https://review.openstack.org/619687
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=8aea412a4faed1b622a172fe60cd7df2675fa387
Submitter: Zuul
Branch:master
commit 8aea412a4faed1b622a172fe60cd7df2675fa387
Author: manchandavishal
Date: Fri Nov 23 09:33:42
** Also affects: networking-bigswitch
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/1805235
Title:
[neutron-tempest-plugin] delete_router
I'm marking this fix-released for bionic and xenial.
The fix is available in bionic-updates and xenial-updates
and was SRU'd under bug 1795953.
If you are experiencing this problem still, re-open the bug.
Thank you.
** Changed in: cloud-init (Ubuntu Xenial)
Status: Confirmed => Fix
Public bug reported:
- [x] This doc is inaccurate in this way:
This bug is specifically about the weights section here:
https://docs.openstack.org/nova/rocky/admin/configuration/schedulers.html#weights
There are a few issues:
1. Mentioning cells in here is not qualified as only for cells v1,
Public bug reported:
A recent change [1] to neutron-tempest-plugin is causing a tempest
failure when running against networking-bigswitch neutron plugin with L3
functionality provided by networking-bigswitch.
The failure stack trace looks as follows:
17:12:37 tearDownClass
Hi,
I recreated the issue using the Ubuntu upstream kernel builds at
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
After launching a 18.04 instance, and then installing those kernels
and rebooting (generic_4.20.0-999.201811252100) I saw the issue.
I noticed that cloud-init's
Public bug reported:
Permissions errors are seen when running collect-logs as non-root user
cloud-init 18.4.24
$ cloud-init collect-logs
Traceback (most recent call last):
File "/usr/bin/cloud-init", line 11, in
load_entry_point('cloud-init==18.4', 'console_scripts', 'cloud-init')()
Released in cloud-init v18.4-22-g6062595b-0ubuntu1. Currently avaialable
in Ubuntu Disco series.
** Changed in: cloud-init
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
** Changed in: cloud-init
Status: Fix Committed => 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/1797480
Title:
Azure: Support ephemeral disk handling on Gen2
Hi.
I added a 'linux' package task here. It seems that in bug 1551419 patches were
added
to the ubuntu kernel to do the right thing. Possibly those patches were
inadvertantly
dropped? Either way, it seems like the [Ubuntu] kernel should promise this
consistently
so that multiple consumers do
Public bug reported:
I'm trying to disable nova services, but the requests fail.
python-nova-17.0.7-1.el7.noarch
openstack-nova-api-17.0.7-1.el7.noarch
openstack-nova-novncproxy-17.0.7-1.el7.noarch
openstack-nova-placement-api-17.0.7-1.el7.noarch
python2-novaclient-10.1.0-1.el7.noarch
*** This bug is a duplicate of bug 1718455 ***
https://bugs.launchpad.net/bugs/1718455
This has been fixed awhile ago, I need to find the duplicate bug.
** This bug has been marked a duplicate of bug 1718455
[pike] Nova host disable and Live Migrate all instances fail.
--
You received
Public bug reported:
As domain admin, i would like to list role assignments on projects of my
domain. The default v3 policies are:
"admin_on_domain_filter": "rule:admin_required and
domain_id:%(scope.domain.id)s",
"admin_on_project_filter": "rule:admin_required and
Public bug reported:
I create a network with two subnets(The dhcp is enabled by default.).
Then I disable dhcp on one of the two subnets. I found the dhcp port
still have two fixed ips. Then, I restart the neutron-dhcp-agent, the
redundant fixed ip is cleaned up.
** Affects: neutron
Public bug reported:
Concurrently creating (many) security group rules in a security group,
either posting concurrently directly to the api, or by using heat fails
(on queens) with:
Retry wrapper got retriable exception: UPDATE statement on table
'standardattributes' expected to update 1
Public bug reported:
"``dns_domain`` functionality for ports" should be "``dns_domain for
ports`` functionality" i guess
** Affects: neutron
Importance: Undecided
Assignee: YAMAMOTO Takashi (yamamoto)
Status: In Progress
** Tags: dns doc
** Tags added: doc
** Tags added:
commit de5df89ed5a7687921915cc14e04b1c7438b4fb2 fixed this, but
unfortunately the patch author forgot to add a bug link in the commit
message.
** Changed in: horizon
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering
After upgrading this site to Queens I cannot reproduce the issue anymore.
Now a migration returns just one resource and there is no timeout when doing a
migration:
2018-11-26 10:23:54.312 326318 DEBUG neutron.agent.resource_cache
[req-8e2ea784-51f5-49de-ad31-cdcf978d72e3 - - - - -] 1 resources
Public bug reported:
One of our clients recently started to use Windows 10 (update 1803)
guest instances and reported very "slow responsiveness" of those
instances. E.g. the boot up times are in a range of minutes whereas
older Windows instances boot up in seconds.
After some tests with plain
21 matches
Mail list logo
