Skip to content
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

fixed asa_show_run_object_network_fqdn_issue #1238

Closed

Conversation

vsurresh
Copy link

@vsurresh vsurresh commented Dec 7, 2022

ISSUE TYPE

Bugfix Pull Request

COMPONENT

cisco_asa, cisco_asa_show_running-config_object_network.textfsm

SUMMARY

The current template doesn't take FQDN into account therefore if you try to parse an output with FQDN, textfsm throws an error.

textfsm.parser.TextFSMError: State Error raised. Rule Line: 21. Input Line:  fqdn google.com

jmcgill298 and others added 30 commits June 4, 2020 19:10
k-ribot and others added 17 commits November 3, 2022 11:39
Change docs to mkdocs, update dev environment, move to click for scripts
Update arista_eos_show_ip_route for message of no ip routing
* Add support for `show version brief`
* Add support for `show platform summary location <location>`
* Add support for `show vrf all detail`
* Add support for `show ipv4 vrf <vrf> interface brief`
* Add support for `show ospf vrf <vrf> neighbor`
* Add support for `show ospf vrf <vrf> interface brief`
* Add support for `show bgp instance <instance> summary`
* Add support for `show pim ipv4 group-map`
* Add support for `show pim ipv4 neighbor`
* Add support for `show pim ipv4 interface`
…play-routing-table-template

Add Huawei VRP display routing-table template
…exclude-log-messages

MikroTik routeros exclude all log messages in templates
@@ -2,15 2,13 @@ object network corp
subnet 10.0.0.0 255.0.0.0
object network internal
subnet 192.168.0.0 255.255.255.0
object network any
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this being adjusted?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ASA won't allow the creation of objects with the name 'any' so, I had to remove it from my test.

asa_test(config)# object network any
ERROR: This object name is reserved

object network host-10.10.11.1
host 10.10.11.1
object network block
host 10.75.51.11
object network dmz
description dmz GW ip
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this being adjusted?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The description of the object goes to the next line (after the host)

After:

object network dmz
 host 11.1.2.2
 description dmz GW IP

Before:

object network dmz
  description dmz GW IP
  host 11.1.2.2

@jmcgill298
Copy link
Contributor

@vsurresh it looks like there are some changes that aren't necessary and the yamllint check is failing. It doesn't really matter that any is reserved and can't be configured, it is just a fair representative of the type of data that would be there (a string within certain length constraints). Also, the template should be able to handle whatever order the host and description fields appear; imo, the test data would be better to have representation of both order (who knows if that is consistent across all platforms and all versions?).

I think if the changes just added an entry to match FQDN objects, that there will be much less change to the test data, and the tests will pass pretty easily.

@jmcgill298 jmcgill298 self-assigned this Dec 23, 2022
@jmcgill298 jmcgill298 added the changes_requested Waiting on user to address feedback label Dec 23, 2022
@jmcgill298
Copy link
Contributor

replaced by #1752

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changes_requested Waiting on user to address feedback
Projects
None yet
Development

Successfully merging this pull request may close these issues.