-
Notifications
You must be signed in to change notification settings - Fork 30
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
<Netconify> Commit Fail message when there is a warning. #19
Comments
@mamathac - the netconify code use-case was intended to configure only the bare minimum configuration on an Amnesiac device. Please limit the configurations for these scenarios to configure only the following:
In the future we may expand the netconify functionality for broader use-cases; or take a different approach for Console/Termserv based configuration options. Hope this helps! |
Tried console config with a baseline config file on Popeye and worked fine. 2014-05-30 10:31:17,598:NETCONIFY:popeye:login:connecting to TTY:bngsquid25-7010.englab.juniper.net:7010 ... regress@vm-nomadic-ubuntu:~/ansible_junos/mydir_ansible/pb$ ansible-playbook override_config_console --limit popeye -v PLAY [Load Config over console port] ****************************************** GATHERING FACTS *************************************************************** TASK: [junos_install_config host={{inventory_hostname}} file=/usr/local/junos/config/popeye_baseline.conf timeout=3000 user=root console="--telnet=bngsquid25-7010.englab.juniper.net,7010" logfile=/usr/local/junos/log/config_console.log overwrite='yes'] *** PLAY RECAP ******************************************************************** |
This issue is present in both netconfiy and pyez. Deferring for now and will look at fixing this in concert with PyEZ. |
problem mentioned in first post is resolved by this change -> #27 |
Model: SRX5600 standalone
Module: junos_install_config over console port.
Precondition: Device is zeroized and in amnesiac mode
Since the device was zeroized, the license info was lost and configuration has ldp license configuration.
On running YAML code, on the device, the new config gets applied BUT with a warning.
[edit]
regress@asthra# commit
[edit security idp]
'security-package'
warning: requires 'idp-sig' license
commit complete
Playbook returns Incorrect message although commit has gone through:
failed: [asthra] => {"failed": true}
msg: faiure to commit configuration, aborting.
FATAL: all hosts have already failed -- aborting
Expected Behaviour:
Warning should be handled and instead of commit failure message, commit complete and warning should be displayed, as commit went through.
The text was updated successfully, but these errors were encountered: