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

fix: kvm support message for virsh only lp#2053096 #5325

Merged

Conversation

petermakowski
Copy link
Contributor

Done

  • fix: kvm support message for virsh only lp#2053096

QA steps

  • Open deploy form
  • Select "Register as MAAS KVM host" and libvirt for KVM host type
  • Verify the limited support message is displayed

Fixes

Fixes: https://bugs.launchpad.net/maas-ui/+bug/2053096
Fixes: https://bugs.launchpad.net/maas-ui/+bug/2054561

Screenshots

After

Google Chrome screenshot 001593@2x
Google Chrome screenshot 001591@2x

Notes

@webteam-app
Copy link

Demo starting at https://maas-ui-5325.demos.haus

Copy link
Contributor

@ndv99 ndv99 left a comment

Choose a reason for hiding this comment

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

LGTM

state.general.osInfo.data.default_release = "bionic";
}
const store = mockStore(state);
render(
Copy link
Contributor

Choose a reason for hiding this comment

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

nitpick, but you could use renderWithBrowserRouter here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I know! I would need to do that for the entire file though, purposefully avoided it to keep the diff small as it's a bugfix :)

@petermakowski petermakowski merged commit a478045 into canonical:main Feb 29, 2024
6 checks passed
@petermakowski petermakowski deleted the fix-kvm-support-lp#2053096 branch May 9, 2024 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants