Landscape 24.04 LTS Release Notes

Project Discussion Landscape
23

So far the upgrade from Landscape 23.03 to 24.04 LTS has been a terrible experience.
We can no longer create new users, they will recive the link, but are unable to use it to activate their accounts.
Couldnt access the new ui without rebuilding the apache configuration file.

Why is the update offered as an LTS build when its this unstable?

1 Like
24

Salt and Ansible both offer versions where you dont need incoming SSH i believe.

25

Tried upgrading to the new landscape version and I was surprised by how poorly it went 


I followed the limited instructions here:
https://ubuntu.com/landscape/docs/upgrade-landscape

and I want to highlight:
“During your upgrade, you may be asked if you want to replace your configuration file with a later version. Do not replace your configuration; you should keep your existing configuration file.”

After upgrading landscape, I restart it and some services failed to start, looking at the logs it was because there were no definitions for new parameters in /etc/landscape/service.conf

So I had to compare the service.conf file provided by the deb package and take some default values from there and put it into my service.conf file, the default values from it

I don’t have the error messages anymore, since I had to revert my server to a previous version of landscape but it was a python configparser “section not found” error error which I feel could have:
A) During postinst of landscape-server, if those sections don’t exist in the config file, add them
B) Better error handling in the code “if section not in config: use defaults”
C) Stating in the upgrade documentation clearly that these new entries need to be defined

After adding those things, I get it working. great

Then I go to the new “repositories” tab, which 
 is not just repositories, it’s a full UI, why not have a “new ui / old ui” slider or something or at least labeling that button correctly 

and it doesn’t work, that may have been my fault, I am running a modified apache config, it seemed to actually modify the default config, so I can’t fault them on that really.

