Re: [Puppet Users] Puppet apt repository broken?

2019-05-16 Thread Peter Berghold 
After 30+ years in the IT industry I'd have to say "stuff happens."

Thanks for giving it attention

On Wed, May 15, 2019 at 5:06 PM Morgan Rhodes  wrote:

> The bionic repo should be working again. Let us know if you have any more
> issues.
>
> On Wed, May 15, 2019 at 1:45 PM Morgan Rhodes  wrote:
>
>> Hi Peter,
>>
>> Apologies, we've been having some repo issues today. I'm getting the
>> bionic repository updated now and it should be done within the hour. I will
>> send another update here when it completes.
>>
>> On Wed, May 15, 2019 at 1:43 PM Peter Berghold 
>> wrote:
>>
>>> Just this afternoon around 4PM I started noticing this happen in my
>>> Docker builds that incorporate loading the Puppet agent:
>>> W: Skipping acquire of configured file 'puppet/binary-all/Packages' as
>>> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have
>>> the component 'puppet' (component misspelt in sources.list?)
>>> W: Skipping acquire of configured file 'puppet/binary-amd64/Packages' as
>>> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have
>>> the component 'puppet' (component misspelt in sources.list?)
>>> Reading package lists...
>>> Building dependency tree...
>>> Reading state information...
>>> Package puppet-agent is not available, but is referred to by another
>>> package.
>>> This may mean that the package is missing, has been obsoleted, or
>>> is only available from another source
>>>
>>> E: Package 'puppet-agent' has no installation candidate
>>>
>>> same Docker build worked swimmingly earlier today and seems broken now
>>> with NOTHING changing in the build (except to add NTP).  Any idea why this
>>> is happening and more importantly any idea when the issue will go away?
>>>
>>>
>>>
>>> --
>>>
>>> Peter L. Berghold   salty.cowd...@gmail.com
>>>
>>> http://devops.berghold.net
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Puppet Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to puppet-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Morgan Rhodes
>> Release Engineering
>> mor...@puppet.com
>>
>
>
> --
> Morgan Rhodes
> Release Engineering
> mor...@puppet.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv05WW0i2z5sP7q0LyX65_TBR%3DiDOJYNddh%3DCAuxnaXVfA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 

Peter L. Berghold   salty.cowd...@gmail.com

http://devops.berghold.net

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAArvnv1-QMhHU-9-skuWcqwAfwxECEDgze95hPLkYJHQTt_Kxw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet apt repository broken?

2019-05-15 Thread Chris Taylor 
Hi Molly,

That's great news, thank you! (Sadly, I have a lot of inherited, crusty 
puppet code that means I'm stuck running a v3 setup until I can take 
delivery of a sufficient quantity of the round 'tuits' to re-base it all. 
Unfortunately, hexagonal ones are insufficient!)

I shall check in again the morning then.


Many thanks,
Chris

On Wednesday, May 15, 2019 at 11:34:26 PM UTC+1, Molly Waggett wrote:
>
> Hi Chris,
>
> We originally did not plan to support repositories on release-archives, 
> but due to the high demand, yes we are working to enable them as soon as 
> possible.
>
> On Wed, May 15, 2019 at 3:23 PM Chris Taylor  > wrote:
>
>> Guessing this is related to the archiving of the puppet 4 & older 
>> packages?
>>
>> I note that the yum archive still functions as a repo, but the apt one 
>> doesn't have any release files (or a dists folder), in spite of otherwise 
>> being structured appropriately.. Is this going to be fixed? (
>> release-archives.puppet.com/apt/)
>>
>> On Wednesday, May 15, 2019 at 10:06:23 PM UTC+1, Morgan Rhodes wrote:
>>>
>>> The bionic repo should be working again. Let us know if you have any 
>>> more issues.
>>>
>>> On Wed, May 15, 2019 at 1:45 PM Morgan Rhodes  wrote:
>>>
 Hi Peter,

 Apologies, we've been having some repo issues today. I'm getting the 
 bionic repository updated now and it should be done within the hour. I 
 will 
 send another update here when it completes.

 On Wed, May 15, 2019 at 1:43 PM Peter Berghold  
 wrote:

