I'm not sure what upgrade log you are referrin to, this is the matching
output from /var/log/apt/term.log:
Log started: 2017-06-23 13:57:41
(Reading database ... ^M(Reading database ... 5%^M(Reading database ...
10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database
...
Public bug reported:
After openvpn has been upgraded automatically today, client VPN
connections are broken, getting no response from the server anymore.
After a restart of the openvpn service on the server, the issue is
fixed. Seen on multiple servers by me and others in #ubuntu-server. From
So will there be a patch for the stable/ocata branch that fixes this
issue? Or would you expect distros to update to a newer release?
** Changed in: python-openstackclient
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This seems to have been solved by
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1561658,
which could be considered a duplicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564451
May want to borrow some bits of what RHEL does for their packaging:
https://raw.githubusercontent.com/lukehinds/bagpipe-bgp-packaging/master
/bagpipe-bgp.spec
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The package is missing the bagpipe-bgp code that the upstream source
installs as a submodule from https://github.com/Orange-OpenSource
/bagpipe-bgp.git. That repo has been merged into the upstream
networking-bagpipe repo only after the Ocata release.
In order to be useable,
Public bug reported:
The config files need to go into /etc/neutron instead of
/usr/etc/neutron.
** Affects: networking-bgpvpn (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The issue appears for OSC version 3.8.1 in Ubuntu Ocata UCA, after pip-
installing OSC 3.9.0 I get the correct error message:
$ osc/bin/openstack extension list --network
HttpException: Service Unavailable (HTTP 503) (Request-ID:
req-f790c8ee-6185-47de-8512-8405dc5e57cd)
** Also affects:
You are correct, the documentation in OpenStack is still wrong, I'll do
a patch for that.
** Also affects: openstack-manuals
Importance: Undecided
Status: New
** Changed in: openstack-manuals
Assignee: (unassigned) => Dr. Jens Rosenboom (j-rosenboom-j)
--
You received this
The dynamic-routing functionality has indeed been split from the main
project into its own package, so the driver name has changed accordingly
starting with the Newton release.
Do you have any more issues after you changed your config?
** Changed in: neutron (Ubuntu)
Status: New =>
Public bug reported:
In https://bugs.launchpad.net/tripleo/+bug/1632538 a new release of
python-rfc3986 was created and added to Newton UCA. However the python-
nova package also needs to depend on the higher version (>= 0.2.2),
otherwise the installation will still be affected by that bug after
Nova released 14.0.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664306
Title:
newton stable SRU releases
To manage notifications about this bug go to:
Upstream says
global-requirements.txt:pecan>=1.0.0,!=1.0.2,!=1.0.3,!=1.0.4 # BSD
upper-constraints.txt:pecan===1.1.2
while python-neutron only has
Depends: python-pecan (>= 1.0.0)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
With neutron=2:9.1.1-0ubuntu1 installed on Xenial with Newton UCA I get:
# neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file
/etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
Traceback (most recent call last):
File "/usr/bin/neutron-db-manage", line
Public bug reported:
The package only depends on
python-oslo.utils (>= 3.3.0)
but with 3.16.0 from Newton UCA installed I get:
# gnocchi-api -h
Traceback (most recent call last):
File "/usr/bin/gnocchi-api", line 6, in
from gnocchi.rest.app import build_wsgi_app
File
How much work would it be to make corresponding packages for Newton UCA?
I've tried to upgrade just openstack-dashboard from ocata-staging for my
newton installation and that doesn't work too well.
Also at least for my setup /var/lib/openstack-dashboard/static/ should
belong to horizon instead
Hmm, strange, I retried with a new instance too, now after adding the
commands that you missed:
# add-apt-repository cloud-archive:newton
# apt update;apt install strongswan neutron-vpn-agent
# mkdir /tmp/test
# ip netns add testns
I can reproduce with the modified command
# ip netns exec
The packages from the ppa fix the issue for me. In order to reproduce,
install neutron-vpn-agent from Newton UCA and run:
# mkdir /tmp/test
# ip netns add testns
# ip netns exec testns neutron-vpn-netns-wrapper --mount_paths
"/var/run:/tmp/test" --cmd "ipsec,status"
2017-02-07 18:17:06.729 17492
This issue still appears when running neutron-vpnaas from Newton UCA on
Xenial, is there a chance to fix it for Xenial, too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587886
Title:
strongswan
Actually, I was installing it onto a UCA Newton deployment on Xenial, as
that is what murano-dashboard 3.0.0 would match, see
https://releases.openstack.org/newton/index.html#horizon-plugins. Also
needs some django package updated in zesty. If we get this issue fixed,
I would hope that
** Also affects: horizon (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/1659570
Title:
Installing murano-dashboard=3.0.0 deletes needed files
To
In the 2.0.0 version this part in the postinst file is commented out:
# (tlbr) Run of collectstatic is required but do not run it until easy
switch for
# for Horizon package will be implemented.
#/usr/share/openstack-dashboard/manage.py collectstatic --clear
--noinput
I
Public bug reported:
The reason is that in the postinst this is called:
/usr/share/openstack-dashboard/manage.py collectstatic --clear --noinput
where the "--clear" options means "delete existing files". The files are
collected into /usr/share/openstack-dashboard/horizon/static/, now sadly
Verified the proposed packages for xenial and yakkety.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632538
Title:
Using
Upstream fix is in https://review.openstack.org/425418, please update,
also for stable/newton UCA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659270
Title:
Startup of murano-cfapi is broken
To
Public bug reported:
There are two issues here:
- /etc/murano/murano-cfapi-paste.ini is missing from the package, needs to be
included from upstream.
- In /etc/init.d/murano-cfapi the config file name is wrong, referencing
murano.conf instead of murano-cfapi.conf.
--- /etc/init.d/murano-cfapi
I've tried to reproduce this on a yakkety cloud instance as well as with
lxc for some time, but sadly with no success. So I'm not sure whether
this is still present in yakkety at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the hint Mike, I must admit that I never looked at that. In
fact it seems like this would be fixed already in spice-html5-0.1.5
dated more than two years ago, but Ubuntu still ships 0.1.4.
** Also affects: spice-html5 (Ubuntu)
Importance: Undecided
Status: New
--
You
Tested with python-oslo.privsep_1.13.0-0ubuntu1.1_all.deb, fix
confirmed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616240
Sorry for the late reply, I have now been able to find the culprit by
selectively removing all the python-*client packages that I had
installed, the error comes from
python-mistralclient-1:2.0.0-3
Checking upstream code, the error also happens with the current
openstackclient and that
Installing valgrind 1:3.12.0~svn20160714-1ubuntu2 from yakkety onto my
xenial machine seems to resolve the issue, too. But probably including
the patch from https://bugs.kde.org/show_bug.cgi?id=353370#c9 will be
easier than doing an update in xenial, right?
--
You received this bug notification
*** This bug is a duplicate of bug 1632538 ***
https://bugs.launchpad.net/bugs/1632538
** This bug has been marked a duplicate of bug 1632538
Using generate_service_certificate and undercloud_public_vip in
undercloud.conf breaks nova
--
You received this bug notification because you are
Public bug reported:
This happens for every command and is nothing a user can fix:
# openstack --version
WARNING: openstackclient.common.utils is deprecated and will be removed after
Jun 2017. Please use osc_lib.utils
openstack 3.2.0
# apt policy python-openstackclient
python-openstackclient:
*** This bug is a duplicate of bug 1224007 ***
https://bugs.launchpad.net/bugs/1224007
** This bug has been marked a duplicate of bug 1224007
mtu not always set properly on bond/vlan interface
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The patch for xenial solves this issue for me, too. How does the
timeline for getting fixed packages look like?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set
*** This bug is a duplicate of bug 1224007 ***
https://bugs.launchpad.net/bugs/1224007
** This bug has been marked a duplicate of bug 1224007
mtu not always set properly on bond/vlan interface
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
On a node with two 10G interfaces, we configure a bond interface from
these two interfaces and then a vlan interface on top of it. The MTU of
these interfaces shall be set to be 1550 instead of the default 1500, so
we have these settings in /etc/network/interfaces.d:
IIUC an upgrade over multiple OpenStack releases in one step is not
supported, at least not by upstream, since the needed DB migrations need
to be performed one at a time. So maybe you will get better results if
you go 2014.1 (Icehouse) -> 2014.2 (Juno) -> 2015.1 (Kilo) -> 8.1.2
(Liberty) -> 9.2.0
So looking at the tags in the oslo.log repo, it seems that
keystone=stable/newton needs to depend on oslo.log>=3.4.0 in order to
work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628883
Title:
There was a patch merged to glance_store that can serve as a workaround:
https://review.openstack.org/373155
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625489
Title:
image.stat() call sometimes
Upstream bug created: http://tracker.ceph.com/issues/17310
** No longer affects: glance (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625489
Title:
image.stat() call sometimes fails
To
Right, after doing a bit more debugging, this looks like a bug in
python-rbd only. Running the following python code, I am seeing the same
errors about 50% of the time:
import rados
import rbd
cluster = rados.Rados(conffile='/etc/ceph/ceph.conf')
cluster.connect()
ioctx =
Public bug reported:
We have a deployment with three controller nodes running glance version
2:12.0.0-0ubuntu2 with a Ceph backend. About 50% of the image download
requests from compute nodes are failing with an error like this:
2016-09-20 07:37:32.014 29606 WARNING glance.location
Public bug reported:
root@jr-x5:~# keystone
The program 'keystone' can be found in the following packages:
* python-keystoneclient
* python3-keystoneclient
Try: apt install
root@jr-x5:~# apt policy python-keystoneclient
python-keystoneclient:
Installed: 1:3.5.0-0ubuntu1~cloud0
Candidate:
Public bug reported:
root@controller-node14:~# systemctl status ipmievd.service
* ipmievd.service - IPMI event daemon
Loaded: loaded (/lib/systemd/system/ipmievd.service; enabled; vendor preset:
enabled)
Active: failed (Result: exit-code) since Tue 2016-08-30 09:22:42 UTC; 1min
55s ago
** Tags added: newton-rc-potential
** Changed in: nova
Status: In Progress => Confirmed
** Changed in: nova
Assignee: Dr. Jens Rosenboom (j-rosenboom-j) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Under some conditions, the issue also affects the creation of swap
disks, see http://lists.openstack.org/pipermail/openstack-
operators/2016-August/011396.html
** Summary changed:
- ephemeral disk creation fails for local storage with image type raw/lvm
+ ephemeral/swap disk creation fails for
Tested 2.4.1-1ubuntu0.16.04.1 on xenial and seems to work fine for me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586900
Running with 1:18.3-dfsg-1ubuntu3 on Xenial, the issue seems to have
been fixed for me, can anyone confirm this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374109
Title:
epmd does not support
** Changed in: keepalived (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403137
Title:
service keepalived reload leaks file descriptors
To manage
Public bug reported:
This fixes the username deprecation issue, see
https://bugs.launchpad.net/python-keystoneclient/+bug/1552634
** Affects: python-keystoneauth1 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
CONFIRMED FOR: MITAKA
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832507
Title:
console.log grows indefinitely
To manage notifications about this bug go to:
With version 2:8.1.0-0ubuntu0.16.04.2 from xenial-proposed the stale pid
file is removed and the l3-agent can start the new keepalived
successfully.
Maybe we could also get rid of this error that is still being logged:
2016-05-20 10:43:00.913 16153 ERROR neutron.agent.linux.utils [-] Unable
to
Neutron version is Mitaka, in my case 2:8.0.0-0ubuntu1 from Ubuntu
Xenial, but looking at the code the behaviour still seems to be
unmodified in master.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The file gnocchi_resources.yaml is needed when ceilometer is set up with
gnocchi as backend. It is contained in the upstream source. IIUC this
affects Liberty and Mitaka packages.
** Affects: ceilometer (Ubuntu)
Importance: Undecided
Status: New
--
You
Ah, right, sorry for not checking Yakkety, I'm still not used to Xenial
having been released ... ;)
So for me this affects Xenial, package version is 1:1.2.19-1. From a
small check, 1:1.2.7-1ubuntu1 on Trusty seems also to be affected, but
having a fix in Xenial would be good enough for me.
--
It seems that this is mainly a bug in how keepalived handles an empty or
otherwise broken pid file. According to the upstream change log, the
issue has been fixed in 1.2.20.
@Ubuntu: Can you look into updating the package or backporting the fix?
** Also affects: keepalived (Ubuntu)
@Martin: Fixing the installed system is easy, the bad case happens when
the installer sets up the system with "rename2" as the first interface,
making access via console necessary in order to recover.
root@compute-node37:~# SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_id
/sys/class/net/eno1
Looking further, it seems that the BIOS is providing broken information,
see this snippet from dmidecode output:
Handle 0x007E, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard Intel Ethernet 1
Type: Ethernet
Status: Enabled
Type Instance: 1
We have seen the issue only when deploying Xenial, installations running
Precise or Trusty do not seem to be affected.
Running with 4.6.0-040600rc6-generic has shown the same behaviour.
After doing the rmmod/modprobe cycle, I have now found the attached set
of messages in the output of
Public bug reported:
Note: I'm not sure whether this is really a kernel bug or something
within systemd/udev, please advise how to further debug.
On a system with two GE ports, instead of getting named eno1 and eno2, I
am getting eno1 and renameN. Where N starts at 3 and increases by 2 on
every
This is still true for the Mitaka packages in Xenial, making it rather
difficult to create a working installation for new installations.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506665
Title:
Public bug reported:
I have installed percona-xtradb-cluster-server-5.6 on my Xenial server
and try to set the root password with mysqladmin:
# mysqladmin --user=root --password='' password 'secure'
mysqladmin: [Warning] Using a password on the command line interface can be
insecure.
Warning:
Public bug reported:
Currently there is some output from usermod during postinst, even if
there is no change to the user:
Setting up ceph-common (10.1.1-0ubuntu1) ...
usermod: no changes
So just add a "2> /dev/null" to the call to usermod like it is done with
all the other user management calls
Version 1.5.31-0ubuntu1 is now in Xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550853
Title:
package upgrade request
To manage notifications about this bug go to:
** Description changed:
- This log is from installing the pre-release packages, but I got the same
- warnings when installing 10.0.5 earlier:
+ When having a custom /usr/sbin/policy-rc.d, there are various warnings
+ during installation, like:
Preparing to unpack
I'm now seeing the warnings also in the postinst for dmeventd, so
probably deb-systemd-invoke should be fixed as being the common
denominator.
** Also affects: init-system-helpers (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ceph (Ubuntu)
Status: New => Invalid
--
Public bug reported:
There are other options for providing volume backends like RBD, so
having a hard dependency on open-iscsi seems bad, as it prevents admins
from deinstalling the unneeded package. Please remove the dependency or
at least downgrade to Recommends: or Suggests:
** Affects: nova
Public bug reported:
Keystone PKI tokens have been deprecated for security reasons,
deployments should switch to using Fernet tokens instead.
So please remove the call to "keystone-manage pki_setup" from
keystone.postinst at least for Xenial.
** Affects: keystone (Ubuntu)
Importance: Low
Public bug reported:
The service definition in /lib/systemd/system/nova-compute.service
contains
After=libvirtd.service
however that service does not exist, the correct service name would be
libvirt-bin.service. As a result, nova-compute is started too early and
fails because it cannot talk to
Public bug reported:
When using OpenStack, we do not want the default network from installing
libvirt-bin to exist. We can remove the network after installing the
package, but that will remove the file
/etc/libvirt/qemu/networks/default.xml that is included in the package
and it might also
In my case I'm not starting vms directly, but via OpenStack nova, not
sure what happens there in detail and whether that might be a special
case. In my current setup, I can start 4 cirros instances and get about
490 out of 512 tasks used, starting a 5th instance fails.
--
You received this bug
Public bug reported:
When starting virtual machines under libvirt, the qemu process is
accounted for in the TasksAccounting by systemd, see
http://paste.ubuntu.com/15667656/
This should probably not happen, similar to
https://bugs.launchpad.net/systemd/+bug/1564451 the proper solution IMHO
Just found out there is also a discussion on this issue going on
upstream:
http://permalink.gmane.org/gmane.comp.file-systems.ceph.devel/30552
Though that should be no argument not to fix it locally first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I think doing socket based activation properly is non-trivial, as there
are people wanting apache to run only on non-standard ports, e.g. when
deploying OpenStack services. So having a default setup that causes
systemd to listen on port 80, without checking whether the apache config
really does
Sorry, but this is not fixed for me, maybe I wasn't expressing clearly
enough my intentions:
root@controller-node13:~# systemctl status ceph-create-keys
* ceph-create-keys.service - Create Ceph client.admin key when possible
Loaded: loaded (/lib/systemd/system/ceph-create-keys.service; static;
Right, this seems to be something local, I'll have to check where is
comes from. Still it behaves correctly for the "old" service name
without ".service" appended, so this still looks like a bug in deb-
systemd-invoke to me:
root@controller-node11:~# /usr/sbin/policy-rc.d ceph-mon start
** Description changed:
The main reason I would want this upgrade is the confusion regarding the
deprecation of the "username" vs. "user-name" options. This was only
resolved in upstream version 2.4.0 or later.
+ Current status is that when using "username" as option name in a config
+
Public bug reported:
The main reason I would want this upgrade is the confusion regarding the
deprecation of the "username" vs. "user-name" options. This was only
resolved in upstream version 2.4.0 or later.
Debian has just created a new version, it would also be nice to try to
stay in sync
I just found out that the limit is not applied after a reboot, it
appears that this only happens when the service is (re-)started manually
from the shell.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just found out that the limit is not applied after a reboot, it
appears that this only happens when the service is (re-)started manually
from the shell.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
Public bug reported:
This log is from installing the pre-release packages, but I got the same
warnings when installing 10.0.5 earlier:
Preparing to unpack
.../ceph_10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201_amd64.deb ...
deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code
Public bug reported:
This log is from installing the pre-release packages, but I got the same
warnings when installing 10.0.5 earlier:
Preparing to unpack
.../ceph_10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201_amd64.deb ...
deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code
Public bug reported:
When started via systemd, there is a default limit of 512 Tasks, and it
seems that each thread counts as a different task:
# systemctl status ceph-osd@2
Public bug reported:
When started via systemd, there is a default limit of 512 Tasks, and it
seems that each thread counts as a different task:
# systemctl status ceph-osd@2
>From a hardening perspective, it certainly hurts having unneeded
packages installed, so please re-raise the priority of this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cinder in Ubuntu.
https://bugs.launchpad.net/bugs/1079466
>From a hardening perspective, it certainly hurts having unneeded
packages installed, so please re-raise the priority of this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079466
Title:
Public bug reported:
Cinder, Neutron and Nova use rootwrappers that allow selected commands
to be executed with root privileges via sudo. If an adminstrator chooses
to enable sudo logging for security reasons, this will cause a lot of
files being created, leading to filled up file systems pretty
Public bug reported:
Cinder, Neutron and Nova use rootwrappers that allow selected commands
to be executed with root privileges via sudo. If an adminstrator chooses
to enable sudo logging for security reasons, this will cause a lot of
files being created, leading to filled up file systems pretty
Thanks to some help in #systemd I could find the cause: On the affected
systems libpam-systemd was not installed. So maybe it would make sensu
to turn this into a stronger dependency than "recommended", at least in
combination with openssh-server.
--
You received this bug notification because
Thanks to some help in #systemd I could find the cause: On the affected
systems libpam-systemd was not installed. So maybe it would make sensu
to turn this into a stronger dependency than "recommended", at least in
combination with openssh-server.
--
You received this bug notification because
Hmm, on a cloud instance this looks different, even when logged in
multiple time, the output only shows the master process:
# systemctl status ssh
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset:
enabled)
Active: active
Hmm, on a cloud instance this looks different, even when logged in
multiple time, the output only shows the master process:
# systemctl status ssh
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset:
enabled)
Active: active
Do your sleep processes show up in the output of "systemctl status
ssh.service" in the CGroup section? For me they do (sample with just one
process backgrounded):
# systemctl status ssh.service
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service;
Do your sleep processes show up in the output of "systemctl status
ssh.service" in the CGroup section? For me they do (sample with just one
process backgrounded):
# systemctl status ssh.service
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service;
How did you install ceph and which version exactly? Running as ceph
should only happen with >= 9.2, which is available on Xenial.
If I install ceph=10.0.3-0ubuntu1 on a new machine, /var/lib/ceph and
/var/run/ceph have ceph:ceph as owner, which looks fine to me. One could
discuss the ownership of
Public bug reported:
This may be useful for an unexperienced user trying to run ceph on a
small setup, but for an automated deployment of a ceph cluster, it is
pretty annoying that there may be daemons trying to create credentials
that will allow access to the whole cluster if only the new
Public bug reported:
This may be useful for an unexperienced user trying to run ceph on a
small setup, but for an automated deployment of a ceph cluster, it is
pretty annoying that there may be daemons trying to create credentials
that will allow access to the whole cluster if only the new
How did you install ceph and which version exactly? Running as ceph
should only happen with >= 9.2, which is available on Xenial.
If I install ceph=10.0.3-0ubuntu1 on a new machine, /var/lib/ceph and
/var/run/ceph have ceph:ceph as owner, which looks fine to me. One could
discuss the ownership of
IMHO this is a bug for ceph-deploy, which is a separate project from
ceph itself. It should be solved with a new upstream version, probably
1.5.29, see also bug #1550853.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
1 - 100 of 156 matches
Mail list logo
