[Bug 1902960] Re: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases
Hi, We are affected by this issue on Bionic. Upgrading systemd package breaks DNS resolution in VMs that didn't have the workaround above applied. Would it be possible to provide a backport of the systemd fix done to Bionic? We are currently relying on the following workaround to recover from the loss of DNS resolution: udevadm trigger -c add /sys/class/net/eth0 systemctl restart systemd-networkd It seems that we are able to consistently reproduce this problem in our VM images, we had multiple VM images affected by this issue. We'd be happy to provide debug information if you want to investigate the root cause further. Of course I can't tell for sure if the next VM image we build will be affected or not. Thanks, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902960 Title: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910976] Re: Cherry-pick dm-crypt performance improvement patch from Linux 5.9
This LP bug is tracking a feature request and as such, I can't provide logs. I'll therefore change the status to Confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910976 Title: Cherry-pick dm-crypt performance improvement patch from Linux 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910976] [NEW] Cherry-pick dm-crypt performance improvement patch from Linux 5.9
Public bug reported: Hi, I'm asking if it would be possible to cherry-pick patch "dm crypt: add flags to optionally bypass kcryptd workqueues" into the 5.4 Ubuntu kernel. This patch has been merged in mainline kernel 5.9 https://github.com/torvalds/linux/commit/39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 but was not tagged for the stable tree. This patch provides important performance gains for some workloads using dm-crypt / LUKS and cherry-picking it would be very beneficial for dm- crypt users. You can find details on the expected gain in the following links: * https://www.redhat.com/archives/dm-devel/2020-July/msg00138.html * https://blog.cloudflare.com/speeding-up-linux-disk-encryption/ The patch mostly applies cleanly on the Ubuntu 5.4 kernel, the only merge conflict is due to the module version at the end of the patch. I can provide a backport patch if needed. Thanks, ** Affects: linux (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/1910976 Title: Cherry-pick dm-crypt performance improvement patch from Linux 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995234] Re: Merge collectd 5.1.0-3 (universe) from Debian unstable (main)
I found a build of the last collectd debian testing package on the Andrew Cowie PPA here : https://launchpad.net/~afcowie/+archive/network . Might be a starting point to merge the debian package to universe ? There is a Ubuntu patch to support Perl plugin which is dropped in this package, so the perl plugin is currently disabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995234 Title: Merge collectd 5.1.0-3 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/995234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045795] Re: jenkins.util.MarkFindingOutputStream class is missing : Maven build not working in slave mode
** This bug has been flagged as a security vulnerability -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045795 Title: jenkins.util.MarkFindingOutputStream class is missing : Maven build not working in slave mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jenkins/+bug/1045795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045795] [NEW] jenkins.util.MarkFindingOutputStream class is missing : Maven build not working in slave mode
Public bug reported: Maven build doesn't work in slave mode : the Maven build plugin requires the class jenkins.util.MarkFindingOutputStream to work but this class is not in the jenkins WAR built by Ubuntu. This class is present in the official build of Jenkins LTS 1.466.1 When i try to build a Maven project in a slave, i see this stacktrace : Modules changed, recalculating dependency graph FATAL: jenkins/util/MarkFindingOutputStream java.lang.NoClassDefFoundError: jenkins/util/MarkFindingOutputStream at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) at java.net.URLClassLoader.access$000(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:212) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:655) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480) at hudson.model.Run.run(Run.java:1438) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: java.lang.ClassNotFoundException: jenkins.util.MarkFindingOutputStream at java.net.URLClassLoader$1.run(URLClassLoader.java:217) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) ... 16 more I dont understand why the MarkFindingOutputStream class in not present because the source file is in the source package in this folder : core/src/main/groovy/jenkins/util/MarkFindingOutputStream.java. The other source file present in this folder is ServerTcpPort and is correctly compiled and included in the WAR file of Jenkins. Anyway, theses two files are in the wrong folder (groovy sources). Upstream fixed this : https://github.com/jenkinsci/jenkins/commit/2338b6682146e912c9a4d3769eff4864e487c427. I think that the best thing to do is to move theses files in the right source folder. Hope this helps, Yoann. ** Affects: jenkins (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/1045795 Title: jenkins.util.MarkFindingOutputStream class is missing : Maven build not working in slave mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jenkins/+bug/1045795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011640] Re: network configuration is not restored after host reboot
Ok,
** Description changed:
After rebooting a host, nova-compute fails to restart guests VM because
- the network is not configured correctly. I have
- resume_guests_state_on_host_boot=true and
- start_guests_on_host_boot=true flags in /etc/nova/nova.conf
+ the interface used to create vlan is not UP. In our case, this interface
+ is not connected to a physical network and doesn't have an IP address,
+ so it's not configured on boot.
- nova-network crashs because it lacks brXXX and vlanXXX interfaces.
+ It could be good to start nova-network even if vlan interfaces cannot be
+ set up. Here, it crashes while trying to put a vlan interface UP, as you
+ can see in the attached log file
- To restart the guest, i wrote this script to configure the network as
- nova did when creating the guest :
+ For other people eventually affected by the problem, i initially wrote
+ this script to manually configure network so nova-network can start
+ successfully
#!/bin/sh
add_network() {
- BR=br$1
- VLAN=vlan$1
- LAN=$2
- BCAST=$3
- vconfig add eth1 $1
- brctl addbr $BR
- brctl setfd $BR 0
- brctl stp $BR off
- ip link set $BR up
- ip link show dev $BR
- brctl addif $BR $VLAN
- ip addr show dev $BR scope global
- ip addr add "$LAN" brd "$BCAST" dev $BR
+ BR=br$1
+ VLAN=vlan$1
+ LAN=$2
+ BCAST=$3
+ vconfig add eth1 $1
+ brctl addbr $BR
+ brctl setfd $BR 0
+ brctl stp $BR off
+ ip link set $BR up
+ ip link show dev $BR
+ brctl addif $BR $VLAN
+ ip addr show dev $BR scope global
+ ip addr add "$LAN" brd "$BCAST" dev $BR
}
vconfig set_name_type VLAN_PLUS_VID_NO_PAD
add_network 100 "172.16.0.4/24" "172.16.0.255"
add_network 101 "172.16.1.4/24" "172.16.1.255"
add_network 102 "172.16.2.4/24" "172.16.2.255"
add_network 103 "172.16.3.4/24" "172.16.3.255"
add_network 104 "172.16.4.4/24" "172.16.4.255"
-
- I think nova-network should recreate lacking interfaces (brXXX and
- vlanXXX) upon reboot to allow nova-compute to start guests
** Attachment added: "nova-network crash log"
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1011640/+attachment/3185031/+files/nova-network-error.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011640
Title:
network configuration is not restored after host reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1011640/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011640] [NEW] network configuration is not restored after host reboot
Public bug reported:
After rebooting a host, nova-compute fails to restart guests VM because
the network is not configured correctly. I have
resume_guests_state_on_host_boot=true and
start_guests_on_host_boot=true flags in /etc/nova/nova.conf
nova-network crashs because it lacks brXXX and vlanXXX interfaces.
To restart the guest, i wrote this script to configure the network as
nova did when creating the guest :
#!/bin/sh
add_network() {
BR=br$1
VLAN=vlan$1
LAN=$2
BCAST=$3
vconfig add eth1 $1
brctl addbr $BR
brctl setfd $BR 0
brctl stp $BR off
ip link set $BR up
ip link show dev $BR
brctl addif $BR $VLAN
ip addr show dev $BR scope global
ip addr add "$LAN" brd "$BCAST" dev $BR
}
vconfig set_name_type VLAN_PLUS_VID_NO_PAD
add_network 100 "172.16.0.4/24" "172.16.0.255"
add_network 101 "172.16.1.4/24" "172.16.1.255"
add_network 102 "172.16.2.4/24" "172.16.2.255"
add_network 103 "172.16.3.4/24" "172.16.3.255"
add_network 104 "172.16.4.4/24" "172.16.4.255"
I think nova-network should recreate lacking interfaces (brXXX and
vlanXXX) upon reboot to allow nova-compute to start guests
** 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/1011640
Title:
network configuration is not restored after host reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1011640/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966944] Re: proxy support not fully working
** Also affects: vm-builder (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/966944 Title: proxy support not fully working To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/966944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
