networking-ovn-migration-mtu output is confusing during ovn_migration.sh reduce-mtu call

Bug #1814824 reported by Miguel Angel Ajo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-ovn
Fix Released
Undecided
Miguel Angel Ajo

Bug Description

See the arrow, that makes the admin believe that it needs to run that command manually, while in fact ovn_migration.sh will handle it for himself.

(overcloud) [stack@undercloud ovn_migration]$ ovn_migration.sh reduce-mtu
Verifying the tenant network mtu's
adapted_mtu tag is not set for the Network [HA network tenant 5445e312e3804c30aa4bdd6851339aa2]
adapted_mtu tag is not set for the Network [net1]

Please run : "/usr/bin/networking-ovn-migration-mtu update mtu" before starting the migration migration to OVN <------

Updating the tenant network mtu
Updating the mtu and the tag 'adapted_mtu of the network - HA network tenant 5445e312e3804c30aa4bdd6851339aa2
Updating the mtu and the tag 'adapted_mtu of the network - net1

Changed in networking-ovn:
assignee: nobody → Miguel Angel Ajo (mangelajo)
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-ovn (master)

Fix proposed to branch: master
Review: https://review.openstack.org/635042

Changed in networking-ovn:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovn (master)

Reviewed: https://review.openstack.org/635042
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=b6a9d3d5a3717411ee2c9e939cd28b4952cc2b57
Submitter: Zuul
Branch: master

commit b6a9d3d5a3717411ee2c9e939cd28b4952cc2b57
Author: Miguel Angel Ajo <email address hidden>
Date: Tue Feb 5 16:10:51 2019 -0500

    Make networking-ovn-migration-mtu output less confusing

    When called fron ovn_migration.sh the output seems confusing and
    makes it look like the admin still has to go and do something on the
    command line, while in fact ovn_migration.sh will handle it.

    Closes-Bug: 1814824

    Change-Id: I549e23135ead0332e4e92c1044d20f64e20d1106

Changed in networking-ovn:
status: In Progress → Fix Released
tags: added: networking-ovn-proactive-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-ovn (stable/rocky)

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/641296

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovn (stable/rocky)

Reviewed: https://review.openstack.org/641296
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=d5a71d47328c3f6279afa5c627568f0e667fb2bf
Submitter: Zuul
Branch: stable/rocky

commit d5a71d47328c3f6279afa5c627568f0e667fb2bf
Author: Miguel Angel Ajo <email address hidden>
Date: Tue Feb 5 16:10:51 2019 -0500

    Make networking-ovn-migration-mtu output less confusing

    When called fron ovn_migration.sh the output seems confusing and
    makes it look like the admin still has to go and do something on the
    command line, while in fact ovn_migration.sh will handle it.

    Closes-Bug: 1814824

    Change-Id: I549e23135ead0332e4e92c1044d20f64e20d1106
    (cherry picked from commit b6a9d3d5a3717411ee2c9e939cd28b4952cc2b57)

tags: added: in-stable-rocky
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-ovn 6.0.0.0b1

This issue was fixed in the openstack/networking-ovn 6.0.0.0b1 development milestone.

tags: removed: networking-ovn-proactive-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-ovn 5.1.0

This issue was fixed in the openstack/networking-ovn 5.1.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.