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:
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
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
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
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
** 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
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
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:
$
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
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
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.
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
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.
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
@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
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
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
@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
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
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:
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.
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 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
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.
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
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
ATTRIBUTE
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
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
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
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
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
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
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
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
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
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
** 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
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:
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 -
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
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.
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:
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)
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:
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.
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
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.
@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
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
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.
** 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
** 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
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
** 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
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
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
** 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:
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:
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,
*** 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/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
61 matches
Mail list logo
