May 2018 - Infra - oVirt List Archives

Checking out latest notifications on JIRA
by Eyal Edri 09 May '18

09 May '18

Hi, I just noticed a page I missed before on jira.ovirt.org, just because I'm always using the dashboard. You can check https://ovirt-jira.atlassian.net/home/notifications directly to see if you have any notification on cards you're cc'd or assigned to, which is pretty nice and fast to check status on your tickets. -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

[JIRA] (OVIRT-2004) opening ticket through infra-support@ovirt.org doesn't work anymore
by Marc Dequènes (Duck) (oVirt JIRA) 09 May '18

09 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2004?page=com.atlassian.jira.… ] Marc Dequènes (Duck) commented on OVIRT-2004: --------------------------------------------- I see 2-3 new mails in the inbox, so they are delivered, but for some reason JIRA does not fetch them. I looked this morning and found nothing. I just rechecked and found one strange thing: a '/var/mail/%u' directory has been created, so it seems %u is not properly interpreted by Dovecot for some reason. I will check after diner. > opening ticket through infra-support(a)ovirt.org doesn't work anymore > ------------------------------------------------------------------- > > Key: OVIRT-2004 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2004 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: General > Reporter: sbonazzo > Assignee: infra > Priority: Highest > > Tried to open a ticket this morning with subject: [outage] resources.ovirt.org https is not working anymore > but it didn't get created in jira. I had to open it manually. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

Jsonrpc version bump for master and 4.2.4
by Piotr Kliczewski 09 May '18

09 May '18

Hi, I would like to push a patch to update releng-tools repo with correct version but I do not see 4.2.4 files yet. Should I create it? Thanks, Piotr

2 4

Rerun-hooks doesn't work
by Tal Nisan 09 May '18

09 May '18

The Rerun-hooks: all used to rerun the hooks after changing something in the commit message doesn't work for a few months now and it's quite needed

2 1

Disable/remove HE 4.1 jobs?
by Eyal Edri 09 May '18

09 May '18

Should we disable or remove the 4.1 jobs from upstream? On Sun, May 6, 2018 at 11:55 AM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic- > suite-4.1/ > Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic- > suite-4.1/373/ > Build Number: 373 > Build Status: Still Failing > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #364 > [Eyal Edri] update the default template to autogenerate tool > > > Changes for Build #365 > [Eyal Edri] update the default template to autogenerate tool > > > Changes for Build #366 > [Eyal Edri] update the default template to autogenerate tool > > > Changes for Build #367 > [Eyal Edri] update the default template to autogenerate tool > > > Changes for Build #368 > [Eyal Edri] update the default template to autogenerate tool > > > Changes for Build #369 > [Eyal Edri] update the default template to autogenerate tool > > > Changes for Build #370 > [Eyal Edri] update the default template to autogenerate tool > > > Changes for Build #371 > [Eyal Edri] update the default template to autogenerate tool > > > Changes for Build #372 > [Eyal Edri] update the default template to autogenerate tool > > > Changes for Build #373 > [Eyal Edri] update the default template to autogenerate tool > > > > > ----------------- > Failed Tests: > ----------------- > No tests ran. > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

4 14

[oVirt Jenkins] ovirt-node-ng_4.1_build-artifacts-el7-x86_64 - Build # 57 - Failure!
by jenkins＠jenkins.phx.ovirt.org 09 May '18

09 May '18

------=_Part_499_817438584.1525335938512 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_4.1_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_4.1_build-artifacts-el7-x86_64/5… Build Number: 57 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #57 [Sandro Bonazzola] ovirt-engine: add 4.2.3 branch jobs [Barak Korren] Add support for fc28 on x86_64 and x390x [Evgheni Dereveanchin] Create fc28 mirror jobs [Ryan Barry] image-update: fail upgrades if there is a local storage domain on / ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_499_817438584.1525335938512--

1 6

[oVirt Jenkins] ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 46 - Failure!
by jenkins＠jenkins.phx.ovirt.org 09 May '18

09 May '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-… Build Number: 46 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #46 [Evgheni Dereveanchin] Ensure nested KVM is enabled from global_setup [Daniel Belenky] Update legend table of manual OST [Emil Natan] refactor formatters code [Barak Korren] Add jobs for 'jniederm' user on GitHub [Gal Ben Haim] lago: Add fc28 build, drop fc26 build [Yuval Turgeman] Revert "Test building with ansible25" ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2006) Investigate google chrome not being able to access ovirt.org sites
by Anton Marchukov (oVirt JIRA) 09 May '18

09 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2006?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2006: -------------------------------------- Assignee: Anton Marchukov (was: infra) > Investigate google chrome not being able to access ovirt.org sites > ------------------------------------------------------------------ > > Key: OVIRT-2006 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2006 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: sbonazzo > Assignee: Anton Marchukov > > Since May 8th, everything is redirecting to https on ovirt.org at least using google chrome, so with google chrome can't access any .ovirt.org server. > Not sure what happened, but a workaround that helped me is: > - open chrome://net-internals/#hsts > - go to "Delete domain security policies" section > - enter "ovirt.org" and hit "Delete" > Note that this doesn't depend on a recent google chrome update. > Last update of chrome on my system is: > google-chrome-stable-66.0.3359.139-1.x86_64 mer 02 mag 2018 07:52:00 CEST > And it worked fine until May 7th 2018, broken yesterday, May 8th 2018. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2006) Investigate google chrome not being able to access ovirt.org sites
by Anton Marchukov (oVirt JIRA) 09 May '18

09 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2006?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2006: ---------------------------------------- [~duck] I think ovirt.org is currently in the community cage? Can you check why HSTS got enabled and disable in ASAP if possible for now? > Investigate google chrome not being able to access ovirt.org sites > ------------------------------------------------------------------ > > Key: OVIRT-2006 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2006 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: sbonazzo > Assignee: infra > > Since May 8th, everything is redirecting to https on ovirt.org at least using google chrome, so with google chrome can't access any .ovirt.org server. > Not sure what happened, but a workaround that helped me is: > - open chrome://net-internals/#hsts > - go to "Delete domain security policies" section > - enter "ovirt.org" and hit "Delete" > Note that this doesn't depend on a recent google chrome update. > Last update of chrome on my system is: > google-chrome-stable-66.0.3359.139-1.x86_64 mer 02 mag 2018 07:52:00 CEST > And it worked fine until May 7th 2018, broken yesterday, May 8th 2018. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2006) Investigate google chrome not being able to access ovirt.org sites
by sbonazzo (oVirt JIRA) 09 May '18

09 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2006?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-2006: --------------------------------- I would then prioritize providing https access everywhere ASAP. > Investigate google chrome not being able to access ovirt.org sites > ------------------------------------------------------------------ > > Key: OVIRT-2006 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2006 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: sbonazzo > Assignee: infra > > Since May 8th, everything is redirecting to https on ovirt.org at least using google chrome, so with google chrome can't access any .ovirt.org server. > Not sure what happened, but a workaround that helped me is: > - open chrome://net-internals/#hsts > - go to "Delete domain security policies" section > - enter "ovirt.org" and hit "Delete" > Note that this doesn't depend on a recent google chrome update. > Last update of chrome on my system is: > google-chrome-stable-66.0.3359.139-1.x86_64 mer 02 mag 2018 07:52:00 CEST > And it worked fine until May 7th 2018, broken yesterday, May 8th 2018. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0