[
https://ovirt-jira.atlassian.net/browse/OVIRT-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39653#comment-39653
]
Evgheni Dereveanchin edited comment on OVIRT-2774 at 8/14/19 12:12 PM:
-----------------------------------------------------------------------
Looking at the foreman:
grep jenkins_ver /etc/puppet/environments/production/hieradata/common.yaml
ovirt_jenkins::jenkins_ver: 2.164.2-1.1
ls -l /etc/puppet/environments/production/hieradata/common.yaml
rw-rw-r-. 1 puppet-repos puppet-repos 10586 Aug 1 15:05
/etc/puppet/environments/production/hieradata/common.yaml
At the same time from the logs of the last job all looks fine:
[https://jenkins.ovirt.org/job/system_update_puppet/176/console|https://jenkins.ovirt.org/job/system_update_puppet/176/console]
Looking into {{/var/lib/data/jenkins/jobs/system_update_puppet/workspace}} on
the master the hieradata file is correct and contains Jenkins version 2.176.1
as needed.
[~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] do you know how
exactly system_update_puppet invokes r10k? The job config only lists “ssh“ as
the build step and on the foreman the shell of the puppet-repos user is plain
bash so it doesn’t seem to run any hardcoded commands upon login. This stops me
from understanding where the changes are lost.
was (Author: ederevea):
Looking at the foreman:
{{# grep jenkins_ver /etc/puppet/environments/production/hieradata/common.yaml
}}
{{ovirt_jenkins::jenkins_ver: 2.164.2-1.1}}
{{# ls -l /etc/puppet/environments/production/hieradata/common.yaml }}
{{-rw-rw-r--. 1 puppet-repos puppet-repos 10586 Aug 1 15:05
/etc/puppet/environments/production/hieradata/common.yaml}}
At the same time from the logs of the last job all looks fine:
[https://jenkins.ovirt.org/job/system_update_puppet/176/console|https://jenkins.ovirt.org/job/system_update_puppet/176/console]
Looking into {{/var/lib/data/jenkins/jobs/system_update_puppet/workspace}} on
the master the hieradata file is correct and contains Jenkins version 2.176.1
as needed.
[~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] do you know how
exactly system_update_puppet invokes r10k? The job config only lists “ssh“ as
the build step and on the foreman the shell of the puppet-repos user is plain
bash so it doesn’t seem to run any hardcoded commands upon login. This stops me
from understanding where the changes are lost.
> system_update_puppet job does not work properly
> -----------------------------------------------
>
> Key: OVIRT-2774
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2774
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Evgheni Dereveanchin
> Assignee: infra
> Priority: Highest
>
> The job performs incorrect updates to the puppet repo. This seems to just
> have caused a Jenkins restart and downgraded its version
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100107)
_______________________________________________
Infra mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/IWB7MXNO7PN54NY3BZD4DITKEIBIL6FZ/
