The command magnum service-create has been changed to coe-service-create.

Bug #1509273 reported by Dean Meehan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Invalid
Low
Unassigned

Bug Description

Upon working with Magnum commands (kilo) I seems that the command `magnum service-create` is not recognized.

This command should be changed in the docs to `magnum coe-service-create`

https://github.com/openstack/magnum/blob/stable/kilo/doc/source/dev/dev-quickstart.rst

EDIT:
Placed the wrong URL into the bug report. Bug found on the line `magnum service-create --manifest ./redis-sentinel-service.yaml --bay testbay`

it should say 'magnum coe-service-create --manifest ./redis-sentinel-service.yaml --bay testbay'

Changed in magnum:
assignee: nobody → Ruchi Parmar (ruchiparmar143)
Revision history for this message
Guangya Liu (Jay Lau) (jay-lau-513) wrote :

The dev quick start guide do not have such command use case.

Changed in magnum:
status: New → Invalid
Revision history for this message
Dean Meehan (d3an-meehan) wrote :

I have placed the wrong URL incorrectly into the bug report. Please reevaluate

description: updated
Changed in magnum:
status: Invalid → Opinion
status: Opinion → New
Revision history for this message
Guangya Liu (Jay Lau) (jay-lau-513) wrote :

'coe-service-create' was introduced in L release, and in K release, we should still use "service-create"

Revision history for this message
Dean Meehan (d3an-meehan) wrote :

I am not sure how to check the CLI commands on devstack on github, but I can assure you that I currently am working on Magnum Stable Kilo:

`
i316653@i316653-devstack:/opt/stack/magnum>git status
On branch stable/kilo
Your branch is up-to-date with 'origin/stable/kilo'.
nothing to commit, working directory clean
`

Then running `magnum service-create` returns the following error:
`
i316653@i316653-devstack:/opt/stack/devstack> magnum service-create
usage: magnum [--version] [--debug] [--os-cache]
              [--os-region-name <region-name>]
              [--os-tenant-id <auth-tenant-id>]
              [--service-type <service-type>]
              [--endpoint-type <endpoint-type>]
              [--magnum-api-version <magnum-api-ver>]
              [--os-cacert <ca-certificate>] [--bypass-url <bypass-url>]
              [--os-auth-system <auth-system>] [--os-username <username>]
              [--os-password <password>] [--os-tenant-name <tenant-name>]
              [--os-token <token>] [--os-auth-url <auth-url>]
              <subcommand> ...
error: argument <subcommand>: invalid choice: u'service-create'
Try 'magnum help ' for more information.
`

Note:
`Magnum --version` returns 1.0.0

Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
Revision history for this message
Janki Chhatbar (jankihchhatbar) wrote :

Hi

I have found a reason for this command mismatch and have found a solution to this bug. If no one is working on this, could I please take this bug. Also I am new to OpenStack contributions. This will give me an opportunity to contribute.

Thanks

Revision history for this message
Ruchi Parmar (ruchiparmar143) wrote :

Yes, go ahead. :)

Changed in magnum:
assignee: Ruchi Parmar (ruchiparmar143) → nobody
Revision history for this message
hongbin (hongbin034) wrote :

Sorry, it looks this bug has been fixed in L release. I am going to close this bug. If you are looking for entry level task, please check https://bugs.launchpad.net/magnum/+bugs?field.tag=low-hanging-fruit

Changed in magnum:
status: New → Invalid
Revision history for this message
Janki Chhatbar (jankihchhatbar) wrote :

This is more of a Devstack configuration bug than a documentation bug. Installing Kilo magnum through Devstack installs master magnumclient. This leads to commands mismatch in kilo version. Kilo magnumclient has command "magnum service-create" whereas master has "magnum coe-service-create".

Steps to reproduce:
Run Devstack with the following line in local.conf
"enable_plugin magnum https://github.com/openstack/magnum stable/kilo"

Should I file another bug for this or reopen this one?

Changed in magnum:
assignee: nobody → Janki Chhatbar (jankihchhatbar)
Changed in magnum:
status: Invalid → New
Revision history for this message
Adrian Otto (aotto) wrote :

I think we can fix this by creating a retroactive branch for stable/kilo for python-magnumclient. That's something I have not tried before, but it should be possible. We should be able to branch on any commit hash, even if it's not the most recent one. This is something I can help with.

Changed in magnum:
status: New → Triaged
milestone: mitaka-1 → mitaka-3
importance: Undecided → Low
Revision history for this message
Janki Chhatbar (jankihchhatbar) wrote :

The stable/kilo repo is available (https://github.com/openstack/python-magnumclient/tree/stable/kilo).
The branch (GITBRANCH["python-magnumclient"]=${MAGNUMCLIENT_BRANCH:-master}) is to changed in the magnum file (https://github.com/openstack/magnum/blob/stable/kilo/devstack/lib/magnum).

Revision history for this message
Janki Chhatbar (jankihchhatbar) wrote :

Submitted a fix for this issue.
https://review.openstack.org/#/c/292742/

Though tests (gate-magnum-python27 and magnum-coverage) are failing. Can anyone please guide me into solving these.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on magnum (stable/kilo)

Change abandoned by Janki Chhatbar (<email address hidden>) on branch: stable/kilo
Review: https://review.openstack.org/292742
Reason: Abandoning this and starting with editing the latest Magnum branch.

BassT (mt104b)
Changed in magnum:
status: Triaged → In Progress
Changed in magnum:
status: In Progress → Invalid
assignee: Janki Chhatbar (jankihchhatbar) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.