Welcome to the new Linux Foundation Forum!

"clean" doesn't clean up

Following up on my other post I want to note that the provided scripts in the devstack distribution aren't of much help. I tried to "unstack.sh" followed by "clean.sh" but the configuration is still far from clean. For instance the eth2 interface no longer has an IPv4 address, but there's a br100 (bridge?) interface with severall IPv4 addresses:

4: eth2: mtu 1500 qdisc pfifo_fast master br100 state UP group default qlen 1000

link/ether bc:76:4e:06:31:e8 brd ff:ff:ff:ff:ff:ff

inet6 fe80::be76:4eff:fe06:31e8/64 scope link

valid_lft forever preferred_lft forever

5: virbr0: mtu 1500 qdisc noqueue state DOWN group default

link/ether ca:76:f7:45:ce:1f brd ff:ff:ff:ff:ff:ff

inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0

valid_lft forever preferred_lft forever

6: br100: mtu 1500 qdisc noqueue state UP group default

link/ether bc:76:4e:06:31:e8 brd ff:ff:ff:ff:ff:ff

inet 10.10.129.255/20 brd 10.10.143.255 scope global br100

valid_lft forever preferred_lft forever

inet 192.168.97.1/24 brd 192.168.97.255 scope global br100

valid_lft forever preferred_lft forever

inet 192.168.100.129/32 scope global br100

valid_lft forever preferred_lft forever

inet6 fe80::d46d:cdff:fe71:4326/64 scope link

valid_lft forever preferred_lft forever

So I guess there's no other option than to restart the whole lab environment.

Comments

  • serewiczserewicz Posts: 514
    The clean.sh script and the unstack.sh script have been created and maintained by the OpenStack foundation and contributors to DevStack.org. It does not undo the network configuration you mention.

    The quickest way to return to a starting point would be to use the "Start Over" button provided.
Sign In or Register to comment.