-
Notifications
You must be signed in to change notification settings - Fork 173
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
Lab 3.1 Failing #163
Comments
@aosaedi is this in Class 1 or Class 2? Are you restoring the UCS from TMSH? or from TMUI? |
Hi John,
This was for lab 2 and restored UCS using TMSH.
Thanks,
Ahmad Saedi
… On Mar 2, 2018, at 2:02 PM, Jon Calalang ***@***.***> wrote:
@aosaedi is this in Class 1 or Class 2? Are you restoring the UCS from TMSH? or from TMUI?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
just make sure if both the devices are in sync and manually run 3.1 it should work. |
Thank you, yes at the end decided to do it manually and it worked.
Thanks again,
Ahmad Saedi
… On Mar 3, 2018, at 3:02 AM, avinkush ***@***.***> wrote:
just make sure if both the devices are in sync and manually run 3.1 it should work.
it worked for me doing manually without any failed test.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello
I have tried two times the same lab 3.1 and both times it fails on the same spot. The two times I have tried they were on two different lab time slots, restored UCS files from emergency folder, for both LTM a and b, run the same steps from Postman Runner and got the same 1 failed result at the end. And unfortunately can't move to next lab base on the previous one not completed.
It fails at Step 3 with fail error "Max Tries Reached" for bigip-b.f5.local and stops at that.
I am not sure if that would be a bug or I am missing something.
Your help is greatly appreciated,
The text was updated successfully, but these errors were encountered: