| Anonymous | Login | 2024-04-25 13:23 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0013701 | ClearOS | app-suva | public | 2017-03-12 10:03 | 2017-03-12 10:04 | ||||
| Reporter | user2 | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | major | Reproducibility | have not tried | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 7.3.1 | ||||||||
| Target Version | 7.3.1 Updates | Fixed in Version | 7.3.1 Updates | ||||||
| Summary | 0013701: Workaround new method for setting a hostkey | ||||||||
| Description | The system hostkey used to be set at install time (i.e. via anaconda). In order to support cloud and VM images (and other stuff), this policy was changed. The system hostkey is now created on first boot - see tracker 0012061 Make sure that existing systems do not reset the hostkey on first boot! | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2017-03-12 10:03 | user2 | New Issue | |
| 2017-03-12 10:03 | user2 | Status | new => resolved |
| 2017-03-12 10:03 | user2 | Fixed in Version | => 7.3.1 Updates |
| 2017-03-12 10:03 | user2 | Resolution | open => fixed |
| 2017-03-12 10:03 | user2 | Assigned To | => user2 |
| 2017-03-12 10:04 | user2 | Status | resolved => closed |
|
Issue History |