action #17366
[sle][functional] Autoyast verify module is failing
100%
Description
Needs more investigation as every job has it's own script for checking
https://openqa.suse.de/tests/790513#step/autoyast_verify/8
https://openqa.suse.de/tests/790515#step/autoyast_verify/8
https://openqa.suse.de/tests/790507#step/autoyast_verify/8
https://openqa.suse.de/tests/790508#step/autoyast_verify/8
https://openqa.suse.de/tests/790510#step/autoyast_verify/8
https://openqa.suse.de/tests/790609#step/autoyast_verify/8
https://openqa.suse.de/tests/790608#step/autoyast_verify/8
Related issues
History
#2
Updated by okurz about 6 years ago
psladek: can you help?
#3
Updated by okurz about 6 years ago
wrote an email to psladek asking for help.
#4
Updated by riafarov almost 6 years ago
- Status changed from New to In Progress
- Assignee set to riafarov
#5
Updated by mkravec almost 6 years ago
I think autoyast-supportserver uses outdated repository
We are solving it with YaST team.
#6
Updated by mkravec almost 6 years ago
I replaced AYTESTS_REPO=http://download.suse.de/ibs/Devel:/YaST:/SLE-12-SP3/SLE_12_SP3/ - verify tests should be greener next run
#7
Updated by okurz almost 6 years ago
great. I added a corresponding comment to the test suite description as well. I am thinking about the alternative to look up the always latest repository from within the scenario's supportserver test code but I guess it's not necessary for now.
#8
Updated by dzedro almost 6 years ago
I work on this autoyast tests:
ftp https://openqa.suse.de/tests/1026186#step/autoyast_verify/7
supportserver https://openqa.suse.de/tests/1027041#step/autoyast_verify/7
#9
Updated by riafarov almost 6 years ago
#10
Updated by SLindoMansilla almost 6 years ago
- Blocks action #20064: [sles][functional][yast] Bring peace and order to autoyast profiles added
#11
Updated by riafarov almost 6 years ago
#13
Updated by dzedro almost 6 years ago
I didn't touch supportserver https://openqa.suse.de/tests/1027041#step/autoyast_verify/7
I worked on ftp https://openqa.suse.de/tests/1026186#step/autoyast_verify/7 and created PR,
with this change ftp was running, but there is still some issue with connecting to ftp.
Listen=NO partially solved the connection problem, but I have no idea if this can be set in .xml,
when I created profile with yast2 auotyast there was this comment:
NOTE: Remember to set both listen and listen_ipv6 to NO in /etc/vsftpd.conf in order to have working xinetd connection.
Imo also wrote ⇩ , but when I created new profile with yast2 autoyast it was very similar as the old (pureftpd) one ...
<imobach> jpupava: fun enough, options in the ftp-server section look like pureftpd option, not vsftpd: https://github.com/yast/yast-ftp-server/blob/558b33913f2875102b81fb1c5c473baa80f14b42/src/include/ftp-server/write_load.rb#L63
<imobach> jpupava: ok, the ftp.xml looks weird because those settings are for pureftpd (which is not available in my SLE 12 SP3)
#14
Updated by riafarov almost 6 years ago
- Target version set to Milestone 9
#15
Updated by riafarov almost 6 years ago
- Subject changed from Autoyast verify module is failing to [sle][functional] Autoyast verify module is failing
#16
Updated by riafarov almost 6 years ago
All tests are fixed now from openQA side, waiting for 4 fixes to get all tests green:
https://bugzilla.suse.com/show_bug.cgi?id=1047232
https://bugzilla.suse.com/show_bug.cgi?id=1046605
https://bugzilla.suse.com/show_bug.cgi?id=1046083
https://bugzilla.suse.com/show_bug.cgi?id=1047646
#17
Updated by riafarov almost 6 years ago
- Status changed from In Progress to Feedback
As of now tests are fixed from openQA side, wait for other bug fixes to get all tests green and proceed with improvements.
#18
Updated by riafarov almost 6 years ago
- Status changed from Feedback to In Progress
Introducing soft-failure for dns tests
#19
Updated by riafarov almost 6 years ago
- Status changed from In Progress to Feedback
No actions required from openQA side ATM.
#20
Updated by riafarov almost 6 years ago
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
Task is accomplished. If something pops up, new ticket should be created.