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

"Not Available" Client ID When Device Deleted Before Adding It To a Job #2221

Closed
LeoNerdoG opened this issue Nov 30, 2018 · 4 comments
Closed
Assignees
Labels
Bug This is a bug or an unexpected behaviour. Fix it! Console GWT This issue/PR is related to Admin Web Console

Comments

@LeoNerdoG
Copy link
Contributor

If user deletes a device just before it is added as a target to a job, Kapua adds the device anyway and the name of the device is "No available" (look at the screenshot).

Testflow:

  1. Login as kapua-sys or any other user that has proper permissions
  2. Go to Devices, add a device (e.g. device0)
  3. Go to Jobs create a job (e.g. job0) and go to its Target tab, click Add
  4. Now open kapua in new browser (e.g. Chrome or Opera), login as kapua-sys and go to Devices.
  5. Select device0 and delete it.
  6. Now go back to the first browser and try to add the deleted device.

Expected behavior
Kapua should close the Add Targets window and report that "device is not available/missing" or soemthing similar.

Screenshots
screenshot 2018-11-30 at 09 40 02

Version of Kapua
1.1.0-SNAPSHOT

Type of deployment
[ ] Local Vagrant deployment
[x] Docker
[ ] Openshift (in its variants)
[ ] Others

Main component affected
[x] Console (in case of console please report info on which browser you encountered the problem)
[ ] REST API
[ ] Message Broker
[ ] - Others

Browsers used:

  • Google Chrome (Version 69.0.3497.100 (Official Build) (64-bit))
  • Safari (Version 12.0 (13604.3.5))
  • Mozilla Firefox (63.0 (64-bit))
  • Opera (Version 55.0.2994.44)
@Coduz Coduz added Bug This is a bug or an unexpected behaviour. Fix it! Console GWT This issue/PR is related to Admin Web Console labels Nov 30, 2018
@muros-ct muros-ct self-assigned this Dec 5, 2018
@LeoNerdoG
Copy link
Contributor Author

I have checked status of this issue in latest develop but it seems that it has not been fixed - @lorthirk, @muros-ct can you check on your side please?
I have successfully reproduced this issue on two different machines (2 Firefox browsers, 2 Opera browsers) on latest develop.

@LeoNerdoG
Copy link
Contributor Author

@lorthirk @muros-ct
I have rebuild the develop branch once again and now I get the following error if I just go to Jobs -> Targets:
screenshot 2019-01-07 at 09 49 05

Can you check on your side if you can encounter this issue?

@lorthirk
Copy link

lorthirk commented Jan 7, 2019

It seems to work for me...

Chrome 71.0.3578.98 on MacOS 10.14.2

schermata 2019-01-07 alle 10 13 02

@LeoNerdoG
Copy link
Contributor Author

Hey,
It looks like there was a problem on my side. After clearing caches, history, rebooting machine, rebulding project and deployin again everything works fine. I am closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug This is a bug or an unexpected behaviour. Fix it! Console GWT This issue/PR is related to Admin Web Console
Projects
None yet
Development

No branches or pull requests

4 participants