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

Display failover ip for a specific server is broken #8734

Open
1 of 2 tasks
BarbUk opened this issue Jan 11, 2023 · 1 comment
Open
1 of 2 tasks

Display failover ip for a specific server is broken #8734

BarbUk opened this issue Jan 11, 2023 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@BarbUk
Copy link

BarbUk commented Jan 11, 2023

Have you already contacted our help centre?

  • Yes, I have contacted the help centre.

Is there an existing issue for this?

  • I have checked the existing issues

Describe the bug

Before

Using the bare metal server page at https://www.ovh.com/manager/#/dedicated/server/<server_id>, we could click on the network widget to see a page with the routed failover ip on this server.

image

Now

Using the same workflow, we are redirected on https://www.ovh.com/manager/#/dedicated/ip.
On this page it's not possible anymore to filter failover ips by server.

Steps To Reproduce

  1. Open the manager on bare metal cloud
  2. Open a server page (https://www.ovh.com/manager/#/dedicated/server/)
  3. Using the network widget, click on the three dots menu and choose the manage option

Expected Behavior

A page with the network configuration of the selected server.

What browsers are you using?

Chrome

Which devices are used?

Desktop

Additional information to add?

No response

@BarbUk BarbUk added the bug Something isn't working label Jan 11, 2023
@BarbUk
Copy link
Author

BarbUk commented Mar 1, 2023

This issue seem fixed by 63c4cdd

Thanks @y4nnL and @ghyenne.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants