Jira (PUP-6824) Use UUIDs for certificate serial numbers
Title: Message Title Justin Stoller updated an issue Puppet / PUP-6824 Use UUIDs for certificate serial numbers Change By: Justin Stoller Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7744) Puppet CA's CRL is prone to duplicate entries
Title: Message Title Justin Stoller updated an issue Puppet / PUP-7744 Puppet CA's CRL is prone to duplicate entries Change By: Justin Stoller Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8226) Warning in manifest causing invalid byte sequence error on Redhat 7 server
Title: Message Title Justin Stoller updated an issue Puppet / PUP-8226 Warning in manifest causing invalid byte sequence error on Redhat 7 server Change By: Justin Stoller Sprint: Platform Core Grooming Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8249) Certain environments return "invalid byte sequence in " when parsing module PO files
Title: Message Title Justin Stoller commented on PUP-8249 Re: Certain environments return "invalid byte sequence in " when parsing module PO files Maggie Dreyer should pair with Ethan Brown to keep root causing this and perhaps with someone on the Coremunity team for the fix /cc Jacob Helwig. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8226) Warning in manifest causing invalid byte sequence error on Redhat 7 server
Title: Message Title Justin Stoller commented on PUP-8226 Re: Warning in manifest causing invalid byte sequence error on Redhat 7 server We want to try setting the kCode first and then continue with other options if that doesn't work. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7737) Add HTTP report processor setting for including system truststore
Title: Message Title Justin Stoller updated an issue Puppet / PUP-7737 Add HTTP report processor setting for including system truststore Change By: Justin Stoller Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2189) The CRL can get corrupted if two workers revoke certs at same time
Title: Message Title Justin Stoller updated an issue Puppet / PUP-2189 The CRL can get corrupted if two workers revoke certs at same time Change By: Justin Stoller Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7744) Puppet CA's CRL is prone to duplicate entries
Title: Message Title Justin Stoller commented on PUP-7744 Re: Puppet CA's CRL is prone to duplicate entries This should be done in both Puppet Server (threaded through to jvm-ssl-utils) in addition to Puppet. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2189) The CRL can get corrupted if two workers revoke certs at same time
Title: Message Title Justin Stoller commented on PUP-2189 Re: The CRL can get corrupted if two workers revoke certs at same time I assume we should move this out of the active sprint and into the backlog, since it looks like it needs to go back and be prioritized with other CA work? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7517) Add logic for restarting hung catalog application
Title: Message Title Justin Stoller assigned an issue to Justin Stoller Puppet / PUP-7517 Add logic for restarting hung catalog application Change By: Justin Stoller Assignee: Justin Stoller Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7517) Add logic for restarting hung catalog application
Title: Message Title Justin Stoller updated an issue Puppet / PUP-7517 Add logic for restarting hung catalog application Change By: Justin Stoller Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6807) referencing non-existant variable in custom function crashes puppetserver
Title: Message Title Justin Stoller updated an issue Puppet / PUP-6807 referencing non-existant variable in custom function crashes puppetserver Change By: Justin Stoller Release Notes Summary: Puppet extensions with Ruby errors (specifically noted in custom functions that referenced undefined local variables) would cause Puppet to create an error message that contained most of the Ruby object space. This message could be gigabytes in size and under load would cause the Puppet Server process to die with an OutOfMemoryError. Now failure to load a Puppet extension will create a reasonably short error string that will *not* use gigabytes of memory. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6807) referencing non-existant variable in custom function crashes puppetserver
Title: Message Title Justin Stoller commented on PUP-6807 Re: referencing non-existant variable in custom function crashes puppetserver The fix was merged into Puppet at: 2fe2216 and was promoted into puppet-agent at: fa70f7b which passed a full CI run here: puppet-agent (master) Suite Pipeline Step 7 – Puppet Tests : Build 232 Closing as complete. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6807) referencing non-existant variable in custom function crashes puppetserver
Title: Message Title Justin Stoller moved an issue Puppet / PUP-6807 referencing non-existant variable in custom function crashes puppetserver Change By: Justin Stoller Affects Version/s: PE 2016.2.1 Component/s: Puppet Server Component/s: Puppet Server Key: PE PUP - 17527 6807 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsu
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller updated an issue Puppet / PUP-3827 Errors from indirected routes don't match error schema Change By: Justin Stoller Release Notes Summary: In Puppet 4.0 many errors returned by our API were moved to follow best practices wrt HTTP error codes and a JSON format that follows our documented JSON schema. However one major subsystem of Puppet (the indirector) was not converted to follow this pattern. As of this release API endpoints that hit this subsystem will return proper HTTP error codes and message bodies that conform to our documented JSON standard. The previous behavior was to return a 400 Server Error for all issues with this subsystem. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6257) Add --allow-authorization-extensions to puppet cert sign
Title: Message Title Justin Stoller assigned an issue to Nathaniel Smith Puppet / PUP-6257 Add --allow-authorization-extensions to puppet cert sign Change By: Justin Stoller Assignee: Nathaniel Smith Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6268) Display cert information when interacting with certs via `puppet cert` application
Title: Message Title Justin Stoller assigned an issue to qa Puppet / PUP-6268 Display cert information when interacting with certs via `puppet cert` application Change By: Justin Stoller Status: Ready for CI Test Assignee: Justin Stoller qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6268) Display cert information when interacting with certs via `puppet cert` application
Title: Message Title Justin Stoller updated an issue Puppet / PUP-6268 Display cert information when interacting with certs via `puppet cert` application Change By: Justin Stoller Summary: Display cert information when interacting with certs via `puppet cert` face application Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6268) Display cert information when interacting with certs via `puppet cert` face
Title: Message Title Justin Stoller assigned an issue to Justin Stoller Puppet / PUP-6268 Display cert information when interacting with certs via `puppet cert` face Change By: Justin Stoller Assignee: Justin Stoller Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6268) Display cert information when interacting with certs via `puppet cert` face
Title: Message Title Justin Stoller commented on PUP-6268 Re: Display cert information when interacting with certs via `puppet cert` face I've implemented the format changes we decided on after the UX testing in this PR: https://github.com/puppetlabs/puppet/pull/5023 In it I left the full output, human friendly format, and the interactivity of the sign command as opt-in. I believe folks wanted to push to get those as default behavior as soon as possible. And from our testers reactions they wouldn't mind the defaults changing sooner rather than later. I'd love to update this PR to have those defaults, though I felt like I should get final sign off from UX, Product, and Dev either in this ticket or in the PR. I also figured it would be beneficial one more time to have the output and a functional environment on hand for folks to play with if desired. See the PR for details on how to log into, or reproduce, the environment. I've /cc the same group of folks there as here. Lori Landesman, e0 S0renson, Nathaniel Smith, Kevin Corcoran. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6268) Display cert information when interacting with certs via `puppet cert` face
Title: Message Title Justin Stoller commented on PUP-6268 Re: Display cert information when interacting with certs via `puppet cert` face The confluence doc with high level take aways from the UX testing is here: https://confluence.puppetlabs.com/display/UX/Cert+Information+Display+Research+-+June%2C+2016 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller assigned an issue to qa Puppet / PUP-3827 Errors from indirected routes don't match error schema Change By: Justin Stoller Status: Ready for CI Test Assignee: Justin Stoller qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller assigned an issue to qa Puppet / PUP-3827 Errors from indirected routes don't match error schema Change By: Justin Stoller Status: Ready for CI Test Assignee: Justin Stoller qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6268) Display cert information when interacting with certs via `puppet cert` face
Title: Message Title
Justin Stoller updated an issue
Puppet / PUP-6268
Display cert information when interacting with certs via `puppet cert` face
Change By:
Justin Stoller
In Scope* CLI usage only* {{puppet cert}} face only* When signing a cert, display cert information* When listing certnames, show cert information* Information to show: expiry, certname, extensionsOpen Questions* Any other info to show?* should cert sign block on user input? (with a toggle for interactivity)?
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6268) Display cert information when interacting with certs via `puppet cert` face
Title: Message Title Justin Stoller updated an issue Puppet / PUP-6268 Display cert information when interacting with certs via `puppet cert` face Change By: Justin Stoller Summary: Display cert information when signing and listing interacting with certs via `puppet cert` face Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6268) Display cert information when signing and listing certs
Title: Message Title Justin Stoller commented on PUP-6268 Re: Display cert information when signing and listing certs Kevin Corcoran To which method(s) of signing/listing a certificate does this apply? For signing, I think we discussed that it's only puppet cert sign ... right? In particular, I believe we decided that we didn't care to update /certificate_status to allow signing these cert requests, yeah? I think there are other puppet ... subcommands which can sign cert requests, and I think the same thing applies to them - they'll just reject these requests always - but that'd be good to call out here. I'm not Nathaniel Smith, but I've been doing the due diligence on this ticket in preparation for working it (hence my notes above). PE-15436 is the R&D around the GUI side of displaying the new info we adding in this epic. I believe this ticket is solely scoped to the CLI work. The puppet faces that allow interaction with certs and/or the ca are: ca, cert, certificate, certificate_request, certificate_revocation_list. All of those but the cert face just defer to the generic base indirection face for formatting their results. All of those could be updated to show additional cert information, though at this point they do nothing cert specific in their formatting (see the awesome output of puppet certificate generate above). The cert face is the only place that we currently do certificate specific CLI formatting, the updating of which is what I believe this ticket is scoped to. I'll update this ticket summary and description accordingly. If anyone thinks that's an incorrect scope for this ticket please let me know here. note: to connect the backend services Kevin was talking with user workflows: we're using tk-auth to validate authorization into a particular puppet route (now using the new OIDs referenced in this Epic), in practice the clj-ca handles basic signing scenarios and those can also be handled via the GUI, for scenarios that utilize the new OIDs (core puppet infrastructure) we defer to the ruby-ca and its tools for signing (hopefully also auto-signing). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6268) Display cert information when signing and listing certs
Title: Message Title Justin Stoller commented on PUP-6268 Re: Display cert information when signing and listing certs Lori Landesman, I put the above info up so you, and any other stakeholder, would have the current output for the lifecycle of a cert in the ticket when weighing in on potential design changes. Let me know if you need anything else. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6268) Display cert information when signing and listing certs
Title: Message Title Justin Stoller commented on PUP-6268 Re: Display cert information when signing and listing certs Here's an example of generating, listing, signing, cleaning, and revoking certs, with and without alt-names from the CLI currently: [root@xxj5w66u5j0qhx5 ~]# puppet certificate generate foo.example.com --ca-location remote true [root@xxj5w66u5j0qhx5 ~]# puppet cert list "foo.example.com" (SHA256) 67:8E:5A:D3:11:62:98:BE:29:58:E7:71:DB:2C:1F:A3:B5:30:EA:4B:41:F1:6E:C0:BF:30:0A:46:AC:E5:73:09 [root@xxj5w66u5j0qhx5 ~]# puppet cert sign foo.example.com Notice: Signed certificate request for foo.example.com Notice: Removing file Puppet::SSL::CertificateRequest foo.example.com at '/etc/puppetlabs/puppet/ssl/ca/requests/foo.example.com.pem'
Jira (PUP-6268) Display cert information when signing and listing certs
Title: Message Title Justin Stoller commented on PUP-6268 Re: Display cert information when signing and listing certs Here's an example of our current output: [root@xxj5w66u5j0qhx5 puppet-enterprise-2016.1.2-el-7-x86_64]# puppet cert list --all + "pe-internal-classifier"(SHA256) 32:09:71:C8:09:E3:CB:F7:EB:DE:48:3B:D6:45:B5:90:74:56:F9:14:D7:15:61:01:C0:03:73:8B:E2:B2:49:C0 + "pe-internal-dashboard" (SHA256) 17:A7:4C:1E:29:F1:59:58:FC:77:46:F5:BC:65:35:3B:7D:41:79:B8:81:E5:FE:B5:3A:4B:86:B3:78:2F:35:2A + "pe-internal-mcollective-servers" (SHA256) 93:84:48:78:1B:82:97:B2:6A:03:6D:78:21:54:81:F4:17:68:35:0D:84:DD:06:36:2A:C5:38:11:AB:94:59:B7 + "pe-internal-orchestrator" (SHA256) 73:05:DB:E7:72:11:6E:9A:4D:88:DD:92:18:4C:F4:8E:FB:D9:68:66:56:54:46:10:51:E7:F2:CE:E6:AD:A9:C2 + "pe-internal-peadmin-mcollective-client"(SHA256) 2F:A4:A9:A4:98:56:6C:32:DB:22:6E:42:B3:2E:13:26:AE:AC:D6:04:39:D6:C3:68:33:2B:98:31:6D:31:FA:84 + "pe-internal-puppet-console-mcollective-client" (SHA256) 91:DC:99:8C:44:E5:F1:94:2F:4C:31:2B:09:B6:FE:64:A8:50:03:F6:AE:D0:00:A1:60:B2:22:78:C2:C0:36:B1 + "xxj5w66u5j0qhx5.delivery.puppetlabs.net" (SHA256) 23:0F:98:C4:4C:19:B4:78:80:E1:7C:F1:1B:AA:A6:A2:F8:D5:D2:DD:8C:CF:81:38:2F:CF:D2:3A:3C:3C:E0:46 (alt names: "DNS:xxj5w66u5j0qhx5", "DNS:xxj5w6
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller commented on PUP-3827 Re: Errors from indirected routes don't match error schema Yes, AFAIK this PR is in good shape and ready to be merged but waiting on the PA release for master to un-freeze, and folks on the Client team have the time to merge. /cc Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller assigned an issue to Justin Stoller Puppet / PUP-3827 Errors from indirected routes don't match error schema Change By: Justin Stoller Assignee: Justin Stoller Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller updated an issue Puppet / PUP-3827 Errors from indirected routes don't match error schema Change By: Justin Stoller Fix Version/s: PUP 4.y Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller commented on PUP-3827 Re: Errors from indirected routes don't match error schema FWIW, I don't believe there's any time pressure to release this fix. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller commented on PUP-3827 Re: Errors from indirected routes don't match error schema Updated PR ready for review here: https://github.com/puppetlabs/puppet/pull/4957 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller commented on PUP-3827 Re: Errors from indirected routes don't match error schema This was reverted as it was causing errors in CI Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6270) tests/environment/environment_scenario-bad.rb fails on all master platforms
Title: Message Title Justin Stoller assigned an issue to Justin Stoller Puppet / PUP-6270 tests/environment/environment_scenario-bad.rb fails on all master platforms Change By: Justin Stoller Assignee: Justin Stoller Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller commented on PUP-3827 Re: Errors from indirected routes don't match error schema I've put up a PR for this here: https://github.com/puppetlabs/puppet/pull/4875 I initially began with an approach that would check to see if the accept headers had been set, but I quickly realized in testing that the accept headers will sometimes have to be set to "text/pson" to be a valid request to the indirector. So a valid request will sometimes not trigger the "application/json" requirement and backwards compatibility cannot be kept unless we explicitly ignore the accept header in those cases. Given that, I just made the indirected route handler as similar to other handlers as possible (no attempt to catch errors). We are validating a fair bit of functionality of the IndirectedRoutes class by return codes, which had to be changed to validate based on the error raised since catching errors and updating the response with return codes is now done higher up the stack. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller updated an issue Puppet / PUP-3827 Errors from indirected routes don't match error schema Change By: Justin Stoller Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller updated an issue Puppet / PUP-3827 Errors from indirected routes don't match error schema Change By: Justin Stoller Labels: low-hanging-fruit server Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller commented on PUP-3827 Re: Errors from indirected routes don't match error schema So, looking into this is seems that the simplest route would be to just delete the exception handling code in the indirected_routes. Since that would be backwards incompatible, left to my own devices, I would refactor the exception handling in indirected_routes to check to see if json was a requested response format, if so re-raising the exceptions so that the wrapper handler can correctly deal with them (and we don't have to duplicate the code). If json wasn't specified I'd log a deprecation notice and do same reply that exists currently. Maybe adding a comment in the code that this should be removed in Puppet 5. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller commented on PUP-3827 Re: Errors from indirected routes don't match error schema Testing-wise we're testing that the structured error handling is done in a unit test for the generic handler interface. There's also an integration test for the indirected_routes handler that doesn't test the error handling, and uses a different set of test utils to test. Though I think it would be fairly easy to replicate the kind of testing done to test the error handling in the handler unit test. Grepping about I didn't see any acceptance tests for this kind of thing. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller commented on PUP-3827 Re: Errors from indirected routes don't match error schema Reviewing the docs it seems that there's some conflation what what is happening in our API (or I'm misreading it) The error return information seems to be nested within the Puppet Server Specific Endpoints and explicitly says that it is applicable to the /environments endpoint (which isn't a Puppet Server specific endpoint). It looks like the documentation is also opinionated about return formats, specifying that if a return type other than json is requested a 406 will be returned (I could not get that behavior by providing a header of "Accept: text/plain" to the environments endpoint). Ahhh... Looking at the code for the environment route, I see now that the generic handler code, included in the generic rack-rest handler handles all of the error processing correctly. Our issue is that indirected routes are implementing their own error handling, doing the wrong thing, and never letting the errors percolate up to the correct error handling code. So with that, there'd be a pretty simple solution to this by simply deleting the exception catching in indirected_routes which should let the wrapper handler do the right thing. The only issue with that is that it would change the behavior of the endpoint error codes not in a major version bump... Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller commented on PUP-3827 Re: Errors from indirected routes don't match error schema My notes so far: We catch any errors raised in our handler's call method (and raise if there's any issue anywhere in processing) in 'network/http/api/indirected_routes' where both handlers for exceptions explicitly set the content type to "text/plain" and pass the exception message through to the message body (via Puppet::Network::HTTP::Response#respond_with, Puppet::Network::HTTP::RackREST#set_response, Rack::Response#write). Exceptions outside of the handler's call (issues with the rack app itself) return a 500 via a substantively similar, but different code path, in 'network/http/rack'. Setting the content type properly, retrieving the requested format (defaulting to P JSON), and rendering the content accordingly – similar to our code for indirector paths should work. That approach should work assuming the Exception/message instance that we pass into the formatter chooser has supported_formats and to_pson defined that list pson as a valid serialization format and can serialize to the schema linked in the description respectively. Fantastically, nearly the exact same described beast exists in 'network/http/error' and conveniently its subclasses are the exceptions we're throwing all over the place. Given the above I think we can implement this by: Update do_http_control_exception to pass the exception it receives to the formatter and pass the properly formatted response on to the request. Update the do_exception handler to do similar after first wrapping the passed exception in a Puppet::Network::HTTP::Error::HTTPError:: HTTPBadRequestError. Update the 500 error handling to be substantively similar to the #2 above but first wrapping any exceptions in a Puppet::Network::HTTP::Error::HTTPError::HTTPServerError, natch. Gotcha: the HTTP error classes don't implement a supported_formats method, so we either need to implement that on their base class or rework/write our own version of accepted_response_formatter_for/accepted_response_formatter_or_pson (we may have to roll our own anyways/extract that functionality out for the 500 processing since that happens in the Rack app outside of an indirected route). Open question: 1. Accept header requirements and pson vs json: accepted_response_formatter_for requires an accepts header to be specified by the client. Is that the correct level of pedantry? accepted_response_formatter_or_pson defaults to pson if the accepts header isn't present, which is basically json, which seems fine... But pson serialization is implemented for indirector classes and/or resources while the current HTTP exceptions have implemented json serialization. I'm spacing on when and why its okay to do one and not the other (see if there's docs for that).
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller assigned an issue to Justin Stoller Puppet / PUP-3827 Errors from indirected routes don't match error schema Change By: Justin Stoller Assignee: Justin Stoller Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4807) enable Pipeline for running puppet (facter, hiera) on PE-only agent platforms
Title: Message Title Justin Stoller commented on PUP-4807 Re: enable Pipeline for running puppet (facter, hiera) on PE-only agent platforms I think this ticket is superseded by other more specific tickets from the platform addition process i.e. solaris 10 and el 4 are now in, and we have individual tickets in the QENG project for the remaining work (QENG-2866, QENG-2869, QENG-2875, QENG-2972, QENG-2900). Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4864) Get pre-suites working for Fedora 22
Title: Message Title Justin Stoller commented on PUP-4864 Re: Get pre-suites working for Fedora 22 Sounds good, I've updated stable and QENG-2677 accordingly. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4864) Get pre-suites working for Fedora 22
Title: Message Title
Justin Stoller commented on PUP-4864
Re: Get pre-suites working for Fedora 22
Also, you should be able to build packages for any platform locally by checking out puppet-agent and after {{bundle install}}ing run: bundle exec build puppet-agent where platform is the filename at (from the root of the puppet-agent repo) configs/platforms/.rb
NB: if the ssh key to log into pooler vms isn't part of your ssh agent then you'll need to specify VANAGON_SSH_KEY=/path/to/pooler/key
That should leave you with a local package, I know CI calls a ship and a repo command (in that order) to stage the local packages to builds.d.pl.n and create the package repositories that the acceptance tests expect, respectively. Melissa Stone & Matthaus Owens would have to chime in if that's something Developers can do locally (I don't know if there'd be permissions issues). They might also know if there's a confluence page on this (I couldn't find it).
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-4864) Get pre-suites working for Fedora 22
Title: Message Title Justin Stoller commented on PUP-4864 Re: Get pre-suites working for Fedora 22 Should I bite off part of QENG-2677 and put F22 into the master Puppet pipeline as a build only target and folks can test locally the ci:test:aio target? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5004) Add node definitions for Fedora 22 to the source repos
Title: Message Title Justin Stoller assigned an issue to Eric Sorenson Puppet / PUP-5004 Add node definitions for Fedora 22 to the source repos Change By: Justin Stoller Assignee: qeng Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5004) Add node definitions for Fedora 22 to the source repos
Title: Message Title Justin Stoller moved an issue Puppet / PUP-5004 Add node definitions for Fedora 22 to the source repos Change By: Justin Stoller Fix Version/s: PE 2015.2.1 Fix Version/s: PUP 4.2.2 Component/s: CI Component/s: QA Workflow: Quality Engineering Scrum Team Workflow Key: QENG PUP - 2749 5004 Project: Quality Engineering Puppet Add Comment
Jira (PUP-4864) Get pre-suites working for Fedora 22
Title: Message Title Justin Stoller commented on PUP-4864 Re: Get pre-suites working for Fedora 22 I've updated the Confluence doc to more closely match what I believed reality to be (and the tickets that Melissa is creating I believe are based on that). Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4864) Get pre-suites working for Fedora 22
Title: Message Title Justin Stoller commented on PUP-4864 Re: Get pre-suites working for Fedora 22 That seems like an error in the Confluence page. I believe the scrum teams own the tests for any given project (Dev + QA). I know that Kevin Imber helped out with the PE only platforms because no one seemed to actually own that and I've helped out with other changes when deadlines were tight, but I believe both of those examples are QE pitching in when a project goes sideways and (save for us all pitching in to help each other) not how things should go in the future. I'll update the Confluence page, as far as I know this is definitely Client work. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4949) Puppet Agent - Add PE testing in Jenkins pipeline
Title: Message Title Justin Stoller commented on PUP-4949 Re: Puppet Agent - Add PE testing in Jenkins pipeline Sounds good. What is the timeframe on this? I will pull working on that into our next sprint. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4949) Puppet Agent - Add PE testing in Jenkins pipeline
Title: Message Title Justin Stoller commented on PUP-4949 Re: Puppet Agent - Add PE testing in Jenkins pipeline puppet_agent (master): Step 6 – System Tests with Enterprise Stable on All Automated Systems This is typically targeted at the latest released version of PE. New versions of a module must pass this in order to be considered supported. NB: this still points to PE 3.8.1 and I would normally update it later this week to point to PE 2015.2.0. puppet_agent (master): Step 7.a – System Tests with Enterprise Next on All Automated Systems This tests whatever the version of PE is currently in Development (It currently points to the gold, tagged build of PE 2015.2.0. We would normally update it next week for the PE 3.8.2 release and after that ships update it to point to 2015.2.1) puppet_agent (master): Step 7.b – System Tests with FOSS 3.x on Core Platforms Step 5 is currently pointed at puppet-agent 1.x and this remains to ensure we continue to support Puppet 3.x for a while Two major things of note: 1. I currently have a PR open for review that will move managing pipeline into JJB (the puppet_agent pipeline isn't included yet, but aside from it and catalog_preview every module in the "linux", "windows" and "cross platform" tabs in Jenkins should be accounted for). I'm hoping to roll those out later this week and not do any more updating of the older pipelines. In the JJB work we have moved from using the terminology of PE "stable" and "next" to named jobs after the Y version (ie PE 3.8.x, PE 2015.2.x). 2. I believe the puppet_agent module, at least as far as upgrading goes, doesn't really need those steps... (which is why I haven't included it in the current JJB PR). I was planning on reaching out (to you folks, cloud, and netdev) after the brunt of the module pipeline JJB work had been approved and merged. But if we can hash out what the steps should be for testing here I'll go ahead and roll it into the current PR (: Add Comment
Jira (PUP-4808) Enable testing puppet_agent module with full build matrix in jenkins-modules
Title: Message Title Justin Stoller updated an issue Puppet / PUP-4808 Enable testing puppet_agent module with full build matrix in jenkins-modules Change By: Justin Stoller Scope Change Reason: Needed for SG Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4808) Enable testing puppet_agent module with full build matrix in jenkins-modules
Title: Message Title Justin Stoller commented on PUP-4808 Re: Enable testing puppet_agent module with full build matrix in jenkins-modules Whoopsie! I've gone ahead and removed it and re-kicked the pipeline. Lemme know when it looks right to you. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4808) Enable testing puppet_agent module with full build matrix in jenkins-modules
Title: Message Title Justin Stoller assigned an issue to Michael Smith Puppet / PUP-4808 Enable testing puppet_agent module with full build matrix in jenkins-modules Change By: Justin Stoller Assignee: Justin Stoller Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4808) Enable testing puppet_agent module with full build matrix in jenkins-modules
Title: Message Title Justin Stoller assigned an issue to Michael Smith Puppet / PUP-4808 Enable testing puppet_agent module with full build matrix in jenkins-modules Change By: Justin Stoller Assignee: Justin Stoller Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4808) Enable testing puppet_agent module with full build matrix in jenkins-modules
Title: Message Title Justin Stoller commented on PUP-4808 Re: Enable testing puppet_agent module with full build matrix in jenkins-modules I've gone ahead and added these, though Utopic is failing now. I'm unclear if this is a CI issue or a setup issue or a code issue. Can you please let me know Michael Smith? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4808) Enable testing puppet_agent module with full build matrix in jenkins-modules
Title: Message Title Justin Stoller updated an issue Puppet / PUP-4808 Enable testing puppet_agent module with full build matrix in jenkins-modules Change By: Justin Stoller Sprint: Client QE 2015-07- 22 15 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4455) Create Boilerplate C++ Project Repo in Github
Title: Message Title Justin Stoller commented on PUP-4455 Re: Create Boilerplate C++ Project Repo in Github Looks good, Michael Smith! Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4757) Update pre-suites to install puppet-agent on "pe" platforms
Title: Message Title Justin Stoller commented on PUP-4757 Re: Update pre-suites to install puppet-agent on "pe" platforms Per an email from Michael Stahnke yesterday the scope of this ticket (for the SG launch) is only SLES & Ubuntu 10.04. The remaining platforms will be post launch. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4807) enable Pipeline for running puppet (facter, hiera) on PE-only agent platforms
Title: Message Title Justin Stoller commented on PUP-4807 Re: enable Pipeline for running puppet (facter, hiera) on PE-only agent platforms I've removed EL4 from the build/test matrix per Michael Stahnke's request. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4807) enable Pipeline for running puppet (facter, hiera) on PE-only agent platforms
Title: Message Title Justin Stoller commented on PUP-4807 Re: enable Pipeline for running puppet (facter, hiera) on PE-only agent platforms This pipeline was set up a while ago but the tests were disabled so we could continue to promote stable into PE. I've gone ahead and set the jobs to trigger downstream jobs always (even if they fail) so that we can see what platforms are failing and even if they are we can get the passing platforms promoted into PE. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4757) Update pre-suites to install puppet-agent on "pe" platforms
Title: Message Title Justin Stoller commented on PUP-4757 Re: Update pre-suites to install puppet-agent on "pe" platforms AFAICT, these are the PE only platforms that we need to support: Redhat 4 Centos 4 SLES 10 SLES 11 SLES 12 Ubuntu 1004 AIX 5 AIX 6 AIX 7 Solaris 10 Solaris 11 The first 5 should have host configs in the Facter, Hiera, and Puppet repos. The remaining will need to be added I assume. A complete list of supported platforms can be found here: https://confluence.puppetlabs.com/display/PROD/Supported+Platforms+for+Shallow+Gravy Of those listed SLES 10, 11, 12 and Ubuntu 1004 are the only platforms we actually can build puppet-agent for currently (linked tickets RE-4096, RE-4098, and RE-4668 about the work for EL 4, Solaris and AIX). The PE only pipeline is here (platforms with known build issues have been excluded so we can continue with testing) https://jenkins.puppetlabs.com/view/PE%20AIO/ Add Comment
Jira (PUP-4808) Enable testing puppet_agent module with full build matrix in jenkins-modules
Title: Message Title Justin Stoller commented on PUP-4808 Re: Enable testing puppet_agent module with full build matrix in jenkins-modules Michael Smith, we usually just test FOSS on the basic platforms (for a smoke test) and then test all the platforms on PE (that's the way the job currently is set up). If I'm understanding correctly, you want me to add all the supported platforms for Deb and EL? Including Jessie? What about Sci, OEL, and CentOS? Fedora??? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4757) Update pre-suites to install puppet-agent on "pe" platforms
Title: Message Title Justin Stoller created an issue Puppet / PUP-4757 Update pre-suites to install puppet-agent on "pe" platforms Issue Type: Task Assignee: Unassigned Created: 2015/06/16 4:02 PM Priority: Normal Reporter: Justin Stoller Specifically SLES and EL4 are failing: https://jenkins.puppetlabs.com/view/PE%20AIO/job/platform_aio-suite_intn-sys_stable-pe-puppet/2/ Note: both erring later in the pre-suite because the install_repos_on and install_packages_on methods are silently skipping platforms that they don't support. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4478) Extend upgrade module to deb platforms
Title: Message Title Justin Stoller commented on PUP-4478 Re: Extend upgrade module to deb platforms Is it a big deal if they use masters of the same platform as the agent? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4478) Extend upgrade module to deb platforms
Title: Message Title Justin Stoller commented on PUP-4478 Re: Extend upgrade module to deb platforms Thanks for the heads up! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4688) Ensure tests work correctly on OSX
Title: Message Title Justin Stoller created an issue Puppet / PUP-4688 Ensure tests work correctly on OSX Issue Type: Task Assignee: Unassigned Created: 2015/06/03 8:55 AM Priority: Normal Reporter: Justin Stoller Initial testing on Facter has shown some test failures 1 . I believe the pre-suite may also be needed for Puppet (besides an audit in general). I'm unclear of the scope of this, but I wanted to get a ticket filed for further discussion and provide a place for those more knowledgeable to dump their information. OSX packages to test the suites are available here: http://builds.delivery.puppetlabs.net/puppet-agent/ed7945e129242f6074a4f842b10dd92b5ed19044/artifacts/osx/PC1/ 1. https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Master/view/Facter/job/platform_aio-facter_intn-sys_master/18/SLAVE_LABEL=beaker,TEST_TARGET=osx-1010-x86_64/ Add Comment
Jira (PUP-4550) Audit acceptance tests for user type
Title: Message Title Justin Stoller commented on PUP-4550 Re: Audit acceptance tests for user type That makes a lot of sense, Kurt Wall, thanks! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4550) Audit acceptance tests for user type
Title: Message Title Justin Stoller commented on PUP-4550 Re: Audit acceptance tests for user type what are the appropriate test levels for testing a user type? I would imagine the exhaustive testing that you've found via puppet resource user would be best at the spec/unit level? With maybe the riskiest ones done at the spec/integration level and the maybe one large test at the acceptance/ level? (Sorry if this is derailing the ticket, this is something I'm also personally interested in. if this is a non-sequitor to the ticket please tell me to shut up (: ) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4638) Rename module to puppetlabs-puppet_agent
Title: Message Title Justin Stoller commented on PUP-4638 Re: Rename module to puppetlabs-puppet_agent You renamed the pipeline? I assume you mean repo. Please let me know if you manually changed the pipelines. I've deleted the old pipeline now that we've seen the new one go green end to end. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4638) Rename module to puppetlabs-puppet_agent
Title: Message Title Justin Stoller commented on PUP-4638 Re: Rename module to puppetlabs-puppet_agent pipeline deployed here: https://jenkins-modules.puppetlabs.com/view/4.%20cross%20platform/view/puppet_agent/view/master/ just ping me and I'll enable it (its disabled so it isn't red on the radiator) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-3742) Acceptance test Windows Gems
Title: Message Title Justin Stoller commented on PUP-3742 Re: Acceptance test Windows Gems This is a fairly broad ticket. Could we say that the goal here is to run a task, say rake ci:test:gem that installs the puppet/facter/hiera gems that are laid down on builds.delivery.puppetlabs.net. This task shouldn't run the full suite, instead it should run a few specific smoke test commands (puppet agent -t, facter -p, and friends). Would this be work that John Duarte takes on? Would this be solely for Windows (yes, I can read the summary, but I thought we had issues installing gems on other platforms as well). Did we decide that the risk was too small for other open source platforms to be worth the effort? /cc Kylo Ginsberg I believe the goal would be to put this into only the release branch pipeline (aardwolf), and would only run during normal release branch testing. Is that true? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4567) Fix acceptance infrastructure
Title: Message Title Justin Stoller commented on PUP-4567 Re: Fix acceptance infrastructure Michael Smith, thanks for the heads up. I've updated the scripts, redeployed the pipeline and kicked it off. It looks like it's appropriately failing (since it requires 3.8.x and it hasn't been released to FOSS yet) here: https://jenkins-modules.puppetlabs.com/view/4.%20cross%20platform/view/agent_upgrade/view/master/job/modules_puppetlabs-agent_upgrade_intn-sys_core-master-foss-stable/11/PLATFORM_CONFIG=redhat-7-64mda-inverted,SLAVE_LABEL=beaker/consoleFull Let me know if there's anything else I can do! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4532) Remove passenger testing in AIO pipelines
Title: Message Title Justin Stoller commented on PUP-4532 Re: Remove passenger testing in AIO pipelines Kylo Ginsberg, not nitpicky at all. My apologies about that. Updated. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4532) Remove passenger testing in AIO pipelines
Title: Message Title Justin Stoller commented on PUP-4532 Re: Remove passenger testing in AIO pipelines Deleted Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4623) Port package tests to be able to test against MSIs
Title: Message Title Justin Stoller created an issue Puppet / PUP-4623 Port package tests to be able to test against MSIs Issue Type: Task Assignee: Unassigned Created: 2015/05/18 9:19 AM Priority: Normal Reporter: Justin Stoller Currently the 3.x pipeline is testing Windows installations from source. For many reasons we would like to test from built MSIs hosted at builds.delivery.puppetlabs.net. It seems as if the simplest approach would be to amend the pre-suite used by the ci:test:packages rake task to install MSIs if the task was given a config file with windows hosts. This work would be similar to the AIO installation steps. Add Comment This message was sent by Atlassian JIRA (
Jira (PUP-4492) Investigate: plan for module testing with puppet-agent
Title: Message Title Justin Stoller assigned an issue to Kylo Ginsberg Puppet / PUP-4492 Investigate: plan for module testing with puppet-agent Change By: Justin Stoller Assignee: Justin Stoller Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4492) Investigate: plan for module testing with puppet-agent
Title: Message Title Justin Stoller commented on PUP-4492 Re: Investigate: plan for module testing with puppet-agent For spec level testing currently module authors can continue to use Facter 2. And hopefully an SDK will provide that functionality later on. (Though there's been discussion about shipping compiled gems if the SDK isn't going to be until after Puppet 5, and I think that Eric Sorenson owns that convo) As far as acceptance testing goes there's a small amount of Beaker updates and a chain of module team work that culminates in testing the modules against AIO in PE: QENG-2371 (supported modules are only technically supported against PE releases). That chain AFAICT is roughly: Module team updates supported modules to include puppet 4 via gem in spec testing on travis (as a non-failing cell) Module team to triage failures, ticket issues Once the module team is ready to turn puppet 4 on in CI spec tests we'll do that (QENG-2374) (either when they've fixed the issues in an ad hoc way, or their ready for it to be their primary focus and have their board go red) Once specs are green we'll enable testing of the puppet-agent package in the FOSS.next stage of their pipelines (QENG-2372, requires BKR-195) The module team will fix any issues that arise with that Once FOSS.next is stable green, we'll migrate the puppet-agent to be the FOSS.stable step in their pipeline. We'll remove the FOSS.next step and replay it with a FOSS.legacy step that tests old puppet 3.x compat (QENG-2373 a CI maintenance task) After the FOSS issues have been ironed out and SG goes code complete we'll re-enable the PE.next step in the pipelines and make sure they point at SG (QENG-2371, BKR-252). Then the module team will fix any issues that shake out from SG integrations with puppet-agent. I've ticket the work that I think needs ticketing. I believe the module team is in the process of ticketing what work they can (though it may just be "triage failures" that this point). Either way I think FM-2657 is the place for the action.
Jira (PUP-4380) Split non-core puppet functionality into modules
Title: Message Title Justin Stoller commented on PUP-4380 Re: Split non-core puppet functionality into modules Kylo Ginsberg, Eric Sorenson, just to clarify, the MVP for this in the SG timeframe is not to simply "module-ify" nagios within the puppet code base, but to remove it from the code base and transition it to being a supported module (supported by either the module or client team)? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module A basic module pipeline is up here (with Ruby 1.8). I will enable it (and iterate on it) once dev is ready to go! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module FWIW, there's also these docs that are important to scoping work with a supported module: RE Supported Release Process Module Team Checklist Intro to Module Team Practices and Tools Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module From initial blush, I'd like to just go ahead and create the pipeline once we have a repo set up with the values listed above and then we can iterate if there's issues that arise. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module One thing that just struct me was that usually in a request for a module pipeline there's a name for the module already. What will the name for the module be (and there's a convention assumed of being puppetlabs-) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module It may be important to point out that the module team doesn't write bare rspec tests only rspec-puppet and beaker-rspec tests and they have refused any PRs that touch the underlying system. If there's going to be rspec tests that test the underlying operating system the module team's pipeline isn't going to work. There are tickets (related to QENG-1633) to set up module pipelines for the Window's team that are an amalgamation of the platform team's spec workflow and the module team's acceptance testing workflow. However that's a work in progress and isn't as well automated as the module team's workflow yet. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module what are the versions of Puppet - is - (it) supports (3.x?) We are only supporting upgrades from 3.8.0 to 4.y. There will be behavior differences when running on puppet < 3.8 and >= 4.0, though I don't think we need acceptance testing for that. This question is for rspec-puppet testing. The module team runs specs via rspec-puppet and different versions of puppet are used like different versions of ruby. The version of puppet to install is passed into the Gemfile via the PUPPET_GEM_VERSION environment variable. See a good example of a Gemfile here. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module what are the platforms it supports at the acceptance level? (all PE supported Linices?) Initially, I'd suggest starting with tier 1 open source platforms. Eventually this should also include PE supported platforms including Windows. For some context, the module team's acceptance pipelines are split into several steps: Step 5 is the first acceptance test job. It's for fast feedback/smoke testing/if-and-when-we-ever-get-pr-testing-what-will-be-tested-on-pr. Even though there is explicitly no support for FOSS it uses FOSS installs because it has been traditionally much faster to install than a PE stack. It is between 2 and 4 platforms, whatever gives the best bang for buck testing wise. The module team hasn't approached me about updating them, but I have a feeling we should (since they were created we created testing tiers and rhel7 has become mainstream). Step 6 is against all PE supported platforms that the module supports using the latest released version of PE. This is the explicitly supported test matrix for the module, though it is situated so that it can be ran nightly (if there's been commits) when we need to constrain resources. Step 7 is additional testing against upcoming platform features. There are multiple jobs in this step, currently they are: 7.a – PE next testing. These are typically enabled once PE next goes code complete. Testing against a tagged RC for these modules is a release criteria for PE. 7.b – Future platform support. These are jobs that run with future parser and strict variables (and any toggles the platform team has opened up to the community for preparing for future releases of the platform that the module team is concerned with). Add Comment
Jira (PUP-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module what is the command to run the acceptance tests (bundle exec rspec spec/acceptance)? Why not rake? The MVP of beaker-rspec was to allow module developers to run their acceptance tests via the same style of short command line invocation that they use to run their other tests. That, of course, doesn't preclude using rake to wrap that command, and since the beaker-rspec MVP the community added a rake task for doing exactly that. However, I haven't discussed with the module team if they'd like to update their default since then and they haven't approached me about it. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module I usually ask two sets of questions wrt setting up a module pipeline, first around infrastructure/tooling: I don't see any unusual infrastructure needs for this testing, please correct me if I'm wrong. As far as tooling goes, beaker supports upgrades for PE and in a normal situation could support them fine for FOSS. However, what we'd be doing in beaker terms is switching the "type" of test run we're doing (from "foss" to "aio"). Which we can't do in a run without some hacks. We would need to run the pre-suite as "foss" and then manually set the hosts' metadata about where to find puppet after the upgrade. There's going to be a number of other gotchas using our automated tooling (is the module going to be upgrading the master as well? the "type" of test run in beaker sets up a number of assumptions). Its certainly feasible, I don't know at this point, if it would be worthwhile however. Second set is for the pipeline itself, here's the normal questionnaire: Basically does this module adhere to the "standard" module team owned module pipelines, if not, how does it different? I've broken that down into specific questions below (defaults for the module team owned module pipelines are in parens). should it be lint tested (yes)? what are the versions of Ruby it supports (1.9.3 & 2.1.5?) what are the versions of Puppet is supports (3.x?) are there different axes that are important to spec testing (no)? what is the command to run the unit tests (bundle exec rake spec?) what are the platforms it supports at the acceptance level? (all PE supported Linices?) are there different axes that are important to acceptance testing beside platforms (like how AWS doesn't have platform dependent code but does vary based on IAM account type – default: no)? what is the command to run the acceptance tests (bundle exec rspec spec/acceptance)? does a pipeline that tests against a couple of FOSS platforms for rapid feedback and then against all PE platforms for final validation make sense (yes)?
Jira (PUP-4380) Split non-core puppet functionality into modules
Title: Message Title Justin Stoller commented on PUP-4380 Re: Split non-core puppet functionality into modules Also, to provide info to the question I raised, I believe elsewhere Eric Sorenson set the initial scope of this (Puppet 4.2 timeframe) to include organizing the types and providers internally as modules so they are pulled down via filesync. Though they continue to be in tree and maintained by PL they otherwise "look" like modules. Then through the PUP 4 lifetime they would be moved to community namespace or wherever. I still have a feeling that the "wherever" for PE support through the 4.x lifecycle will mean some kind of collaboration with the supported modules team. But that decision doesn't need to be made now. Kylo Ginsberg, are the core/external types going to be documented somewhere, like an arm? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (FACT-963) Investigate usage of JSON gem in acceptance tests
Title: Message Title Justin Stoller created an issue Facter / FACT-963 Investigate usage of JSON gem in acceptance tests Issue Type: Bug Assignee: Unassigned Created: 2015/04/24 10:28 AM Priority: Normal Reporter: Justin Stoller The acceptance tests attempt to install the JSON gem everywhere for all types of installations. The tests require them and certain features for certain installation types require them. Where and when exactly is unknown. Specifically testing is blocked for AIO on Debian 8 because it does not contain the same libjson-gem that the tests try to install. Either the pre-suite needs to be updated to install the correct lib in the correct way, or if it isn't necessary to install it on the hosts for testing in AIO, the dependency should be removed from the AIO pre-suite. Add Comment
Jira (FACT-963) Investigate usage of JSON gem in acceptance tests
Title: Message Title Justin Stoller updated an issue Facter / FACT-963 Investigate usage of JSON gem in acceptance tests Change By: Justin Stoller Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4380) Split non-core puppet functionality into modules
Title: Message Title Justin Stoller commented on PUP-4380 Re: Split non-core puppet functionality into modules Does this have implications for for supported modules and module pipelines (eg tagmail)? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (PDB-1300) Make acceptance tests compatible with Puppet 4.0
Title: Message Title Justin Stoller commented on PDB-1300 Re: Make acceptance tests compatible with Puppet 4.0 Kenneth Barber, what did you decide on how you'd like to see this in CI? I've got the ticket QENG-1997 for a new job, but it sounded like you'd prefer another axis in your matrix, maybe? If so there's little work for me to do and I'm going to close out my QENG ticket as unnecessary (just ping me in this ticket if/when you want me to add an axis to your matrix (: ). Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (PDB-1300) Make acceptance tests compatible with Puppet 4.0
Title: Message Title Justin Stoller commented on PDB-1300 Re: Make acceptance tests compatible with Puppet 4.0 Kenneth Barber, I believe the idea was that PDB would need to support installation with both Puppet 3 and AIO for the foreseeable future. And that initially it wouldn't need the "upgrade" value of the installation type axis. And so a new job was preferable to a fourth (sparse) matrix axes. If that's not the case, let me know and we can change the implementation in CI. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (FACT-887) Submodules should use internal mirror if so configured
Title: Message Title Justin Stoller commented on FACT-887 Re: Submodules should use internal mirror if so configured > Why the "largely" qualifier? I read the idea above as "do not use the gitmirror" – period. I'm generally opposed to the mirror, but we could use it for the initial checkout. There are also some technical limitations that would prevent us from moving directly to a mirror free world where I'm confident we won't have sporadic github issues. We need to up some way to extract our archives on a Windows slave (QENG-2124) We need to get Vanagon (and the Windows build script) to accept our archives instead of cloning every component (RE-4237) We do this for the modules currently (zero usage of the mirror) and I don't recall a failure from git checkouts occurring in recent memory. However those are relatively small repositories. I didn't realize this would be problematic and deployed the AIO pipelines using a similar configuration, (Josh has requested that we start using the mirror in the AIO pipeline in QENG-1855 – though it should be mentioned that failures noted in that ticket are from Vanagon's cloning behavior and will be resolved by RE-4237). Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (FACT-887) Submodules should use internal mirror if so configured
Title: Message Title Justin Stoller commented on FACT-887 Re: Submodules should use internal mirror if so configured Relating this to another git mirror ticket as my preferred solution to this issue largely removes our usage of the gitmirror and I want to track the convo that may or may not happen as it relates to both Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (FACT-887) Submodules should use internal mirror if so configured
Title: Message Title Justin Stoller commented on FACT-887 Re: Submodules should use internal mirror if so configured I think the best way to handle things like this is to have an init job that resolves the dependencies and then creates a tarball the downstream tests, packaging and promotion can consume. That way you're you limiting your exposure to Github flakiness at one unambiguous point in your pipeline. We do this on the modules side of the house. None of the modules are mirrored internally. We reach out to the internet only once in the init step of each pipe. Combined with the SCM retry feature of Jenkins I don't know if Github has ever been a source of flakiness in the 400+ jobs that run on their Jenkins. This may require tooling updates for some of RE's tools (like the AIO pipeline currently creates said artifact, uses it every test target whether spec or acceptance[1] but then vanagon reaches out to the internet for every build target). 1. We aren't doing this for Windows specs because the slaves aren't currently set up to untar archives. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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.
