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

[WIP] BZ1975701: Clarify static IP workaround for Tang encryption on vSphere #37362

Closed
wants to merge 1 commit into from

Conversation

bobfuru
Copy link
Contributor

@bobfuru bobfuru commented Oct 11, 2021

BZ1975701
As mentioned in #33497 (comment) and documented in 4.9 Release Notes (#37356), this adds a workaround that avoids a Tang server switching from static IP addressing to DHCP on second boot on a vSphere UPI.

Impacts 4.8+ docs. (Updates Configuring disk encryption and mirroring, step 2.d.)

Preview link (adds step 2.d.ii): https://deploy-preview-37362--osdocs.netlify.app/openshift-enterprise/latest/installing/install_config/installing-customizing?utm_source=github&utm_campaign=bot_dp#installation-special-config-storage-procedure_installing-customizing

@bobfuru bobfuru added this to the Next Release milestone Oct 11, 2021
@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Oct 11, 2021
@netlify
Copy link

netlify bot commented Oct 11, 2021

✔️ Deploy Preview for osdocs ready!

🔨 Explore the source changes: 3c32a46

🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/616492a6f17c8300085ad4c8

😎 Browse the preview: https://deploy-preview-37362--osdocs.netlify.app/openshift-enterprise/latest/installing/install_config/installing-customizing

@bobfuru
Copy link
Contributor Author

bobfuru commented Oct 11, 2021

@dustymabe or @bgilbert Could you PTAL for SME review?
@jinyunma Could you PTAL for QE?
Cc: @miabbott

Edit: Added WIP label based on feedback from @jinyunma - I will revise this PR to use the suggested workaround that has been verified.

nameserver='8.8.8.8'
echo "ip=${ip}::${gateway}:${netmask}:${hostname}:${interface}:none:${nameserver}"
----

Choose a reason for hiding this comment

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

The workaround listed here is not the right one I applied and verified, because this is node-specific config and need to be applied on each master/worker node ( IP is different on each node), I use the workaround provided in doc https://docs.google.com/document/d/1rnAutjuxzUAauqOZwc8Iccl7SSZVWGJXH5VJL08YvTU/edit#, which also mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1975701#c12

@jinyunma
Copy link

jinyunma commented Oct 12, 2021

4.7 is also impacted, this workaround need to be added on 4.7+ docs.

@bobfuru bobfuru changed the title BZ1975701: Clarify static IP workaround for Tang encryption on vSphere [WIP] BZ1975701: Clarify static IP workaround for Tang encryption on vSphere Oct 12, 2021
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 12, 2021
@bobfuru
Copy link
Contributor Author

bobfuru commented Oct 12, 2021

4.7 is also impacted, this workaround need to be added on 4.7+ docs.

I'll look at how to address this in the 4.7 docs as well. There were some architectural changes to these docs in 4.8, so it might require a separate PR for 4.7.

@bobfuru
Copy link
Contributor Author

bobfuru commented Oct 20, 2021

This workaround requires a Support Exception, so I am closing this PR.

@bobfuru bobfuru closed this Oct 20, 2021
@bobfuru bobfuru deleted the BZ1975701 branch October 20, 2021 22:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.7 branch/enterprise-4.8 branch/enterprise-4.9 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants