Bug 1226078 - Missing repeated hint how to register
Summary: Missing repeated hint how to register
Status: RESOLVED FEATURE
Alias: None
Product: PUBLIC SUSE Linux Enterprise Micro 6.0
Classification: openSUSE
Component: Image-based Installation (show other bugs)
Version: unspecified
Hardware: All Other
: P3 - Medium : Major
Target Milestone: ---
Assignee: Fabian Vogt
QA Contact: Jose Lausuch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-07 09:27 UTC by Dr. Werner Fink
Modified: 2024-07-05 11:14 UTC (History)
5 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

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 Dr. Werner Fink 2024-06-07 09:27:44 UTC 
During installation in a VM via virt-manager there was a short hint how to register but I was not able to copy this hint into the clip stack.

After getting the Micro System up no further hint was found in the system
how to register.  I found the information later via search at google.
Comment 1 Ignaz Forster 2024-06-10 13:45:37 UTC 
From what I know this message is shown by jeos-firstboot - reassigning (to the hopefully correct component).
Comment 5 Fabian Vogt 2024-07-05 10:15:26 UTC 
I don't understand what this bug report is about.

jeos-firstboot shows a message that SUSEConnect or transactional-update needs to be used for system registration. That is not persistent.

If the goal is to have a reminder in e.g. /etc/issue, that would have to be managed by SUSEConnect itself or maybe issue-generator.
Comment 6 Dr. Werner Fink 2024-07-05 10:50:19 UTC 
(In reply to Fabian Vogt from comment #5)
> I don't understand what this bug report is about.
> 
> jeos-firstboot shows a message that SUSEConnect or transactional-update
> needs to be used for system registration. That is not persistent.

This is exactly the problem ... there is no way to consult a manual
after fist boot.

> 
> If the goal is to have a reminder in e.g. /etc/issue, that would have to be
> managed by SUSEConnect itself or maybe issue-generator.
Comment 7 Fabian Vogt 2024-07-05 11:14:13 UTC 
Ok, so it's not a bug. Please file a feature request on jira, needs some discussion on how to present that to the user.