Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Comments

fix: [M3-9705] - IPv6 rDNS does not update immediately in Cloud Manager#12147

Merged
carrillo-erik merged 9 commits intolinode:developfrom
carrillo-erik:fix/M3-9705
May 8, 2025
Merged

fix: [M3-9705] - IPv6 rDNS does not update immediately in Cloud Manager#12147
carrillo-erik merged 9 commits intolinode:developfrom
carrillo-erik:fix/M3-9705

Conversation

@carrillo-erik
Copy link
Contributor

@carrillo-erik carrillo-erik commented May 2, 2025

Description 📝

This PR provides the user with visual feedback that updates to a Linode's IPv6 rDNS have been captured, however, those changes may take up to 1 hour to reflect in the Cloud Manager UI. This is accomplished by making the toast notification persist until the user dismisses it.

Changes 🔄

  • The text copy for the success toast notification has been updated to include the following: "RDNS entry updates may take up to one hour to show."

Preview 📷

Before After
Screenshot 2025-05-07 at 4 49 26 AM Screenshot 2025-05-06 at 5 57 51 PM

How to test 🧪

Reproduction steps

⚠️ These steps were copied from the accompanying ticket.

  • Create a Linode
  • Allocate an IPv6 range on the Linode
  • Using that IPv6 range, click edit the rDNS
  • In the drawer, in the IPv6 address field, enter an IPv6 that exists in the range
  • In the drawer, in the domain name field, enter a domain name that has a AAAA record with the value of the IPv6 address you entered into the IPv6 address field
  • Save changes
  • Observe that you saw a success toast, but the UI does not update to reflect the new rDNS settings

‼️ Every time I tried to edit the IPv6 rDNS I kept getting the We were unable to perform a lookup for 'your-hostname.com' at this time. As a workaround, I edited the Public IPv4 rDNS to trigger the success toast notification since it uses the same component as the IPv6 rDNS toast notification.

Verification steps

(How to verify changes)

  • Verify that the success notification for the IPv6 rDNS updates does not get automatically dismissed, rather the user has to actively dismiss it.
Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support


  • I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

  • All unit tests are passing
  • TypeScript compilation succeeded without errors
  • Code passes all linting rules

@carrillo-erik carrillo-erik changed the title fix: [M3-9705] - S fix: [M3-9705] - IPv6 rDNS does not update immediately in Cloud Manager May 2, 2025
@carrillo-erik carrillo-erik self-assigned this May 2, 2025
@carrillo-erik carrillo-erik marked this pull request as ready for review May 7, 2025 05:14
@carrillo-erik carrillo-erik requested review from a team as code owners May 7, 2025 05:14
@carrillo-erik carrillo-erik requested review from hana-akamai, hasyed-akamai and jdamore-linode and removed request for a team May 7, 2025 05:14
@carrillo-erik carrillo-erik added the Bug Fixes for regressions or bugs label May 7, 2025
const StyledMaterialDesignContent = styled(MaterialDesignContent)(
({ theme }: { theme: Theme }) => ({
'#notistack-snackbar': {
alignItems: 'flex-start',
Copy link
Contributor

Choose a reason for hiding this comment

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

This positioning was actually intentional #12064

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hmmm, I did review the changes in #11962 and looked at the mocks, but didn't see where this was intentional. I will revert it now. Thanks for pointing this out.

@github-project-automation github-project-automation bot moved this from Review to Approved in Cloud Manager May 8, 2025
@hana-akamai hana-akamai added the Approved Multiple approvals and ready to merge! label May 8, 2025
@linode-gh-bot
Copy link
Collaborator

Cloud Manager UI test results

🎉 586 passing tests on test run #5 ↗︎

❌ Failing✅ Passing↪️ Skipped🕐 Duration
0 Failing586 Passing6 Skipped117m 44s

@carrillo-erik carrillo-erik merged commit 9d20be2 into linode:develop May 8, 2025
35 checks passed
@github-project-automation github-project-automation bot moved this from Approved to Merged in Cloud Manager May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved Multiple approvals and ready to merge! Bug Fixes for regressions or bugs

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants