Skip to content
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

Merged
merged 1 commit into from
Jul 4, 2023

Conversation

Vicente-Cheng
Copy link
Contributor

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

@@ -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"
Copy link
Contributor

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?

Copy link
Member

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.

Copy link
Contributor Author

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

Copy link
Member

@bk201 bk201 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@guangbochen guangbochen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks.

@masteryyh
Copy link
Contributor

Cannot boot into Harvester using the ISO built from this branch...
After installed and rebooted it always goes in installation screen, even the virtual CDROM is not inserted.
Using harvester/harvester master branch, installed on Hyper-V
image

@Vicente-Cheng
Copy link
Contributor Author

Cannot boot into Harvester using the ISO built from this branch... After installed and rebooted it always goes in installation screen, even the virtual CDROM is not inserted. Using harvester/harvester master branch, installed on Hyper-V image

Update the 91_installer.yaml, caused by the root label change.
Only affect the dashboard display. The installation is successful.

@Vicente-Cheng
Copy link
Contributor Author

I also found the debug menu could not display as usual.
Change this to draft until I fix that.

@Vicente-Cheng Vicente-Cheng marked this pull request as draft June 30, 2023 04:47
@Vicente-Cheng Vicente-Cheng marked this pull request as ready for review June 30, 2023 05:20
@Vicente-Cheng
Copy link
Contributor Author

Updated, the debug menu is back

Copy link
Contributor

@masteryyh masteryyh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks.

@bk201
Copy link
Member

bk201 commented Jun 30, 2023

Tow places might need modify, still using COS_ACTIVE label:

    - 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 <vicente.cheng@suse.com>
@Vicente-Cheng
Copy link
Contributor Author

Tow places might need modify, still using COS_ACTIVE label:

Thanks for the reminder!
Update for os2: harvester/os2#74
Installer has also been updated!

@bk201
Copy link
Member

bk201 commented Jul 3, 2023

Screenshot 2023-07-03 at 10 32 06 AM

Stuck at booting after upgrading the first node, probably due to label change?

cmdline:
Screenshot 2023-07-03 at 10 35 36 AM

@Vicente-Cheng
Copy link
Contributor Author

Screenshot 2023-07-03 at 10 32 06 AM Stuck at booting after upgrading the first node, probably due to label change?

cmdline: Screenshot 2023-07-03 at 10 35 36 AM

Yes, we still need the latest elemental when we upgrade from v1.1.2.
Related to PR: harvester/harvester#4164

Copy link
Member

@bk201 bk201 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@guangbochen guangbochen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks.

@guangbochen guangbochen merged commit 08ad34a into harvester:master Jul 4, 2023
4 checks passed
@Vicente-Cheng
Copy link
Contributor Author

@mergify v1.2

@mergify
Copy link

mergify bot commented Jul 4, 2023

v1 .2

❌ Sorry but I didn't understand the command. Please consult the commands documentation 📚.

@Vicente-Cheng
Copy link
Contributor Author

@Mergifyio backport v1.2

@mergify
Copy link

mergify bot commented Jul 4, 2023

backport v1.2

✅ Backports have been created

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants