-
Notifications
You must be signed in to change notification settings - Fork 138
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
Fix failing acceptance tests #100
Comments
I get a pass for If, for example, the IP Can you check if you have a similar problem with 1.? |
Yes passing now thanks, I've added a note to the readme explaining how to housekeep stale netbox data volumes |
Closed by #102 |
make testacc
has the following failures:1.
=== CONT TestAccNetboxAvailablePrefix_multiplePrefixesSerial resource_netbox_available_prefix_test.go:92: Step 1/2 error: Error running apply: exit status 1
=== CONT TestAccNetboxAvailableIPAddress_basic resource_netbox_available_ip_address_test.go:18: Step 1/1 error: Check failed: Check 1/3 error: netbox_available_ip_address.test: Attribute 'ip_address' expected "1.1.2.1/24", got "1.1.2.2/24"
=== CONT TestAccNetboxAvailableIPAddress_multipleIpsSerial resource_netbox_available_ip_address_test.go:85: Step 1/1 error: Check failed: Check 1/3 error: netbox_available_ip_address.test1: Attribute 'ip_address' expected "1.1.4.1/24", got "1.1.4.5/24"
=== RUN TestAccNetboxAvailablePrefix_basic resource_netbox_available_prefix_test.go:42: Step 1/2 error: Check failed: Check 1/5 error: netbox_available_prefix.test: Attribute 'prefix' expected "1.1.0.0/25", got "1.1.0.128/25"
=== CONT TestAccNetboxVirtualMachinesDataSource_basic data_source_netbox_virtual_machines_test.go:15: Step 4/5 error: Check failed: Check 1/3 error: data.netbox_virtual_machines.test: Attribute 'vms.#' expected "2", got "7"
=== CONT TestAccNetboxInterfacesDataSource_basic data_source_netbox_interfaces_test.go:16: Step 4/4 error: Check failed: Check 1/2 error: data.netbox_interfaces.test: Attribute 'interfaces.#' expected "1", got "3"
The text was updated successfully, but these errors were encountered: