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

[TC_24] App deployment on NebulOuS-managed node fails due to lack of resources #45

Open
jchmielewska opened this issue Sep 4, 2024 · 1 comment
Assignees
Labels
failed Test Case failed Test-Case Description of the Test Case

Comments

@jchmielewska
Copy link

Objective

  • Test if sufficient debug information is provided when an APP deployment fails due to lack of resources to deploy it.

Preconditions

  • NebulOuS core is running.
  • A NebulOuS cloud provider is registered in NebulOuS.
  • User has appropriate access rights to deploy APPs in NebulOuS.

Steps

  1. Action
  • User registers an application that can’t be deployed using resources from the registered NebulOuS cloud provider for one of the following reasons:
    User doesn’t have permissions to deploy APPs using resources from the cloud provider.
    The cloud provider can’t fulfill the hardware requirements of the application.
    User launches the application.

Expected result

  • NebulOuS tries to allocate new NebulOuS managed node but fails.
  • Sufficient information is provided to the user to identify the problem.

Result
#23

  • Doesn't pass
@jchmielewska jchmielewska added the Test-Case Description of the Test Case label Sep 4, 2024
@Iqqdd99 Iqqdd99 added the bug Something isn't working label Sep 5, 2024
@jchmielewska jchmielewska added failed Test Case failed and removed bug Something isn't working labels Sep 5, 2024
@jchmielewska
Copy link
Author

  • for manual and automatic execution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed Test Case failed Test-Case Description of the Test Case
Projects
None yet
Development

No branches or pull requests

4 participants