So I had been smashing my head against a wall, unsure why I was receiving an
error trying to utilize a Facter fact for Munin interface generation.
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Duplicate definition: Munin::Interfaces[eth0] is already defined in file
/etc/puppet/modules/munin/manifests/init.pp at line 14; cannot redefine at
/etc/puppet/modules/munin/manifests/init.pp:14 on node foo.bar
This led me down many roads until I decided to use notify {} to check the
contents of the variable inside of my maniest...
notice:
eth0,eth0_0,eth0_1,eth0_2,eth0_3,eth0_4,eth0_5,eth0_6,eth0_7,eth0_8,eth0_9,eth0_10,eth0_11,eth0_12,eth0_13,eth0_14,eth0_15,eth0_16,eth0_17,eth0_18,eth0_19,eth0_20,eth0_21,eth0_22,eth0_23,eth0_24,eth0_25,eth0_26,eth0_27,eth0_28,eth0_29,eth0_30,eth0_31,eth0
Ah-ha! So it''s truncating. Specifically after 256 characters.
# echo
"eth0,eth0_0,eth0_1,eth0_2,eth0_3,eth0_4,eth0_5,eth0_6,eth0_7,eth0_8,eth0_9,eth0_10,eth0_11,eth0_12,eth0_13,eth0_14,eth0_15,eth0_16,eth0_17,eth0_18,eth0_19,eth0_20,eth0_21,eth0_22,eth0_23,eth0_24,eth0_25,eth0_26,eth0_27,eth0_28,eth0_29,eth0_30,eth0_31,eth0"
| wc -c
256
Is this a known situation and if so, how can I augment Puppet, my manifest, or
otherwise to allow me to not have this limit?
Thanks!
-Mark
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Yeah, fire up MySQL and alter the column to be of type TEXT instead of VARCHAR(255). I ran into the same problem. I believe the column you are looking for is fact_values.value. On Feb 18, 2011, at 12:26 PM, Mark Stanislav wrote:> So I had been smashing my head against a wall, unsure why I was receiving an error trying to utilize a Facter fact for Munin interface generation. > > err: Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate definition: Munin::Interfaces[eth0] is already defined in file /etc/puppet/modules/munin/manifests/init.pp at line 14; cannot redefine at /etc/puppet/modules/munin/manifests/init.pp:14 on node foo.bar > > This led me down many roads until I decided to use notify {} to check the contents of the variable inside of my maniest... > > notice: eth0,eth0_0,eth0_1,eth0_2,eth0_3,eth0_4,eth0_5,eth0_6,eth0_7,eth0_8,eth0_9,eth0_10,eth0_11,eth0_12,eth0_13,eth0_14,eth0_15,eth0_16,eth0_17,eth0_18,eth0_19,eth0_20,eth0_21,eth0_22,eth0_23,eth0_24,eth0_25,eth0_26,eth0_27,eth0_28,eth0_29,eth0_30,eth0_31,eth0 > > Ah-ha! So it''s truncating. Specifically after 256 characters. > > # echo "eth0,eth0_0,eth0_1,eth0_2,eth0_3,eth0_4,eth0_5,eth0_6,eth0_7,eth0_8,eth0_9,eth0_10,eth0_11,eth0_12,eth0_13,eth0_14,eth0_15,eth0_16,eth0_17,eth0_18,eth0_19,eth0_20,eth0_21,eth0_22,eth0_23,eth0_24,eth0_25,eth0_26,eth0_27,eth0_28,eth0_29,eth0_30,eth0_31,eth0" | wc -c > 256 > > Is this a known situation and if so, how can I augment Puppet, my manifest, or otherwise to allow me to not have this limit? > > Thanks! > > -Mark > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Ahhh, that makes a lot of sense, Brian. I wouldn''t have thought about my store directly. Thanks, I''ll try that out. -Mark On Feb 18, 2011, at 3:47 PM, Brian Gallew wrote:> Yeah, fire up MySQL and alter the column to be of type TEXT instead of VARCHAR(255). I ran into the same problem. I believe the column you are looking for is fact_values.value. > > On Feb 18, 2011, at 12:26 PM, Mark Stanislav wrote: > >> So I had been smashing my head against a wall, unsure why I was receiving an error trying to utilize a Facter fact for Munin interface generation. >> >> err: Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate definition: Munin::Interfaces[eth0] is already defined in file /etc/puppet/modules/munin/manifests/init.pp at line 14; cannot redefine at /etc/puppet/modules/munin/manifests/init.pp:14 on node foo.bar >> >> This led me down many roads until I decided to use notify {} to check the contents of the variable inside of my maniest... >> >> notice: eth0,eth0_0,eth0_1,eth0_2,eth0_3,eth0_4,eth0_5,eth0_6,eth0_7,eth0_8,eth0_9,eth0_10,eth0_11,eth0_12,eth0_13,eth0_14,eth0_15,eth0_16,eth0_17,eth0_18,eth0_19,eth0_20,eth0_21,eth0_22,eth0_23,eth0_24,eth0_25,eth0_26,eth0_27,eth0_28,eth0_29,eth0_30,eth0_31,eth0 >> >> Ah-ha! So it''s truncating. Specifically after 256 characters. >> >> # echo "eth0,eth0_0,eth0_1,eth0_2,eth0_3,eth0_4,eth0_5,eth0_6,eth0_7,eth0_8,eth0_9,eth0_10,eth0_11,eth0_12,eth0_13,eth0_14,eth0_15,eth0_16,eth0_17,eth0_18,eth0_19,eth0_20,eth0_21,eth0_22,eth0_23,eth0_24,eth0_25,eth0_26,eth0_27,eth0_28,eth0_29,eth0_30,eth0_31,eth0" | wc -c >> 256 >> >> Is this a known situation and if so, how can I augment Puppet, my manifest, or otherwise to allow me to not have this limit? >> >> Thanks! >> >> -Mark >> >> -- >> You received this message because you are subscribed to the Google Groups "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
That indeed solved the issue. I don''t see a case open with regard to increasing the default column size but I think it may be prudent to do so. Anyone adamantly opposed? I''ll open a case if not. mysql> describe fact_values; | value | varchar(255) | NO | | NULL | | mysql> ALTER TABLE fact_values MODIFY value TEXT; Query OK, 1131 rows affected (0.04 sec) Records: 1131 Duplicates: 0 Warnings: 0 mysql> describe fact_values; | value | text | YES | | NULL | | defined ''message'' as ''eth0,eth0_0,eth0_1,eth0_2,eth0_3,eth0_4,eth0_5,eth0_6,eth0_7,eth0_8,eth0_9,eth0_10,eth0_11,eth0_12,eth0_13,eth0_14,eth0_15,eth0_16,eth0_17,eth0_18,eth0_19,eth0_20,eth0_21,eth0_22,eth0_23,eth0_24,eth0_25,eth0_26,eth0_27,eth0_28,eth0_29,eth0_30,eth0_31,eth0_32,eth0_33,eth0_34,eth0_35,eth0_36,eth0_37,eth0_38,eth0_39,eth0_40,eth0_41,eth0_42,eth0_43,eth0_44,eth0_45,eth0_46,eth0_47,eth0_48,eth0_49,eth0_50,eth0_51,eth0_52,eth0_53,eth0_54,eth0_55,eth0_56,eth0_57,eth0_58,eth0_59,eth0_60,eth0_61,eth0_62,eth0_63,eth0_64,eth0_65,eth0_66,eth0_67,eth0_68,eth0_69,eth0_70,eth0_71,eth0_72,eth0_73,eth0_74,eth0_75,eth0_76,eth0_77,eth0_78,eth0_79,eth0_80,eth0_81,eth0_82,eth0_83,eth0_84,eth0_85,eth0_86,eth0_87,eth0_88,eth0_89,eth0_90,eth0_91,eth0_92,eth0_93,eth0_94,eth0_95,eth0_96,eth0_97,eth0_98,eth0_99,eth0_100,eth0_101,eth0_102,eth0_103,eth0_104,eth0_105,eth0_106,eth0_107,eth0_108,eth0_109,eth0_110,eth0_111,eth0_112,eth0_113,eth0_114,eth0_115,eth0_116,eth0_117,eth0_118,eth0_119,eth0_120,eth0_121,eth0_122,eth0_123,eth0_124,eth0_125,eth0_126,eth0_127,eth0_128,eth0_129,eth0_130,eth0_131,eth0_132,eth0_133,eth0_134,eth0_135,eth0_136,eth0_137,eth0_138,eth0_139,eth0_140,eth0_141,eth0_142,eth0_143,eth0_144,eth0_145,eth0_146,eth0_147,eth0_148,eth0_149,eth0_150,eth0_151,eth0_152,eth0_153,eth0_154,eth0_155,eth0_156,eth0_157,eth0_158,eth0_159,eth0_160,eth0_161,eth0_162,eth0_163,eth0_164,eth0_165,eth0_166,eth0_167,eth0_168,eth0_169,eth0_170,eth0_171,eth0_172,eth0_173,eth0_174,eth1,eth2,eth3,sit0'' -Mark On Feb 18, 2011, at 3:47 PM, Brian Gallew wrote:> Yeah, fire up MySQL and alter the column to be of type TEXT instead of VARCHAR(255). I ran into the same problem. I believe the column you are looking for is fact_values.value. > > On Feb 18, 2011, at 12:26 PM, Mark Stanislav wrote: > >> So I had been smashing my head against a wall, unsure why I was receiving an error trying to utilize a Facter fact for Munin interface generation. >> >> err: Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate definition: Munin::Interfaces[eth0] is already defined in file /etc/puppet/modules/munin/manifests/init.pp at line 14; cannot redefine at /etc/puppet/modules/munin/manifests/init.pp:14 on node foo.bar >> >> This led me down many roads until I decided to use notify {} to check the contents of the variable inside of my maniest... >> >> notice: eth0,eth0_0,eth0_1,eth0_2,eth0_3,eth0_4,eth0_5,eth0_6,eth0_7,eth0_8,eth0_9,eth0_10,eth0_11,eth0_12,eth0_13,eth0_14,eth0_15,eth0_16,eth0_17,eth0_18,eth0_19,eth0_20,eth0_21,eth0_22,eth0_23,eth0_24,eth0_25,eth0_26,eth0_27,eth0_28,eth0_29,eth0_30,eth0_31,eth0 >> >> Ah-ha! So it''s truncating. Specifically after 256 characters. >> >> # echo "eth0,eth0_0,eth0_1,eth0_2,eth0_3,eth0_4,eth0_5,eth0_6,eth0_7,eth0_8,eth0_9,eth0_10,eth0_11,eth0_12,eth0_13,eth0_14,eth0_15,eth0_16,eth0_17,eth0_18,eth0_19,eth0_20,eth0_21,eth0_22,eth0_23,eth0_24,eth0_25,eth0_26,eth0_27,eth0_28,eth0_29,eth0_30,eth0_31,eth0" | wc -c >> 256 >> >> Is this a known situation and if so, how can I augment Puppet, my manifest, or otherwise to allow me to not have this limit? >> >> Thanks! >> >> -Mark >> >> -- >> You received this message because you are subscribed to the Google Groups "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Fri, Feb 18, 2011 at 13:00, Mark Stanislav <mark.stanislav@gmail.com> wrote:> That indeed solved the issue. I don''t see a case open with regard to increasing the default column size but I think it may be prudent to do so. Anyone adamantly opposed? I''ll open a case if not.Even if someone was opposed, having that recorded in a ticket, along with the arguments each way, would be ideal: it would let the next person to run into the issue discover why things are the way they are without having to involve the list. :) Daniel -- ⎋ Puppet Labs Developer – http://puppetlabs.com ✉ Daniel Pittman <daniel@puppetlabs.com> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 ♲ Made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
http://projects.puppetlabs.com/issues/6380 <-- if anyone is interested. Thanks for the help; a good way to end a Friday at work :) -Mark On Feb 18, 2011, at 4:21 PM, Daniel Pittman wrote:> On Fri, Feb 18, 2011 at 13:00, Mark Stanislav <mark.stanislav@gmail.com> wrote: > >> That indeed solved the issue. I don''t see a case open with regard to increasing the default column size but I think it may be prudent to do so. Anyone adamantly opposed? I''ll open a case if not. > > Even if someone was opposed, having that recorded in a ticket, along > with the arguments each way, would be ideal: it would let the next > person to run into the issue discover why things are the way they are > without having to involve the list. :) > > Daniel > -- > ⎋ Puppet Labs Developer – http://puppetlabs.com > ✉ Daniel Pittman <daniel@puppetlabs.com> > ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 > ♲ Made with 100 percent post-consumer electrons-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I actually moved that forward in our process to getting a design decision made, so it will work out what happens. If you wanted to produce an appropriate patch or whatever we would be happy to see that attached – I certainly see it as likely we will decide to approve such a change. Daniel On Fri, Feb 18, 2011 at 13:31, Mark Stanislav <mark.stanislav@gmail.com> wrote:> http://projects.puppetlabs.com/issues/6380 <-- if anyone is interested. Thanks for the help; a good way to end a Friday at work :) > > -Mark > > On Feb 18, 2011, at 4:21 PM, Daniel Pittman wrote: > >> On Fri, Feb 18, 2011 at 13:00, Mark Stanislav <mark.stanislav@gmail.com> wrote: >> >>> That indeed solved the issue. I don''t see a case open with regard to increasing the default column size but I think it may be prudent to do so. Anyone adamantly opposed? I''ll open a case if not. >> >> Even if someone was opposed, having that recorded in a ticket, along >> with the arguments each way, would be ideal: it would let the next >> person to run into the issue discover why things are the way they are >> without having to involve the list. :) >> >> Daniel >> -- >> ⎋ Puppet Labs Developer – http://puppetlabs.com >> ✉ Daniel Pittman <daniel@puppetlabs.com> >> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 >> ♲ Made with 100 percent post-consumer electrons > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- ⎋ Puppet Labs Developer – http://puppetlabs.com ✉ Daniel Pittman <daniel@puppetlabs.com> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 ♲ Made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
A final follow-up to this. Puppet is configured as ''text'' already after having viewed the source. However I am using ''The Foreman'' with it and the schema sets a string for that field. I''m guessing Brian was, too. Sorry for the crazyness, case was closed. Filing a bug instead with that project for schema parity. -Mark On Feb 18, 2011, at 4:35 PM, Daniel Pittman wrote:> I actually moved that forward in our process to getting a design > decision made, so it will work out what happens. If you wanted to > produce an appropriate patch or whatever we would be happy to see that > attached – I certainly see it as likely we will decide to approve such > a change. > > Daniel > > On Fri, Feb 18, 2011 at 13:31, Mark Stanislav <mark.stanislav@gmail.com> wrote: >> http://projects.puppetlabs.com/issues/6380 <-- if anyone is interested. Thanks for the help; a good way to end a Friday at work :) >> >> -Mark >> >> On Feb 18, 2011, at 4:21 PM, Daniel Pittman wrote: >> >>> On Fri, Feb 18, 2011 at 13:00, Mark Stanislav <mark.stanislav@gmail.com> wrote: >>> >>>> That indeed solved the issue. I don''t see a case open with regard to increasing the default column size but I think it may be prudent to do so. Anyone adamantly opposed? I''ll open a case if not. >>> >>> Even if someone was opposed, having that recorded in a ticket, along >>> with the arguments each way, would be ideal: it would let the next >>> person to run into the issue discover why things are the way they are >>> without having to involve the list. :) >>> >>> Daniel >>> -- >>> ⎋ Puppet Labs Developer – http://puppetlabs.com >>> ✉ Daniel Pittman <daniel@puppetlabs.com> >>> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 >>> ♲ Made with 100 percent post-consumer electrons >> >> -- >> You received this message because you are subscribed to the Google Groups "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >> >> > > > > -- > ⎋ Puppet Labs Developer – http://puppetlabs.com > ✉ Daniel Pittman <daniel@puppetlabs.com> > ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 > ♲ Made with 100 percent post-consumer electrons-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Sat, Feb 19, 2011 at 12:00 AM, Mark Stanislav <mark.stanislav@gmail.com>wrote:> A final follow-up to this. Puppet is configured as ''text'' already after > having viewed the source. > > However I am using ''The Foreman'' with it and the schema sets a string for > that field. I''m guessing Brian was, too. > > Sorry for the crazyness, case was closed. Filing a bug instead with that > project for schema parity. > > Just as a follow up, this was originally changed due to the lack of abilityto search for case sensitive fact values within text records, and should be corrected for the next upcoming release [1]. Ohad [1] - http://theforeman.org/issues/495 -Mark> > On Feb 18, 2011, at 4:35 PM, Daniel Pittman wrote: > > > I actually moved that forward in our process to getting a design > > decision made, so it will work out what happens. If you wanted to > > produce an appropriate patch or whatever we would be happy to see that > > attached – I certainly see it as likely we will decide to approve such > > a change. > > > > Daniel > > > > On Fri, Feb 18, 2011 at 13:31, Mark Stanislav <mark.stanislav@gmail.com> > wrote: > >> http://projects.puppetlabs.com/issues/6380 <-- if anyone is interested. > Thanks for the help; a good way to end a Friday at work :) > >> > >> -Mark > >> > >> On Feb 18, 2011, at 4:21 PM, Daniel Pittman wrote: > >> > >>> On Fri, Feb 18, 2011 at 13:00, Mark Stanislav < > mark.stanislav@gmail.com> wrote: > >>> > >>>> That indeed solved the issue. I don''t see a case open with regard to > increasing the default column size but I think it may be prudent to do so. > Anyone adamantly opposed? I''ll open a case if not. > >>> > >>> Even if someone was opposed, having that recorded in a ticket, along > >>> with the arguments each way, would be ideal: it would let the next > >>> person to run into the issue discover why things are the way they are > >>> without having to involve the list. :) > >>> > >>> Daniel > >>> -- > >>> ⎋ Puppet Labs Developer – http://puppetlabs.com > >>> ✉ Daniel Pittman <daniel@puppetlabs.com> > >>> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 > >>> ♲ Made with 100 percent post-consumer electrons > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups "Puppet Users" group. > >> To post to this group, send email to puppet-users@googlegroups.com. > >> To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > >> For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >> > >> > > > > > > > > -- > > ⎋ Puppet Labs Developer – http://puppetlabs.com > > ✉ Daniel Pittman <daniel@puppetlabs.com> > > ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 > > ♲ Made with 100 percent post-consumer electrons > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.