Closed Bug 1342124 Opened 8 years ago Closed 8 years ago

test httpd update on releng-puppet1

Categories

(Infrastructure & Operations :: RelOps: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dhouse, Assigned: dhouse)

Details

No description provided.
Set up change in my environment on puppet2. Tested from vm with old/current httpd, httpd-tools, and mod_ssl and it was updated correctly with the puppet change and new repo: dhouse@dhouse-1330169:~$ rpm -q httpd httpd-tools mod_ssl httpd-2.2.15-56.el6.centos.3.x86_64 httpd-tools-2.2.15-56.el6.centos.3.x86_64 mod_ssl-2.2.15-56.el6.centos.3.x86_64
Same test with releng-puppet1.srv.releng.use1.mozilla.com: No problems in puppet run. Pinned to my puppet env on puppet2: dhouse@releng-puppet1:~$ rpm -q httpd httpd-tools mod_ssl httpd-2.2.15-56.el6.centos.3.x86_64 httpd-tools-2.2.15-56.el6.centos.3.x86_64 mod_ssl-2.2.15-56.el6.centos.3.x86_64 Leaving puppet1 running the new httpd, and I'll test using it as a puppet master from a vm.
No problems found with a puppet client run from a vm against the puppet1 server with the updated httpd, httpd-tools, and mod_ssl.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Un-pinned puppet1. However, it will keep the newer httpd since previously httpd was not specified in puppet.
You need to log in before you can comment on or make changes to this bug.