[Bug 1898547] Re: neutron-linuxbridge-agent fails to start with iptables 1.8.5
I've tested this (s390x, groovy) and im able to launch an instance with the specific version of iptables mentioned above -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898547 Title: neutron-linuxbridge-agent fails to start with iptables 1.8.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1898547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902270] Re: iptables-restore fails on groovy
Repaste with public pastebin https://pastebin.ubuntu.com/p/mpVNJmRv5b/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902270 Title: iptables-restore fails on groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1902270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902270] [NEW] iptables-restore fails on groovy
Public bug reported: Deploying victoria on groovy (on s390x in this case), I see the following error: https://pastebin.canonical.com/p/XVXsW3tdkx/ Which has the end result of neutron not allocating VIFs correctly (timeouts) If I update-alternatives so that iptables-restore and ip6tables-restore use iptables-legacy, everything is OK. ** Affects: neutron (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/1902270 Title: iptables-restore fails on groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1902270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891203] Re: arm64 - services not running that should be - missing capabilities
i have finally verified this on focal - i am able to launch nova instances with 1:4.2-3ubuntu6.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891203 Title: arm64 - services not running that should be - missing capabilities To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1891203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891203] Re: arm64 - services not running that should be - missing capabilities
Corey rebuilt qemu with the patch suggested - i've tested it on one machine and it has worked. I am going to retest on a fresh deployment but it looks good ppa:corey.bryant/bionic-ussuri 1:4.2-3ubuntu6.3~cloud1~ubuntu18.04.1~ppa202008131000 This patch is already in 4.2.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891203 Title: arm64 - services not running that should be - missing capabilities To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1891203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859844] Re: Impossible to rename the Default domain id to the string 'default.'
** Changed in: charm-keystone Status: New => Invalid ** Changed in: keystone (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859844 Title: Impossible to rename the Default domain id to the string 'default.' To manage notifications about this bug go to: https://bugs.launchpad.net/charm-keystone/+bug/1859844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851290] Re: Add backport for (s390x) endian fixes to ceph nautilus
Verified functionality in bionic, train-proposed, both status and a functional test (storage) work OK - Same test and results in comment #5, Test Case is OK ** Tags removed: verification-needed-train ** Tags added: verification-done-train -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851290 Title: Add backport for (s390x) endian fixes to ceph nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1851290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851290] Re: Add backport for (s390x) endian fixes to ceph nautilus
I have tested this with Eoan proposed - ceph-mon now bootstraps and ceph reports that an OK health status: https://pastebin.ubuntu.com/p/9brKDGmHcf/ ceph-osd also passes a storage test once related to this particular ceph-mon, when the following was executed from one of the ceph-mon nodes: $ sudo ceph osd pool create rbd 128 $ echo 123456789 > /tmp/input.txt $ sudo rados put -p rbd test_input /tmp/input.txt $ sudo rados get -p rbd test_input /dev/stdout 123456789 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851290 Title: Add backport for (s390x) endian fixes to ceph nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1851290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850530] Re: qemu-system-s390x permission denied in container on Eoan
sorry, i was using kvm_grp_gid as a placeholder variable for what the gid is -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850530 Title: qemu-system-s390x permission denied in container on Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1850530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850530] Re: qemu-system-s390x permission denied in container on Eoan
The host is bionic - surprisingly (as I thought it was the obvious fix), adding kvm to the modules to be loaded didn't help It turns out that previously, passing /dev/kvm through like this was enough: kvm: path: /dev/kvm type: unix-char The perms for /dev/kvm on the host are: crw-rw 1 root kvm 10, 232 Oct 30 19:36 /dev/kvm However, its being passed through with root group ownership. Adding the kvm gid to the pass-through for /dev/kvm allows me to launch an instance - not sure when this changed but it was working in previous releases. So fix is: kvm: path: /dev/kvm type: unix-char gid: kvm_grp_gid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850530 Title: qemu-system-s390x permission denied in container on Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1850530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850530] Re: qemu-system-s390x permission denied in container on Eoan
This is what we're applying to the juju-default profile after bootstrapping: https://raw.githubusercontent.com/openstack-charmers/openstack-on- lxd/master/lxd-profile.yaml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850530 Title: qemu-system-s390x permission denied in container on Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1850530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850530] [NEW] qemu-system-s390x permission denied in container on Eoan
Public bug reported: qemu-system-s390x (nova-compute) on eoan (train) in an lxd container Short detail, when trying to launch an instance: Could not access KVM kernel module: Permission denied 2019-10-29T18:03:09.314636Z qemu-system-s390x: failed to initialize KVM: Permission denied Full libvirt debug log: https://pastebin.ubuntu.com/p/8Hh2SsB6SS/ Potentially a new kernel module or char dev which needs to be enabled for LXD or passed through? Potentially related to this bug: https://github.com/openstack-charmers /octavia-diskimage-retrofit/issues/3 ** Affects: ubuntu-z-systems Importance: Undecided Status: Triaged ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: s390x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850530 Title: qemu-system-s390x permission denied in container on Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1850530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828830] Re: ceph mon fails to bootstrap - cosmic (mimc) and disco on arm64
same problem on disco ** Summary changed: - ceph mon fails to bootstrap - cosmic (mimc) on arm64 + ceph mon fails to bootstrap - cosmic (mimc) and disco on arm64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828830 Title: ceph mon fails to bootstrap - cosmic (mimc) and disco on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-mon/+bug/1828830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713032] Re: [luminous] ceph-mon crashes when it is elected leader (s390x)
If you add the debug symbols repo as follows here: https://wiki.ubuntu.com/Debug%20Symbol%20Packages#Manual_install_of_debug_packages then the debug symbols should be available for install - it was mentioned that they may be available for luminous but not mimic - in this case, luminous can be used as the bug is exactly the same between both versions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713032 Title: [luminous] ceph-mon crashes when it is elected leader (s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1713032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
@Joseph I think I have bandwidth, please provide specific links and instructions:) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797092] [NEW] xenial guest on arm64 drops to busybux under openstack bionic-rocky
Public bug reported: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: libvirt ** Attachment added: "xenial_console_log.txt" https://bugs.launchpad.net/bugs/1797092/+attachment/5199436/+files/xenial_console_log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792947] Re: OSError: [Errno 22] failed to open netns (bionic-rocky)
This has been resolved as pyroute2 0.5.2-1 is now in the bionic-rocky cloud-archive, which resolves the issue. ** Changed in: ubuntu-z-systems Status: Triaged => Fix Released ** Changed in: glibc (Ubuntu) Status: New => Invalid ** Changed in: pyroute2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792947 Title: OSError: [Errno 22] failed to open netns (bionic-rocky) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1792947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
@Dann - good news, I am able to deploy a bionic guest using the non-uefi image (still tagged as such) and connect to it with bionic-rocky: Result of running uname -a on 10.245.172.3: Linux bionic-101103 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:22:18 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux Will also now validate on bionic-queens -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771662 Title: [bionic] libvirtError: Node device not found: no node device with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
Have tested libvirt-bin from dann's PPA re comment 45 with partial success. This results in hypervisors being listed via openstack hypervisor list, and instances can be launched. https://pastebin.canonical.com/p/pDDmYQsvSr/ However, the instance build is not really successful - there is no network connectivity to the tenant network, as the guest instance just drops to an initramfs prompt. https://pastebin.canonical.com/p/N2JQPvfsGv/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771662 Title: [bionic] libvirtError: Node device not found: no node device with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792947] Re: OSError: [Errno 22] failed to open netns (bionic-rocky)
I have just confirmed that I can launch and connect to an instance on bionic-rocky using the master branch from the pyroute2 github page. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792947 Title: OSError: [Errno 22] failed to open netns (bionic-rocky) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1792947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792947] Re: OSError: [Errno 22] failed to open netns (bionic-rocky)
Using the latest version of pyroute2 on the neutron-gateway node gets rid of the netns errors. However, there is now a stack trace: https://pastebin.canonical.com/p/SptkxkCYC8/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792947 Title: OSError: [Errno 22] failed to open netns (bionic-rocky) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1792947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792947] [NEW] OSError: [Errno 22] failed to open netns (bionic-rocky)
Public bug reported:
The bionic-rocky deployment fails to allocate DHCP to new instances:
neutron/neutron-dhcp-agent.log:2018-09-17 07:08:01.432 190830 ERROR
neutron.agent.dhcp.agent [-] Unable to enable dhcp for ade593b1-153b-
47b8-84a9-009fca692003.: OSError: [Errno 22] failed to open netns
This can be tracked to the pyroute2 package, where it is simply
executing:
pyroute2.NetNS("qdhcp-UUID", flags=0")
While the namespace is visible with the "ip netns" command, the pyroute2
method fails (and this is with either python 2.7 or 3.?) with OSError
22, and this associated syscall:
[pid 51036] openat(AT_FDCWD,
"/var/run/netns/qdhcp-ade593b1-153b-47b8-84a9-009fca692003", O_RDONLY) = 4
[pid 51036] tee(4, 1073741824, 17109518126325597131, 0xaa7bac30 /* SPLICE_F_???
*/) = -1 EINVAL (Invalid argument)
This is specific to s390x, and does not occur on bionic-queens, only
using the bionic-rocky cloud archive. These archives do not contain
different versions of pyroute2 so this seems unlikely to be the issue.
Downgrading openvswitch to the bionic-queens version (2.10.0-0ubuntu2
--> 2.9.0-0ubuntu1) did not seem to make a difference but more testing
may be necessary.
A bug has also been logged against pyroute2:
https://github.com/svinota/pyroute2/issues/542
** Affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Affects: pyroute2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: pyroute2 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- network namespace inaccessible via pyroute2 package to charms with
bionic-rocky cloud-archive
+ OSError: [Errno 22] failed to open netns (bionic-rocky)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792947
Title:
OSError: [Errno 22] failed to open netns (bionic-rocky)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1792947/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713032] Re: [luminous] ceph-mon crashes when it is elected leader (s390x)
this same problem is still present in rocky, using ceph mimic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713032 Title: [luminous] ceph-mon crashes when it is elected leader (s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1713032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780885] Re: hangs at Building initial module for 4.15.0-23-generic (promptless password prompt)
Further info: I am running bionic, upgraded from xenial -> zesty -> bionic, and have done previous apt-get upgrade's in bionic without running into 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/1780885 Title: hangs at Building initial module for 4.15.0-23-generic (promptless password prompt) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1780885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780885] [NEW] hangs at Building initial module for 4.15.0-23-generic (promptless password prompt)
Public bug reported: This bug may more specifically be with dkms, but assume most people will hit it this way sudo apt-get update ; sudo apt-get upgrade would hang at: Building initial module for 4.15.0-23-generic after a few seconds, keypresses/enter were not being registered, but there is a secret password prompt - i.e., at this point, when things appear to have hung, entering your password twice will continue the process. It may also be related to 'secure boot' but I am unsure. Similar issue and resolution found here: https://github.com/teejee2008/ukuu/issues/81 ** Affects: apt (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/1780885 Title: hangs at Building initial module for 4.15.0-23-generic (promptless password prompt) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1780885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772461] Re: chzdev behaviour change in bionic
Also, after a reboot: ubuntu@s4lp5:~$ lszdev --configure --info c003 DEVICE qeth 0.0.c003:0.0.c004:0.0.c005 Names : encc003 Network interfaces : encc003 Modules: qeth Online : yes Exists : yes Persistent : yes ATTRIBUTEACTIVEPERSISTENT bridge_hostnotify"0" - bridge_reflect_promisc "none"- bridge_role "none""primary" buffer_count "64" - hw_trap "disarm" - isolation"none"- layer2 "1" "1" online "1" "1" performance_stats"0" - portname ""- portno "0" - priority_queueing"always queue 0" - vnicc/bridge_invisible "n/a" - vnicc/flooding "n/a" - vnicc/learning "n/a" - vnicc/learning_timeout "n/a" - vnicc/mcast_flooding "n/a" - vnicc/rx_bcast "n/a" - vnicc/takeover_learning "n/a" - vnicc/takeover_setvmac "n/a" - It appears that the error from the tool is just misleading, as I have just found this in dmesg: [ 14.218702] qeth.8c5944: 0.0.c003: The LAN already has a primary Bridge Port -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772461 Title: chzdev behaviour change in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772461] [NEW] chzdev behaviour change in bionic
Public bug reported:
This may be less of a bug, and more of a change of usage:
Using preseeds for xenial I was successfully able to configure
bridge_role=primary on a qeth device, using this command:
chzdev --no-root-update -pVe ${NIC_ID} layer2=1 bridge_role=primary
However, this no longer works - upon reboot, bridge_role is set to none.
Running this command manually, on the built lpar, without --no-root-
update, returns:
QETH device 0.0.c003:0.0.c004:0.0.c005 already configured
Running sudo chzdev -Ve 0.0.c003 layer2=1 bridge_role=primary
returns
Error: Cannot set layer2='1' while online='1' (*)
Running with --force still complains about being online, so first i take
the dev offline, and rerun the command, but get this:
Error: Settings bridge_role and vnicc/rx_bcast are in conflict (*)
ubuntu@s4lp5:/sys/devices/qeth/0.0.c003$ cat vnicc/rx_bcast
n/a
ubuntu@s4lp5:/sys/devices/qeth/0.0.c003$
The only combination that seems to work is:
ubuntu@s4lp5:/sys/devices/qeth/0.0.c003$ sudo chzdev -Ve 0.0.c003 layer2=1
bridge_role=primary online=0 --force
Scanning for devices in all configurations:
ECKD DASD : 268
Loading required kernel module: dasd_fba_mod
Failed to load kernel module: dasd_fba_mod
FBA DASD : 0
FCP device : 20
zFCP LUN : 0
QETH device: 42
Loading required kernel module: ctcm
Failed to load kernel module: ctcm
CTC device : 0
Loading required kernel module: lcs
Failed to load kernel module: lcs
LCS device : 0
Generic CCW device : 1
Total : 331
QETH device 0.0.c003:0.0.c004:0.0.c005 configured
Changes: online=0 bridge_role=primary
Network interface: encc003
Warning: Settings bridge_role and vnicc/rx_bcast are in conflict
ubuntu@s4lp5:/sys/devices/qeth/0.0.c003$ cat bridge_role
primary
ubuntu@s4lp5:/sys/devices/qeth/0.0.c003$ sudo chzdev -Ve 0.0.c003 online=1
Scanning for devices in all configurations:
ECKD DASD : 268
Loading required kernel module: dasd_fba_mod
Failed to load kernel module: dasd_fba_mod
FBA DASD : 0
FCP device : 20
zFCP LUN : 0
QETH device: 42
Loading required kernel module: ctcm
Failed to load kernel module: ctcm
CTC device : 0
Loading required kernel module: lcs
Failed to load kernel module: lcs
LCS device : 0
Generic CCW device : 1
Total : 331
QETH device 0.0.c003:0.0.c004:0.0.c005 configured
Changes: online=1
Network interface: encc003
ubuntu@s4lp5:/sys/devices/qeth/0.0.c003$ cat bridge_role
none
ubuntu@s4lp5:/sys/devices/qeth/0.0.c003$
** Affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Affects: s390-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: s390x
** Also affects: ubuntu-z-systems
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/1772461
Title:
chzdev behaviour change in bionic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772461/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name
Further information: Using juju 2.4 beta2 I was able to deploy magpie on bionic in lxd and baremetal via MAAS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771662 Title: libvirtError: Node device not found: no node device with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM
I have tried to add this to the XML but it seems that it is missing from the libvirt domain schema. error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domain.rng Extra element devices in interleave Element domain failed to validate content -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664737 Title: [ARM] : Unable to use Cinder volumes on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1664737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM
Meanwhile, I have been testing this on xenial queens, and am receiving what appears to be a more documented error. [ 720.314053] virtio_blk virtio4: virtio: device uses modern interface but does not have VIRTIO_F_VERSION_1 [ 720.325082] virtio_blk: probe of virtio4 failed with error -22 https://pastebin.canonical.com/209188/ - this happens every time the volume is added. "Removing" the volume produces an acceptable set of messages, e.g. https://pastebin.canonical.com/209298/ e.g. https://lists.gnu.org/archive/html/qemu-devel/2016-08/msg03385.html The implication here is to test toggling disable-modern and disable- legacy although I am not sure how to achieve this via openstack to test. qemu, libvirt and kernel versions: ubuntu@node-loewy:~$ qemu-system-aarch64 --version QEMU emulator version 2.10.1(Debian 1:2.10+dfsg-0ubuntu5~cloud0) Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers ubuntu@node-loewy:~$ libvirtd --version libvirtd (libvirt) 4.0.0 ubuntu@node-loewy:~$ uname -a Linux node-loewy 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:10:26 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux qemu-system-aarch64 command: https://pastebin.canonical.com/209299/ domain xml with disk added: https://pastebin.canonical.com/209300/ domain xml diff (with and without disk): https://pastebin.canonical.com/209301/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664737 Title: [ARM] : Unable to use Cinder volumes on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1664737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM
I can confirm this is still an issue with pike + arm64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664737 Title: [ARM] : Unable to use Cinder volumes on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1664737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719196] Re: [arm64 ocata] newly created instances are unable to raise network interfaces
I've tested with the packages from the ppa: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2995 qemu: Installed: 1:2.8+dfsg-3ubuntu2.7~ppa5cloud qemu-system-arm: Installed: 1:2.8+dfsg-3ubuntu2.7~ppa5cloud qemu-system-aarch64: Installed: 1:2.8+dfsg-3ubuntu2.7~ppa5cloud Rebooted the instance and it aquired an IP address and booted. more info, virsh dumpxml excerpt: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719196 Title: [arm64 ocata] newly created instances are unable to raise network interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1719196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719196] Re: [arm64 ocata] newly created instances are unable to raise network interfaces
The problem is with virtio-mmio. https://bugzilla.redhat.com/show_bug.cgi?id=1422413 Instances launched with virtio-mmio on aarch64 will not get DHCP (will not have a nic) xml with libvirt 2.5.0 I have updated libvirt-daemon to 3.6.0 on a particular compute node - when an instance is booted now, the nic section of the virsh xml looks like this: The instance then gets a NIC and is able to get DHCP and complete cloud- init successfully. ** Bug watch added: Red Hat Bugzilla #1422413 https://bugzilla.redhat.com/show_bug.cgi?id=1422413 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719196 Title: [arm64 ocata] newly created instances are unable to raise network interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1719196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM
For sanity sake I am currently attempting to reproduce this with pike on arm64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664737 Title: [ARM] : Unable to use Cinder volumes on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1664737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation
I'm seeing this installing 17.10 on s390x also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1704929 Title: Repeating "can't open /dev/ttyX: No such device or address" messages during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713032] Re: [luminous] ceph-mon crashes when it is elected leader (s390x)
This was using the openstack-on-lxd and instructions, but was not using zfs backend - it is using directory backend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713032 Title: [luminous] ceph-mon crashes when it is elected leader (s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1713032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary
** Tags removed: verification-needed-zesty ** Tags added: verification-zesty-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697610 Title: aarch64: logfile not supported in this QEMU binary To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1697610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary
I have completed zesty-ocata/proposed testing and its working (I am able to launch and connect to an instance successfully) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697610 Title: aarch64: logfile not supported in this QEMU binary To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1697610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706630] Re: aarch64: MSI is not supported by interrupt controller
Re the state of qemu ver, I've asked someone else to comment on that. XML from before was: ==> nova/nova-compute.log <== 2017-08-28 13:15:46.413 23162 ERROR nova.virt.libvirt.guest [req-e2fc9a90-7433-479c-9d96-c2818641fe45 b147293e0a7941899301c59b48068e51 18b9fc2bdb6b45a0a682d79d9130a975 - default default] Error launching a defined domain with XML: instance-0007 674a2e53-cfbb-4043-a6f0-09536acc1781 http://openstack.org/xmlns/libvirt/nova/1.0";> openstack-on-lxd-ftw 2017-08-28 13:15:40 256 3 0 0 1 admin admin 262144 262144 1 1024 hvm /usr/share/AAVMF/AAVMF_CODE.fd /var/lib/libvirt/qemu/nvram/instance-0007_VARS.fd destroy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706630 Title: aarch64: MSI is not supported by interrupt controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1706630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706630] Re: aarch64: MSI is not supported by interrupt controller
Can confirm this bug exists as of today, with xenial-pike/proposed Linux juju-25b69e-14 4.4.0-79-generic #100-Ubuntu SMP Wed May 17 19:58:30 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux libvirt0: 3.6.0 qemu: 2.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706630 Title: aarch64: MSI is not supported by interrupt controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1706630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713099] Re: ceph + pike - ceph-disk prepare fails when directory specified rather than block device
accidentally logged against libvirt ** Package changed: libvirt (Ubuntu) => charm-ceph ** Also affects: charm-ceph-osd 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/1713099 Title: ceph + pike - ceph-disk prepare fails when directory specified rather than block device To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph/+bug/1713099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713099] [NEW] ceph + pike - ceph-disk prepare fails when directory specified rather than block device
Public bug reported: Charm Config (with xenial-pike on arm64, although suspect this is not restricted to arm64): ceph: annotations: gui-x: '750' gui-y: '500' charm: cs:~openstack-charmers-next/ceph num_units: 3 options: fsid: 5a791d94-980b-11e4-b6f6-3c970e8b1cf7 monitor-secret: AQAi5a9UeJXUExAA+By9u+GPhl8/XiUQ4nwI3A== osd-devices: /srv/osd use-direct-io: False source: cloud:xenial-pike/proposed error summary: 2017-08-25 15:03:46.288447 78497000 -1 bdev(0xaaab0f0d8780 /srv/osd/block) open open got: (22) Invalid argument 2017-08-25 15:03:46.288509 78497000 -1 bluestore(/srv/osd) mkfs failed, (22) Invalid argument 2017-08-25 15:03:46.288523 78497000 -1 OSD::mkfs: ObjectStore::mkfs failed with error (22) Invalid argument 2017-08-25 15:03:46.288681 78497000 -1 ** ERROR: error creating empty object store in /srv/osd: (22) Invalid argument More complete log: https://pastebin.canonical.com/196755/ ** Affects: charm-ceph Importance: Undecided Status: New ** Affects: charm-ceph-osd Importance: Undecided Status: New ** Tags: ceph ceph-osd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713099 Title: ceph + pike - ceph-disk prepare fails when directory specified rather than block device To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph/+bug/1713099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673467] Re: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor
A general description of the workaround for 'logfile not supported in
this QEMU binary' on arm64 with ocata is:
in nova/virt/libvirt/guest.py:115, in the create function, added:
xml = etree.fromstring(xml)
for bad in xml.xpath("//log"):
bad.getparent().remove(bad)
#for item in xml.findall('console'):
# xml.remove(item)
#for item in xml.findall('serial'):
# xml.remove(item)
xml = etree.tostring(xml)
# for debugging...
txt_file = open("/tmp/xml_out.xml", "w")
txt_file.write(xml)
txt_file.close()
It appears removing just the 'log' element should be sufficient as this
was the specific error, but i tested more thoroughly with removing
console and serial elements entirely.
The workaround for the error 'libvirtError: Requested operation is not
valid: domain is already running' was to modify dist-
packages/libvirt.py:1097, and completely pass the resume function- seems
like the check of whether the domain is already running or not is
faulty?
Once these changes were made I could launch an instance with host-
passthrough, give it a floating IP and ssh into it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673467
Title:
[ocata] unsupported configuration: CPU mode 'host-model' for aarch64
kvm domain on aarch64 host is not supported by hypervisor
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-compute/+bug/1673467/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673467] Re: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor
I managed to get around this issue: libvirtError: unsupported configuration: logfile not supported in this QEMU binary By modifying the domain xml and removing the child nodes for serial and console. So now there are more reasonable errors for cpu-modes none and host- model none: https://pastebin.canonical.com/192075/ host-model: https://pastebin.canonical.com/192074/ however, host-passthrough also does not work: https://pastebin.canonical.com/192073/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673467 Title: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1673467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697610] Re: logfile not supported in this QEMU binary
Sorry, it was intended for this bug - the idea was to double-check these other modes on x86 for xenial ocata just to ensure we didn't get the same errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697610 Title: logfile not supported in this QEMU binary To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1697610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697610] Re: logfile not supported in this QEMU binary
I've tested this on x86 (xenial ocata) - cpu-mode "none" works, as expected. Neither host-model nor host-passthrough work - the error how ever is not the same - in fact the xml to create the instance doesn't get passed through at all. It is a generic openstack instance creation error. Error creating server: xenial-SERVERNAME Error creating server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697610 Title: logfile not supported in this QEMU binary To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1697610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697610] Re: logfile not supported in this QEMU binary
Deploying instances works in newton - with debug enabled we can see that there is no "log file=" passed in the xml https://pastebin.canonical.com/190844/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697610 Title: logfile not supported in this QEMU binary To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1697610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673467] Re: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor
@paelzer #27 - yes the data was a follow up to #21 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673467 Title: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1673467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697610] Re: logfile not supported in this QEMU binary
When set debug=False, I still get the xml output and the error "logfile not supported in this QEMU binary" so the debug switch is not relevant -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697610 Title: logfile not supported in this QEMU binary To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1697610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618463] Re: udev race condition with qeth device and bridge_role
Hi Brian, I have tested "s390-tools 1.34.0-0ubuntu8.3" in Xenial and can confirm it fixes the bug in Xenial. I am not currently able to test in Yakkety or Zesty Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618463 Title: udev race condition with qeth device and bridge_role To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1618463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673992] Re: init-premount/sysconfig_hardware does not online all DASDs in primary VG - drops to busybox initramfs prompt
** Description changed:
Unsure if this is an initfs-tools issue, or s390-tools, or other?
Linux s4lpb 4.4.0-67-generic #88-Ubuntu SMP Wed Mar 8 16:39:07 UTC 2017
s390x s390x s390x GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial
iibusybox-initramfs1:1.22.0-15ubuntu1
iiinitramfs-tools 0.122ubuntu8.8
iiinitramfs-tools-bin 0.122ubuntu8.8
iiinitramfs-tools-core 0.122ubuntu8.8
iilibklibc 2.0.4-8ubuntu1.16.04.3
ii s390-tools 1.34.0-0ubuntu8.3
Brief description:
I have an s390x LPAR with multiple DASD disks in the 'system' VG -
kernel param specifies root=/dev/mapper/system-root. After preseeding,
and rebooting once, the system drops to BusyBox initramfs prompt, after
errors:
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... lvm
etad is not active yet, using direct activation during sysinit
Couldn't find device with uuid VudDPr-jSTm-ekaq-bWf7-xnVX-uFAd-lHUlfU.
Couldn't find device with uuid ySbAlW-I9M5-UV60-oHF3-uwAu-iXkH-H7zwPB.
Refusing activation of partial LV system/root. Use '--activationmode partial'
to override.
lvmetad is not active yet, using direct activation during sysinit
Couldn't find device with uuid VudDPr-jSTm-ekaq-bWf7-xnVX-uFAd-lHUlfU.
Couldn't find device with uuid ySbAlW-I9M5-UV60-oHF3-uwAu-iXkH-H7zwPB.
done.
Begin: Running /scripts/local-premount ... done.
Begin: Waiting for root file system ...
Begin: Running /scripts/local-block ... lvmetad is not active yet, using direc
t activation during sysinit
Couldn't find device with uuid VudDPr-jSTm-ekaq-bWf7-xnVX-uFAd-lHUlfU.
Couldn't find device with uuid ySbAlW-I9M5-UV60-oHF3-uwAu-iXkH-H7zwPB.
Running vgchange -ay at this point just causes the same error - the DASD
disks still have not been brought online.
+ To replicate:
+
+ Create a volume group with 2 DASDS, e.g. /dev/dasda and /dev/dasdb.
+ Create a logical volume which you will mount as root, using slightly less
space than is available on the first drive - then attempt to reboot a few times.
+
init-premount/sysconfig_hardware script brings the first disk in the VG
online - then /scripts/local-top/lvm2 tries to online the LV/VG. This
fails and causes the above error, as the DASD's have not been brought
online by init-premount. If the VG only contains one root disk then the
other/extra DASDS are brought online later which is fine, but in this
situation to boot the system I need all the PVs in the root VG to be
brought online by init-premount (or something else before the initfs
lvm2 scripts).
The preseed uses d-i partman to create LVM on the primary disk. Other
DASDs are added manually by a script using dasdfmt, fdasd, chzdev.
Validated workaround:
Create a script, e.g.
/usr/share/initramfs-tools/scripts/init-premout/online_all_dasds
containing:
echo 1 > /sys/bus/ccw/devices/${DASD_ID}/online
and then:
update-initramfs -u
All DASDS in the system VG are brought online by initramfs, allowing the
lvm2 scripts in initramfs to work - I can then reboot the LPAR
successfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673992
Title:
init-premount/sysconfig_hardware does not online all DASDs in primary
VG - drops to busybox initramfs prompt
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1673992/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673992] Re: init-premount/sysconfig_hardware does not online all DASDs in primary VG - drops to busybox initramfs prompt
** Description changed:
Unsure if this is an initfs-tools issue, or s390-tools, or other?
Linux s4lpb 4.4.0-67-generic #88-Ubuntu SMP Wed Mar 8 16:39:07 UTC 2017
s390x s390x s390x GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial
-
iibusybox-initramfs1:1.22.0-15ubuntu1
iiinitramfs-tools 0.122ubuntu8.8
iiinitramfs-tools-bin 0.122ubuntu8.8
iiinitramfs-tools-core 0.122ubuntu8.8
iilibklibc 2.0.4-8ubuntu1.16.04.3
ii s390-tools 1.34.0-0ubuntu8.3
Brief description:
I have an s390x LPAR with multiple DASD disks in the 'system' VG -
kernel param specifies root=/dev/mapper/system-root. After preseeding,
and rebooting once, the system drops to BusyBox initramfs prompt, after
errors:
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... lvm
etad is not active yet, using direct activation during sysinit
Couldn't find device with uuid VudDPr-jSTm-ekaq-bWf7-xnVX-uFAd-lHUlfU.
Couldn't find device with uuid ySbAlW-I9M5-UV60-oHF3-uwAu-iXkH-H7zwPB.
Refusing activation of partial LV system/root. Use '--activationmode partial'
to override.
lvmetad is not active yet, using direct activation during sysinit
Couldn't find device with uuid VudDPr-jSTm-ekaq-bWf7-xnVX-uFAd-lHUlfU.
Couldn't find device with uuid ySbAlW-I9M5-UV60-oHF3-uwAu-iXkH-H7zwPB.
done.
Begin: Running /scripts/local-premount ... done.
- Begin: Waiting for root file system ...
+ Begin: Waiting for root file system ...
Begin: Running /scripts/local-block ... lvmetad is not active yet, using direc
t activation during sysinit
Couldn't find device with uuid VudDPr-jSTm-ekaq-bWf7-xnVX-uFAd-lHUlfU.
Couldn't find device with uuid ySbAlW-I9M5-UV60-oHF3-uwAu-iXkH-H7zwPB.
Running vgchange -ay at this point just causes the same error - the DASD
disks still have not been brought online.
init-premount/sysconfig_hardware script brings the first disk in the VG
online - then /scripts/local-top/lvm2 tries to online the LV/VG. This
fails and causes the above error, as the DASD's have not been brought
online by init-premount. If the VG only contains one root disk then the
- DASDS are brought online later, but in this situation to boot the system
- I need all the PVs in the root LV to be brought online.
+ other/extra DASDS are brought online later which is fine, but in this
+ situation to boot the system I need all the PVs in the root VG to be
+ brought online by init-premount (or something else before the initfs
+ lvm2 scripts).
The preseed uses d-i partman to create LVM on the primary disk. Other
DASDs are added manually by a script using dasdfmt, fdasd, chzdev.
Validated workaround:
Create a script, e.g.
- /usr/share/initramfs-tools/scripts/init-premout/online_all_dasds
+ /usr/share/initramfs-tools/scripts/init-premout/online_all_dasds
containing:
- echo 1 > /sys/bus/ccw/devices/${DASD_ID}/online
+ echo 1 > /sys/bus/ccw/devices/${DASD_ID}/online
- and then:
-
- update-initramfs -u
+ and then:
+ update-initramfs -u
- All DASDS in the system VG are brought online by initramfs, allowing the lvm2
scripts in initramfs to work - I can then reboot the LPAR successfully.
+ All DASDS in the system VG are brought online by initramfs, allowing the
+ lvm2 scripts in initramfs to work - I can then reboot the LPAR
+ successfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673992
Title:
init-premount/sysconfig_hardware does not online all DASDs in primary
VG - drops to busybox initramfs prompt
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1673992/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673992] [NEW] init-premount/sysconfig_hardware does not online all DASDs in primary VG - drops to busybox initramfs prompt
Public bug reported:
Unsure if this is an initfs-tools issue, or s390-tools, or other?
Linux s4lpb 4.4.0-67-generic #88-Ubuntu SMP Wed Mar 8 16:39:07 UTC 2017
s390x s390x s390x GNU/Linux
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename: xenial
ii busybox-initramfs1:1.22.0-15ubuntu1
ii initramfs-tools 0.122ubuntu8.8
ii initramfs-tools-bin 0.122ubuntu8.8
ii initramfs-tools-core 0.122ubuntu8.8
ii libklibc 2.0.4-8ubuntu1.16.04.3
ii s390-tools 1.34.0-0ubuntu8.3
Brief description:
I have an s390x LPAR with multiple DASD disks in the 'system' VG -
kernel param specifies root=/dev/mapper/system-root. After preseeding,
and rebooting once, the system drops to BusyBox initramfs prompt, after
errors:
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... lvm
etad is not active yet, using direct activation during sysinit
Couldn't find device with uuid VudDPr-jSTm-ekaq-bWf7-xnVX-uFAd-lHUlfU.
Couldn't find device with uuid ySbAlW-I9M5-UV60-oHF3-uwAu-iXkH-H7zwPB.
Refusing activation of partial LV system/root. Use '--activationmode partial'
to override.
lvmetad is not active yet, using direct activation during sysinit
Couldn't find device with uuid VudDPr-jSTm-ekaq-bWf7-xnVX-uFAd-lHUlfU.
Couldn't find device with uuid ySbAlW-I9M5-UV60-oHF3-uwAu-iXkH-H7zwPB.
done.
Begin: Running /scripts/local-premount ... done.
Begin: Waiting for root file system ...
Begin: Running /scripts/local-block ... lvmetad is not active yet, using direc
t activation during sysinit
Couldn't find device with uuid VudDPr-jSTm-ekaq-bWf7-xnVX-uFAd-lHUlfU.
Couldn't find device with uuid ySbAlW-I9M5-UV60-oHF3-uwAu-iXkH-H7zwPB.
Running vgchange -ay at this point just causes the same error - the DASD
disks still have not been brought online.
init-premount/sysconfig_hardware script brings the first disk in the VG
online - then /scripts/local-top/lvm2 tries to online the LV/VG. This
fails and causes the above error, as the DASD's have not been brought
online by init-premount. If the VG only contains one root disk then the
DASDS are brought online later, but in this situation to boot the system
I need all the PVs in the root LV to be brought online.
The preseed uses d-i partman to create LVM on the primary disk. Other
DASDs are added manually by a script using dasdfmt, fdasd, chzdev.
Validated workaround:
Create a script, e.g.
/usr/share/initramfs-tools/scripts/init-premout/online_all_dasds
containing:
echo 1 > /sys/bus/ccw/devices/${DASD_ID}/online
and then:
update-initramfs -u
All DASDS in the system VG are brought online by initramfs, allowing the lvm2
scripts in initramfs to work - I can then reboot the LPAR successfully.
** Affects: initramfs-tools
Importance: Undecided
Status: New
** Affects: s390-dasd (Ubuntu)
Importance: Undecided
Status: New
** Tags: s390x uosci
** Also affects: initramfs-tools
Importance: Undecided
Status: New
** Package changed: initramfs-tools (Ubuntu) => s390-dasd (Ubuntu)
** Tags added: s390x uosci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673992
Title:
init-premount/sysconfig_hardware does not online all DASDs in primary
VG - drops to busybox initramfs prompt
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1673992/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655224] Re: add-machine ssh:user@$IP fails if $IP is associated with lxdbr0
** Package changed: juju (Ubuntu) => juju -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655224 Title: add-machine ssh:user@$IP fails if $IP is associated with lxdbr0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1655224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655224] [NEW] add-machine ssh:user@$IP fails if $IP is associated with lxdbr0
Public bug reported: Juju 2.0.2 Ubuntu 16.04 arch s390x bootstrapped with manual provider (controller is s390x) When add-machine is executed against a host via IP, e.g. juju add-machine ssh:ubuntu@10.13.3.10 If the ip specified is associated with a bridge interface named lxdbr0, the machine state will be stuck in pending state 1 pending 10.13.3.10 manual:10.13.3.10xenial 2017-01-10 04:42:47 DEBUG juju.worker.apicaller connect.go:99 connecting with current password 2017-01-10 04:42:47 DEBUG juju.worker.apicaller connect.go:139 failed to connect 2017-01-10 04:42:47 DEBUG juju.worker.dependency engine.go:492 "api-caller" manifold worker stopped: cannot open api: validating info for opening an API connection: missing addresses not valid 2017-01-10 04:42:47 ERROR juju.worker.dependency engine.go:539 "api-caller" manifold worker returned unexpected error: cannot open api: validating info for opening an API connection: missing addresses not valid 2017-01-10 04:42:50 DEBUG juju.worker.apicaller connect.go:99 connecting with current password full log: http://paste.ubuntu.com/23774484/ If the interface is renamed (to, e.g. "notlxdbr0") and the old bridge is removed (brctl delbr lxdbr0) and the same add-machine command is executed, the agent will start: 2 started 10.13.3.10 manual:10.13.3.10xenial http://paste.ubuntu.com/23774518/ ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Tags: juju lxd manual-provider -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655224 Title: add-machine ssh:user@$IP fails if $IP is associated with lxdbr0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1655224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654448] [NEW] XPS 13 9360, Realtek ALC3246, Headphone audio hiss
Public bug reported: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example ** Affects: alsa-driver (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/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618463] Re: udev race condition with qeth device and bridge_role
** Tags added: uosci -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618463 Title: udev race condition with qeth device and bridge_role To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1618463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618463] [NEW] udev race condition with qeth device and bridge_role
Public bug reported:
Attempting to set bridge_role = primary with the following command in
preseed:
in-target chzdev --no-root-update -pVe c003 bridge_role=primary;
...works, and generates the following udev rule for this device:
https://pastebin.canonical.com/164271/
However, after reboot:
systemd-udevd[2634]: error opening
ATTR{/sys/devices/qeth/0.0.c003/bridge_role} for writing: Permission
denied
More logging:
https://pastebin.canonical.com/164272/
after the system has booted, we are able to write to the file and set
bridge_role to primary:
root@10-13-3-10:/var/log# cat /sys/devices/qeth/0.0.c003/bridge_role
none
root@10-13-3-10:/var/log# echo primary > /sys/devices/qeth/0.0.c003/bridge_role
root@10-13-3-10:/var/log# cat /sys/devices/qeth/0.0.c003/bridge_role
primary
** Affects: s390-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: s390x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618463
Title:
udev race condition with qeth device and bridge_role
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1618463/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 763688] Re: [915GM] S-video output doesn't work in Natty (i386)
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/921636 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/763688 Title: [915GM] S-video output doesn't work in Natty (i386) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/763688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 892770] Re: tv-out on s-video port is broken on ubuntu 11.10
*** This bug is a duplicate of bug 921636 *** https://bugs.launchpad.net/bugs/921636 ** This bug has been marked a duplicate of bug 921636 intel GM965 (X3100) no TV-Out (S-Video) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/892770 Title: tv-out on s-video port is broken on ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/892770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921636] Re: intel GM965 (X3100) no TV-Out (S-Video)
I have the same problem. TV-out (svideo) worked in 10.04, upgraded to 12.04 and now everything works as before except for the picture appearing, just as described above (also an Intel GM965 integrated video card). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921636 Title: intel GM965 (X3100) no TV-Out (S-Video) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/921636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
