You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2023. It is now read-only.
Seems a classic issue of standing on the tree branch that you are sawing off at the trunk...
Using a PA byol in AWS.
In my ansible playbook, I create new credentials with which to log into the PA.
Then I import a templated xml with those credentials.
Finally, I run panos_loadcfg and I get the following error: The error was: pan.xapi.PanXapiError: commit show jobs id "3": URLError: reason: [Errno 111] Connection refused
I can, of course, log into the PA UI with the credentials that were embedded in the xml. All Good.
Obviously, once the xml config is loaded/committed, it tosses out the temporary admin user. But it throws this ugly error.
I can live with that but it would be nice to have a clean exit.
A colleague suggested that we include the temporary password inside the XML but we would prefer to keep it out of our config.
Another option, I suppose, is ignore_errors: true
Any other tips appreciated.
Thanks,
Chris.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Seems a classic issue of standing on the tree branch that you are sawing off at the trunk...
Using a PA byol in AWS.
In my ansible playbook, I create new credentials with which to log into the PA.
Then I import a templated xml with those credentials.
Finally, I run
panos_loadcfg
and I get the following error:The error was: pan.xapi.PanXapiError: commit show jobs id "3": URLError: reason: [Errno 111] Connection refused
I can, of course, log into the PA UI with the credentials that were embedded in the xml. All Good.
Obviously, once the xml config is loaded/committed, it tosses out the temporary admin user. But it throws this ugly error.
I can live with that but it would be nice to have a clean exit.
A colleague suggested that we include the temporary password inside the XML but we would prefer to keep it out of our config.
Another option, I suppose, is
ignore_errors: true
Any other tips appreciated.
Thanks,
Chris.
The text was updated successfully, but these errors were encountered: