Thank you for the update. If this changes again on the server size,
please change the bug status back to New.
** Changed in: puppet (Ubuntu Trusty)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug report can be rejected, the redirect has been removed on the
server side so the existing code and clients using API v1 work again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594316
Thanks. If upstream decline to provide a patch, I think someone else
providing a patch would be fine. But I'd prefer to not diverge from
upstream if possible, so would like to give them first refusal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes, I think it only affects Trusty.
I think it's unlikely that upstream will provide a patch as upstream
since 3.6.0 has moved to a newer API version that isn't affected by this
issue. It does look likely from the FORGE-327 ticket above that the
server behaviour will be changed for this older
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I think this affects Trusty only - no other current
Ubuntu releases? I'll mark the bug accordingly. If upstream commits a
patch, we can certainly cherry-pick it. Since a workaround is available,
I'll set the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: puppet (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594316
Title:
** Summary changed:
- HTTP response we received was '404 Not Found' when using "puppet module
install"
+ HTTP response we received was '302 Found' when using "puppet module install"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
