I haven't been able to reproduce this again, so marking as invalid.
Thanks for all your help previously, Martin.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
** Changed in: juju-core
Status: Confirmed => Invalid
--
You received this bug notification because you
Juju will issue a systemctl link to link the unit files, then run
systemctl enable. I cannot recreate this issue on wily, either as a
host, or a wily container running on a wily host (with or without KVM
enabled).
Martin - what information could Adam gather to help debug the issue?
--
You
Opening up a systemd record so that team can take a look.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Bug #1515463 reveals that this change broke Juju. Marking as
verification failed.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Tags removed: bug-squad
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1509747
Title:
Intermittent lxc failures on wily, juju-template-restart.service race
condition
I was working on implementing your suggested changes yesterday, but
could not get a recreate on ec2 without the changes as a baseline. I
tried multiple instance types, thinking that would help trigger the
hang, but to no avail :(
I hit this a lot using canonistack and will try to recreate there
Thanks for digging into this so much, Martin!
1 - Yes, I will try the runcmd you mention and see if it works.
2 - However, I thought adding in After=cloud-config.target would ensure
that it wouldn't start until after cloud-init completes?
3 - The recreate steps for this are:
- Bootstrap local
** Changed in: juju-core
Assignee: (unassigned) => Cheryl Jennings (cherylj)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1509747
Title:
Intermittent lxc failu
** Changed in: juju-core
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1509747
Title:
Intermittent lxc failures on wily,
Is there anything else needed from the container? I'm going to mark
this back to new as I've uploaded the requested information.
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Attachment added: "user-data.txt"
https://bugs.launchpad.net/juju-core/+bug/1509747/+attachment/4505640/+files/user-data.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
root@juju-wily-lxc-template:/# systemctl daemon-reload
root@juju-wily-lxc-template:/# systemctl restart systemd-update-utmp-runlevel
Job for systemd-update-utmp-runlevel.service failed because the control process
exited with error code. See "systemctl status
systemd-update-utmp-runlevel.service"
** Attachment added: "update-utmp.trace"
https://bugs.launchpad.net/juju-core/+bug/1509747/+attachment/4505694/+files/update-utmp.trace
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I see many failures in journalctl of this type:
systemd[1]: Failed to reset devices.list on /lxc/juju-wily-lxc-
template/system.slice/systemd-update-utmp.service: Permission denied
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "journalctl"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1509747/+attachment/4505077/+files/journalctl
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Kicked off instances for testing with Juju. Will update with results
once my testing is complete.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
Verified that Juju can start lxc containers with the proposed changes.
The containers came up and were able to communicate with the state
server, even when on a separate machine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Serge - your changes from comment #22 will break juju with lxc. juju
will need to be modified to call systemctl add-wants multi-user.target
lxc.service
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
This appears to be a regression in systemd. I extracted the unit file
we're trying to link and manually linked it through systemctl and it
succeeded with 222-2ubuntu1, but failed with 223-1ubuntu1:
ubuntu@cherylj-wily4:~$ apt-cache policy systemd
systemd:
Installed: 222-2ubuntu1
Candidate:
21 matches
Mail list logo
