Created attachment 1315897 [details]
screenshots and engine log
Description of problem:
Network name with special character '&' is added with prefix 'amp' and sometimes created without vNIC profile.
When creating name with special character '&', it added with prefix 'amp'.
If creating network such as: $fffffff , it will be created without vNIC profile and will look like this in the engine - &fffffff
If creating network like this : fffffdsfds& , it will look like this in the engine - fffffdsfds&
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create network &newnet1
2. Create network newnet1&
1. Network created as - &newnet1
2. Network created as - newnet1&
No prefix 'amp' should be added to the special character '&'
I really don't think we need to support any character in a network name. '&' for example is not really something one cannot do without.
Dan - CLOSE-WONTFIX?
*something* has to be done regarding this bug. currently we have the gate open and evil chars can storm inside, creating havoc. If we fail to fix Engine to properly handle xml-special chars, we can avoid this bug by blocking their input.
vnic profiles are not created due to unrelated bug 1485927
This should be fixed for the VM's vNIC profile as well(as showed in attached screenshots).
The 'amp' prefix still displayed in the VM's network interfaces profiles list.
Created attachment 1321677 [details]
This should be fixed for 4.1 as well. I don't see patches for 4.1, only for master.
Oh, I thought that the problem shows up only in the new UX.
Verified on - rhevm-184.108.40.206-0.1.el7.noarch