Public bug reported:
I'm running precise amd64, but the problem appears to exist on oneiric i386 and
amd64 as well. Natty and older versions support a -p option in ntp-keygen, i.e.
ntp-keygen -p test
Oneiric and precise do not support this, but the man page has not been updated,
and the
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/913857
Title:
ntp-keygen documentation lists options that ntp-keygen does not
support
To manage notifications about this bug go to:
Public bug reported:
We automatically update cobbler profiles to provision systems for jobs running
in jenkins, and when we run commands such as:
sudo cobbler system edit --name=acer-veriton-01
--profile=quantal-2012-06-20_16-00-37-acer-veriton-01-x86_64 --netboot-enabled=Y
cobbler shows an
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/1015678
Title:
Cobbler exits with status 0 when failure occurs
To manage notifications about this bug go to:
TESTCASE:
Run:
sudo cobbler system edit --name=this-name-matches-no-existing-cobbler-system
Expected results:
internal error, unknown system name
this-name-matches-no-existing-cobbler-system on stdout, exit status of 0.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I'm trying to init and bootstrap the juju local provider on utopic. I keep
getting a chown: invalid user error:
max@eden:~$ rm -rf .juju
max@eden:~$ juju init
A boilerplate environment configuration file has been written to
/home/max/.juju/environments.yaml.
Edit the file
I see this with the amazon provider as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1329429
Title:
local bootstrap fails
To manage notifications about this bug go to:
I still have the same problem on my workstation running utopic after a
long series of upgrades, so I don't think it's exclusive to cloud
images.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
There we go! I have /home/ubuntu left over from an old setup simulating
the conditions in the CI lab, but I have no ubuntu user. I'll delete
/home/ubuntu and try again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in
The deployments I've been doing all need swift, so I had to get canonistack
working anyway. I'll retry this later this week.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
So mine is working if I remove /home/ubuntu. Is there something else I
should check?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider run on server
Public bug reported:
When I run juju with the local provider on utopic, all of the containers are
created with the same MAC address. I tried adding lxc-clone: true and
lxc-clone-aufs: true to my environments.yaml local section, but now I can't get
a bootstrap to complete, with or without
I re-ran this job:
https://platform-qa-jenkins.ubuntu.com/view/smoke-default/job/ubuntu-xenial-desktop-amd64-smoke-default/
It installs from the daily iso using utah. It uses a preseed here:
http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/desktop/view/head:/preseeds/default.cfg
This is blocking current image promotions. Is there something I can do
to provide more data for getting it fixed?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1554266
Title:
sshd
FWIW, this doesn't happen on current server installs, just desktop.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1554266
Title:
sshd does not start on newly installed desktop
I've confirmed that openssh-server is installed on the system, and can
be started manually after the first reboot. I previously saw that it
started automatically after the second reboot, but I haven't confirmed
that this week.
--
You received this bug notification because you are a member of
Can I pin i-s-h during install or is there some other way I can help
verify this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1554266
Title:
sshd does not start on newly
Public bug reported:
When I preseed a desktop install using utah for daily iso testing, the
ssh service is not running when it starts up. journalctl -u ssh shows no
entries. If I manually start the ssh service, it seems to work. If I
reboot, sshd is running. On the first boot, however, it is not.
If we enable oem config in the preseed, this problem doesn't occur.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1554266
Title:
sshd does not start on newly installed desktop
19 matches
Mail list logo
