search

openbmc / phosphor-networkd

Apache License 2.0
18 stars 49 forks source link

IP configuration is not persistent on Disabling Interface and enabling back. #55

Open swe12345 opened 2 years ago

swe12345 commented 2 years ago

Problem: IP configuration is not persistent on Disabling Interface and enabling it back.

Steps to recreate:

  1. Settings the interface as false using the curl command curl -k -H "X-Auth-Token: $bmc_token" -D get.txt -X PATCH -d '{"InterfaceEnabled":false}' https://$bmc/redfish/v1/Managers/bmc/EthernetInterfaces/eth0

2.Now check the configuration- it is lost- expected

  1. Now Enable the interface back using curl commands curl -k -H "X-Auth-Token: $bmc_token" -D get.txt -X PATCH -d '{"InterfaceEnabled":true}' https://$bmc/redfish/v1/Managers/bmc/EthernetInterfaces/eth0

Expected Results: IP configuration should persist

@sunharis @wak-google

prkatti1 commented 2 years ago

I think changing the state of the interface should not have any impact on existing network settings.

swe12345 commented 2 years ago

@wak-google Any update on this please

wak-google commented 2 years ago

This is expected, it refreshes the interface after it gets disabled which clears out all the IP info. We don't have a way to read IP information outside of what is configured on the interface.

swe12345 commented 2 years ago

Disabling the interface, we should not loose the IP details right @wak-google??

wak-google commented 1 year ago

We do lose them today, AFAICT it will be difficult for us to model a change to this to preserve the details.

sunharis commented 1 year ago

We do lose them today, AFAICT it will be difficult for us to model a change to this to preserve the details.

Yes. @swe12345 Can this issue be closed? This is working as per the design.