| 2024-02-13 22:26:42 |
Ferran Diego Andilla |
bug |
|
|
added bug |
| 2024-02-14 08:37:06 |
Joanna Chmielewska |
tags |
|
test-case-r.1.0 |
|
| 2024-05-21 09:36:04 |
Joanna Chmielewska |
nebulous: assignee |
|
Francisco Álvarez Terribas (franciscoat) |
|
| 2024-05-21 15:38:52 |
Francisco Álvarez Terribas |
description |
Objective
Validate that sufficient feedback is given to the user when the process of onboarding a manually-managed node fails.
Preconditions
A NebulOuS core installation is up and running. It’s IP is known.
Two users exists:
Device owner: A user with “device owner” role in NebulOuS.
Resource manager: A user with “resource manager” role in NebulOuS.
A machine WITHOUT the minimum requirements for NebulOuS agent is available. NebulOuS has network visibility over it. A pair of SSH keys of the machine linked with a user account with appropriate rights to install new software are known by the user “device owner”.
Steps
Step 1
Action
User “device owner” logs in to NebulOuS and fills in a device registration request as described in XXX. It provides a device Id, the public IP and the SSH keys. Some of the provided values are intentionally invalid.
Expected results
A device registration request is created.
NebulOuS tries to collect the device capabilities but fails due to the invalid parameters provided.
Device owner and resource manager are informed about the status of the process. Relevant error logs are collected and made can be seen by these users.
Step 2
Action
User “device owner” logs in to NebulOuS and fills in a device registration request as described in XXX. It provides a device Id, the public IP and the SSH keys.
Expected results
A device registration request is created.
NebulOuS tries to collect the device capabilities but fails due to the device not meeting the requirements for installing the NebulOuS agent.
Device owner and resource manager are informed about the status of the process. Relevant error logs are collected and made can be seen by these users. |
Objective
Validate that sufficient feedback is given to the user when the process of onboarding a manually-managed node fails.
Preconditions
A NebulOuS core installation is up and running. It’s IP is known.
Two users exists:
Device owner: A user with “device owner” role in NebulOuS.
Resource manager: A user with “resource manager” role in NebulOuS.
A machine WITHOUT the minimum requirements for NebulOuS agent is available. NebulOuS has network visibility over it. A pair of SSH keys of the machine linked with a user account with appropriate rights to install new software are known by the user “device owner”.
Steps
Step 1
Action
User “device owner” logs in to NebulOuS and fills in a device registration request as described in XXX. It provides a device Id, the public IP and the SSH keys. Some of the provided values are intentionally invalid.
Expected results
A device registration request is created.
NebulOuS tries to collect the device capabilities but fails due to the invalid parameters provided.
Device owner and resource manager are informed about the status of the process. Relevant error logs are collected and made can be seen by these users.
Step 2
Action
User “device owner” logs in to NebulOuS and fills in a device registration request as described in XXX. It provides a device Id, the public IP and the SSH keys.
Expected results
A device registration request is created.
NebulOuS tries to collect the device capabilities but fails due to the device not meeting the requirements for installing the NebulOuS agent.
Device owner and resource manager are informed about the status of the process. Relevant error logs are collected and made can be seen by these users.
Result
Doesn't pass |
|
| 2024-05-21 15:39:04 |
Francisco Álvarez Terribas |
description |
Objective
Validate that sufficient feedback is given to the user when the process of onboarding a manually-managed node fails.
Preconditions
A NebulOuS core installation is up and running. It’s IP is known.
Two users exists:
Device owner: A user with “device owner” role in NebulOuS.
Resource manager: A user with “resource manager” role in NebulOuS.
A machine WITHOUT the minimum requirements for NebulOuS agent is available. NebulOuS has network visibility over it. A pair of SSH keys of the machine linked with a user account with appropriate rights to install new software are known by the user “device owner”.
Steps
Step 1
Action
User “device owner” logs in to NebulOuS and fills in a device registration request as described in XXX. It provides a device Id, the public IP and the SSH keys. Some of the provided values are intentionally invalid.
Expected results
A device registration request is created.
NebulOuS tries to collect the device capabilities but fails due to the invalid parameters provided.
Device owner and resource manager are informed about the status of the process. Relevant error logs are collected and made can be seen by these users.
Step 2
Action
User “device owner” logs in to NebulOuS and fills in a device registration request as described in XXX. It provides a device Id, the public IP and the SSH keys.
Expected results
A device registration request is created.
NebulOuS tries to collect the device capabilities but fails due to the device not meeting the requirements for installing the NebulOuS agent.
Device owner and resource manager are informed about the status of the process. Relevant error logs are collected and made can be seen by these users.
Result
Doesn't pass |
Objective
Validate that sufficient feedback is given to the user when the process of onboarding a manually-managed node fails.
Preconditions
A NebulOuS core installation is up and running. It’s IP is known.
Two users exists:
Device owner: A user with “device owner” role in NebulOuS.
Resource manager: A user with “resource manager” role in NebulOuS.
A machine WITHOUT the minimum requirements for NebulOuS agent is available. NebulOuS has network visibility over it. A pair of SSH keys of the machine linked with a user account with appropriate rights to install new software are known by the user “device owner”.
Steps
Step 1
Action
User “device owner” logs in to NebulOuS and fills in a device registration request as described in XXX. It provides a device Id, the public IP and the SSH keys. Some of the provided values are intentionally invalid.
Expected results
A device registration request is created.
NebulOuS tries to collect the device capabilities but fails due to the invalid parameters provided.
Device owner and resource manager are informed about the status of the process. Relevant error logs are collected and made can be seen by these users.
Step 2
Action
User “device owner” logs in to NebulOuS and fills in a device registration request as described in XXX. It provides a device Id, the public IP and the SSH keys.
Expected results
A device registration request is created.
NebulOuS tries to collect the device capabilities but fails due to the device not meeting the requirements for installing the NebulOuS agent.
Device owner and resource manager are informed about the status of the process. Relevant error logs are collected and made can be seen by these users.
Result
Doesn't pass https://bugs.launchpad.net/nebulous/+bug/2065319 |
|
| 2024-05-21 15:39:13 |
Francisco Álvarez Terribas |
nebulous: status |
New |
Confirmed |
|