> Just this afternoon around 4PM I started noticing this happen in my 
> Docker builds that incorporate loading the Puppet agent:
> W: Skipping acquire of configured file 'puppet/binary-all/Packages' as 
> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have 
> the component 'puppet' (component misspelt in sources.list?)
> W: Skipping acquire of configured file 'puppet/binary-amd64/Packages' 
> as repository 'http://apt.puppetlabs.com bionic InRelease' doesn't 
> have the component 'puppet' (component misspelt in sources.list?)
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Package puppet-agent is not available, but is referred to by another 
> package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
>
> E: Package 'puppet-agent' has no installation candidate
>
> same Docker build worked swimmingly earlier today and seems broken now 
> with NOTHING changing in the build (except to add NTP).  Any idea why 
> this 
> is happening and more importantly any idea when the issue will go away? 
>
>
>
> -- 
>
> Peter L. Berghold   salty@gmail.com
>
> http://devops.berghold.net
>
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to puppet...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


 -- 
 Morgan Rhodes
 Release Engineering
 mor...@puppet.com

>>>
>>>
>>> -- 
>>> Morgan Rhodes
>>> Release Engineering
>>> mor...@puppet.com
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to puppet...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/5eaf34fc-a524-45b2-9c94-8ba176bb8c94%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> *Molly Waggett*
> she/her/hers
> Release Engineer @ Puppet, Inc.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5fa3bd92-2ba0-467e-8035-3ce035cd1970%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet apt repository broken?

2019-05-15 Thread Molly Waggett 
Hi Chris,

We originally did not plan to support repositories on release-archives, but
due to the high demand, yes we are working to enable them as soon as
possible.

On Wed, May 15, 2019 at 3:23 PM Chris Taylor  wrote:

> Guessing this is related to the archiving of the puppet 4 & older packages?
>
> I note that the yum archive still functions as a repo, but the apt one
> doesn't have any release files (or a dists folder), in spite of otherwise
> being structured appropriately.. Is this going to be fixed? (
> release-archives.puppet.com/apt/)
>
> On Wednesday, May 15, 2019 at 10:06:23 PM UTC+1, Morgan Rhodes wrote:
>>
>> The bionic repo should be working again. Let us know if you have any more
>> issues.
>>
>> On Wed, May 15, 2019 at 1:45 PM Morgan Rhodes  wrote:
>>
>>> Hi Peter,
>>>
>>> Apologies, we've been having some repo issues today. I'm getting the
>>> bionic repository updated now and it should be done within the hour. I will
>>> send another update here when it completes.
>>>
>>> On Wed, May 15, 2019 at 1:43 PM Peter Berghold 
>>> wrote:
>>>
 Just this afternoon around 4PM I started noticing this happen in my
 Docker builds that incorporate loading the Puppet agent:
 W: Skipping acquire of configured file 'puppet/binary-all/Packages' as
 repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have
 the component 'puppet' (component misspelt in sources.list?)
 W: Skipping acquire of configured file 'puppet/binary-amd64/Packages'
 as repository 'http://apt.puppetlabs.com bionic InRelease' doesn't
 have the component 'puppet' (component misspelt in sources.list?)
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Package puppet-agent is not available, but is referred to by another
 package.
 This may mean that the package is missing, has been obsoleted, or
 is only available from another source

 E: Package 'puppet-agent' has no installation candidate

 same Docker build worked swimmingly earlier today and seems broken now
 with NOTHING changing in the build (except to add NTP).  Any idea why this
 is happening and more importantly any idea when the issue will go away?



 --

 Peter L. Berghold   salty@gmail.com

 http://devops.berghold.net


 --
 You received this message because you are subscribed to the Google
 Groups "Puppet Users" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to puppet...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>> --
>>> Morgan Rhodes
>>> Release Engineering
>>> mor...@puppet.com
>>>
>>
>>
>> --
>> Morgan Rhodes
>> Release Engineering
>> mor...@puppet.com
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/5eaf34fc-a524-45b2-9c94-8ba176bb8c94%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFOE68B7P8zFT0Y49fGLJMMc8N8iZKo4xeLWLg_7akwzm4PD4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet apt repository broken?

2019-05-15 Thread Chris Taylor 
Guessing this is related to the archiving of the puppet 4 & older packages?

I note that the yum archive still functions as a repo, but the apt one 
doesn't have any release files (or a dists folder), in spite of otherwise 
being structured appropriately.. Is this going to be fixed? 
(release-archives.puppet.com/apt/)

