** Changed in: ntp-charm
Status: Fix Committed => 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/1744072
Title:
[MIR] Chrony in 18.04
To manage notifications about this bug go
** Changed in: ntp-charm
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
[MIR] Chrony in 18.04
To manage notifications about this bug go
Hi Mathias - that was for both to support configuring chrony for ntp services.
Both are done AFAIK, setting fix released.
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: maas (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug
clout-init and maas are already in main. why are these still open?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
[MIR] Chrony in 18.04
To manage notifications about this bug go to:
** Changed in: serverguide
Status: Fix Committed => 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/1744072
Title:
[MIR] Chrony in 18.04
To manage notifications about this bug go
I've added initial support for chrony to the ntp charm:
https://code.launchpad.net/~paulgear/ntp-charm/+git/ntp-
charm/+merge/340780
Very lightly tested at present - nagios check known to be non-working,
other features should work. It's available as cs:~paulgear/ntp if
anyone would like to test:
** Merge proposal linked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/339706
** Merge proposal linked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/339707
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Merge proposal linked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/336685
** Changed in: maas (Ubuntu)
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification
** Branch linked: lp:serverguide
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
[MIR] Chrony in 18.04
To manage notifications about this bug go to:
** Changed in: serverguide
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
[MIR] Chrony in 18.04
To manage notifications about this bug go to:
FYI Proposed documentation update:
https://code.launchpad.net/~paelzer/serverguide/serverguide-
chrony-18.04/+merge/338892
** Branch linked: lp:~paelzer/serverguide/serverguide-chrony-18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package ceph - 12.2.2-0ubuntu2
---
ceph (12.2.2-0ubuntu2) bionic; urgency=medium
* d/control: Re-order Recommends to prefer chrony over time-daemon
(chrony/openntp) and ntp for Ubuntu (LP: #1744072).
-- Christian Ehrhardt
The ceph change to modify the dependencies (reorder recommends) are in
proposed and hopefully soon to migrate.
Of the rather time critical bits (to demote ntp in time before FF) what
is left is the change in MAAS. Since the sprint there was no reply by
MAAS yet, so pinging on IRC in addition to
** Changed in: maas (Ubuntu)
Importance: Undecided => Critical
** Changed in: ceph (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
Override component to main
chrony 3.2-2ubuntu3 in bionic amd64: universe/admin/extra/100% -> main
chrony 3.2-2ubuntu3 in bionic arm64: universe/admin/extra/100% -> main
chrony 3.2-2ubuntu3 in bionic armhf: universe/admin/extra/100% -> main
chrony 3.2-2ubuntu3 in bionic i386:
Thanks Nish that you took a look.
I merged the two open and already approved seed changing branches.
Will also do the ceph upload soon.
All those will make chrony show up in component mismatches to then be added.
(and hopefully ntp will show up soon after for demotion to universe)
--
You
I reviewed chrony; it's fine to MIR (and has security team approval).
MIR ACKed.
** Changed in: chrony (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
I reviewed chrony; it's fine to MIR (and has security team approval).
MIR ACKed.
** Changed in: chrony (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: chrony (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Changed in: chrony (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Changed in: chrony (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Changed in: chrony (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@paelzer: As I looked at chrony's config and the options which would be
needed in a new chrony charm, I found that most of them were common with
ntp, so I'm going to start work on a branch of the ntp charm which
supports switching between ntp and chrony. I'll link the branch here
when I have some
** Description changed:
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the
architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main
MP's for the seed changes are up:
platform:
https://code.launchpad.net/~paelzer/ubuntu-seeds/18.04-ntp-to-chrony-platform/+merge/337257
ubuntu:
https://code.launchpad.net/~paelzer/ubuntu-seeds/18.04-ntp-to-chrony-ubuntu/+merge/337256
Waiting now for:
- the general MIR team ack and setting to
Ok, this now has all prereqs resolved.
It is ready for the actual MIR + seed change.
Setting the state back to new (we reused the bugno, but it is for the MIR
actually)
So todo's now are:
@MIR Team ack and set fix committed
@Cpaelzer - Propose a seed change.
** Changed in: chrony (Ubuntu)
This bug was fixed in the package chrony - 3.2-2ubuntu2
---
chrony (3.2-2ubuntu2) bionic; urgency=medium
* d/control: use to nss instead of tomcrypt (in main) (LP: #1744072)
* d/chrony.conf: use ubuntu ntp pool and server (LP: #1744664)
* d/chrony.default, d/chrony.service:
Builds complete against new nss, also all other bugs we wanted are grouped.
New chrony uploaded to bionic - once passed we can do the seeding.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
** Description changed:
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the
architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main
On 22/01/18 17:27, ChristianEhrhardt wrote:
> Hi Paul,
> I subscribed you as I wanted to clarify something.
> Back in [1], you mentioned it was important to you to get ntpdate (single
> shot cli) and ntpd (daemon) to work together nicely for the ntp charm.
>
> Now if the ntp charm would be
** Description changed:
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the
architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main
re: ifup/down hooks --
In the end, it's the same situation with either ntpd or chrony. let's
just add it to the tasks to do after promotion in general for 18.04. I
wouldn't conflate the MIR with this point at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
ifup/down hooks are undirected (just chronyc offline/online).
There are networkmanager dispatchers which are smarter.
All of this is to allow to handle lossy/changing connections which is
far more a laptop or similar (=>NetworkManager) than a server.
We might consider moving on without a
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/336844
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
MIR Chrony in 18.04
FYI - It seems a bit dead here, but most work atm is going into
dependent bug 1744328
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
MIR Chrony in 18.04
To manage notifications about
I reviewed chrony version 3.2-1build1 as checked into bionic. This isn't a
full security audit but rather a quick gauge of maintainability.
- There are ten CVEs in our database; the fixes mostly aren't enumerated
in our database, but many of the descriptions sound like they were
handed out
** Description changed:
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the
architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main
FYI: Debian accepted all our apparmor changes already plus a few
cleanups - synced that new version into Bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
MIR Chrony in 18.04
To
We will also have to rewrite parts of the server guide
- Chrony usage in general
- Maybe how to convert a config from ntp to chrony
** Also affects: serverguide
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Simin and Ken, both great to know about!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
MIR Chrony in 18.04
To manage notifications about this bug go to:
** Description changed:
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the
architectures it is designed to work on.
2. Rationale:
- 2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
- which is the current implementation in main
Ceph tracker to switch from ntpd to chronyd:
http://tracker.ceph.com/issues/22751
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
MIR Chrony in 18.04
To manage notifications about
RE: ntpdate equivalent, upstream recommends "chrony -q" with or without
a config file.
https://chrony.tuxfamily.org/faq.html#_does_code_chronyd_code_have_an_ntpdate_mode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
MIR
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ceph (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
MIR
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chrony (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
While some things are up in the air we should step this forward as good
as we can, so @ubuntu-mir Team pleas ack and set it so the next status
(if ok) so that the security Team can do an official check and ack as
well.
** Description changed:
- Note: I know it is the template so far, but after
** Description changed:
Note: I know it is the template so far, but after the discussions at the
sprint I want something we can start working on together.
Background: after evaluation it was considered easier to maintain to
provide a good and secure ntp experience as well as some
bug 1718227 covers the need for hook integration from ifup to systemd,
this is a soft prereq to consider it fully complete for 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
MIR
Hi Paul,
I subscribed you as I wanted to clarify something.
Back in [1], you mentioned it was important to you to get ntpdate (single shot
cli) and ntpd (daemon) to work together nicely for the ntp charm.
Now if the ntp charm would be modified to use chrony from 18.04 onward,
would that break it
Discussion about usability of libnss forked into bug 1744328
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
MIR Chrony in 18.04
To manage notifications about this bug go to:
TOOD: add docs like serverguide to move to chrony
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
MIR Chrony in 18.04
To manage notifications about this bug go to:
TODO: add tasks for charms by paul geer
** Description changed:
Note: I know it is the template so far, but after the discussions at the
sprint I want something we can start working on together.
Background: after evaluation it was considered easier to maintain to
provide a good and
Current TODOs to get the MIR started:
1. complete the template
2. check dependencies and file MIRs as needed
3. Add bug tasks for all other affected packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
53 matches
Mail list logo
