Jira (PUP-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.

Joshua Partlow (JIRA) Thu, 23 Oct 2014 22:19:46 -0700

Title: Message Title

Joshua Partlow commented on an issue

OK, we got a new build through with a specific fix for PUP-3500 and a tweak to

~~PUP-3244~~ 's new acceptance test, plus all the fixes I don't have visiblity for in the rest of the pe components that are being integrated. That brought our failures down to 41 total, across 6 tests.

24 are all on redhat platforms, and are related to selinux seluser settings on the environments dir and contents of pe-puppet-dashboard dir. This type of failure began showing up (middle of?) last week, does anyone know what, perhaps module changes, might be causing this?

14 are the check_woy_cache_works.rb test that has been plaguing us, but this time it's across the board. Puppet server doesn't seem to restart after configuration changes. I'll look into this in the morning.

Remaining three look to be related to SERVER-38, except one failure is coming back from a node classifier call:

/classifier-api/v1/classified/nodes/j69mmigph5wx69q.delivery.puppetlabs.net.
Reason:
org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint \"event_commits_pkey\"
Detail: Key (id)=(8b2a42e83adfdd8b92e46903a3bf9aba4d540340) already exists.

Dan Lidral-Porter does that look familiar to you? I failed to turn up anything in Jira for it. We've had failures within this test that we couldn't see the details of before, and I'm guessing we're getting more visibility on this thanks to you closing NC-280, so it may not be brand new.

http://jenkins-enterprise.delivery.puppetlabs.net/view/Build%20Board%20-%20FOSS/job/PE%20Puppet%20Acceptance%20Tests/lastCompletedBuild/testReport/

14 failures => tests/node/check_woy_cache_works.rb (every platform)

puppet server fails to start (or, at any rate, we can't curl it with 120 attempts)

8 failures => tests/ticket_5477_master_not_dectect_sitepp.rb (every redhat platform)

An agent run is seeing unexpected selinux seluser changes to reports in pe-puppet-dashboard:

Notice: /File[/var/log/pe-puppet-dashboard/failed_reports/report_20141023180225.yaml]/seluser: seluser changed 'unconfined_u' to 'system_u'

Notice: /File[/var/log/pe-puppet-dashboard/failed_reports/report_20141023180225_1.yaml]/seluser: seluser changed 'unconfined_u' to 'system_u'

8 failures => tests/environment/directory.rb (every redhat platform)

Also an agent run showing unexpected selinux seluser changes, this time to the environments directory:

Notice: /File[/etc/puppetlabs/puppet/environments/production]/seluser: seluser changed 'unconfined_u' to 'system_u'

...

Notice: /File[/etc/puppetlabs/puppet/environments]/seluser: seluser changed 'unconfined_u' to 'system_u'

8 failures => tests/environment/dynamic.rb (every redhat platform)

Two different agent runs failing on an selinux seluser change to the environments directory same as in the directory test above:

Notice: /File[/etc/puppetlabs/puppet/environments]/seluser: seluser changed 'unconfined_u' to 'system_u'

2 failures => tests/concurrency.ticket_2659_concurrent_catalog_requests.rb (debian7 and scientific6)

debian7 - Might be SERVER-38

Failed when searching for node lgxlgo7jhp6ct55.delivery.puppetlabs.net: Bad file descriptor - Bad file descriptor

scientific6 is more interesting:

Connection #0 to host opihydcuz889q91.delivery.puppetlabs.net left intact

* Closing connection #0

Failed when searching for node j69mmigph5wx69q.delivery.puppetlabs.net: unexpected token at '<html>

<head>

<meta http-equiv=\"Content-Type\" content=\"text/html;charset=ISO-8859-1\"/>

<title>Error 500 </title>

</head>

<body>

<h2>HTTP ERROR: 500</h2>

<p>Problem accessing /classifier-api/v1/classified/nodes/j69mmigph5wx69q.delivery.puppetlabs.net. Reason:

<pre>    org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint \"event_commits_pkey\"

  Detail: Key (id)=(8b2a42e83adfdd8b92e46903a3bf9aba4d540340) already exists.</pre></p>

<hr /><i><small>Powered by Jetty://</small></i>

</body>

</html>

'3601 Completed

1 failure => tests/agent.agent_disable_lockfile.rb (redhat5)

from an agent run - SERVER-38 ?

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Bad file descriptor - Bad file descriptor

Add Comment

Puppet /

PUP-3277

A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments.

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.

Reply via email to