false change reported since package is not deployed on ost
Description
Activity
Eyal Edri August 21, 2018 at 2:31 PM
open for more than 2 weeks, will reopen if it happens again
Eyal Edri August 21, 2018 at 2:31 PM
I want to start a new policy of closing tickets if we don't get answers for 2 weeks or the issue isn't happening for 2 weeks.
Otherwise we'll be swamped with tickets.
If a race happens again, you can search for it in JIRA with ost_race to check if it happened in the past before opening a new ticket.
Dafna Ron June 12, 2018 at 10:24 AM
I did not keep the original build.
will leave open until we see this again.
Barak Korren June 3, 2018 at 10:04 AM
track which test is failing - its probably failing sporadically on various occasions.
Dafna Ron May 31, 2018 at 11:41 AM
Barak, any advice on how to start investigating this?
Barak Korren May 25, 2018 at 7:17 AM
Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere?
If its being used you will see in installed in the 'deploy' phase, or by engins-setup or during AddHost.
The interesting thing here is why did the CQ test fail if the patch is not being actually tested.
Details
Assignee
infrainfraReporter
Dafna RonDafna Ron(Deactivated)Priority
Medium
Details
Details
Assignee
infraReporter
Dafna RonPriority
Medium
Change 91507,1 (ovirt-engine-sdk-java) is probably the reason behind recent
system test failures in the "ovirt-master" change queue and needs to be fixed.
This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.
For further details about the change see:
https://gerrit.ovirt.org/#/c/91507/1
For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/
The package is not deployed on OST so it could not have been the reason for failure.
+ I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report.
Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere?