Page MenuHomeVyOS Platform

Migration to latest rolling fails with vyos.configtree.ConfigTreeError: Path [b'interfaces bridge br0 igmp-snooping querier'] doesn't exist
Closed, ResolvedPublic

Description

Migrating from 1.2.0-rolling+201906210337 to 1.2-rolling-201908240337 fails:

Aug 24 20:48:04 debian vyos-router[867]: Starting VyOS router: migrateTraceback (most recent call last):
Aug 24 20:48:04 debian vyos-router[867]: File "/opt/vyatta/etc/config-migrate/migrate/interfaces/0-to-1", line 41, in <module>
Aug 24 20:48:04 debian vyos-router[867]: igmp_val = config.return_value(base + [br, 'igmp-snooping', 'querier'])
Aug 24 20:48:04 debian vyos-router[867]: File "/usr/lib/python3/dist-packages/vyos/configtree.py", line 275, in return_value
Aug 24 20:48:04 debian vyos-router[867]: raise ConfigTreeError("Path [{}] doesn't exist".format(path_str))
Aug 24 20:48:04 debian vyos-router[867]: vyos.configtree.ConfigTreeError: Path [b'interfaces bridge br0 igmp-snooping querier'] doesn't exist
Aug 24 20:48:04 debian vyos-router[867]: Called process error: Command '['/opt/vyatta/etc/config-migrate/migrate/interfaces/0-to-1', '/opt/vyatta/etc/config/config.boot']' returned non-zero exit status 1.

Details

Difficulty level
Unknown (require assessment)
Version
1.2-rolling-201908240337
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Bug (incorrect behavior)

Event Timeline

jjakob created this object in space S1 VyOS Public.

vyos-1x src/migration-scripts/interfaces/0-to-1 line 41:
https://github.com/vyos/vyos-1x/blob/2f3aa28f259ee7f23ef8a4a091db8ced2202bbd8/src/migration-scripts/interfaces/0-to-1#L41:

# igmp-snooping: check if enabled
igmp_val = config.return_value(base + [br, 'igmp-snooping', 'querier'])

This should be preceded by a if config.exists, as should line 33:

    # STP: check if enabled
        stp_val = config.return_value(base + [br, 'stp'])
`
c-po reassigned this task from c-po to jjakob.
c-po added a subscriber: c-po.
erkin set Is it a breaking change? to Unspecified (possibly destroys the router).Aug 31 2021, 6:57 PM
erkin set Issue type to Bug (incorrect behavior).