1
81%
develop: 81%

Ran 06 May 2020 11:04AM UTC

Files 0

Run time 0s

Badge

Embed ▾

Committed 06 May 2020 11:03AM UTC coverage: 0.0%. Remained the same

Job # TOXENV=black

Build Type

push

travis-ci

Committed by

web-flow

Commit Message

SRX cluster devices stack RPC replies under multi-routing-engine-results (#1196)

The usual replies look like:

```
mircea@switch> show chassis environment | display xml
<rpc-reply xmlns:junos="http://xml.juniper.net/junos/15.1X49/junos">
    <environment-information xmlns="http://xml.juniper.net/junos/15.1X49/junos-chassis">
    ...
    </environment-information>
</rpc-reply>
```

On SRX multi-node devices, the reply is encapsulated under the
``<multi-routing-engine-results><multi-routing-engine-item>`` tags,
e.g.,

```
mircea@srx> show chassis environment | display xml
<rpc-reply xmlns:junos="http://xml.juniper.net/junos/15.1X49/junos">
    <multi-routing-engine-results>
        <multi-routing-engine-item>
            <re-name>node0</re-name>
            <environment-information xmlns="http://xml.juniper.net/junos/15.1X49/junos-chassis">
            ...
            </environment-information>
        </multi-routing-engine-item>
    </multi-routing-engine-results>
</rpc-reply>
```

The same goes for other RPC calls such as
``get-route-engine-information`` or
``get-temperature-threshold-information``.

Fixes #1183. Partially, at least, as the ``get_environment`` structure
doesn't currently permit a multi-node structure, so on SRX clusters it
will only return the details for the primary node.

Run Details

0 of 0 relevant lines covered (NaN%)

0.0 hits per line

napalm-automation / napalm / 2956 / 1
81%
develop: 81%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 2956.1 (TOXENV=black)

napalm-automation / napalm / 2956 / 1 81% develop: 81%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 2956.1 (TOXENV=black)

napalm-automation / napalm / 2956 / 1
81%
develop: 81%

README BADGES
x