Skip to content

Networking / routers: Allow updating routers, without specifying the static routes#2043

Merged
jtopjian merged 3 commits intogophercloud:masterfrom
stefreak:master
Oct 31, 2020
Merged

Networking / routers: Allow updating routers, without specifying the static routes#2043
jtopjian merged 3 commits intogophercloud:masterfrom
stefreak:master

Conversation

@stefreak
Copy link
Copy Markdown
Contributor

@stefreak stefreak commented Oct 26, 2020

This is helpful when it is necessary to rename a router,
but it is not desired by the user to touch the static routes.

The OpenStack API just allows to omit the static routes (e.g.
verifyable with openstack router set --name new_name --debug).

This change makes sure that static routes parameter can be omitted with
gophercloud as well.

Also added a unit test.

For #2044

Links to the line numbers/files in the OpenStack source code that support the
code in this PR:

(I could not find a specific line of code, but provided the openstack CLI command for quick verification that this works above)

This is helpful when it is necessary to rename a router,
but it is not desired by the user to touch the static routes.

The OpenStack API just allows to omit the static routes (e.g.
verifyable with `openstack router set --name new_name --debug`).

This change makes sure that static routes parameter can be omitted with
gophercloud as well.

Also added a unit test.
@stefreak stefreak changed the title Allow updating routers, without specifying the static routes Networkingv2 / routers: Allow updating routers, without specifying the static routes Oct 26, 2020
@stefreak stefreak changed the title Networkingv2 / routers: Allow updating routers, without specifying the static routes Networking / routers: Allow updating routers, without specifying the static routes Oct 26, 2020
@coveralls
Copy link
Copy Markdown

coveralls commented Oct 26, 2020

Coverage Status

Coverage remained the same at 79.585% when pulling 47ec05e on stefreak:master into 0e6f9ce on gophercloud:master.

@theopenlab-ci
Copy link
Copy Markdown

theopenlab-ci bot commented Oct 26, 2020

Build failed.

@jtopjian
Copy link
Copy Markdown
Contributor

recheck

@theopenlab-ci
Copy link
Copy Markdown

theopenlab-ci bot commented Oct 26, 2020

Build failed.

@stefreak
Copy link
Copy Markdown
Contributor Author

I also noticed that the documentation needed an update.
Also, I simplified the unit test.

@jtopjian I am not sure how I can see what fails in the acceptance test – or is it just flaky? Thanks for sending the retest command ;)

@jtopjian
Copy link
Copy Markdown
Contributor

@stefreak The full suite usually takes 2-3 hours, so 1.5hrs may be pointing to an issue with OpenLab. It happens from time to time. Let's give it a day and if it's still failing, I'll open a ticket.

If I get some time, I'll run the tests in devstack to confirm if any of them need updating from this change.

@theopenlab-ci
Copy link
Copy Markdown

theopenlab-ci bot commented Oct 26, 2020

Build failed.

@stefreak
Copy link
Copy Markdown
Contributor Author

recheck

@theopenlab-ci
Copy link
Copy Markdown

theopenlab-ci bot commented Oct 27, 2020

Build failed.

@jtopjian
Copy link
Copy Markdown
Contributor

From the logs, it looks like the devstack installation is not completing successfully. I'll give it one more try and then open a ticket.

@jtopjian
Copy link
Copy Markdown
Contributor

recheck

@theopenlab-ci
Copy link
Copy Markdown

theopenlab-ci bot commented Oct 28, 2020

Build succeeded.

Copy link
Copy Markdown
Contributor

@jtopjian jtopjian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants