Skip to content
This repository was archived by the owner on Feb 8, 2021. It is now read-only.
This repository was archived by the owner on Feb 8, 2021. It is now read-only.

Hyperd reported wrong IPs after pod has been restarted #468

Closed
@feiskyer

Description

@feiskyer

The pod IP is remaining old one after pod has been restarted:

hyperctl exec 06a17596ae1a796da5cb5d7dc02bdb5c72840ee6879d906db8ec49692499fe64 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:ac:23:1b:7a brd ff:ff:ff:ff:ff:ff
    inet 192.168.140.9/24 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:acff:fe23:1b7a/64 scope link
       valid_lft forever preferred_lft forever

echo -e "GET /pod/info?podName=xxxxxx HTTP/1.0\r\n" | socat unix-connect:/var/run/hyper.sock STDIO
HTTP/1.0 200 OK
Content-Type: application/json
Server: Docker/library-import (linux)
Date: Tue, 13 Dec 2016 06:32:27 GMT

...
"podIP":["192.168.140.8"]
...

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions