Your message dated Tue, 10 Apr 2018 03:08:34 +0200
with message-id <20180410010834.gb17...@mapreri.org>
and subject line Re: [Qa-jenkins-dev] Bug#895326: jenkins.debian.org: All armhf
nodes are missing ssh port configuration
has caused the Debian Bug report #895326,
regarding jenkins.debian.org: All armhf nodes are missing ssh port configuration
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
895326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jenkins.debian.org
Severity: serious
As of commit bb559740baac88dc98f9f41176cd1fbecda3faf4:
https://anonscm.debian.org/git/qa/jenkins.debian.net.git/commit/hosts/common/etc/ssh/sshd_config?id=bb559740baac88dc98f9f41176cd1fbecda3faf4
All the armhf nodes no longer have the correct ssh port configuration,
as each node has a specific port that needs configuration in sshd_config
to be used.
I've added the correct port back into all of the currently running
nodes, but haven't figured out how to do this from jdn_update.sh.
I noticed this because several machines recently rebooted were not
responding on the correct ssh port...
The other machines were only still working because ssh had not been
restarted. At least it was only a couple machines and caught before it
became a bigger problem!
live well,
vagrant
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Mon, Apr 09, 2018 at 03:31:44PM -0700, Vagrant Cascadian wrote:
> As of commit bb559740baac88dc98f9f41176cd1fbecda3faf4:
>
>
> https://anonscm.debian.org/git/qa/jenkins.debian.net.git/commit/hosts/common/etc/ssh/sshd_config?id=bb559740baac88dc98f9f41176cd1fbecda3faf4
>
> All the armhf nodes no longer have the correct ssh port configuration,
> as each node has a specific port that needs configuration in sshd_config
> to be used.
Oh, I didn't know of that detail!!!
> I've added the correct port back into all of the currently running
> nodes, but haven't figured out how to do this from jdn_update.sh.
I've done it now:
https://anonscm.debian.org/git/qa/jenkins.debian.net.git/commit/?id=d937951
https://anonscm.debian.org/git/qa/jenkins.debian.net.git/commit/?id=8b1c4fd
> I noticed this because several machines recently rebooted were not
> responding on the correct ssh port...
Indeed, I had noticed a machine suddenly not responding to ssh, but
looking very fine over console earlier today, but couldn't look further.
> The other machines were only still working because ssh had not been
> restarted. At least it was only a couple machines and caught before it
> became a bigger problem!
Indeed, thank you for noticing and debugging the issue!!
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
--- End Message ---
