Code Monkey home page Code Monkey logo

pulp-ci's Issues

Pulp-manage-db times out on first puppet run

That's the behaviour i get with pulp-manage-db when using puppet to manage the installation of pulp servers:

1 puppet run ) pulp-manage-db fails, timeout exceeded
2 puppet run ) pulp-manage-db completed successfully
3 puppet run ) no action

What i expect:

1 puppet run ) pulp-manage-db completed successfully
2 puppet run ) no action

Probably the error is due to the MongoDB server starting too late

remove traces of pulp2 

[ipanova@puffy pulp-ci]$ git grep '2.2[1|2]'
ci/config/releases/supported-releases.json:    "2.21",
ci/jjb/jobs/projects.yaml:    - 2.21:
ci/jjb/jobs/projects.yaml:        pulp_version: '2.21'
ci/jjb/jobs/projects.yaml:        pulp_version: '2.22'
[ipanova@puffy pulp-ci]$ git grep 2-master
ci/ansible/roles/pulp-coverage/tasks/install.yaml:    version: 2-master
ci/config/releases/2-master.yaml:    git_branch: 2-master
ci/config/releases/2-master.yaml:    git_branch: 2-master
ci/config/releases/2-master.yaml:    git_branch: 2-master
ci/config/releases/2-master.yaml:    git_branch: 2-master
ci/config/releases/2-master.yaml:    git_branch: 2-master
ci/config/releases/2-master.yaml:    git_branch: 2-master
ci/docs-builder.py:    # rsync the nightly "2-master" docs to an unversioned "nightly" dir for
ci/docs-builder.py:    if build_type == 'nightly' and opts.release == '2-master':
ci/jjb/jobs/projects.yaml:      - 2-master
ci/jjb/jobs/projects.yaml:    - 2-master:
ci/jjb/jobs/projects.yaml:        reverse_trigger: '2-master'
ci/jjb/jobs/projects.yaml:            - 2-master
ci/jjb/jobs/projects.yaml:            - 2-master
ci/jjb/jobs/projects.yaml:            - 2-master
ci/jjb/jobs/projects.yaml:            - 2-master
ci/jjb/jobs/projects.yaml:            - 2-master
ci/jjb/jobs/projects.yaml:            - 2-master
ci/jjb/jobs/projects.yaml:            - 2-master
ci/jjb/jobs/projects.yaml:            - 2-master
ci/jjb/jobs/projects.yaml:            - 2-master
ci/jjb/jobs/projects.yaml:            - 2-master
ci/jjb/jobs/projects.yaml:            - 2-master
ci/jjb/jobs/projects.yaml:            - 2-master
ci/jjb/jobs/pulp-packaging.yaml:            ssh [email protected] "rsync -avz --delete /mnt/koji/releases/split/yum/pulp-nightly/pulp/ [email protected]:/srv/repos/pulp/pulp/testing/automation/2-master/stage/"
ci/jjb/jobs/unittests.yaml:            - 2-master
ci/jjb/jobs/unittests.yaml:                REPO_URL="https://repos.fedorapeople.org/pulp/pulp/testing/automation/2-master/stage/\$releasever/\$basearch/"
ci/jjb/jobs/unittests.yaml:                REPO_URL="https://repos.fedorapeople.org/pulp/pulp/testing/automation/2-master/stage/fedora-\$releasever/\$basearch/"

`Exec[Migrate DB]` runs every time

these messages appear every time Puppet is run:

Notice: /Stage[main]/Pulp::Server::Install/Exec[yum install pulp-server]/returns: executed successfully
Notice: /Stage[main]/Pulp::Server::Config/Exec[Migrate DB]/returns: executed successfully

best practice is to not run a resource change unless something has actually changed. resource changes cause "eventful reports" that clutter up logs/histories and irritate Ops people when they need to produce reports for auditors :P

this doc provides some possible solutions: https://docs.puppetlabs.com/references/latest/type.html#exec

Puppet doesn't apply config changes

Example... First puppet run with:

class {'::pulp::consumer':
    pulp_server => 'pulp-server.qwerty.ext',
    verify_ssl => False,
}

If i change the manifest for the second puppet run to:

class {'::pulp::consumer':
    pulp_server => 'pulp-server.qwerty.ext',
    verify_ssl => False,
    consumer_profile_minutes => '10',
}

The configuration file doesn't change. I think it's due to the strong link between the subclasses inside the puppet manifest:

anchor { 'pulp::consumer::start': } ->
class { 'pulp::consumer::install': } ->
class { 'pulp::consumer::config': } ->
class { 'pulp::consumer::service': } ->
anchor { 'pulp::consumer::end': }

The unless condition in pulp::consumer::install is verified so it just skips everything after it

no CentOS support? 

Currently, this module only supports RedHat and Fedora operating systems. at /etc/puppet/modules/pulp/manifests/globals.pp:40 on node REDACTED

root@REDACTED:~# facter | grep operating
operatingsystem => CentOS
operatingsystemmajrelease => 6
operatingsystemrelease => 6.5

is there any technical reason for this?

Dedicated puppet module repository

Would you care to move out the puppet module code into dedicated repo? It will easier to find it and recognize the structure as it will be similar to other module repos out there.

Enhance puppet module to manage pulp hosted repos

Similar to other available pulp modules it would be great if the official module would support managing repos in pulp. An example would be

puppet_repo { 'repo_id':
  # Default pulp admin login/password
  ensure              => 'present',
  display_name    => 'my test repo',
  description         => "puppet forge mirror",
  feed                    => 'http://forge.puppetlabs.com',
  feed-key             => '/etc/pki/consumer/key.pem'
  feed-cert            => '/etc/pki/consumer/cert.pem'
  retain-old-count => 1
  relative-url         => 'repo/os'
  schedules         => [ '2012-12-16T00:00Z/P1D', '2012-12-17T00:00Z/P1D' ],
  serve_http         => true,
  serve_https       => true,
  }

registry-admin.py unable to create grant

This command line is taken from the README.md file.

[lvu@lvupulp ~]$ python repos/pulp_packaging/dockerfiles/registry-admin.py pulp "auth permission grant --role-id contributor --resource /repositories -o create -o read -o update -o execute"
User certificate not found.
Enter registry username [lvu]: admin
Enter registry password: 
Warning: path should have mode 0700 because it may contain sensitive information: /root/.pulp/

Command: login
Description: login and download a session certificate

Available Arguments:

  --username, -u - (required) server account username
  --password, -p - server account password
The following options were specified but do not exist on the command:
  --role-id
Warning: path should have mode 0700 because it may contain sensitive information: /root/.pulp/

The server hostname configured on the client did not match the name found in the
server's SSL certificate. The client attempted to connect to
[lvupulp.dyn.intelerad] but the server returned [pulpapi] as its hostname. The
expected hostname can be changed in the client configuration file.

[lvu@lvupulp ~]$

fix Puppet module packaging or bump version on Forge

I really would like to deploy commit 444446c or newer to my network. the version published on Puppet Forge is out-of-date and librarian-puppet is not able to clone the module via git because it is not the "root" of the repository.

for now, I think I'll workaround by mirroring the puppet/pulp directory into my own repository :/

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.