And at that point, I was somewhat annoyed but happy to have the new version up and running but then, it all comes crashing down, landscape is no longer capable of keeping my repo’s up to date and without that functionality it is abselutely useless to me ( this bug: Bug #2064622 “Landscape Server Upgrade 23.03 to 24.04 causes rep...” : Bugs : Landscape Server ).

after reading up on this a bit, I revert my landscape server to the previous version, however a lot of the client-servers had already been talking to the new landscape server, had upgraded the client 


Now I don’t know if the next part is because of the upgrade or the downgrade but I had a lot of clients not reporting into landscape, taking a closer look I see a lot of “name_of_server” that hasn’t reported in for an hour and “name_of_server (clone)” that has reported in the last couple of minutes, I tried manually deleting some entries and stuff but doing that for a fleet of servers seemed like a daunting task so I created a removal profile, set it for the minimum time (1 day) and waited for 24 hours.

Thankfully, I have some custom monitoring to see if all hosts that should be registered, were and after all of this, I had a lot of servers that were no longer a part of landscape, I don’t know if that is because of the upgrade, downgrade or manual efforts by me but I had to re-register a large number of servers and if I didn’t have that monitoring in place, I might have missed that.

So overall experience of upgrading was terrible, I will not be upgrading this server to 24 until I create a test instance to try it on once the repo problem is solved

1 Like
26

I am getting this as well. Somehow I ended up on 24.10~beta.5 BETA but still have never had this new dashboard working. Page not found or 404.

28

There are some additional steps here (if you haven’t done those): https://ubuntu.com/landscape/docs/upgrade-landscape-to-24#manual-installations.

29

I followed the steps to a T and no matter what I do, I cannot get the new dashboard to load. What am I missing?

30

Digging a little more, I got this in logs trying to load the new page.

Aug 31 01:28:48 landscape.domain.com appserver-1[134241]: http://landscape.domain.com/new_dashboard request_id=c58f522a-d925-412a-9fb6-48710b5c2bba
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/zope/publisher/publish.py”, line 143, in publish
obj = request.traverse(obj)
File “/usr/lib/python3/dist-packages/zope/publisher/browser.py”, line 598, in traverse
ob = super(BrowserRequest, self).traverse(obj)
File “/usr/lib/python3/dist-packages/zope/publisher/http.py”, line 516, in traverse
ob = super(HTTPRequest, self).traverse(obj)
File “/usr/lib/python3/dist-packages/zope/publisher/base.py”, line 263, in traverse
obj = publication.traverseName(self, obj, entry_name)
File “/usr/lib/python3/dist-packages/zope/app/publication/zopepublication.py”, line 195, in traverseName
ob2 = adapter.publishTraverse(request, nm)
File “/opt/canonical/landscape/canonical/routes/publisher.py”, line 173, in publishTraverse
raise NotFound(self.context, name)
zope.publisher.interfaces.NotFound: Object: <canonical.landscape.model.root.landscape.LandscapeRoot object a
t 0x7f4854ce16f0>, name: ‘new_dashboard’

Same message @itdsystems is getting. Landscape 24.04 LTS Release Notes - #12 by itdsystems

31

@metalcated Thank you for providing your process and the error message. I think we may know what the issue is - is this RewriteRule in your Apache config?

RewriteRule ^/(new_dashboard.*) http://localhost:8080/$1 [P,L]

If not, it needs to be added. This wasn’t noted in our upgrade guide–just in the fresh install guide. I’ve just added this information to our upgrade to 24.04 LTS document, so you can see the details there.

Hopefully that fixes your issue, but please respond here if it doesn’t.

1 Like
32

Where do I find the billing information in 24.04?

33

@yanisa-hs - can you answer? :point_up:

34

@jby We had a new portal released to SaaS users recently, but the billing information isn’t in the new web portal yet. For now, you have to go back to the older web portal in the Billing tab (same process as before the upgrade).

From the new web portal, you can click Old dashboard in the bottom left of your screen to go back to the previous portal and access your billing information. But just a heads up - we also have a bug out right now with this process: LP#2085129. If the old dashboard link doesn’t work for you, follow the steps listed in that bug.

35

Thank you for the info!

1 Like
36

Another question fro you @yanisa-hs:
How do I print/export a list of all my computers?
Is it the same answer, i.e. Old dashboard?

37

@jby Yes, you can use the old portal. We’re still in process of migrating features into the new portal, so there are some features that haven’t made it yet (but will come later)

38

@yanisa-hs - is searching for packages also a feature that’s missing?

39

I think it’s technically there if you click on Packages after selecting your instance(s), but the functionality is different (and will be changed more later on). Package search in the old portal may work better for you for now, though.

40

Are there other sites where sysadmins are collaborating on the day-to-day use of self-hosted Landscape? Zero offense, but there just is not enough here. Looking for scripts, how-to’s, best practices, etc. and looking to share as well. A lot of what I am finding here is outdated or lacking documentation - again no offense just my experience. Would enjoy working with others to better all of our Landscape days.

1 Like
41

@oaitadmin Our Landscape Discourse forum (i.e., what you’re commenting on here :blush:) is the only Canonical-hosted forum that’s specific to Landscape. Most of the posts are authored by me because Discourse currently backs our public documentation, but you are absolutely welcome to make your own posts too, comment on other posts and interact with community members. As a heads up - Discourse uses a trust system which grants experienced users more rights over time. You can read about it in our contribution guide.

I’m not aware of any other sites where sysadmins collaborate on the day-to-day use of self-hosted Landscape.

And here are some more links that you may find helpful:

  • Landscape Documentation: Our public documentation. Each page has a Help improve this document in the forum link at the bottom if you’d like to provide feedback on a specific page (it links you to the relevant post on Discourse). There are many how-to guides there, but if you have specific documentation topic(s) you’d like us to consider adding to the Docs, please comment or make a post in Discourse. This is our feedback process for now, although it may change in the future as we continue improving our documentation.
  • Landscape scripts repository on GitHub: Various sample scripts you may find useful. We also welcome pull requests on this repo if you have scripts you want to share with the community. :slight_smile:
  • Landscape Server bugs on Launchpad: Our publicly-reported Launchpad bugs for Landscape
  • Canonical Support portal: Our Canonical-wide support portal for Landscape and other products. (This support is available for those who purchase Ubuntu Pro.)
1 Like
42

Thank you @yanisa-hs. I appreciate the reply. I’ll take a look at some of the links I have not seen before.

Is support available with purchased Ubuntu Pro? Or Ubuntu Pro with weekday or greater support? I was told I have to have a paid support plan even though I bought Ubuntu Pro.

43

@oaitadmin Hello there - this is so much on point that I had to ask my colleague if he wrote that :smiley:
We already have an extensive setup but getting ‘under the hood’ is sometimes challenging for us cause of the same reasons.
Currently on the 23.03 self hosted and are testing the LTS on the side.