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

Cd removal from new VM page #496

Merged
merged 3 commits into from
Feb 26, 2018
Merged

Cd removal from new VM page #496

merged 3 commits into from
Feb 26, 2018

Conversation

jniederm
Copy link
Contributor

@jniederm jniederm commented Feb 21, 2018

Only last commit is relevant. Please try to merge #495 first.


This change is Reviewable

The translations were previously erroneously based on backend class
VMStatus instead of REST class VmStatus.
Previously enum translation threw an exception in case of unknown enum or
unknow enum member.

Now the enum item name is returned and problem is logged to browser
console.
@jniederm jniederm changed the title Cd removal Cd removal from new VM page Feb 21, 2018
@jniederm jniederm self-assigned this Feb 21, 2018
@@ -33,6 +33,7 @@ import SelectBox from '../SelectBox'
import { MAX_VM_MEMORY_FACTOR } from '../../constants/index'

import { msg } from '../../intl'
import { Fragment } from '../utils'
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we use React.Fragment instead of creating new component?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We would need to upgrade to React 16 to use native React.Fragment which is not wanted before 4.2 oVirt release.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Unfortunately (props) => props.children only works since React 16.0. So I resorted to <div> wrapper.

@jelkosz jelkosz added this to the v1.3.4 milestone Feb 22, 2018
Problem: If a new VM was based on a template with disks then
`createNewVm` saga first sent a request to create a VM which was
immediately locked for the time of disk image copying. Then the saga
fired a request to set a CD image. However the request failed because
the VM was locked.

Solution: CD image can no longer be customized from New VM page, it is
possible only from Edit VM page.
@mareklibra mareklibra merged commit afb07c1 into oVirt:master Feb 26, 2018
@mareklibra mareklibra mentioned this pull request Feb 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants