action #88315
open
Complete the worker container test obtaining the key/secret to complete the connection with the web UI
Added by ilausuch over 3 years ago.
Updated over 3 years ago.
Category:
Feature requests
Description
Problem¶
The ticket https://progress.opensuse.org/issues/80682 test that the worker container starts and try to connect to the web UI. But this connection cannot be completed because there are not existing credentials by default.
Acceptance Criteria¶
- AC1: Create a pair of credentials
- AC2: Set the client.conf with the new credentials and check that the worker connects to the web UI without problems.
- Category set to Feature requests
- Priority changed from Normal to Low
- Target version set to future
Hm, I tend to reject this ticket. Our ACs as defined in #80682 correctly describe what is needed and that does not include the "proper connection", just trying to start and failing as expected. The idea for this ticket is certainly valid but I do not see us realistically progressing in near future for little benefit. Do you agree?
I'm slightly confused... when I suggested a new ticket I was thinking of the openQA support needed here. If there's no way to supply or obtain credentials, we need to add that facility. That should consequently by tested, but I wouldn't have filed a ticket for that.
cdywan wrote:
I'm slightly confused... when I suggested a new ticket I was thinking of the openQA support needed here. If there's no way to supply or obtain credentials, we need to add that facility.
Are you confused about the ticket as reported by ilausuch or my comment?
If we don't want to be further with the container tests this ticket won't be necessary. Next step in the test would be to complete the connection with the web UI using the credentials. But I guess this is already tested on other parts of the test suite and is not necessary to repeat that. For me, the worker container test could be considered completed.
So, I agree with reject this ticket.
okurz wrote:
Are you confused about the ticket as reported by ilausuch or my comment?
My confusion stems from the ticket being about creating credentials and filling in configuration for the existing test.
ilausuch wrote:
If we don't want to be further with the container tests this ticket won't be necessary.
Allow me to rephrase. Is it possible to trivially implement such a test right now without adding new features to openQA?
My understanding was No - please correct me if I'm wrong.
About "Is it possible to trivially implement such a test right now without adding new features to openQA?"
I don't know if there are any way to do this without using the UI. Possible solutions is to run a selenium script to do this, or creating by default credentials if some env variable is set on
Also available in: Atom
PDF