pulp-2to3-migration 0.11.2 depends on pulpcore<3.13 and >=3.6
What pulp-2to3-migration is compatible with pulpcore 3.13?
On 15 June 2021 4:20:11 am Tanya Tereshchenko wrote:
See the announcement here:
https://github.com/pulp/community/discussions/24
___
Jun 1, 2021 at 3:12 AM Ben Stanley wrote:
Hello Daniel,
I attempted to upgrade my pulp installation using these instructions.
I upgraded the pulp_installer as described.
Note that I am behind a proxy server, and I have to edit the file
~/.ansible/collections/ansible_collections/pulp_installer/
Hello Daniel,
I attempted to upgrade my pulp installation using these instructions.
I upgraded the pulp_installer as described.
Note that I am behind a proxy server, and I have to edit the file
~/.ansible/collections/ansible_collections/pulp_installer/roles/pulp_common/tasks/repos.yml
to remo
"type": "rpm"
}
]
}
}
[root@honeybee ~]# pulp migration plan reset --href
"/pulp/api/v3/migration-plans/eeb9ad6e-ef60-4d17-b238-a7bf79e752e1/"
Error: ["Only one migration plan can run or be reset at a time"]
[root@hone
type": "rpm"
}
]
}
}
[root@honeybee plans]#
Finally it worked!
Ben.
[1] https://pulp-2to3-migration.readthedocs.io/en/latest/configuration.html
On 14/5/21 4:34 pm, Matthias Dellweg wrote:
It seems to be the mongodb pulp is unable to connect to.
Can you check with syst
This problem is preventing me from making further progress migrating my
server now.
Could I please get some help to diagnose the problem and get the system
going again?
Thanks,
Ben Stanley
On 13/5/21 1:20 pm, Ben Stanley wrote:
Hello pulp-list,
I was able to migrate my pulp2 iso repos
;: "3.2.0"
},
{
"component": "file",
"version": "1.7.0"
},
{
"component": "deb",
"version": "2.11.1"
},
{
"component": "container",
pulp2 repository list
On Wed, May 12, 2021 at 9:43 AM Ben Stanley <mailto:ben.stan...@gmail.com>> wrote:
Please see responses inline.
On 6/5/21 8:15 pm, Matthias Dellweg wrote:
On Thu, May 6, 2021 at 2:32 AM Ben Stanley mailto:ben.stan...@gmail.com>> wrote:
I
Please see responses inline.
On 6/5/21 8:15 pm, Matthias Dellweg wrote:
On Thu, May 6, 2021 at 2:32 AM Ben Stanley <mailto:ben.stan...@gmail.com>> wrote:
I have changed my ~/.config/pulp/settings.toml file as follows:
Old: base_url = "http://honeybee"; <ht
ible/devel/user_guide/collections_using.html#installing-collections
<https://docs.ansible.com/ansible/devel/user_guide/collections_using.html#installing-collections>
Best of luck!
Matthias
On Thu, May 6, 2021 at 1:52 AM Ben Stanley <mailto:ben.stan...@gmail.com>> wrote:
Matth
in your CLI config file.
We captured the problem earlier here:
https://github.com/pulp/pulp-cli#known-issues
<https://github.com/pulp/pulp-cli#known-issues>
And we will try to capture that case in the abovementioned issue and
create a better error message.
T
r as i remember "--force" is needed with the ansible-galaxy
command to (re-)install any already installed collection. Even if the
collection is available in a newer version.
I'm sorry for the inconvenience.
Matthias
On Wed, May 5, 2021 at 8:10 AM Ben Stanley <mailto:b
20210505_pulp_status.txt
I have also re-run the migration plan create with -vvv . The output is
attached as 20210505_pulp_migration_create_vvv.txt . I hope it means
more to you than it does to me.
Ben Stanley.
On 4/5/21 6:58 pm, Matthias Dellweg wrote:
Hello again.
The pulp cli is using requests to talk to
'3.12.0'. Use --force to overwrite
[root@honeybee ]#
Sorry I'm no expert on ansible or ansible-galaxy.
Could you please explain how I can upgrade pulp.pulp_installer?
Thanks,
Ben Stanley
On 4/5/21 4:14 am, Tanya Tereshchenko wrote:
Pulpcore 3.12.2 is now available [0].
This rel
hope this can give some insight.
On Tue, May 4, 2021 at 2:18 AM Ben Stanley <mailto:ben.stan...@gmail.com>> wrote:
Hello pulp-list,
I am attempting to migrate my pulp2 to pulp3.
I seem to be facing difficulties at every step.
After overcoming the initial difficulties of
t(response.status_code / 100))]
KeyError: '200'
[root@honeybee plans]#
What do I need to fix to proceed with my migration?
And I'd also like to know how I can get it to work without having to
specify --no-verify-ssl . Note that I have a self-signed certificate. I
don't mind pointing the pulp command to the self-signed certificate file
so that it will accept it, but I don't know how to do that.
Thanks,
Ben Stanley.
___
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
self-signed certificate. I
think this will be adequate for my purposes, if someone can explain to
me how to allow me to use it with pulp-cli and clients.
If it is *necessary* to provide a certificate I will inquire internally
about how I can obtain one.
Thanks,
Ben Stanley.
On 29/4/21 6:
I don't have a https command installed from the python2-httpie package.
How can I install the https command on RHEL 7?
Thanks,
Ben Stanley.
On 29/4/21 9:06 pm, David Davis wrote:
Ben,
Is your server at http://localhost <http://localhost> or
https://localhost <https://localh
e cli with "--no-verify-ssl".
On Thu, Apr 29, 2021 at 10:19 AM Ben Stanley <mailto:ben.stan...@gmail.com>> wrote:
Ina,
Thank you for this. I have started looking at the docs and trying
to follow them.
The first problem I had was how to install pulp-cli, but I see
ost/pulp/api/v3/migration-plans/
<https://localhost/pulp/api/v3/migration-plans/>.
Also, we've since added support for the pulp-2to3-migration to our CLI
which may be a bit easier to use than httpie.
https://github.com/pulp/pulp-cli <https://github.com/pulp/pulp-cli>
David
On
added support for the pulp-2to3-migration to our
CLI which may be a bit easier to use than httpie.
https://github.com/pulp/pulp-cli <https://github.com/pulp/pulp-cli>
David
On Wed, Apr 28, 2021 at 4:32 AM Ben Stanley mailto:ben.stan...@gmail.com>> wrote:
Hel
Hello Pulp People,
I think I've finally got my pulp3 + plugins installed. I can access
http://localhost/pulp/api/v3/ and see the schema.
Now I'm up to trying to migrate the content from my pulp2 server. I have
installed the pulp-2to3-migration plugin (note that the ansible
installation instr
om/ansible/ansible/issues/38050#issuecomment-768501547
<https://github.com/ansible/ansible/issues/38050#issuecomment-768501547>
See in-line replies.
On Sun, Apr 18, 2021 at 10:14 PM Ben Stanley <mailto:ben.stan...@gmail.com>> wrote:
Hello Pulp people,
I'm trying
n:
[Errno 101] Network is unreachable .
I have not figured out how to work around this problem. It seems
that the pip ansible command is also not passing on the correct
proxy settings. I haven't even figured out how to work around this
problem running pip manually ye
machine and I copy the whole virtual machine. This method avoids
RPM replication, and has proved to be much faster than export_distributor.
Ben Stanley.
On 10 June 2019 10:57:37 pm Tatiana Tereshchenko wrote:
As you probably know, we are in the process of designing a tool which will
provide
This approach of locking the repo before the new release will fail to get
updates for the old version.
I advise to use Kodiak's method of examining the entitlements and finding
the proper version locked repo names. Then you will receive the proper
updates for each version.
On 12 January 2019
below are
still missing.
Advice?
On 5 March 2018 09:15:00 Ben Stanley wrote:
Hello pulp-list,
While supporting a legacy project, I noticed that the following packages
are missing from my synced repo of rhel 5 workstation.
gcc
glibc-devel
glibc
glibc-common
glibc-headers
nscd
kernel
advice on where to proceed from here?
Thanks,
Ben Stanley
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
x27;m not sure how to resolve this, so I will just raise this to your
attention and let you figure it out. The consequence of being listed in
this database is being excluded from internet safety filters. I don't think
this is in your interests.
B
Hello pulp-list,
I'm interested in replicating a pulp server over an air gap, using a HDD.
I tried once to backup one pulp system and restore on another. I
transferred the directories:
/var/lib/pulp
/var/lib/mongodb
After restoration on the second machine, accessing the web server failed to
s
I have tried to use the pulp export functionality in an industrial context
(several hundred repos).
It works, but it isn't up to the task in my industrial context.
It might be ok for one or two repos, but for multiple related repos (e.g.
multiple versions of RHEL), there are severe issues:
*
I have observed something like this, and reported it previously. I didn't
think about the tasks being stored in qpid.
I found that this spotted when I removed all my sync schedules.
Ben.
On 16 November 2015 8:39:03 pm Cristian Falcas wrote:
Hello,
After we restart a pulp server, it recei
ig problem, but others might.
Ideal Solution
--
I agree that the method of disconnected synchronisation outlined above is
not ideal, but it is the only thing I have that works. Feel free to
propose a more comprehensive solution for later, but I need something that
works now.
B
r/lib/pulp/published/yum/master/* directories that it
still had to scan? Migration 20 is scanning that directory and modifying
the contents. That should not be particularly intensive unless there is
something going on with the filesystem. Regards,
-Barnaby
- Original Message -----
From: &q
for published delta rpm files. If you have many
>> published
>> repositories on a slow filesystem this could take a while as it could be
>> removing a lot of bad symlinks.
>>
>> -Barnaby
>>
>> - Original Message -
>> From: "ben stanley"
>
? pulp_rpm migration 20 is fixing an issue with the directory
structure created for published delta rpm files. If you have many published
repositories on a slow filesystem this could take a while as it could be
removing a lot of bad symlinks.
-Barnaby
- Original Message -
From: &quo
I had some trouble running pulp-manage-db on a fresh installation.
The update process locks up at update 20.
I have provided a script of what I did (attached pulp_installation.txt).
I can reproduce it by removing all the packages, cleaning
out /var/lib/mongodb, and running the pulp installation a
ng, I deleted, recreated the repo, and
it appears to be working. It's downloading metadata now, no error off the
bat, so I'm feeling confident this is all set.
Thanks for the reply!
Jason
On Fri, Jun 5, 2015 at 4:32 PM, Ben Stanley
wrote:
> Ideas:
> 1) did you set the keys for th
This is a known temporary problem.
Just install the qpid-tools package, and it will all work.
https://www.redhat.com/archives/pulp-list/2015-June/msg0.html
Ben.
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinf
> Hello Pulp Team,
>
> I have a problem with syncing
> http://elrepo.org/linux/elrepo/el7/x86_64
>
> It seems that the package
> nvidia-x11-drv-304xx-304.125-1.el7.elrepo.x86_64.rpm
> is not included in my yum metadata. However, it is published in my local
> repo.
>
I have raised an issue for this
Hello Pulp Team,
I have a problem with syncing
http://elrepo.org/linux/elrepo/el7/x86_64
It seems that the package
nvidia-x11-drv-304xx-304.125-1.el7.elrepo.x86_64.rpm
is not included in my yum metadata. However, it is published in my local
repo.
[root@stig ]# yum list nvidia-x11-drv-304xx
Loade
The first task is completed. The state is Successful. Pulp does not remove
completed tasks from the task list - yet. For now, they just ... accumulate.
The second task is waiting on something. Pulp 2.6 and later are somewhat
better at getting on with tasks than their predecessors. You may have
> Hello pulp-list,
>
> I have just observed a repeatable pulp sync failure of an ISO repo, where
> curl managed to fetch the PULP_MANIFEST successfully.
>
> The pulp sync failure reason appears to be the following log message:
>
> May 13 17:38:11 bumblebee pulp: pulp_rpm.plugins.importers.iso.sync:
found at
the end of this email.
* pulp-admin iso repo create
* pulp-admin iso repo sync
* pulp.log containing failure
* successful curl command
* pulp rpm versions
I am hoping that someone will be able to help me to sync the repo
successfully, or reproduce the problem and initiate a fix.
Message -
From: "ben stanley"
To: pulp-list@redhat.com
Sent: Sunday, May 10, 2015 11:38:37 PM
Subject: [Pulp-list] pulp-admin rpm repo export documentation
Hi,
I need to configure a second pulp server that is disconnected from the
first one. I need to export the repositories from
data may be imported at the other end?
>
> Do I have to create the repos and then import them, or can I just
> import the repo to create it?
>
> Regards, Ben Stanley.
>
>
> ___ Pulp-list mailing
> list Pulp-list@redhat.com
>
?highlight=export
However, there is no description of how the command is used.
Could you please show me where this command is documented, and how the
data may be imported at the other end?
Do I have to create the repos and then import them, or can I just import
the repo to create it?
Regards,
Ben Stanley
On 4 May 2015 10:26:53 PM Brian Bouterse wrote:
Regarding the tasks getting stuck, what version of Pulp are you running?
Getting stuck was on 2.5.1.
I upgraded to pulp 2.6.0 today. I had to bypass my local epel repo to do
the upgrade, due to an issue with the errata on epel.
Pulp behavio
Check the output of
pulp-admin tasks list
The output will likely be large. How many tasks are Running?
pulp-admin tasks list | grep Running | wc -l
If there are lots of tasks running already, then your new task will be on
the end of the queue, waiting for the other tasks to finish. Check [0]
e that this script proves to be useful for stress-testing pulp. If
this isn't enough, I can send you a few more functions to create several
hundred more repos, although I'm sure you can see how to add a few more
repos yourselves. Hint: s/workstation/server/ .
Ben Stanley.
Create
> Ben,
>
> It looks like you might have an "alternate content source" configured that
> it's trying to refresh.
>
> https://pulp.readthedocs.org/en/2.6-release/user-guide/content-sources.html
>
> Michael
Thank you, Michael.
That was it.
Ben.
___
Pulp
I found this in my pulp logs:
/var/log/pulp.log
May 4 11:55:46 bumblebee pulp: pulp.server.content.sources.model:INFO:
Refreshing [rhel-7-workstation-rpms]
url:https://cdn.redhat.com/content/dist/rhel/workstation/7
May 4 11:55:46 bumblebee pu
There is a bigger question here:
Is the dependency on RHEL Server deliberate or accidental?
It would be nice if pulp only required RHEL Workstation.
Ben Stanley.
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman
)
RHEL 6 & 7
Fedora 19 & 20
CentOS 6 & 7
Could you please amend the documentation to indicate that RHEL Server is
required, at least for RHEL 7?
Ben Stanley.
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/l
sSock.UsePIDFromSystem on
in combination with using the imuxsock module provided PIDs on some of the
log lines, but not all. This problem is not completely solved yet.
How can this change be inserted into the documentation?
Ben Stanley.
___
Pulp-list
Brian, please find my replies inline below.
In summary, your advice helped, and I was able to delete some repos. I
have documented the solution in detail below so that any others afflicted
by this problem may find it.
> use pulp-admin to list tasks: `pulp-admin tasks list`. The list is
> long an
ere useful information almost doesn't
exist), but *also* in the logs. I see that there is a ticket for some of
this [0], but I think that another ticket is required to improve the error
reporting in the logs as well.
Regards,
Ben Stanley.
[0] https://pulp.pla
king to be made even
stronger.
I would prefer that the package signature is checked against the repo
signing key to be sure that the package hasn't been tampered with or been
corrupted along the way.
Ben Stanley.
___
Pulp-list mailing list
Pulp-l
-client-lib-2.5.1-1.el7.noarch
---
I know these aren't the latest, but I can't update pulp until I can solve
getting pulp to update its repos [1].
Thanks,
Ben Stanley.
[1] I installed pulp on workstation, but now there is
n the script if it helps to reproduce
things.
Thanks for describing the way that you restart the whole system. You have
included more services in the list than I have tried.
Regards,
Ben Stanley.
On 31 January 2015 10:10:06 AM "Pier, Bryce" wrote:
I’ve been having a lot of troub
I have mirrored Cygwin using my own scripts for many years. Now that I am
migrating to pulp, is there any way to use pulp to mirror and publish Cygwin?
Note that I am not pushing Cygwin out to a cloud of VMs, but rather making
it available to engineer's desktop PC's.
I suppose this would requ
> In the end I solved it by deleting the repo and re-creating it from
> scratch. After a new sync, it appears to work properly.
>
I have now been able to sync all my repos without getting stuck. It
appears that deleting and re-creating the pulp-2-el7-x86_64 repo was the
crucial change that allow
> Ben,
>
> Here is info about where pulp logs things:
> https://pulp-user-guide.readthedocs.org/en/latest/troubleshooting.html#logging
>
The documentation there regarding rsyslogd is incorrect (at least for RHEL7).
Configuring the log with the line
pulp.* /var/log/pulp.log
causes the following e
> I found that there was a feed URL with two forward slashes in it:
> Jan 7 11:55:29 bumblebee pulp: pulp_rpm.plugins.importers.yum.sync:INFO:
> Downloading metadata from
> http://repos.fedorapeople.org/repos/pulp//pulp/stable/2/7Server/x86_64/.
Contrary to my previous email, removing the double s
I found that there was a feed URL with two forward slashes in it:
Jan 7 11:55:29 bumblebee pulp: pulp_rpm.plugins.importers.yum.sync:INFO:
Downloading metadata from
http://repos.fedorapeople.org/repos/pulp//pulp/stable/2/7Server/x86_64/.
Syncronising this repository never completed:
pulp-admin rpm
As I examine the logs, I see this entry:
Jan 7 11:44:28 bumblebee pulp: pulp.server.content.sources.model:ERROR:
source [rhel-7-workstation-rpms] not valid
However, I can't find what this source is. There is no repo with this name:
pulp-admin repo list --details | grep -e rhel-7-workstation-rpms
gt; task where you saw this behavior. You can probably grep the system log the
> task ID to find what we need.
>
> Here is info about where pulp logs things:
> https://pulp-user-guide.readthedocs.org/en/latest/troubleshooting.html#logging
>
> Does the task eventually move to a comple
In the output from pulp-admin tasks list, I have observed tasks that are in
the Running state, but have a Finish Time.
Most Running tasks have a Finish Time of Incomplete, and this seems
sensible. Under what circumstances should a Running task have a finite
Finish Time? Is it an estimated time
I have researched the bandwidth limiting problem a bit, and I have come up
with a solution that works for me.
Note that I only have one pulp server, and I access the internet through a
proxy server. This simplifies my problem considerably.
I use the following iptables commands to perform rate lim
I am having trouble synching my pulp repos.
I am using pulp 2.5.0-1 on RHEL 7.
I have configured 570 repos (I used a script). If I want to synchronise
them right now, I run this bash script:
--- SyncAllRepos.sh --
AllRepoNames=( $(pulp-admin rpm repo list --fields=Id | sed --
The method you describe is the only way I have found for rpm repos. I have
done it, and I can tell you it works (for rpm repos).
However, this does appear to be a design oversight.
Regards,
Ben Stanley
On 24 December 2014 10:36:31 PM Paul Gonin wrote:
Hi,
I want to unpublish an ISO
I see that there is a command to limit the bandwidth consumed by an
individual sync:
https://fedorahosted.org/pulp/wiki/RepoSync/LimitBandwidth
However, I wish to limit the collective bandwidth consumed by my pulp
system, not the bandwidth of one sync.
Any suggestions?
Thanks,
Ben Stanley
pulp-admin login -u $user
After doing that, you won't have to log in again until it times out (which
seems to be a few days).
Ben.
On 9 December 2014 6:04:57 AM "Davis, Daniel P"
wrote:
Hello all,
Is there a way to avoid using passwords for authentication on the pulp
server? Permane
attempt to configure a client to use it, it attempts to access the
rpm in the letter sub-directory.
How can I get pulp to publish the rpms as they are upstream?
Or, alternatively, can pulp generate a new repomd.xml reflecting the flat
layout?
Thanks,
Ben Stanley
fy the root cause I
believe. Also the Pulp output logs would be good too. You should look in
those places for errors.
Brian
- Original Message -
> From: "ben stanley"
> To: pulp-list@redhat.com
> Sent: Thursday, November 27, 2014 12:47:59 AM
> Subject: [Pulp-list
Hello,
I have only been using pulp for a week, someone else may know better than
me, but I think I know where to find the answers to these questions.
How to export to an internal disconnected repo:
https://pulp-rpm-user-guide.readthedocs.org/en/latest/recipes.html#export-repositories-and-repos
thing important in the database yet, so it is acceptable to
erase it and start again (if I knew how).
Thanks,
Ben Stanley
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
77 matches
Mail list logo
