-
Notifications
You must be signed in to change notification settings - Fork 81
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
boot: update the bootargs.cfg #516
Conversation
@@ -17,7 +17,7 @@ source ${SCRIPTS_DIR}/version-harvester ${TOP_DIR}/../harvester | |||
source ${SCRIPTS_DIR}/version-monitoring | |||
source ${SCRIPTS_DIR}/version-logging | |||
|
|||
BASE_OS_IMAGE="rancher/harvester-os:20230615" | |||
BASE_OS_IMAGE="rancher/harvester-os:sle-micro-head" |
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.
do we need to set a fixed version for a new release or plan to use the head instead?
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.
Yes, we need it. @Vicente-Cheng Please help create a new tag on the harvester-v1.2.x branch.
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.
Hi @guangbochen,
We prefer to use sle-micro-head for the master branch.
And now, when we tag the OS image like v1.2-20230629
or v1.1-20230628
(for example).
The GitHub action will create PR to the related installer branch, so we could make master branch use sle-micro-head image for development. cc @bk201
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.
LGTM
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.
LGTM, thanks.
f775401
to
8701c2a
Compare
I also found the debug menu could not display as usual. |
8701c2a
to
b7c704b
Compare
Updated, the debug menu is back |
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.
LGTM, thanks.
Tow places might need modify, still using
|
- we need to update the /proc/cmdline for looks cos_state as root - use latest sle-micro baseOS image as dev branch - change some oem files that depend on the old root label Signed-off-by: Vicente Cheng <[email protected]>
b7c704b
to
c730836
Compare
Thanks for the reminder! |
Stuck at booting after upgrading the first node, probably due to label change? Yes, we still need the latest elemental when we upgrade from v1.1.2. |
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.
LGTM
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.
LGTM, thanks.
@mergify v1.2 |
❌ Sorry but I didn't understand the command. Please consult the commands documentation 📚. |
@Mergifyio backport v1.2 |
✅ Backports have been created
|
Problem:
We must update the
bootargs.cfg
due to new elemental-toolkits.Or we could not find root partition
Solution:
Update
bootargs.cfg
Related Issue:
harvester/harvester#4113
Test plan:
Tested with fresh installation and upgrade