July 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2361) Remove 4.1 tested repo
by Ehud Yonasi (oVirt JIRA) 22 Jul '18

22 Jul '18

Ehud Yonasi created OVIRT-2361: ---------------------------------- Summary: Remove 4.1 tested repo Key: OVIRT-2361 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2361 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Ehud Yonasi Assignee: infra current utilization is 93G under: /srv/resources/repos/ovirt/tested/4.1 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2361) Remove 4.1 tested repo
by Ehud Yonasi (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2361?page=com.atlassian.jira.… ] Ehud Yonasi updated OVIRT-2361: ------------------------------- Epic Link: OVIRT-2044 > Remove 4.1 tested repo > ---------------------- > > Key: OVIRT-2361 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2361 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Ehud Yonasi > Assignee: infra > > current utilization is 93G under: /srv/resources/repos/ovirt/tested/4.1 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2359: ------------------------------------- Here is how you can gain access to the env vars you passed to Dokcer, no need to pass them as files: https://unix.stackexchange.com/questions/146995/inherit-environment-variabl… and, as mentioned on that ticket, its a good idea to have an early one-shot service that will copy the variables you need into /etc/environment to make them available to non-root services. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2360) Enable setting a default version for the OST manual job and set 4.2 as the default.
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2360?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2360: ----------------------------------- Assignee: Ehud Yonasi (was: infra) > Enable setting a default version for the OST manual job and set 4.2 as the default. > ----------------------------------------------------------------------------------- > > Key: OVIRT-2360 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2360 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST Manual job > Reporter: Barak Korren > Assignee: Ehud Yonasi > Priority: High > > We need to ensure the default oVirt version can be configure when using the OST mnaul job template. Once we do that we need to also configure the default to be 4.2 currently. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2360) Enable setting a default version for the OST manual job and set 4.2 as the default.
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

Barak Korren created OVIRT-2360: ----------------------------------- Summary: Enable setting a default version for the OST manual job and set 4.2 as the default. Key: OVIRT-2360 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2360 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Manual job Reporter: Barak Korren Assignee: infra Priority: High We need to ensure the default oVirt version can be configure when using the OST mnaul job template. Once we do that we need to also configure the default to be 4.2 currently. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Daniel Belenky edited comment on OVIRT-2359 at 7/22/18 11:11 AM: ----------------------------------------------------------------- But we're off-topic for this ticket. The task here is to have some indication we're inside a container. I think mounting a file in read-only mode with some system infomration about stdci in /etc/stdci is a good solution. WDYT? was (Author: dbelenky(a)redhat.com) But we're off-topic for this ticket. The task here is to have some indication we're inside a container. I think mounting a file in read-only mode that some system infomration about stdci in /etc/stdci is a good solution. WDYT? > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2359: --------------------------------------- But we're off-topic for this ticket. The task here is to have some indication we're inside a container. I think mounting a file in read-only mode that some system infomration about stdci in /etc/stdci is a good solution. WDYT? > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2359: --------------------------------------- I think that systemd drops environment information by design in order to ensure clean environment for every process it starts. Maybe there is a workaround but what's wrong with EnvironmentFiles? You'll have to provide this infomration to systemd anyway, so by having a well know directory in a host with N systemd environment files, one for every container, you have all the needed information you need to run them. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-1993) Looking for a new task to help with
by Eyal Edri (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1993?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1993: ---------------------------------- Its on the previous comment: 3. Join the infra weekly meetings on Wed 14:00 UTC ( https://bluejeans.com/902682731 ), this week is off, but next week should be on. > Looking for a new task to help with > ----------------------------------- > > Key: OVIRT-1993 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1993 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sailesh baskar > Assignee: infra > > I would like to open a new ticket in the infrastructure team. Can you help > in the process? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[CQ]: 93234,1 (ioprocess) failed "ovirt-4.2" system tests
by oVirt Jenkins 22 Jul '18

22 Jul '18

Change 93234,1 (ioprocess) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/93234/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2693/

2 1