I setup a test environment to re-run the recreation script I attached
above while using the fix from xenial-proposed.
What I found was that the fix helps but is not perfect.
While the UCA repo is in the hourly update time window, the apt-get
update can still leave the user in the error case
[Impact]
An apt update of an apt repository that does not use InRelease during the time
it is being updated can cause the gpg file to not be downloaded and updated.
This makes the packages from the repository be unable to be authenticated.
The Ubuntu Cloud Archive is one of the archives that
This upstream patch needs to be backported to the 1.2 series for Xenial.
If left unfixed in Xenial it opens a timing window every hour with
Ubuntu Cloud Archive where users can fall into the "Some packages could
not be authenticated" state without Release.gpg that is described in the
description.
** Attachment added: "Recreation script"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1657440/+attachment/4814822/+files/recreate.py
** Changed in: apt (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have verified on Xenial ppc64le with a Ceph-ansible deployment of the
xenial-proposed 10.2.5. The ceph monitor starts on reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646583
Title:
Ceph
Thanks James.
I did a ceph-ansible cluster deploy using the SRU PPA on Xenial.
I rebooted the ceph monitor node and the ceph mon daemon started on reboot.
I tried out these commands on an OSD node and the OSDs were all stopped/started:
systemctl stop ceph-osd\*.service ceph-osd.target
systemctl
I am very new to debian package rules but I suspect the reason the units are
enabled in the ceph.com package and not in the Ubuntu package is that upstream
debian rules has:
dh_systemd_enable
at [1], whereas Ubuntu Ceph has:
override_dh_systemd_enable:
## Do not enable services
I installed Ceph 10.2.5 from the SRU PPA, https://launchpad.net
/~openstack-ubuntu-testing/+archive/ubuntu/ceph-sru, on a clean system
and "# systemctl list-units | grep ceph" lists nothing.
As noted in comment 10, an install of Ceph 10.2.5 from Ceph.com gives this
output:
# systemctl list-units
I installed Ceph from the SRU PPA using Ceph ansible and while the ceph-
mon target file is there the Ceph monitor does not auto-start on reboot.
I've installed 10.2.5 from ceph.com apt repo simply using apt-get install and
these are the units listed:
# systemctl list-units | grep ceph
I reproduced this again as well and it seems the OSDs do restart OK on
reboot while the Mon does not. I must have been confused when writing
the bug as I opened it several days after encountering the issue.
Ceph-Ansible does the following to enable the ceph-mon in the init
sequence and it is
I will add that Ceph Ansible v2.0.0 was used to install Ceph from both
the distro apt repo and UCA, both with the same result.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646583
Title:
Ceph mon
Public bug reported:
The ceph monitor and osd daemons do not restart automatically on server
reboot on Xenial.
$ apt-cache policy ceph
ceph:
Installed: 10.2.2-0ubuntu0.16.04.2
Candidate: 10.2.2-0ubuntu0.16.04.2
Version table:
*** 10.2.2-0ubuntu0.16.04.2 500
500
** Also affects: mitaka (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: mitaka (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488111
Title:
Boot from volumes
Public bug reported:
Per [1] ceph-ansible fails when attempting to install Ceph Jewel from
UCA (on Trusty) or from Xenial's default repo.
The fix for [2] needs to be picked up by the downstream Ubuntu packages
and then made available for Xenial updates and on Trusty Mitaka UCA.
[1]
This is purely a Glance bug and can be recreated without Nova in the
picture at all, therefore I do not believe that the bug fix mentioned in
comment 5 will fix this.
See the recreation steps in comment 2. This can be completely
abstracted from Nova. The bug is that Glance v1 allows you to set
This is purely a Glance bug and can be recreated without Nova in the
picture at all, therefore I do not believe that the bug fix mentioned in
comment 5 will fix this.
See the recreation steps in comment 2. This can be completely
abstracted from Nova. The bug is that Glance v1 allows you to set
This is not fixed and I'm seeing it with a recent version of
stable/kilo.
The description reproduction steps don't accurately reproduce. These
steps do:
# glance --os-image-api-version 1 image-list
++--+-+--+--++
| ID | Name | Disk Format |
I'm going to mention this bug, as I did on #1447193 that I'm using a new
glanceclient:
# glance --version
0.17.1
While I'm adding yet another comment I thought I'd drop in the nova
stack for how this fails spawn in code that uses clone and image
locations.
File
I used slightly different reproduction steps.
# glance --os-image-api-version 1 image-list
++--+-+--+--++
| ID | Name | Disk Format | Container Format | Size | Status |
++--+-+--+--++
I forgot to add that I'm using 0.17.1 client:
# glance --version
0.17.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447193
Title:
Glance client fails with v2 API / Failed validating 'Type' in
20 matches
Mail list logo
