| Summary: | [FRI2] ssh keys cannot be loaded | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Alexandru Palalau <alexandrux.palalau> |
| Component: | core | Assignee: | Saul Wold <sgw> |
| Status: | VERIFIED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | dvhart, jessica.zhang, meta.mr.watcher, meta.watcher, tom.zanussi |
| Version: | 1.4 | ||
| Target Milestone: | 1.5 | ||
| Hardware: | FRI2 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Alexandru Palalau
2013-04-23 08:39:35 UTC
Surely this is not BSP specific? It was only encountered on the FRI2 until now. Other BSPs that I've tested on this test run (NUC) did not show this behavior I just booted my FRI2 today using a minimal and sato image created using mkefidisk.sh from the respective hddimg and both start ssh successfully. Please provide a complete description of how you are creating the image and how you are booting it. . This was reproduced with an autobuilder image: http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20130418-2/machines/fri2/core-image-sato-sdk-fri2.hddimg dd on USB stick and install on the FRI2. Ok, I tested with the image listed below along with my own generated image both using the HDD Image boot direct from USB stick, no issues with sshd starting and running on either of my images. Can you please verify your setup and if needed send more details about this. Checked it with the same image on another FRI2 with Fast Boot and everything works fine. Alex confirmed! Switching to verified as per last comments. The behavior was not again encountered. |