I think this should be solved at otopi level in core.config plugin.
Files specified as additional configuration should show a warning to the user if not existing.
by design configuration is allowed to be missing.
the search for configuration is:
1. file: configuration name
2. directory: configuration name + '.d/*.conf'
missing configuration is valid.
I added a warning for missing config append, although not very happy... as I can think of many scenarios in which this is valid.
(In reply to Sandro Bonazzola from comment #5)
> (In reply to Alon Bar-Lev from comment #3)
> > Not sure how do I set 3.4.1 without robot revert.
>
> You need 3.5.0 and 3.4.z flags request.
Probably I have no permissions as I did not see the 3.4.z.
Thank you for taking care of that.
Comment 7Yedidyah Bar David
2016-08-17 07:35:18 UTC
*** Bug 1224720 has been marked as a duplicate of this bug. ***
Description of problem: [root@pb-rh34 ~]# ls nonexistent ls: cannot access nonexistent: No such file or directory [root@pb-rh34 ~]# rhevm-setup --config-append=nonexistent [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'] Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20140429104643.log Version: otopi-1.2.0 (otopi-1.2.0-1.el6ev) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection <snip/> Version-Release number of selected component (if applicable): rhevm-setup-3.4.0-0.15.beta3.el6ev.noarch Actual results: Wrong filename is silently ignored Expected results: A wargning.