-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add a warning on how to work with sysprep #671
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest the following re-write of the first sentence
@@ -81,3 +81,5 @@ You can define the following as part of a Windows-based appliance install profil | |||
* ``Welcome Message``: You can enter a welcome message. | |||
|
|||
.. image:: /images/install-profile-windowsfp3.png | |||
|
|||
.. warning:: For now, please do not select to run sysprep, if the target cloud platform injects CloudBase-Init during its import process, for example, on K5. If you want to run sysprep, run sysprep after the import process has finished. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To avoid possible conflicts we recommend you avoid running sysprep, particularly if the target cloud platform injects CloudBase-Init during its import process (this is the case for example on K5).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For K5 platform, running sysprep is not recommended due to a conflict with CloudBase-Init. You can run sysprep on the instance after publication if needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To avoid possible conflicts we recommend you avoid running sysprep, particularly if the target cloud platform injects CloudBase-Init during its import process (this is the case for example on K5). You can run sysprep on the instance after publication if needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe you can make another commit directly? I think the wording is a bit long but it's fine :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your last proposition is ok for me
This warning gives users the instruction on how to work with sysprep, especially when cloudbase-init is injected by the target platform. In mid- and long-term, the issue will be fixed programatically. For now, users are advised not to run sysprep by UForge to avoid possible conflicts with cloudbase-init.