Same behavior in 20.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721648
Title:
lsmem -v replaced with -V
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-syste
I redeployed the system where this failures was original observed and recreated
the issue.
Running 'sudo vgck --updatemetadata s5lp8-vg' did work around this bug, when
run after the upgrade but prior to the reboot.
Here is the vgdisplay output requested by Steve:
ubuntu@s5lp8:~$ sudo vgdisplay
Solutions QA has tested Cloud-init 20.2-45-g5f7825e2 within our CI
testing of Foundation Cloud Builds on Bionic. Artifacts for all test
runs are available by following the links on the test plan page here:
https://solutions.qa.canonical.com/#/testplans/testplaninstance/06ff68c9-dd19-4470-98d5-a4757
Solutions-QA completed validation using python3-curtin_20.1-2-g42a9667f from
maas to deploy kubernetes on focal. Deployment artifacts are available here:
https://solutions.qa.canonical.com/#/testplans/testplaninstance/5c3995e7-6595-414a-9894-885fb0f54748
--
You received this bug notification bec
Solutions-QA has completed our validation using
python3-curtin_20.1-2-g42a9667f-0ubuntu1~18.04.1.
Deployment artifacts are available here:
https://solutions.qa.canonical.com/#/testplans/testplaninstance/5c3995e7-6595-414a-9894-885fb0f54748
--
You received this bug notification because you are a
** Tags added: s390x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874138
Title:
Installing package s390-tools-zkey reports cryptsetup: ERROR: Couldn't
resolve device
To manage notifications abo
Public bug reported:
Output from installing the s390-tools-zkey shows the following error:
cryptsetup: ERROR: Couldn't resolve device
UUID=ff81d97b-e273-4ec3-8e82-a2c0aa4e7e20
It's unclear if this ERROR has caused a problem, as the package
completes it's installation with an exit code of ze
Public bug reported:
Executing lsluns on an LPAR results in many error messages reporting
/sbin/udevsettle No such file or directory.
$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04
$ apt-cache policy s390-tools
s390-tools:
Installed: 2.12.0-0ubuntu3
Candidate: 2.12.
Solutions-QA has completed validation of this curtin SRU version.
Deployment artifacts are available here:
https://solutions.qa.canonical.com/#/testplans/testplaninstance/e303f452-9467-4f55-9eec-49dd3b6aeff6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Solutions QA has completed our Bionic based Openstack Foundation Cloud
Build deployments and is happy to report no issues with
19.4-33-gbb4131a2-0ubuntu1~18.04.1.
Test run results and logs can be found at the following URL:
https://solutions.qa.canonical.com/#/qa/testRun/ecd43d34-2466-40aa-b8d2-66
Solutions QA has completed a Openstack Stein Bionic Foundation Cloud Build. All
test results are available at:
https://solutions.qa.canonical.com/#/qa/testRun/b1986996-1ac5-4b6e-91d0-2729eb37ee28
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Solutions QA MAAS Bionic install log.
** Attachment added: "bionic_maas_install.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1844334/+attachment/5291617/+files/bionic_maas_install.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Solutions QA MAAS Xenial install log.
** Attachment added: "xenial_maas_install.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1844334/+attachment/5291616/+files/xenial_maas_install.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Attachment added: "Solutions QA bionic maas install log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1841099/+attachment/5287825/+files/bionic_maas_install.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Solutions QA xenial MAAS install log
** Attachment added: "xenial_maas_install.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1841099/+attachment/5287824/+files/xenial_maas_install.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I've also verified Solutions QA tests succeed with the proposed Bionic
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784665
Title:
bcache: bch_allocator_thread(): hung task timeout
To mana
Passing run details from Solutions QA using
python3-curtin_19.1-7-g37a7a0f4-0ubuntu1~18.04.1 with
maas_2.5.3-7533-g65952b418-0ubuntu1~18.04.1 during a hyper-converged Openstack
cloud deployment are available at:
https://solutions.qa.canonical.com/#/qa/testRun/4a79a1f5-a0d9-4d77-982d-ae1b78462f97
This does not reproduce when the full proposed system upgrade is
configured in curtin_userdata:
+apt:
+ sources:
+proposed.list:
+ source: deb $MIRROR {{release}}-proposed main universe multiverse
+
+system_upgrade:
+ enabled: True
Also observed no issues when first deploying stable B
Successful Xenail Maas deployment log with full proposed system upgrade
set to True.
ubuntu@hoskins:~$ apt-cache policy cloud-init
cloud-init:
Installed: 19.1-1-gbaa47854-0ubuntu1~16.04.1
Candidate: 19.1-1-gbaa47854-0ubuntu1~16.04.1
Version table:
*** 19.1-1-gbaa47854-0ubuntu1~16.04.1 500
Successful Bionic Maas deployment log with full proposed system upgrade
set to True.
$ apt-cache policy cloud-init
cloud-init:
Installed: 19.1-1-gbaa47854-0ubuntu1~18.04.1
Candidate: 19.1-1-gbaa47854-0ubuntu1~18.04.1
Version table:
*** 19.1-1-gbaa47854-0ubuntu1~18.04.1 500
500 http:
When deploying from maas, using this proposed version of cloud-init, the
deployment fails. More detail is available in
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1830129
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
Deployment fails when maas curtin_userdata is set to install cloud-init
from proposed.
ubuntu@maas:~$ diff -u curtin_userdata-20190522.orig
/etc/maas/preseeds/curtin_userdata
--- curtin_userdata-20190522.orig 2019-05-22 16:54:35.745391284 +
+++ /etc/maas/preseeds/c
** Attachment added: "hoskins_console.proposed_cloud-init"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1830129/+attachment/5265831/+files/hoskins_console.proposed_cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I was unable to reproduce the process faults after reinstalling the
released version of 19.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824004
Title:
apt install of s390-tools-zkey triggers ke
I did not run into this again, when retesting the released version of
19.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824440
Title:
snap.lxd.daemon.service reports unexpected response type 6
This still occurs in 19.04
** Summary changed:
- Z LPAR 17.10 install: ipv6 link-local address presented to user
+ Z LPAR install: ipv6 link-local address presented to user
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Public bug reported:
ubuntu@s5lp8:~$ lsb_release -rd
Description:Ubuntu Disco Dingo (development branch)
Release:19.04
ubuntu@s5lp8:~$ apt-cache policy s390-tools-zkey
s390-tools-zkey:
Installed: 2.8.0-0ubuntu5
Candidate: 2.8.0-0ubuntu5
Version table:
*** 2.8.0-0ubuntu5 500
** Tags added: cdo-qa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800526
Title:
After Upgrading from 18.04.1 to 18.10 librdb1 can not be installed
To manage notifications about this bug go to:
h
It appears that librados2 12.2.7 is available for Bionic in
http://us.ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/main
/binary-s390x/ but only version 12.2.4 is available for Cosmic.
A workaround is to first remove librados2 version 12.2.7.
ubuntu@s5lp8:~/cdoqa-system-tests$ sudo apt-get p
Public bug reported:
This issue was discovered while attempting to setup KVM on s390 after
upgrading an 18.04.1 server to 18.10
librbd1 : Depends: librados2 (= 12.2.4-0ubuntu1.1build1) but
12.2.7-0ubuntu0.18.04.1 is to be installed
It appears to be s390 specific, as I was not able to reproduce t
KVM and metal install logs from the CDOQA test environment.
Both Xenial and Bionic logs are included.
** Attachment added: "cdoqa_LTS_metal_and_kvm_install_logs.tgz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1795953/+attachment/5205646/+files/cdoqa_LTS_metal_and_kvm_install_lo
Public bug reported:
Regression of bug 1683507
With s390-tools-2.6.0-0ubuntu7 znetconf will return an error when passed
informational request options such as --version or --help when
/sys/bus/ccwgroup does not exist.
ubuntu@cosmicKVM:~$ apt-cache policy s390-tools
s390-tools:
Installed: 2.6.0
The issue still exists in 18.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616593
Title:
ziomon: Packaging needs to handle blktrace dependency
To manage notifications about this bug go to:
htt
This still occurs in 18.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720836
Title:
Z LPAR 17.10 install: ipv6 link-local address presented to user
To manage notifications about this bug go to
Public bug reported:
With the LXD packaging switch to snaps, upgrades will fail if access to
the snap store is not available. This is an issue for servers in a
controlled environment. Obviously, firewalls or proxies can be updated
to allow access but no mention is made of this new requirement in t
Solutions QA install logs on Bionic.
** Attachment added: "solutions_QA_cloud-init_install_logs_bionic.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1777912/+attachment/5167830/+files/solutions_QA_cloud-init_install_logs_bionic.tar.gz
--
You received this bug notification
Solutions QA cloud-init logs using maas with juju to scale out an
application.
** Attachment added: "solutions_QA_cloud-init_install_logs.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1777912/+attachment/5167791/+files/solutions_QA_cloud-init_install_logs.tar.gz
--
You re
Solutions QA validation performed with Xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777912
Title:
sru cloud-init (18.2-4-g05926e48-0ubuntu1) to (18.3-9ubuntu1)
To manage notifications abo
MAAS deploy SRU verification
** Attachment added: "cloud-init_SRU_bug_1767412_maas_deploy.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412/+attachment/5137460/+files/cloud-init_SRU_bug_1767412_maas_deploy.log
--
You received this bug notification because you are a membe
Public bug reported:
Selecting previously unselected package python-shade.
Preparing to unpack .../python-shade_1.7.0-2~cloud0_all.deb ...
Unpacking python-shade (1.7.0-2~cloud0) ...
Preparing to unpack .../python3-shade_1.7.0-2~cloud0_all.deb ...
Unpacking python3-shade (1.7.0-2~cloud0) ...
dpkg:
hmm, the bug I was trying to report on has now been fixed and I've re-installed
that test system.
Without the crash from the original bug I don't get a report just 'No pending
crash reports'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
The upgrade was triggered with:
sudo do-release-upgrade -d
Also attached the console upgrade log.
** Attachment added: "upgrade.log"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1766787/+attachment/5127179/+files/upgrade.log
** Changed in: debian-installer (Ubuntu)
** Attachment added: "_usr_bin_apport-bug.0.crash"
https://bugs.launchpad.net/apport/+bug/1766794/+attachment/5127180/+files/_usr_bin_apport-bug.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
After an upgrade from 16.04 to 18.04 deb-src entries in
/etc/apt/sources.list are still set to xenial rather than bionic.
These lines are commented out by default so it's not an issue until the
source repo is enabled. For instance a script that automates enabling
source repos
apport information
** Tags added: apport-collected
** Description changed:
Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in:
Errors were encountered while processing:
initramfs-tools
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an
erro
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1766727/+attachment/5126760/+files/ProcCpuinfoMinimal.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of U
Public bug reported:
Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in:
Errors were encountered while processing:
initramfs-tools
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error
code (1)
Could not install the upgrades
The upgrade has aborte
** Attachment added: "upgrade.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1766727/+attachment/5126731/+files/upgrade.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
$ cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS"
NAME="Ubuntu"
VERSION="16.04.4 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.4 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/";
SUPPORT_URL
Possibly a reproduction but in this case Xenial is deployed and rsyslog
shows the kernel upgraded to 4.4.0-119-generic. These are automated runs
and we don't have the console output to confirm a kernel panic.
** Attachment added: "rsyslog.swoobat_run_11e7681c-d91b-44dc-adb6-143acbb897c1"
https
MAAS kvm deploy SRU verification for xenial
** Attachment added: "maas_pod_kvm_install.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1747059/+attachment/5059911/+files/maas_pod_kvm_install.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
MAAS bare metal deploy SRU verification for xenial
** Attachment added: "maas_hp_gen9_install.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1747059/+attachment/5059910/+files/maas_hp_gen9_install.log
--
You received this bug notification because you are a member of Ubuntu
Bu
This bug falls under the Canonical Cloud Engineering service-level
agreement (SLA) process, as a field critical bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744062
Title:
L3 HA: multiple agen
This bug certainly needs to be treated as urgent. It's being tracked as
part of the critical SLA process and blocks deployments of foundation
bundles in the QA lab and in the field.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
This bug falls under the Canonical Cloud Engineering service-level
agreement (SLA) process, as a field critical bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731595
Title:
L3 HA: multiple agen
This is related to bug SRU bug 1707999.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735015
Title:
FTBFS: ipxe on zesty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
Public bug reported:
ipxe inside a zesty LXD hosted on xenial 16.04.3 LTS, fails to build
from source.
Reproduction steps:
sudo apt-get build-dep ipxe
apt-get source ipxe
cd ipxe-1.0.0+git-20150424.a25a16d/
cd src
make
console output log is attached.
** Affects: ipxe (Ubuntu)
Importance: U
Public bug reported:
The -v options is no longer valid, as -V has replaced it.
This is not really a big issue but it seem odd as this is a shift away from the
standard -v option used by most of the other utilities in the s390-tools
package and forces modification of tests and tools that collect
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721399/+attachment/4962372/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721399
Title:
Z LPAR
** Attachment added: "s5lp7_installer_logs.tgz"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721399/+attachment/4962373/+files/s5lp7_installer_logs.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Attachment added: "systemd-resolve.status.out"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721399/+attachment/4962371/+files/systemd-resolve.status.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
The DNS server provided to the debian-installer is not configured
ubuntu@s5lp7:/var/log/installer$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10
Codename: artful
ubu
This is still the case with 17.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683886
Title:
Z system 17.04 guided partitioning warns about swap
To manage notifications about this bug go to:
http
I did change debconf to medium, due to the system being on a vlan and
bug 1635024.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683907
Title:
Z system installation of 17.04 has duplicate swap file
I did change debconf to medium, due to the system being on a vlan and
bug 1635024.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683871
Title:
Z system guided partitioning, with separate paritions
Public bug reported:
ubuntu@s5lp7:~$ lsb_release -rd
Description:Ubuntu 17.04
Release:17.04
ubuntu@s5lp7:~$ apt-cache policy s390-tools
s390-tools:
Installed: 1.37.0-0ubuntu3
Candidate: 1.37.0-0ubuntu3
Version table:
*** 1.37.0-0ubuntu3 500
500 http://us.ports.ubuntu.c
Public bug reported:
do-release-upgrade was performed on a zKVM guest instance, upgrading
Yakkety to Zesty. After reboot the system was no longer available on the
network. The interface name changed from eth0 to enc1. The following
change was required:
ubuntu@s5lp6-gen01:~$ diff interfaces.ori /e
Public bug reported:
When installing a Z System with 17.04 (Zesty) two dialogues related to
swap file size are presented. The second seems redundant and although it
asks for a maximum percentage of free space to be entered, there is no
input field. Please see the attached screen shots.
** Affects
Public bug reported:
During a Z system installation of 17.04 (Zesty) the guided partitioning
is selected but does not define a partition for swap. This results in a
warning about a missing swap partition. If the user chooses guided it's
expected that a layout will be used that does not result in w
Public bug reported:
During an Z system installation of 17.04 (Zesty) selecting the guided
partitioning options result in a partitioning error, about too many
partitions. please see the attached screen shots.
** Affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
Public bug reported:
While installing a Z LPAR with 17.04 (Zesty), non-auto network
configuration is selected and when prompted for the system IP address an
IPv4 address is provided by the user. Once the installation process
reaches the 'Continue installation remotely using SSH' phase, an IPv6
add
** Attachment added: "install_console.out"
https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1683540/+attachment/4863929/+files/install_console.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 17.04
Release:17.04
$ apt-cache policy s390-tools
s390-tools:
Installed: 1.37.0-0ubuntu3
Candidate: 1.37.0-0ubuntu3
Version table:
*** 1.37.0-0ubuntu3 500
500 http://us.ports.ubuntu.com/ubuntu-ports zesty/main s3
I applied the patch to /usr/lib/python3/dist-
packages/provisioningserver/refresh/node_info_scripts.py on our failing
maas and restarted maas-regiond.service (sudo systemctl status maas-
regiond.service).
Storage was reported as expected, after re-commission of existing nodes;
I also removed a no
** Summary changed:
- Commission scripts select the wrong nvme device link, then fail to report any
storage
+ Commission scripts select the wrong nvme device link, then fails to report
any storage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Please mark this bug critical, as it blocks all integration testing.
** Description changed:
- Block devices are not discovered on all 7 of our HP ProLiant DL360 Gen9
- servers. These servers are used with daily MAAS testing, so are proven
- to normally commission and deploy. We also experienced
Public bug reported:
An ssh connection to installer@, after starting a manually driven install
of Yakkety to a Z LPAR, can not continue as described to the user in the
interactive console window output because ssh connections are not possible.
When attempting to connect an ssh client will give
Public bug reported:
$ lsb_release -rd
Description:Ubuntu Yakkety Yak (development branch)
Release:16.10
$ apt-cache policy s390-tools
s390-tools:
Installed: 1.36.1-0ubuntu2
Candidate: 1.36.1-0ubuntu2
Version table:
*** 1.36.1-0ubuntu2 500
500 http://us.ports.ubuntu.com
Public bug reported:
$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
$ apt-cache policy s390-tools
s390-tools:
Installed: 1.34.0-0ubuntu8.1
Candidate: 1.34.0-0ubuntu8.1
Packaging needs to handle the installation of dependencies.
The unexpected output is shown here:
ubuntu
Public bug reported:
$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
$ apt-cache policy s390-tools
s390-tools:
Installed: 1.34.0-0ubuntu8.1
Candidate: 1.34.0-0ubuntu8.1
When benign options such as --help or --version are passed to ziomon_util the
expected output is printed bu
Public bug reported:
$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
$ apt-cache policy s390-tools
s390-tools:
Installed: 1.34.0-0ubuntu8.1
Candidate: 1.34.0-0ubuntu8.1
Packaging needs to handle the installation of dependencies.
The unexpected output is shown here:
ubuntu
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
$ apt-cache policy s390-tools
s390-tools:
Installed: 1.34.0-0ubuntu8.1
Candidate: 1.34.0-0ubuntu8.1
When benign options such as --help or --version are passed to a command that is
installed with wo
I still get the same failure:
cdoqa@maas-node-1:~$ maas maas sshkeys create key='ssh-rsa PUB_KEY_TEXT'
{"key": ["Invalid SSH public key: 'PosixPath' object has no attribute 'path'"]}
Looking at the installed code it appears one use of keypath.path was
changed (i.e. line 139) but a second was not (
** Tags added: cdoqa-blocker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604147
Title:
pathlib.Path.path attribute has disappeared
To manage notifications about this bug go to:
https://bugs.laun
What can be done to further investigate this bug? It causes frequent
MAAS deployment failures in our environment. I believe this bug should
be critical or high, since it blocks Landscape Autopilot from
successfully installing an Openstack cloud.
--
You received this bug notification because you a
For comparison here is the console log after switching back to the
Trusty kernel.
** Attachment added: "console_log_with_trusty_kernel_grub_prompt.out"
https://bugs.launchpad.net/maas-images/+bug/1532935/+attachment/4680168/+files/console_log_with_trusty_kernel_grub_prompt.out
--
You receive
When switching to the Xenial kernel the Trusty installation fails even
earlier, complaining about 'unrecognised disk label' during the
installation phase of the deploy.
** Attachment added: "console_log_with_xenial_kernel_cloud_init_fails.out"
https://bugs.launchpad.net/maas-images/+bug/153293
Typing 'normal' at the prompt does boot the system.
So far a trusty kernel has been used during install. I'll see if there
is a hwe-xenial kernel available through MaaS, although this issue is
intermittent, so all I could do is run with it for awhile and see if the
issue reproduces.
--
You recei
Public bug reported:
Attempted to upgrade Trusty from 1.5 to 1.9.
Please see the output below.
jenkins@juju-qa-maas-server-1:~$ sudo apt-get upgrade maas
[sudo] password for jenkins:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgra
Public bug reported:
Having tried to install 12.04 without success (and rerported installer
problems) I tried to reinstall 11.10.
After successfully installing nearly all the software including all
downloads, when nearly finishing full installation, and finally starting
to install system, the ins
Public bug reported:
DVD boots OK. Then gives install options. Chose 1st option (keep data
files). Get nessage saying partition needs to be larger. Hit "Go Back"
button. screen message shows "Scanning disk". When finished, get error
message showing unrecoverable error and sends a bug report.
91 matches
Mail list logo
