-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feature/casmpet 7175 #285
Feature/casmpet 7175 #285
Conversation
CASMPET-7126: CFS play for k8s labelling fails when it is already applied - fixed to avoid applying k8s lebel when it is already exist
CASMPET-7126: CFS play for k8s labelling fails when it is already applied - fixed iSCSI LIO provisioning to exclude HSN portal config when HSN is not configured - fixed DNS "SRV" and "A" records creation for HSN when HSN is not configured
CASMPET-7126: CFS play for k8s labelling fails when it is already applied - review comments incorporated
…to find a keyring..." part of s3fs mount for "boot-images" - fixed CFS play to create s3 access/ secret key on master node followed by mounting s3 boot images on worker nodes using this s3 key.
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.
This change is already in the code -- it can be removed from this PR
As is, this PR now has conflicts. Please rebase this, clean up the conflicts, and squash down whatever is left. |
After last PR has been merged to "develop" branch, I'm still seeing conflicts after rebase/ corrections with "develop" branch. To quick fix for now, i'm closing this PR and reopened another fresh PR: #291 with required changes merged on top of latest "develop" branch. |
Summary and Scope
CASMPET-7175: iSCSI SBPS: radosgw-admin cmd fails with "auth: unable to find a keyring..." part of s3fs mount for "boot-images"
- "radosgw-admin cmd..." is supposed to be issued on master node to generate s3 access/ secret key and not on worker
nodes. Fixed CFS play to create s3 access/ secret key on master node followed by mounting s3 boot images
on all worker nodes using this s3 key.
Issues and Related PRs
[List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.]
Need to merge the PR "#284" first before merging this PR to delelop branch.
Testing
Tested worker nodes personalization on bare metal system: starlord with CSM 1.6.0-alpha.55 bits
Tested on:
starlord
Test description:
Tested iSCSI SBPS CFS plays (worker node personalization) on starlord with CSM 1.6. Observed that radosgw-admin command for s3 access/ secret key generation on master node followed by mounting s3 boot images using s3fs command on worker nodes is successful.
Risks and Mitigations
None
Pull Request Checklist