[Bug 1554266] Re: sshd does not start on newly installed desktop system
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 system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1554266/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1554266] Re: sshd does not start on newly installed desktop system
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 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 system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1554266/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1554266] Re: sshd does not start on newly installed desktop system
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 does not start on newly installed desktop system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1554266/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1554266] Re: sshd does not start on newly installed desktop system
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 system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1554266/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1554266] Re: sshd does not start on newly installed desktop system
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 that installs openssh-server via pkgsel. To verify what was going on, I connected virt-manager to the jenkins executor node (venonat) and opened a console on the VM while it was waiting to time out. If you need assistance setting up this recreate method, I can provide that. On Wed, Mar 9, 2016 at 11:24 AM, Martin Pitt wrote: > I tried to purge and reinstall openssh-server on today's cloud image > (with i-s-h 1.29ubuntu1) and ssh.service does start up right away as > expected. So this naïve reproducer doesn't work. Max, how does openssh- > server get installed in your case? Sorry for my ignorance, I don't know > much about preseeding -- is this just translated into some apt-get > install calls? Do they happen in a chroot with a policy-rc.d or similar? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1554266 > > Title: > sshd does not start on newly installed desktop system > > Status in openssh package in Ubuntu: > New > > Bug description: > 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. This > problem appears to have started on the March 5 image. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1554266/+subscriptions > -- 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 system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1554266/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1554266] Re: sshd does not start on newly installed desktop system
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 installed desktop system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1554266/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1554266] [NEW] sshd does not start on newly installed desktop system
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. This problem appears to have started on the March 5 image. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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 system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1554266/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1362224] [NEW] local provider creates all containers with the same MAC address
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 those options. I get:
max@ursus:~/bzr/merges/nfss-insert-timestamp$ juju bootstrap
uploading tools for series [precise trusty utopic]
Logging to /home/max/.juju/local/cloud-init-output.log on remote host
Bootstrapping Juju machine agent
Starting Juju machine agent (juju-agent-max-local)
345b964937a7e650135bca9443637a92bacf83dfaae1323589f1946a010b97ff
/home/max/.juju/local/tools/1.20.5.1-utopic-amd64/tools.tar.gz
2014-08-27 15:37:04 INFO juju.cmd supercommand.go:37 running jujud
[1.20.5.1-utopic-amd64 gc]
2014-08-27 15:37:04 DEBUG juju.agent agent.go:377 read agent config, format
"1.18"
2014-08-27 15:37:04 INFO juju.provider.local environprovider.go:42 opening
environment "local"
2014-08-27 15:37:04 DEBUG juju.cmd.jujud bootstrap.go:210 starting mongo
2014-08-27 15:37:04 DEBUG juju.cmd.jujud bootstrap.go:235 calling
ensureMongoServer
2014-08-27 15:37:04 INFO juju.mongo mongo.go:171 Ensuring mongo server is
running; data directory /home/max/.juju/local; port 37017
2014-08-27 15:37:04 INFO juju.mongo mongo.go:326 installing juju-mongodb
2014-08-27 15:37:04 INFO juju.utils.apt apt.go:128 Running: [apt-get
--option=Dpkg::Options::=--force-confold
--option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install
juju-mongodb]
2014-08-27 15:37:05 DEBUG juju.mongo mongo.go:275 using mongod:
/usr/lib/juju/bin/mongod --version: "db version v2.4.10\nWed Aug 27
11:37:05.432 git version: nogitversion\n"
2014-08-27 15:37:05 DEBUG juju.worker.peergrouper initiate.go:41 Initiating
mongo replicaset; dialInfo &mgo.DialInfo{Addrs:[]string{"127.0.0.1:37017"},
Direct:false, Timeout:3000, FailFast:false, Database:"", Source:"",
Service:"", Mechanism:"", Username:"", Password:"", PoolLimit:0,
DialServer:(func(*mgo.ServerAddr) (net.Conn, error))(nil), Dial:(func(net.Addr)
(net.Conn, error))(0x5be180)}; memberHostport "10.0.3.1:37017"; user "";
password ""
2014-08-27 15:37:05 DEBUG juju.mongo open.go:96 connection failed, will retry:
dial tcp 127.0.0.1:37017: connection refused
2014-08-27 15:37:05 DEBUG juju.mongo open.go:96 connection failed, will retry:
dial tcp 127.0.0.1:37017: connection refused
2014-08-27 15:37:05 INFO juju.mongo open.go:104 dialled mongo successfully
2014-08-27 15:37:05 INFO juju.replicaset replicaset.go:67 Initiating replicaset
with config replicaset.Config{Name:"juju", Version:1,
Members:[]replicaset.Member{replicaset.Member{Id:1, Address:"10.0.3.1:37017",
Arbiter:(*bool)(nil), BuildIndexes:(*bool)(nil), Hidden:(*bool)(nil),
Priority:(*float64)(nil), Tags:map[string]string{"juju-machine-id":"0"},
SlaveDelay:(*time.Duration)(nil), Votes:(*int)(nil)}}}
2014-08-27 15:37:05 WARNING juju.replicaset replicaset.go:87 Initiate: fetching
replication status failed: cannot get replica set status: Received
replSetInitiate - should come online shortly.
2014-08-27 15:37:06 WARNING juju.replicaset replicaset.go:87 Initiate: fetching
replication status failed: cannot get replica set status: Received
replSetInitiate - should come online shortly.
2014-08-27 15:37:06 WARNING juju.replicaset replicaset.go:87 Initiate: fetching
replication status failed: cannot get replica set status: Received
replSetInitiate - should come online shortly.
2014-08-27 15:37:07 WARNING juju.replicaset replicaset.go:87 Initiate: fetching
replication status failed: cannot get replica set status: Received
replSetInitiate - should come online shortly.
2014-08-27 15:37:08 WARNING juju.replicaset replicaset.go:87 Initiate: fetching
replication status failed: cannot get replica set status: Received
replSetInitiate - should come online shortly.
2014-08-27 15:37:08 WARNING juju.replicaset replicaset.go:87 Initiate: fetching
replication status failed: cannot get replica set status: Received
replSetInitiate - should come online shortly.
2014-08-27 15:37:09 WARNING juju.replicaset replicaset.go:87 Initiate: fetching
replication status failed: cannot get replica set status: Received
replSetInitiate - should come online shortly.
2014-08-27 15:37:09 WARNING juju.replicaset replicaset.go:87 Initiate: fetching
replication status failed: cannot get replica set status: Received
replSetInitiate - should come online shortly.
2014-08-27 15:37:10 WARNING juju.replicaset replicaset.go:87 Initiate: fetching
replication status failed: cannot get replica set status: Received
replSetInitiate - should come online shortly.
2014-08-27 15:37:10 INFO juju.mongo open.go:104 dialled mongo successfully
2014-08-27 15:37:10 WARNING juju.replicaset replicaset.go:87 Initiate: fetching
replication status failed: cannot get replica set status: Received
replSetInitiate - should come online shortly.
2014-08-27 15:37:11 WARNING juju.replicaset
Re: [Bug 1328958] Re: Local provider run on server images requires an ubuntu user
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 images requires an ubuntu user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1328958] Re: Local provider run on server images requires an ubuntu user
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 Title: Local provider run on server images requires an ubuntu user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1328958] Re: Local provider run on server images requires an ubuntu user
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 Ubuntu. https://bugs.launchpad.net/bugs/1328958 Title: Local provider run on server images requires an ubuntu user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1328958] Re: Local provider run on cloud images want ubuntu user
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. https://bugs.launchpad.net/bugs/1328958 Title: Local provider run on cloud images want ubuntu user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1329429] Re: local bootstrap fails
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: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1329429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1328958] [NEW] Local provider fails to bootstrap on utopic
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 to configure your juju environment and run bootstrap. max@eden:~$ juju switch local amazon -> local max@eden:~$ juju bootstrap uploading tools for series [utopic precise trusty] Logging to /home/max/.juju/local/cloud-init-output.log on remote host chown: invalid user: ‘ubuntu:ubuntu’ Bootstrap failed, destroying environment ERROR exit status 1 max@eden:~$ ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- 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 fails to bootstrap on utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1328958/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1015678] Re: Cobbler exits with status 0 when failure occurs
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 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: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/1015678/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1015678] Re: Cobbler exits with status 0 when failure occurs
-- 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: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/1015678/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1015678] [NEW] Cobbler exits with status 0 when failure occurs
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 error: internal error, unknown system name acer-veriton-01 but still exits with status 0. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cobbler 2.2.2-0ubuntu33 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed Jun 20 16:16:13 2012 InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cobbler UpgradeStatus: Upgraded to precise on 2012-05-18 (33 days ago) mtime.conffile..etc.cobbler.ubuntu.server.preseed: 2012-05-16T20:38:45.876247 ** Affects: cobbler (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/1015678/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 913857] Re: ntp-keygen documentation lists options that ntp-keygen does not support
-- 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: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/913857/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 913857] [NEW] ntp-keygen documentation lists options that ntp-keygen does not support
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 referenced documentation at /usr/share/doc/ntp-doc/html/keygen.html (in the ntp-doc package) mentions the -p option as well. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ntp 1:4.2.6.p3+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0 Uname: Linux 3.2.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Mon Jan 9 10:54:45 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) NtpStatus: ntpq: read: Connection refused ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: Upgraded to precise on 2012-01-09 (0 days ago) ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug manual-testing precise running-unity -- 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: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/913857/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
