Bug 268199 - Upgrade from 12.3-RELEASE to 12.4-RELEASE breaks remote ssh until next reboot
Summary: Upgrade from 12.3-RELEASE to 12.4-RELEASE breaks remote ssh until next reboot
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.4-RELEASE
Hardware: Any Any
: --- Affects Many People
Assignee: Graham Perrin
URL: https://www.freebsd.org/releases/12.4...
Keywords:
: 268200 (view as bug list)
Depends on: 263489
Blocks:
  Show dependency tree / graph
 
Reported: 2022-12-06 15:31 UTC by hk
Modified: 2023-04-19 21:01 UTC (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description hk 2022-12-06 15:31:01 UTC 
I have a vanilla FreeBSD 12.3-RELEASE-p6 (amd64) system. Upgraded to 12.4-RELEASE as follows:

remote login via ssh
  freebsd-update upgrade -r 12.4-RELEASE
  freebsd-update install
  reboot
remote login via ssh
  freebsd-update install

now (after second install-run) remote login vi ssh is no longer possible

Current solution:
  whilst still logged on, reboot again

remote login via ssh is then possible again (at least when I tested this)

Originally tested with FreeBSD 12.3-RELEASE-p6 on VMWare Fusion (on MacBook Pro with macOS Monterey 12.4), retested with a vanilla FreeBSD12.3-RELEASE install (installed from ISO-Image FreeBSD-12.3-RELEASE-amd64-dvd1.iso), same problem.

This might bite all people who have remote systems without (remote) console access.

Best regards
Holger

(not sure if this is similar to bug #41202)
Comment 1 Graham Perrin freebsd_committer freebsd_triage 2022-12-06 16:22:30 UTC 
*** Bug 268200 has been marked as a duplicate of this bug. ***
Comment 2 Graham Perrin freebsd_committer freebsd_triage 2022-12-06 16:30:33 UTC 
Given bug 263489 comment 23, I imagine that there was an omission from release notes for 12.4.
Comment 3 Graham Perrin freebsd_committer freebsd_triage 2022-12-07 03:01:56 UTC 
Late-breaking news, maybe?

<https://www.freebsd.org/releases/12.4R/errata/#late-news>

I can't offer to create a diff at the moment (limited to an iPad). 

Edit an existing page, plus another newsflash, plus maybe an email to freebsd-announce with reference to the newsflash.

True: <https://www.freebsd.org/news/newsflash/#2022-12-05:1> does already direct readers to late-breaking news, however (if this bug is what I think) we have an unusual situation where an email might help to raise awareness; for  operators to not have unplanned journeys to remote computers, and so on. 

Thanks
Comment 4 Robert Blayzor 2022-12-07 18:47:29 UTC 
Workaround: Just restart sshd after your second freebsd-update install.
Comment 5 Graham Perrin freebsd_committer freebsd_triage 2023-03-09 01:22:45 UTC 
<https://old.reddit.com/r/freebsd/comments/11madit/-/> pinned as an announcement in the FreeBSD subreddit.
Comment 6 Graham Perrin freebsd_committer freebsd_triage 2023-03-22 21:35:38 UTC 
With the erratum published on 21st March in the 12.4R area, I think we can close this. 

<https://cgit.freebsd.org/doc/commit/?id=84b3c465a201d3cc9fea228b0547bc8673afa1a6>

> Add OpenSSH updating note to 12.4 errata page

Thanks @emaste