On Wednesday, May 15, 2019 at 10:06:23 PM UTC+1, Morgan Rhodes wrote:
>
> The bionic repo should be working again. Let us know if you have any more 
> issues.
>
> On Wed, May 15, 2019 at 1:45 PM Morgan Rhodes  > wrote:
>
>> Hi Peter,
>>
>> Apologies, we've been having some repo issues today. I'm getting the 
>> bionic repository updated now and it should be done within the hour. I will 
>> send another update here when it completes.
>>
>> On Wed, May 15, 2019 at 1:43 PM Peter Berghold > > wrote:
>>
>>> Just this afternoon around 4PM I started noticing this happen in my 
>>> Docker builds that incorporate loading the Puppet agent:
>>> W: Skipping acquire of configured file 'puppet/binary-all/Packages' as 
>>> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have 
>>> the component 'puppet' (component misspelt in sources.list?)
>>> W: Skipping acquire of configured file 'puppet/binary-amd64/Packages' as 
>>> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have 
>>> the component 'puppet' (component misspelt in sources.list?)
>>> Reading package lists...
>>> Building dependency tree...
>>> Reading state information...
>>> Package puppet-agent is not available, but is referred to by another 
>>> package.
>>> This may mean that the package is missing, has been obsoleted, or
>>> is only available from another source
>>>
>>> E: Package 'puppet-agent' has no installation candidate
>>>
>>> same Docker build worked swimmingly earlier today and seems broken now 
>>> with NOTHING changing in the build (except to add NTP).  Any idea why this 
>>> is happening and more importantly any idea when the issue will go away? 
>>>
>>>
>>>
>>> -- 
>>>
>>> Peter L. Berghold   salty@gmail.com 
>>> 
>>>
>>> http://devops.berghold.net
>>>
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Puppet Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to puppet...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> -- 
>> Morgan Rhodes
>> Release Engineering
>> mor...@puppet.com 
>>
>
>
> -- 
> Morgan Rhodes
> Release Engineering
> mor...@puppet.com 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5eaf34fc-a524-45b2-9c94-8ba176bb8c94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet apt repository broken?

2019-05-15 Thread Morgan Rhodes 
The bionic repo should be working again. Let us know if you have any more
issues.

On Wed, May 15, 2019 at 1:45 PM Morgan Rhodes  wrote:

> Hi Peter,
>
> Apologies, we've been having some repo issues today. I'm getting the
> bionic repository updated now and it should be done within the hour. I will
> send another update here when it completes.
>
> On Wed, May 15, 2019 at 1:43 PM Peter Berghold 
> wrote:
>
>> Just this afternoon around 4PM I started noticing this happen in my
>> Docker builds that incorporate loading the Puppet agent:
>> W: Skipping acquire of configured file 'puppet/binary-all/Packages' as
>> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have the
>> component 'puppet' (component misspelt in sources.list?)
>> W: Skipping acquire of configured file 'puppet/binary-amd64/Packages' as
>> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have the
>> component 'puppet' (component misspelt in sources.list?)
>> Reading package lists...
>> Building dependency tree...
>> Reading state information...
>> Package puppet-agent is not available, but is referred to by another
>> package.
>> This may mean that the package is missing, has been obsoleted, or
>> is only available from another source
>>
>> E: Package 'puppet-agent' has no installation candidate
>>
>> same Docker build worked swimmingly earlier today and seems broken now
>> with NOTHING changing in the build (except to add NTP).  Any idea why this
>> is happening and more importantly any idea when the issue will go away?
>>
>>
>>
>> --
>>
>> Peter L. Berghold   salty.cowd...@gmail.com
>>
>> http://devops.berghold.net
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Morgan Rhodes
> Release Engineering
> mor...@puppet.com
>


-- 
Morgan Rhodes
Release Engineering
mor...@puppet.com

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv05WW0i2z5sP7q0LyX65_TBR%3DiDOJYNddh%3DCAuxnaXVfA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet apt repository broken?

2019-05-15 Thread Morgan Rhodes 
Hi Peter,

Apologies, we've been having some repo issues today. I'm getting the bionic
repository updated now and it should be done within the hour. I will send
another update here when it completes.

On Wed, May 15, 2019 at 1:43 PM Peter Berghold 
wrote:

> Just this afternoon around 4PM I started noticing this happen in my Docker
> builds that incorporate loading the Puppet agent:
> W: Skipping acquire of configured file 'puppet/binary-all/Packages' as
> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have the
> component 'puppet' (component misspelt in sources.list?)
> W: Skipping acquire of configured file 'puppet/binary-amd64/Packages' as
> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have the
> component 'puppet' (component misspelt in sources.list?)
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Package puppet-agent is not available, but is referred to by another
> package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
>
> E: Package 'puppet-agent' has no installation candidate
>
> same Docker build worked swimmingly earlier today and seems broken now
> with NOTHING changing in the build (except to add NTP).  Any idea why this
> is happening and more importantly any idea when the issue will go away?
>
>
>
> --
>
> Peter L. Berghold   salty.cowd...@gmail.com
>
> http://devops.berghold.net
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Morgan Rhodes
Release Engineering
mor...@puppet.com

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv24Rs2%2BuQUKS2vLSZqk1cxRXfft6WOorxcy_14sTtDZGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.