One of our customer helped test focal_yoga.debdiff on one isolated
compute host in their test env. post installation they have created
about 100 networks, routers and VMs that were spawned on this isolated
compute host. they haven't seen any issues so far with VM creation (all
the VMs were created
** Patch added: "jammy.debdiff"
https://bugs.launchpad.net/neutron/+bug/2017748/+attachment/5778137/+files/jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2017748
Title:
[SRU] OVN:
** No longer affects: cloud-archive/zed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2017748
Title:
[SRU] OVN: ovnmeta namespaces missing during scalability test causing
DHCP issues
To manage
** Patch added: "mantic.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/2054799/+attachment/5772487/+files/mantic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054799
Title:
** Patch added: "noble.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/2054799/+attachment/5772486/+files/noble.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054799
Title:
[SRU]
** Patch added: "focal_yoga.debdiff"
https://bugs.launchpad.net/neutron/+bug/2017748/+attachment/5759481/+files/focal_yoga.debdiff
** Changed in: cloud-archive/yoga
Assignee: (unassigned) => Hua Zhang (zhhuabj)
** Changed in: cloud-archive/zed
Assignee: (unassigned)
After carefully reviewing many patches, I finally backported the
following 3 patches to Yoga.
[PATCH 1/3] 686698284b Update tap ip in metadata agent when metadata port ip
updated
[PATCH 2/3] 6205158831 ovn-metadata: Refactor events
[PATCH 3/3] b992d639b9 Handle creation of Port_Binding with
** Summary changed:
- OVN: ovnmeta namespaces missing during scalability test causing DHCP issues
+ [SRU] OVN: ovnmeta namespaces missing during scalability test causing DHCP
issues
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
On a fresh devstack install with the q-dns service enable from the
neutron devstack plugin, some features still don't work, e.g.:
$ openstack subnet set private-subnet --dns-publish-fixed-ip
BadRequestException: 400: Client Error for url:
Can anyone add 'ubuntu cloud archive xena' project? It seems that I
don't have permission to do it, thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947127
Title:
[SRU] Some DNS extensions not
** Patch added: "focal-xena.debdiff"
https://bugs.launchpad.net/neutron/+bug/1947127/+attachment/5586824/+files/focal-xena.debdiff
** Summary changed:
- Some DNS extensions not working with OVN
+ [SRU] Some DNS extensions not working with OVN
** Changed in: cloud-archive
Status:
** Description changed:
+ [Impact]
+
On a fresh devstack install with the q-dns service enable from the
neutron devstack plugin, some features still don't work, e.g.:
$ openstack subnet set private-subnet --dns-publish-fixed-ip
BadRequestException: 400: Client Error for url:
Hi, can we should change bug status from Fix Released to Confirmed since
the fix was reverted, the problem behind it (lp bug 1916024) still
exist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927868
Hey @james-page, the customer confirmed that using temporary PPA [0]
mentioned in [1] had fixed lp:1907686 [2], can you continue to merge PPA
into Focal? thanks.
[0] https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3690
[1]
Sucessfully verify python-eventlet in xenial-proposed.
echo 'deb http://archive.ubuntu.com/ubuntu/ xenial-proposed restricted main
multiverse universe' |sudo tee -a /etc/apt/sources.list
sudo apt update
sudo apt-get install python-eventlet/xenial-proposed
sudo systemctl restart nova-novncproxy
I hit this problem in ubuntu 20.04 as well, but I fixed it by switching
lightdm to gdm3
sudo apt install gdm3
sudo dpkg-reconfigure gdm3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302136
Title:
Hey @Robie, TLS 1.2 has already been supported in Bionic, Focal, Groovy
because as Mathew said 'set-defaults-to-be-tlsv1-not-sslv23.patch was
dropped by python-eventlet 0.19.0-2 in Ubuntu Yakkety.'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi Drew, yeah, you're right, it works for both novnc and spice. because
both novnc and spice depends on websockify then websockify depends on
python-eventlet's ssl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+
python-eventlet=0.18.4-1ubuntu1 (xenial) is applying the d/p/set-
defaults-to-be-tlsv1-not-sslv23.patch to set defaults to be tlsv1 not
sslv23
- This will prevent xenial users from using tlsv1_1 and tlsv1_2, so I
- think we should set defaults to be
** Summary changed:
- set defaults to be sslv23 not tlsv1
+ [SRU] set defaults to be sslv23 not tlsv1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904988
Title:
[SRU] set defaults to be sslv23
Public bug reported:
python-eventlet=0.18.4-1ubuntu1 (xenial) is applying the d/p/set-
defaults-to-be-tlsv1-not-sslv23.patch to set defaults to be tlsv1 not
sslv23
This will prevent xenial users from using tlsv1_1 and tlsv1_2, so I
think we should set defaults to be sslv23 not tlsv1.
another related lp bug #1818614 to address multiple master problem
mentioned in the comment #29
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744062
Title:
[SRU] L3 HA: multiple agents are active
I ran into this issue (FATAL: password authentication failed for user
"maas") by running the command 'maas-region createadmin --username admin
--password kNab4Q9fSa --email admin@localhost.localdimain' today as
well. I solved the problem in the following way.
1, confirm database_pass is
@Drew, However, we had a same case as this one in the past, and it was
fixed by using user_id_attribute=uid finally. It looks like your name is
in this test data 'uid=dfreiberger,ou=users,dc=mysite,dc=com', does it
mean that you already have a test env? If yes, is it conventient for you
to do a
@Drew, have you tried user_id_attribute=uid as well in addition to
user_name_attribute=uid ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832766
Title:
LDAP group_members_are_ids = false fails in
Successfully verified mitaka-proposed nova 2:13.1.4-0ubuntu4.4~cloud0
** Tags removed: sts-sru-needed verification-mitaka-needed
** Tags added: sts-sru-done verification-mitaka-done
** Tags removed: sts-sru-done verification-needed
** Tags added: sts-sru-needed verification-done
--
You
Successfully verified xenial-proposed nova 2:13.1.4-0ubuntu4.4
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch removed: "trusty-mitaka.debdiff"
https://bugs.launchpad.net/nova/+bug/1744079/+attachment/5256475/+files/trusty-mitaka.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744079
** Patch added: "trusty-mitaka.debdiff"
https://bugs.launchpad.net/nova/+bug/1744079/+attachment/5256475/+files/trusty-mitaka.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744079
Title:
Successfully verified pike-proposed nova 2:16.1.7-0ubuntu1~cloud2 and
ocata-proposed nova 2:15.1.5-0ubuntu1~cloud3
** Tags removed: verification-ocata-needed verification-pike-needed
** Tags added: verification-ocata-done verification-pike-done
--
You received this bug notification because you
** Patch removed: "lp1744079_xenial.debdiff"
https://bugs.launchpad.net/nova/+bug/1744079/+attachment/5204743/+files/lp1744079_xenial.debdiff
** Patch removed: "lp1744079_pike.debdiff"
https://bugs.launchpad.net/nova/+bug/1744079/+attachment/5224619/+files/lp1744079_pike.debdiff
** Patch
For stable/pike
https://review.openstack.org/#/c/530743
https://review.openstack.org/#/c/631372
For stable/ocata
https://review.openstack.org/#/c/530744
https://review.openstack.org/#/c/631376
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
upstream backported fix for stable/pike- https://review.openstack.org/#/c/631372
upstream backported fix for stable/ocata -
https://review.openstack.org/#/c/631376
Two backported fixes are squashed by the fix
e097c001c8e0efe8879da57264fcb7bdfdf2 and
e2cc275063658b23ed88824100919a6dfccb760d
** Patch added: "lp1744079_pike.debdiff"
https://bugs.launchpad.net/nova/+bug/1744079/+attachment/5224619/+files/lp1744079_pike.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744079
** Patch added: "lp1744079_ocata.debdiff"
https://bugs.launchpad.net/nova/+bug/1744079/+attachment/5224620/+files/lp1744079_ocata.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744079
Hi Corey, could you pls nominate this fix to xenial as well? we have a
customer using xenial-mitaka, I have uploaded a debdiff
'lp1744079_xenial.debdiff', many thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Successfully verified rocky-proposed nova 2:18.0.3-0ubuntu1~cloud0
** Tags removed: verification-rocky-needed
** Tags added: verification-rocky-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Successfully verified queens-proposed nova 2:17.0.7-0ubuntu1~cloud0
** Tags removed: verification-queens-needed
** Tags added: verification-queens-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Successfully verified bionic-proposed nova 2:17.0.7-0ubuntu1
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744079
Successfully verified cosmic-proposed nova 2:18.0.3-0ubuntu1
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744079
Hi Corey, sorry for the late reply because I am just back from my pto
today, I will verify them ASAP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744079
Title:
[SRU] disk over-commit still not
Successfully verified queens-proposed nova 2:17.0.6-0ubuntu2~cloud0
** Tags removed: verification-queens-needed
** Tags added: verification-queens-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nova (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744079
Title:
[SRU] disk over-commit
I also hit this problem in my x220t + ubuntu 18.04, I successfully fix
it by using the following workaround:
org.gnome.desktop.peripherals.touchpad click-method disabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Failed to verify trusty-proposed/mitaka/main
2.5.5-0ubuntu0.16.04.1~cloud0 since trusty doesn't use systemd as
default
root@trusty:/tmp/openvswitch-2.5.5# grep -r '1048576' ./debian/
./debian/changelog: * Bump nofiles to 1048576 for ovs daemons (LP: #1737866).
sucessfully to verify xenial-proposed/ocata/main
2.6.3-0ubuntu0.17.04.1~cloud0
root@xenial:~# grep -r '1048576' /lib/systemd/system/openvswitch*
/lib/systemd/system/openvswitch-nonetwork.service:LimitNOFILE=1048576
root@xenial:~# grep -r 'Max open files' /proc/`pidof ovsdb-server`/limits
Max open
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737866
Title:
Too many open files when large number of routers on
I have verified openvswitch-switch=2.5.5-0ubuntu0.16.04.1, it looks good
to me.
root@16.04:/tmp/ovs/openvswitch-2.5.5$ grep -r '1048576' ./debian/
./debian/changelog: * Bump nofiles to 1048576 for ovs daemons (LP: #1737866).
I simply add a non-empty value into crash file then I can bypass this
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1427600
Title:
apport-unpack: ValueError: ['UserGroups'] has no binary
I run into the same problem in trusty, any workaround to bypass it ?
$ sudo apport-unpack
_usr_lib_erlang_erts-5.10.4_bin_beam.smp.108.27June2018.crash ./core
Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 74, in
pr.extract_keys(f, bin_keys, dir)
File
I have tested the following mini.iso and can confirm they work for me
http://archive.ubuntu.com/ubuntu/dists/xenial-proposed/main/installer-amd64/20101020ubuntu451.19/images/netboot/mini.iso
I have tested the following mini.iso, it works for me.
http://archive.ubuntu.com/ubuntu/dists/artful-proposed/main/installer-
amd64/20101020ubuntu523.2/images/netboot/mini.iso
Joshua
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug
** Patch added: "lp_1745531_artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1745531/+attachment/5044882/+files/lp_1745531_artful.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "d-i_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1745531/+attachment/5044886/+files/d-i_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "d-i_artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1745531/+attachment/5044883/+files/d-i_artful.debdiff
** Summary changed:
- Reinforce hostname preseed regex
+ [SRU] Reinforce hostname preseed regex
** Description changed:
+ [Impact]
+
This is
** Patch added: "lp_1745531_bonic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1745531/+attachment/5044885/+files/lp_1745531_bonic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp_1745531_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1745531/+attachment/5044863/+files/lp_1745531_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "d-i_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1745531/+attachment/5044864/+files/d-i_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp_1745531_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1745531/+attachment/5044860/+files/lp_1745531_trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
According to Eric's above comment, I've opened a new bug to track this
at - https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1745531
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452202
Title:
Public bug reported:
This is the same issue reported in
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202
However that is marked as 'Fix Released' and the issue is still occurring so it
seems best to just open a new bug according to Eric's comment.
The present hostname preseed
Hi Eric,
I think your proposal '-w' is good, so I will change to use:
if ! echo "$RET" | grep -qw 'ubuntu'; then
Mathieu,
How about using '/b' ? I mean using the following regex
/bin/sed -i "s/\b${CURRENT_HOSTNAME}\b/${NETCFG_HOSTNAME}/g" /etc/hosts
I have done some test below:
I have some thoughts in my mind for this problem as below:
1, First of all, we need to figure out why it will appear multiple
ACTIVE master HA nodes in theory ?
Assume the master is dead (at this time, it's status in DB is still
ACTIVE), then slave will be selected to new master. After the old
Remove the debdiff for "d-i" for Trusty only and Eric will take care of
it in lp bug #1743787
** Attachment removed: "d-i_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/+attachment/5037278/+files/d-i_trusty.debdiff
** Patch removed: "d-i_trusty_v2.debdiff"
** Tags removed: sts-sru-done verification-done
** Tags added: sts-sru-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452202
Title:
ubuntu preseed install fails to set a hostname
To manage
** Patch added: "d-i_xenial_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/+attachment/5042030/+files/d-i_xenial_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "d-i_bionic_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/+attachment/5042032/+files/d-i_bionic_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "d-i_trusty_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/+attachment/5042028/+files/d-i_trusty_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp_1452202_bonic_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/+attachment/5042031/+files/lp_1452202_bonic_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp_1452202_xenial_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/+attachment/5042029/+files/lp_1452202_xenial_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp_1452202_trusty_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/+attachment/5042027/+files/lp_1452202_trusty_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374508
Title:
Mismatch happens between BDM and domain XML If instance does
The following regex is more better
/bin/sed -i
"/^[127|localhost]/s/${CURRENT_HOSTNAME}/${NETCFG_HOSTNAME}/g"
/etc/hosts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452202
Title:
ubuntu preseed
I mean:
/usr/bin/awk '$1 ~ /^127|localhost/ {print $0}' /etc/hosts | /bin/sed
"s/\s*\(${CURRENT_HOSTNAME}\)\(\s*\)/\t${NETCFG_HOSTNAME}/g"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452202
Maybe we can use the following regex instead, 'awk '$1 ~
/^127|localhost/ {print $0}'' is used to fix 'ff02::1 ip6-allnodes'
case, and add 'g' option to modifity all hostname.
$ hostname=ubuntu
$ echo '127.0.1.1 ubuntu.me.com ubuntu' |awk '$1 ~ /^127|localhost/ {print
$0}' |sed
I think Peter Wu is totally right.
In addition to above two problems, there is still another problem with
the patch that the present regular expression '/bin/sed -i
"s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /etc/hosts' can't handle
multiple hostname case:
$ echo '127.0.1.1 ubuntu.me.com ubuntu'
** Patch added: "trusty-mitaka.debdiff"
https://bugs.launchpad.net/nova/+bug/1692397/+attachment/5028727/+files/trusty-mitaka.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692397
Title:
I can not reproduce the problem, I see SQL has used
'compute_nodes.deleted = 0' to filter deleted services as the following
debug info shows (mitaka).
(Pdb)
(Pdb) 'SELECT count(compute_nodes.id) AS count_1, sum(compute_nodes.vcpus) AS
sum_1, sum(compute_nodes.memory_mb) AS sum_2,
xenial-proposed has been verified successfully -
http://paste.ubuntu.com/25520417/
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: sru-sponsors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668410
Title:
[SRU] Infinite loop trying to delete deleted HA router
To manage notifications about this bug go to:
** Tags added: sru-sponsors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668410
Title:
[SRU] Infinite loop trying to delete deleted HA router
To manage notifications about this bug go to:
** Description changed:
[Impact]
When deleting a router the logfile is filled up. See full log -
http://paste.ubuntu.com/25429257/
I can see the error 'Error while deleting router
c0dab368-5ac8-4996-88c9-f5d345a774a6' occured 3343386 times from
_safe_router_removed() [1]:
$
** Description changed:
- Latest Mitaka code, L3 HA
- After running rally create_and_delete_routers (concurrency 100 and times 100,
or more) neutron l3 agent logs on nodes filled (every .003 second timestamp)
with such traces:
- http://paste.openstack.org/show/599851/
- which causes cluster
Hi Eric,
Below is my test script and data which are the same as the case
description, thanks.
# Test script
echo "/- auto.direct --timeout 60" > /etc/auto.master
END=2
for i in $(seq 1 $END); do echo $i; echo "/test/samba/test"$i"
-fstype=cifs,rw,username=hua,password=password
Verified successfully on both xenial-proposed and yakkety-proposed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686679
Title:
** Patch added: "yakkety_v3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1686679/+attachment/4899915/+files/yakkety_v3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Eric,
I have updated debdiff, thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686679
Title:
[SRU] Ubuntu16.04 : autofs is extremely long with large number of
direct maps
To manage
** Patch removed: "xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1686679/+attachment/4883138/+files/xenial.debdiff
** Patch removed: "yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1686679/+attachment/4883139/+files/yakkety.debdiff
**
** Patch added: "yakkety_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1686679/+attachment/4895630/+files/yakkety_v2.debdiff
** Tags removed: patch-needswork
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "xenial_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1686679/+attachment/4895629/+files/xenial_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Eric,
I have updated debdiff to address your comments, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686679
Title:
[SRU] Ubuntu16.04 : autofs is extremely long with large number of
Hi Christian,
Sorry for late response because of sprint and pto during this period, I
have updated the bug description and debdiff to address your concerns,
many thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch removed: "xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1686679/+attachment/4868564/+files/xenial.debdiff
** Patch added: "xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1686679/+attachment/4883138/+files/xenial.debdiff
--
You
** Patch added: "yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1686679/+attachment/4883139/+files/yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686679
** Description changed:
[Impact]
- autofs service in xenial takes extremely long time since its creating
- the directory hierarchy for all direct mounts maps, thus it will take
- too long to make all the automount shares available when using autofs
- with large direct mappings, customer is
** Tags added: sts sts-sponsor sts-sru ubuntu-sponsors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686679
Title:
[SRU] Ubuntu16.04 : autofs takes extreamly long with large number of
direct
** Description changed:
- autofs service takes extremely long time since its creating the
- directory hierarchy for all direct mounts maps, so it will take too long
- to make all the automount shares available when using autofs with large
- direct mappings, customer is complaining about this
Public bug reported:
autofs service takes extremely long time since its creating the
directory hierarchy for all direct mounts maps, so it will take too long
to make all the automount shares available when using autofs with large
direct mappings, customer is complaining about this point. Redhat
I've verified that the new package (1.6.1-0ubuntu1.2~cloud0 and
1.2.0-2ubuntu0.3~cloud0) doesn't break anything and fix the problem. see
https://pastebin.canonical.com/186800/ and
https://pastebin.canonical.com/186797/
** Tags removed: verification-mitaka-needed verification-newton-needed
** Tags
I have found the root cause why I hit the problem, that's because I did
not add snippet ( or ) to expose the host CPU features to the VM described in the link
[1]. This is my new test result [2]. So mark it as incomplete state.
Hi Christian, many thanks.
[1]
1 - 100 of 156 matches
Mail list logo