Updating email configuration
by Shlomo Ben David
Hi All,
Due to some restrictions on our email server we need to update our email
configuration to increase the security on it.
To apply the new configuration i will reboot the server today 31/10/2016 at
20:00 IST.
*Downtime EST: ~5 minutes*
Best Regards,
Shlomi Ben-David | DevOps Engineer | Red Hat ISRAEL
RHCSA | RHCE
IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
OPEN SOURCE - 1 4 011 && 011 4 1
8 years
[JIRA] (OVIRT-751) Persistent maven caches on the mock slaves
by Gil Shinar (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-751?page=com.atlassian.jira... ]
Gil Shinar reassigned OVIRT-751:
--------------------------------
Assignee: Gil Shinar (was: infra)
> Persistent maven caches on the mock slaves
> ------------------------------------------
>
> Key: OVIRT-751
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-751
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Reporter: Anton Marchukov
> Assignee: Gil Shinar
>
> I think we need to design a way to retain maven caches on the mocked jenkins slaves. Currently it is stored inside the mock and thus maven downloads packages from artifactory server each time.
> However there is really no reason for that. Maven artifacts are designed to be immutable so once artifact is in the repo there is no trivial way to change it without creating a new version. In fact it should never be needed and the correct solution for that is to always create a new version.
> SNAPSHOOT artifacts are in fact timestamped and each one have different file name. It is just not visible since maven automatically takes the latest one. But it is not related to caching as the new snapshoot will be a new artifact still.
> So based on that point there is no reason to purge maven cache each time, but there are reasons why not to purge. Not purging them will reduce the build times of all java jobs and also reduce the network traffic we have.
--
This message was sent by Atlassian JIRA
(v1000.482.3#100017)
8 years
[JIRA] (OVIRT-802) ovirt-engine_master_upgrade-from-3.6_el7_merged failing
by Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-802?page=com.atlassian.jira... ]
Evgheni Dereveanchin reassigned OVIRT-802:
------------------------------------------
Assignee: Evgheni Dereveanchin (was: infra)
> ovirt-engine_master_upgrade-from-3.6_el7_merged failing
> -------------------------------------------------------
>
> Key: OVIRT-802
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-802
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Greg Sheremeta
> Assignee: Evgheni Dereveanchin
>
> https://gerrit.ovirt.org/#/c/65899/2
> job:
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_mer...
> failing.
> + which engine-setup
> + engine-cleanup
> --config-append=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi
> [ INFO ] Stage: Initializing
> [ INFO ] Stage: Environment setup
> Configuration files:
> ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
> '/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
> '/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi']
> Log file:
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
> Version: otopi-1.6.0_master
> (otopi-1.6.0-0.0.master.20160829151522.git7547b87.el7.centos)
> [ ERROR ] Could not detect a completed product setup
> Please use the cleanup utility only after a setup or after an
> upgrade from an older installation.
> [ ERROR ] Failed to execute stage 'Environment setup': Could not detect
> product setup
> [ INFO ] Stage: Clean up
> Log file is located at
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
> [ INFO ] Generating answer file
> '/var/lib/ovirt-engine/setup/answers/20161031153445-cleanup.conf'
> [ INFO ] Stage: Pre-termination
> [ INFO ] Stage: Termination
> [ ERROR ] Execution of cleanup failed
> --
> Greg Sheremeta, MBA
> Red Hat, Inc.
> Sr. Software Engineer
> gshereme(a)redhat.com
--
This message was sent by Atlassian JIRA
(v1000.482.3#100017)
8 years
[JIRA] (OVIRT-802) ovirt-engine_master_upgrade-from-3.6_el7_merged failing
by Yedidyah Bar David (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-802?page=com.atlassian.jira... ]
Yedidyah Bar David commented on OVIRT-802:
------------------------------------------
On Mon, Oct 31, 2016 at 5:45 PM, eyal edri [Administrator] (oVirt JIRA) <
No.
setup log has:
2016-10-31 15:34:33 DEBUG
otopi.plugins.ovirt_engine_common.base.system.selinux plugin.execute:926
execute-output: ('/sbin/semanage', 'fcontext', '-a', '-t',
'public_content_rw_t', '/var/lib/exports/iso(/.*)?') stderr:
libsepol.context_from_record: type ovirt_vmconsole_proxy_port_t is not
defined (No such file or directory).
libsepol.context_from_record: could not create context structure (Invalid
argument).
libsepol.port_from_record: could not create port structure for range
2222:2222 (tcp) (Invalid argument).
libsepol.sepol_port_modify: could not load port range 2222 - 2222 (tcp)
(Invalid argument).
libsemanage.dbase_policydb_modify: could not modify record value (Invalid
argument).
libsemanage.semanage_base_merge_components: could not merge local
modifications into policy (Invalid argument).
ValueError: Could not commit semanage transaction
The type public_content_rw_t should have been created during installation
of ovirt-vmconsole-proxy, by its %post scriptlet. I do not see it installed
in the console output, also on successful builds. How/where/when do you
install this package? Perhaps something changed selinux policy after it was
installed?
--
Didi
> ovirt-engine_master_upgrade-from-3.6_el7_merged failing
> -------------------------------------------------------
>
> Key: OVIRT-802
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-802
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Greg Sheremeta
> Assignee: infra
>
> https://gerrit.ovirt.org/#/c/65899/2
> job:
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_mer...
> failing.
> + which engine-setup
> + engine-cleanup
> --config-append=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi
> [ INFO ] Stage: Initializing
> [ INFO ] Stage: Environment setup
> Configuration files:
> ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
> '/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
> '/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi']
> Log file:
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
> Version: otopi-1.6.0_master
> (otopi-1.6.0-0.0.master.20160829151522.git7547b87.el7.centos)
> [ ERROR ] Could not detect a completed product setup
> Please use the cleanup utility only after a setup or after an
> upgrade from an older installation.
> [ ERROR ] Failed to execute stage 'Environment setup': Could not detect
> product setup
> [ INFO ] Stage: Clean up
> Log file is located at
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
> [ INFO ] Generating answer file
> '/var/lib/ovirt-engine/setup/answers/20161031153445-cleanup.conf'
> [ INFO ] Stage: Pre-termination
> [ INFO ] Stage: Termination
> [ ERROR ] Execution of cleanup failed
> --
> Greg Sheremeta, MBA
> Red Hat, Inc.
> Sr. Software Engineer
> gshereme(a)redhat.com
--
This message was sent by Atlassian JIRA
(v1000.482.3#100017)
8 years
[JIRA] (OVIRT-798) outgoing mail failure - SPF fail
by Marc Dequènes (Duck) (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-798?page=com.atlassian.jira... ]
Marc Dequènes (Duck) commented on OVIRT-798:
--------------------------------------------
Summary from the mail thread follows.
Gerrit spoof the sender of notifications using the user's address. But Gerrit is not allowed to send mails from any domain due to SPF policy. The Red Hat policy is getting stricter, and other companies also do so, so we need to change this behavior.
According to:
https://review.openstack.org/Documentation/config-gerrit.html#sendemail
I suggested we could update the sendemail.from setting with the wanted address
instead of USER. I never touched this software so maybe someone more familiar could do the change if it looks ok. Also we need to schedule this to avoid bothering people.
Evgheni suggested using automation(a)ovirt.org as From.
Moreover, to be able to send from the oVirt domain the SPF settings in DNS was changed.
> outgoing mail failure - SPF fail
> --------------------------------
>
> Key: OVIRT-798
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-798
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Yedidyah Bar David
> Assignee: infra
>
> Hi,
> When adding a reviewer to a patch on gerrit, I get an email:
> The original message was received at Mon, 31 Oct 2016 05:07:32 -0400
> from gerrit.ovirt.org [127.0.0.1]
> ----- The following addresses had permanent fatal errors -----
> <sbonazzo(a)redhat.com>
> (reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69],
> 'redhat.com'; REJECT)
> ----- Transcript of session follows -----
> ... while talking to mx1.redhat.com.:
> >>> DATA
> <<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
> 550 5.1.1 <sbonazzo(a)redhat.com>... User unknown
> <<< 554 5.5.1 Error: no valid recipients
> Final-Recipient: RFC822; sbonazzo(a)redhat.com
> Action: failed
> Status: 5.7.1
> Remote-MTA: DNS; mx1.redhat.com
> Diagnostic-Code: SMTP; 551 5.7.1 SPF fail:
> 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
> Last-Attempt-Date: Mon, 31 Oct 2016 05:07:33 -0400
> Please check/handle. Thanks.
> --
> Didi
--
This message was sent by Atlassian JIRA
(v1000.482.3#100017)
8 years
[JIRA] (OVIRT-802) ovirt-engine_master_upgrade-from-3.6_el7_merged failing
by Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-802?page=com.atlassian.jira... ]
Evgheni Dereveanchin commented on OVIRT-802:
--------------------------------------------
[~eedri] first of all, this is not a new slave, second of all SELinux is in permissive mode on it:
[ederevea@el7-vm07 ~]$ getenforce
Permissive
[ederevea@el7-vm07 ~]$ rpm -qa | grep selinux
libselinux-ruby-2.2.2-6.el7.x86_64
selinux-policy-targeted-3.13.1-60.el7_2.3.noarch
selinux-policy-doc-3.13.1-60.el7_2.9.noarch
selinux-policy-3.13.1-60.el7_2.9.noarch
libselinux-2.2.2-6.el7.x86_64
libselinux-utils-2.2.2-6.el7.x86_64
selinux-policy-devel-3.13.1-60.el7_2.9.noarch
libselinux-python-2.2.2-6.el7.x86_64
here's the error from the engine setup log attached to the job:
2016-10-31 15:34:29 DEBUG otopi.plugins.ovirt_engine_common.base.system.selinux plugin.executeRaw:813 execute: ('/sbin/semanage', 'fcontext', '-a', '-t', 'public_content_rw_t', '/var/lib/exports/iso(/.*)?'), executable='None', cwd='None', env=None
2016-10-31 15:34:33 DEBUG otopi.plugins.ovirt_engine_common.base.system.selinux plugin.executeRaw:863 execute-result: ('/sbin/semanage', 'fcontext', '-a', '-t', 'public_content_rw_t', '/var/lib/exports/iso(/.*)?'), rc=1
2016-10-31 15:34:33 DEBUG otopi.plugins.ovirt_engine_common.base.system.selinux plugin.execute:921 execute-output: ('/sbin/semanage', 'fcontext', '-a', '-t', 'public_content_rw_t', '/var/lib/exports/iso(/.*)?') stdout:
2016-10-31 15:34:33 DEBUG otopi.plugins.ovirt_engine_common.base.system.selinux plugin.execute:926 execute-output: ('/sbin/semanage', 'fcontext', '-a', '-t', 'public_content_rw_t', '/var/lib/exports/iso(/.*)?') stderr:
libsepol.context_from_record: type ovirt_vmconsole_proxy_port_t is not defined (No such file or directory).
libsepol.context_from_record: could not create context structure (Invalid argument).
libsepol.port_from_record: could not create port structure for range 2222:2222 (tcp) (Invalid argument).
libsepol.sepol_port_modify: could not load port range 2222 - 2222 (tcp) (Invalid argument).
libsemanage.dbase_policydb_modify: could not modify record value (Invalid argument).
libsemanage.semanage_base_merge_components: could not merge local modifications into policy (Invalid argument).
ValueError: Could not commit semanage transaction
2016-10-31 15:34:33 DEBUG otopi.context context._executeMethod:142 method exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod
method['method']()
File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/system/selinux.py", line 94, in _misc
entry['pattern']
File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 931, in execute
command=args[0],
RuntimeError: Command '/sbin/semanage' failed to execute
2016-10-31 15:34:33 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Misc configuration': Command '/sbin/semanage' failed to execute
> ovirt-engine_master_upgrade-from-3.6_el7_merged failing
> -------------------------------------------------------
>
> Key: OVIRT-802
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-802
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Greg Sheremeta
> Assignee: infra
>
> https://gerrit.ovirt.org/#/c/65899/2
> job:
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_mer...
> failing.
> + which engine-setup
> + engine-cleanup
> --config-append=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi
> [ INFO ] Stage: Initializing
> [ INFO ] Stage: Environment setup
> Configuration files:
> ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
> '/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
> '/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi']
> Log file:
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
> Version: otopi-1.6.0_master
> (otopi-1.6.0-0.0.master.20160829151522.git7547b87.el7.centos)
> [ ERROR ] Could not detect a completed product setup
> Please use the cleanup utility only after a setup or after an
> upgrade from an older installation.
> [ ERROR ] Failed to execute stage 'Environment setup': Could not detect
> product setup
> [ INFO ] Stage: Clean up
> Log file is located at
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
> [ INFO ] Generating answer file
> '/var/lib/ovirt-engine/setup/answers/20161031153445-cleanup.conf'
> [ INFO ] Stage: Pre-termination
> [ INFO ] Stage: Termination
> [ ERROR ] Execution of cleanup failed
> --
> Greg Sheremeta, MBA
> Red Hat, Inc.
> Sr. Software Engineer
> gshereme(a)redhat.com
--
This message was sent by Atlassian JIRA
(v1000.482.3#100017)
8 years
