Description of problem: We can create a matcher for non-existent attribute for Smart Variable as it is described in BZ 1379277. After that, error is raised for that particular entity and it cannot be edited further from UI. In the same moment, we are not able to create or edit any other Smart Variable for that Puppet Class as we are jumped right to the problematical variable page immediately. That means that all variables will be connected to any one that has an error on its page Version-Release number of selected component (if applicable): 6.2 6.3 How reproducible: Always Steps to Reproduce: 1. Have one Smart Variable with failed validation 2. Try to create or edit any variable from the same Puppet Class from Puppet Class-> Smart Variables page 3. Actual results: Described above Expected results: All entities should be independent from each other Additional info:
Does this happen with any other errors or just the one from BZ 1379277?
It happens with any error, but it is probably impossible to create another precondition rather than described in BZ 1379277 as we need to have invalid smart variable in advance. For example, we can choose type 'boolean' and type string into value field for one variable and correct values for second variable. Of course, you will never be able to save second variable, no matter what, but it is not so critical as if we have invalid variable in puppet class already
Basically, issue can be treated as RFE or a bug in the same aspects. Problem here is only in informing user that all Puppet Class sub entities (e.g. Smart Variables) will not be saved when you push 'Submit' button in case one of such sub entities has invalid data. It doesn't matter whether you editing existing entity, sub entity or creating new sub entities. Any triggered validation prevents you to save any changes that you made within last transaction. Of course, as a workaround, you can go to Smart Variable interface derectly (Configure-> Smart Variable) and do whatever action you want
It sounds like this is the appropriate use case for the inline notification (http://www.patternfly.org/pattern-library/communication/inline-notifications/) since it's a fairly critical time sensitive piece of information. It would appear at the top of the page after validation. The messaging should alert the user to the fact that nothing on the page has been saved because of an existing error.
Created redmine issue http://projects.theforeman.org/issues/19582 from this bug
Upstream bug assigned to orabin
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19582 has been resolved.
Created attachment 1475494 [details] [Verification] Screenshot Attached Verified! @ Satellite 6.4 snap 17 Steps: 1. Go to Puppet Class -> Smart Variables. 2. Create one invalid smart variable but don't submit. 3. Create another smart variable but the valid one. 4. Now submit. Observation: 1. Both smart variables are not saved as one of the smart variable is invalid.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2927