Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix neutron-api-plugin-ovn's num-expected-units #598

Merged
merged 1 commit into from Jul 5, 2021

Conversation

lourot
Copy link
Contributor

@lourot lourot commented Jul 5, 2021

After zaza#451 Zaza's application readiness detection
has been improved, which now exposes issues from the
past that were hidden. In other words, we were relying
on a bug on Zaza's side and need to get this straight.

Gerrit review making use of this: https://review.opendev.org/c/openstack/charm-neutron-gateway/+/799443

After zaza#451 Zaza's application readiness detection
has been improved, which now exposes issues from the
past that were hidden. In other words, we were relying
on a bug on Zaza's side and need to get this straight.
Copy link
Collaborator

@ChrisMacNaughton ChrisMacNaughton left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@ChrisMacNaughton ChrisMacNaughton merged commit 6561151 into master Jul 5, 2021
@lourot lourot deleted the lourot/plugin-ovn-expected-units branch July 5, 2021 12:16
openstack-mirroring pushed a commit to openstack/charm-neutron-gateway that referenced this pull request Jul 5, 2021
Fix Zaza's expected application status after
openstack-charmers/zaza#451

Change-Id: I1a6f1316817a444d9cb82a4bc7e57d832a921eae
func-test-pr: openstack-charmers/zaza-openstack-tests#598
openstack-mirroring pushed a commit to openstack/openstack that referenced this pull request Jul 5, 2021
* Update charm-neutron-gateway from branch 'master'
  to 1cc3eba140116c80443c024ebfd09358b98f395a
  - Fix Zaza deployment expectations
    
    Fix Zaza's expected application status after
    openstack-charmers/zaza#451
    
    Change-Id: I1a6f1316817a444d9cb82a4bc7e57d832a921eae
    func-test-pr: openstack-charmers/zaza-openstack-tests#598
@ajkavanagh
Copy link
Contributor

FYI, the other way of doing this is just to delete the 'num-expected-units' key if it is present; this way it will mean 'at least one unit of x' rather than '1 unit of x exactly'. Maybe the key should have been "expect-units" and be a boolean??

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.

None yet

3 participants