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

ui: Bugfix salt redux store #3477

Merged
merged 2 commits into from
Aug 5, 2021
Merged

Conversation

JBWatenbergScality
Copy link
Contributor

Component:

ui

Context:

After playing with node deployment feature on the UI I spot several bugs that this PR is fixing.

Summary:

  • Use of a wrong redux saga function for calling selectors
  • Buggy error handling when a salt Job does not exist

…lting in the state parameter to be null and failling to proceed. This commit replace call by select which is the right function to call for selectors
While working on the UI I met the following error :

```
TypeError: Cannot read property 'return' of undefined
    at getJobStatusFromPrintJob (utils.js:89)
    at refreshJobStatus$ (salt.js:188)
```

This is due to the fact that salt API was returning an empty object in `Result`.

Below  is the row result given by salt API.

```json
{
  "return": [
    {
      "20210802092226728983": {
        "Error": "Cannot contact returner or no job with this jid",
        "StartTime": "2021, Aug 02 09:22:26.728983",
        "Result": {}
      }
    }
  ]
}

This commit is checking wether the `Result` object is empty before trying to parse the error.

```
@JBWatenbergScality JBWatenbergScality requested a review from a team as a code owner August 4, 2021 13:16
@bert-e
Copy link
Contributor

bert-e commented Aug 4, 2021

Hello jbwatenbergscality,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Aug 4, 2021

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

@JBWatenbergScality JBWatenbergScality changed the base branch from development/2.11 to development/2.10 August 4, 2021 13:16
@bert-e
Copy link
Contributor

bert-e commented Aug 4, 2021

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Aug 4, 2021

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

@JBWatenbergScality
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Aug 4, 2021

Build failed

The build for commit did not succeed in branch w/2.11/bugfix/salt-error-management.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Aug 4, 2021

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/2.10

  • ✔️ development/2.11

The following branches will NOT be impacted:

  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Aug 5, 2021

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/2.10

  • ✔️ development/2.11

The following branches have NOT changed:

  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

Please check the status of the associated issue None.

Goodbye jbwatenbergscality.

@bert-e bert-e merged commit 0152295 into development/2.10 Aug 5, 2021
@bert-e bert-e deleted the bugfix/salt-error-management branch August 5, 2021 14:37
gdemonet added a commit that referenced this pull request Aug 5, 2021
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