** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: cloud-init
Assignee: (unassigned) => Arthit Kosachunhanun (richshops)
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Arthit Kosachunhanun (richshops)
** Changed in: cloud-init (Ubuntu)
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701297
Title:
NTP reload failure (unable to read library) on overlayfs
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
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/1701297
Title:
NTP reload failure (unable to read library) on overlayfs
To
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701297
Title:
NTP reload failure (unable to read library) on overlayfs
To manage
Hi all, sorry to necro a thread, but I'm having this issue on MAAS
2.3.1. Is anyone able to provide some insight into this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701297
Title:
NTP
An addition to workaround b.) from #32.
We changed the code in question and restarted the maas rackd service
which fixed the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701297
Title:
NTP
Hi Marzog,
What commit has been committed to Linux? I cannot find it.
Regards,
Daniel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701297
Title:
NTP reload failure (unable to read library) on
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1701297
Title:
NTP reload failure (unable to read library) on overlayfs
To
** Changed in: cloud-init
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701297
Title:
NTP reload failure (unable to read library) on overlayfs
To manage
If you are affected by this bug, then you have the following options:
a.) upgrade to maas 2.2
MAAS 2.2 sends 'apparmor=0' to the installation/commissionging kernel command
line. 2.2 is in -proposed for 16.04, 16.10, 17.04 repositories and
is already available in artful.
Alternatively you can
** Description changed:
After update [1] of cloud-init in Ubuntu (which landed in xenial-updates
on 2017-06-27), it is causing NTP reload failures.
https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
0ubuntu1~16.04.1
In MAAS scenarios, this is causing the machine
There is a xenial test kernel at
http://people.canonical.com/~jj/lp1701297/
I have not had a chance to try it yet. I'll try to get to it in a few
hours after some sleep.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am also getting the same issue with ga kernel
Where we hav to set the hwe kernel?
We have to change the hwe kernel to maas node or to the deploying nodes?
And apparmor and hwe kernel is mandatory to set to deployment work?
--
You received this bug notification because you are a member of
Well that explains it. So we would have seen this issues from release
except for the cloud-init bug.
Now we need to isolate the fix and backport it to the ga kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Tyler,
The reason why this wasn't seen before is that previously in Xenial,
cloud-init did not restart 'ntp' with a new config file. Since cloud-
init recently SRU'd a fixed cloud-init that does restart 'ntp' on
overlay, the issue started to show up.
In other words, after a cloud-init bugfix ,
To elaborate a bit more, the apparmor and overlayfs incompatibility has
been a known kernel issue from before 16.04's release and, at this time,
isn't something that is likely to be fixed in 16.04. I'd like to better
understand if something changed in userspace that started tickling the
@Andres One thing that I'm struggling with is why this bug hasn't been
seen before. IIUC, it should be present in the very first ga-16.04
kernel that Ubuntu 16.04 LTS was released with (in addition to earlier
kernels while Xenial was a development release). Has MAAS 2.1.x and
ga-16.04 kernels just
John is going to build a test kernel, based on the ga-16.04 kernel, with
the binfmt_elf commit cherry-picked from the hwe-16.04. That will let
someone from the MAAS team attempt to reproduce the issue with the test
kernel and, if the deployment succeeds, it'll tell us that the
binfmt_elf commit is
>From an apparmor pov those 2 kernels are almost identical, with the 4.4
kernel picking up a couple of backport patches, that just do some simple
remapping and should not affect behavior.
There are however some external changes that could affect apparmor mediation
binfmt_elf change
Tyler - thanks for that.
John - this is coming up in some internal support team escalations so
I'm going to have a look at the kernel changes myself and will let you
know if I find anything. I'd be keen to sync up if you have any leads.
Regards,
Daniel
--
You received this bug notification
On 07/05/2017 08:14 PM, Daniel Axtens wrote:
> Hi Tyler,
>
> Do you know what the changes between the ga-16.04 and hwe-16.04 kernel
> are that make apparmor+overlayfs work?
No, we're not currently aware of any code changes that would cause the
behavioral change that is reported in the bug. Now
When using the following kernel (the default Xenial kernel, aka ga-16.04
in MAAS), we see this issue:
4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
When using the HWE kernel (aka hwe-16.04 in MAAS), we do NOT see this
issue:
4.8.0-58-generic
Hi Tyler,
Do you know what the changes between the ga-16.04 and hwe-16.04 kernel
are that make apparmor+overlayfs work? I'm worried we might hit this
problem elsewhere...
Regards,
Daniel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Andres,
can you be more specific about the kernel version of the hwe kernel you
are seeing this on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701297
Title:
NTP reload failure (unable to read
@Tyler,
That's is correct, MAAS 2.2.0+ sends the apparmor=0 for the ephemeral
environments.
That said, however, this affects else who is not using 2.2 (which in
fact, affects customers who are still in 2.1). Also, based on my
testing, it seems that when using hwe-16.04 kernel this doesn't
25 matches
Mail list logo
