-
Notifications
You must be signed in to change notification settings - Fork 48
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
Reload is inconsistent #72
Comments
Hi,
Getting stuck at [confirm] prompt until recovery kicks in. One interesting observation though. when the following line appears in syslog, reload is always 100% successful: %IOSXE_RP_CFG_NOT-3-BOOT_VAR_NOT_SET: Either the boot variable does not exist or the buffer is too small.Keep it blank.
|
Hi, can you handle the Dialog the right way? above link will help you thanks |
Hi,
I'm using defaults, shouldn't those work?
Thanks
…On Mon, 19 Dec 2022, 17:40 ketul, ***@***.***> wrote:
Hi,
https://pubhub.devnetcloud.com/media/unicon/docs/user_guide/services/generic_services.html#:~:text=as%20shown%20here.-,execute,-%C2%B6
https://pubhub.devnetcloud.com/media/pyats-getting-started/docs/bestpractices/lib.html#:~:text=smaller%20verifications%20together.-,Dialog,-example
can you handle the Dialog the right way?
above link will help you
thanks
—
Reply to this email directly, view it on GitHub
<#72 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD2CGUE3ROWXXGJWJEGI3QLWOCMYDANCNFSM6AAAAAASNIZTZE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Where can i find dialog handling? At least the default ones?
This may be down to the fact that default dialog does not expect the warning message and isn't handling this properly: WARNING: Boot variable either does not exist or buffer is too small Could this be added to next release? Update |
Sending e.g device.reload() doesn't always produce expected result. It's sitting and waiting for something at the reload confirm prompt and eventually timeouts and prompt recovery kicks in which effectively sends a new line and allows for reload to proceed.
YAML:
LOG output:
The text was updated successfully, but these errors were encountered: