** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Thomas Duell (anonnaki30031972)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645644
Title:
ntp not using expected servers
To
This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
** Description changed:
=== Begin SRU Template ===
[Impact]
Existing security permissions on /etc/ssh/sshd_config file not honored.
[Test Case]
if [ ! -f lxc-proposed-snapshot ]; then
wget
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot
This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-
0ubuntu1~16.04.1
---
cloud-init (0.7.9-153-g16a7302f-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* New upstream snapshot.
- net: fix reading and rendering addresses in cidr format.
[Dimitri John
This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-
0ubuntu1~16.10.1
---
cloud-init (0.7.9-153-g16a7302f-0ubuntu1~16.10.1) yakkety-proposed;
urgency=medium
* New upstream snapshot.
- net: fix reading and rendering addresses in cidr format.
[Dimitri John
This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-
0ubuntu1~17.04.1
---
cloud-init (0.7.9-153-g16a7302f-0ubuntu1~17.04.1) zesty-proposed; urgency=medium
* New upstream snapshot.
- net: fix reading and rendering addresses in cidr format.
[Dimitri John
Ran the above SRU script and mypool setup showed in all cases
Creating test-xenial
remote refid st t when poll reach delay offset jitter
==
1.ntp.mypool.POOL. 16 p- 640
Hello Nobuto, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-153-g16a7302f-0ubuntu1~16.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing
Hello Nobuto, or anyone else affected,
Accepted cloud-init into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-153-g16a7302f-0ubuntu1~16.10.1 in a few hours, and then in
the -proposed repository.
Please help us by testing
Hello Nobuto, or anyone else affected,
Accepted cloud-init into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-153-g16a7302f-0ubuntu1~17.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing
** Description changed:
=== Begin SRU Template ===
[Impact]
Existing security permissions on /etc/ssh/sshd_config file not honored.
[Test Case]
if [ ! -f lxc-proposed-snapshot ]; then
- wget
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot
** Description changed:
- cloud-init: 0.7.8-49-g9e904bb-0ubuntu1~16.04.1
+ === Begin SRU Template ===
+ [Impact]
+ Existing security permissions on /etc/ssh/sshd_config file not honored.
- Expected NTP server address is written in /etc/ntp.conf by cloud-init through
vendor-data. However,
Thank you for uploading this stable release update! To ease the SRU
review process and later package validation, could you please update the
bug description to include the relevant SRU information [1]?
[1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
--
You received this bug
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init
This bug was fixed in the package cloud-init -
0.7.9-144-g2825a917-0ubuntu1
---
cloud-init (0.7.9-144-g2825a917-0ubuntu1) artful; urgency=medium
* New upstream snapshot.
- flake8: move the pinned version of flake8 up to 3.3.0
- tests: Apply workaround for snapd bug in test
** Merge proposal linked:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/319506
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645644
Title:
ntp not using expected servers
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** No longer affects: maas (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've uploaded a cloud-init test package to a ppa; you can test that
this update fixes the ntp issue on an existing node.
On an affected node:
1. sudo add-apt-repository -y ppa:raharper/bugfixes
2. sudo apt update && sudo apt install cloud-init (#installs
0.7.9-6-gf5fdb6c-1~bddeb)
3. cat
** Changed in: cloud-init (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/1645644
Title:
ntp not using expected servers
To manage notifications about
** Merge proposal linked:
https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/314539
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645644
Title:
ntp not using expected
Not a MAAS issue.
** Changed in: maas (Ubuntu)
Status: New => Invalid
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Fri, Jan 6, 2017 at 10:13 AM, Nobuto Murata
wrote:
> I don't have MAAS env right now at hand. But as I attached the log and
> the code above. /etc/ntp.conf and vendor data were correct. Just
> restarting the daemon by cloud-init was missing if I understand it
>
I don't have MAAS env right now at hand. But as I attached the log and
the code above. /etc/ntp.conf and vendor data were correct. Just
restarting the daemon by cloud-init was missing if I understand it
correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
23 matches
Mail list logo