[ https://ovirt-jira.atlassian.net/browse/OVIRT-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27500#comment-27500 ] Barak Korren commented on OVIRT-1170: ------------------------------------- [~gshereme@redhat.com] Could this be resolved at the automation script level with something like: {code} cat 127.0.0.1 host_evil_module_is.connecting.to > /etc/hosts {code} Or {code} rm /etc/hosts {code} ? Hermetically shutting off the connection is not easily achievable at this point because we need the connection to talk back to Jenkins, and the automation scripts are not running in their own network namespace (Until we get around to implementing OVIRT-873)

add option to disable networking (or have it off by default) ------------------------------------------------------------

Key: OVIRT-1170 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1170 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Greg Sheremeta Assignee: infra

Add option to disable networking (or have it off by default). Basically, we want to prevent a job from accessing the internet if we want repeatable builds and/or are doing a downstream build somewhere else. Other/downstream build environments often have networking off. Copr has an option: (See: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.o... ) In particular, the ovirt-engine-nodejs-modules build-artifacts job *tries* to stay offline, but an evil node module called 'phantomjs' connects to the internet in a post-offline-install hook. I'd like the option to disallow that and have the build fail.

-- This message was sent by Atlassian JIRA (v1000.773.2#100032)