search

UKCloud / maloja

A Python toolkit for use with your VMware cloud. You can survey existing infrastructure and automate the task of building VApps.
Apache License 2.0
2 stars 0 forks source link

Found no Edge Gateway error #19

Closed ptburkis closed 8 years ago

ptburkis commented 8 years ago

When running the surveyor, I get an error saying:

2016-01-04 10:59:30,499 ERROR maloja.surveyor.on_edgeGateway|'NoneType' object has no attribute 'iter' 2016-01-04 10:59:30,500 WARNING maloja.surveyor.on_edgeGateway|Found no Edge Gateway.

tundish commented 8 years ago

Multiple issues here arising from items in the demo environment.

The Edge Gateway in 'Bryce (IL0-DEVTEST-BASIC)' is called 'nft001a4i2'. vCloud Director GUI shows it has System Alerts.

SourceIPs and DestinationIPs in the Firewall rules are set to 'internal' and 'external' and yet these are not documented as permitted values:

Type:
    FirewallIpAddressType
Namespace:
    http://www.vmware.com/vcloud/v1.5
Description:
    A valid IPv4 address or "Any".

Maloja log reports this as:

2016-01-18 09:29:29,561 ERROR   maloja.surveyor.on_edgeGateway|'external' does not appear to be an IPv4 or IPv6 network
tundish commented 8 years ago

Found a single example of the following: no Edge Gateway appears in the Query results:

2016-01-18 09:23:47,728 ERROR   maloja.surveyor.on_edgeGateway|
2016-01-18 09:23:47,728 WARNING maloja.surveyor.on_edgeGateway|Found no Edge Gateway.
2016-01-18 09:23:47,744 DEBUG   maloja.surveyor.on_edgeGateway|<?xml version="1.0" encoding="UTF-8"?>
<QueryResultRecords xmlns="http://www.vmware.com/vcloud/v1.5" name="edgeGateway" page="1" pageSize="25" total="0" href="https://api.vcd.portal.skyscapecloud.com/api/admin/vdc/e5338dd8-eb94-46e2-a7aa-d59f29338a6d/edgeGateways?page=1&amp;pageSize=25&amp;format=records" type="application/vnd.vmware.vcloud.query.records+xml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.vmware.com/vcloud/v1.5 http://10.10.6.15/api/v1.5/schema/master.xsd">
    <Link rel="alternate" href="https://api.vcd.portal.skyscapecloud.com/api/admin/vdc/e5338dd8-eb94-46e2-a7aa-d59f29338a6d/edgeGateways?page=1&amp;pageSize=25&amp;format=references" type="application/vnd.vmware.vcloud.query.references+xml"/>
    <Link rel="alternate" href="https://api.vcd.portal.skyscapecloud.com/api/admin/vdc/e5338dd8-eb94-46e2-a7aa-d59f29338a6d/edgeGateways?page=1&amp;pageSize=25&amp;format=idrecords" type="application/vnd.vmware.vcloud.query.idrecords+xml"/>
</QueryResultRecords>

This is consistent with the facts since no Edge Gateway appears in the vCloud Director GUI either.

vDC in question is Skyscape Test (IL0-PROD-BASIC) in Demo Org.

tundish commented 8 years ago

Concluding that no code change is necessary. The messages in the logs accurately describe the situation in the environment. Error handling is robust; survey continues to VApps and Vms in the vDC.