OCPBUGS-84844: VSphere plugin changes broke i18n translations - missing strings in locales/en/

[cajieh]

Analysis / Root cause:

Following recent updates to the vSphere plugin, a regression was identified where several localized strings were removed or omitted from the locales/en/ source directory despite remaining active in the component implementation.

This resulted in:
Broken Translations: Missing keys caused the UI to fallback to raw key names or empty strings in non-English locales.

Sync Mismatch: The Phrase (Memsource) portal lacked these keys, preventing the localization team from providing translations for upcoming releases.

Solution description:

Source Restoration: Re-introduced the missing string keys into frontend/public/locales/en/vsphere-plugin.json to align the locale source with the current code implementation.

Phrase Portal Sync: Will be uploaded to portal later on.

Test setup:

Clean the local environment: rm -rf node_modules && yarn install && yarn i18n

Ensure the vSphere plugin is enabled in your local development environment.

Test cases:
Key Verification: Verify that the "Error loading" and other vSphere-specific messages no longer show raw translation keys in the console or UI.

Locale Switching: Switch the console language to a supported secondary language (e.g., French) and verify that the keys now appear (either as the restored English string or the translated version if already available in the portal).

Build Integrity: Run yarn build to ensure that the i18n asset compilation completes without errors.

Screenshots

Reviewers and assignees:

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-84844, which is invalid:

• expected the bug to target the "5.0.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Analysis / Root cause:

Solution description:

Screenshots / screen recording:

Test setup:

Test cases:

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cajieh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS [cajieh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[cajieh]

/jira refresh

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-84844, which is invalid:

• expected the bug to target the "5.0.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[cajieh]

/jira refresh

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-84844, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[cajieh]

/test backend

[openshift-ci]

@cajieh: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-84844, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Analysis / Root cause:

Following recent updates to the vSphere plugin, a regression was identified where several localized strings were removed or omitted from the locales/en/ source directory despite remaining active in the component implementation.

This resulted in:
Broken Translations: Missing keys caused the UI to fallback to raw key names or empty strings in non-English locales.

Sync Mismatch: The Phrase (Memsource) portal lacked these keys, preventing the localization team from providing translations for upcoming releases.

Solution description:

Source Restoration: Re-introduced the missing string keys into frontend/public/locales/en/vsphere-plugin.json to align the locale source with the current code implementation.

Phrase Portal Sync: Will be uploaded to portal later on.

Test setup:
Clean the local environment: rm -rf node_modules && yarn install && yarn i18n

Ensure the vSphere plugin is enabled in your local development environment.

Test cases:
Key Verification: Verify that the "Error loading" and other vSphere-specific messages no longer show raw translation keys in the console or UI.

Locale Switching: Switch the console language to a supported secondary language (e.g., French) and verify that the keys now appear (either as the restored English string or the translated version if already available in the portal).

Build Integrity: Run yarn build to ensure that the i18n asset compilation completes without errors.

Reviewers and assignees:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.